Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To keep changes after restarting Linux from removable media, create a persistent live USB using a method supported by your distribution—or install Linux fully to an external drive. These are different setups: a live system adds writable storage to a usually read-only image, while a full installation has its own installed operating system and bootloader. The right choice depends on what you want to preserve, how often you will use it, and how much risk and setup complexity you can accept.
Choose the right kind of portable Linux
| Setup | What it keeps | Best for |
|---|---|---|
| Ordinary live USB or SD card | Usually nothing from one session to the next | Installing Linux, rescue work, or temporary testing |
| Persistent live USB or SD card | Files, settings, and other changes supported by its persistence layer | Occasional portable use, testing, and troubleshooting |
| Full Linux installation on removable storage | A conventional installed system, including packages and updates | Regular portable use or a system intended to behave like a normal computer installation |
A live ISO is generally a compressed, read-only system image. Persistence adds writable storage over it, often through an overlay. That can preserve documents, settings, browser profiles, network configuration, and installed packages, but not every change necessarily behaves as it would on a regular installation. Boot parameters, system upgrades, and some configuration changes can be distribution-dependent. The live-boot documentation describes persistence volumes and configurable persistence paths; a persistence.conf entry such as / union requests persistence for the live filesystem tree (live-boot documentation).
Quick decision: choose distribution-native persistence for one supported live system; choose Ventoy when you want several ISOs with separate persistence files; choose a full installation on an external SSD for frequent use and ordinary package updates.
Recommended Free Tools
Choose the storage device and capacity
- USB flash drive: small and convenient, but sustained writes and random-write performance vary widely. A basic drive can work for occasional sessions; frequent package installs and updates are a better fit for an external SSD.
- External SSD: usually the more practical option for a full installation or regular use. It costs more, needs a suitable cable and port, and still depends on the computer allowing external boot.
- SD or microSD card: useful for Raspberry Pi and other embedded systems. Performance, endurance, and boot support vary; a high-endurance card is preferable for write-heavy use, while a USB SSD may be more practical for a desktop workload.
These are planning ranges, not universal minimums:
| Intended use | Suggested starting capacity |
|---|---|
| Small rescue or installer media | 8 GB or more, depending on the image |
| Persistent desktop experimentation | 16–32 GB |
| Persistent desktop with applications and updates | 32–64 GB |
| Full Linux installation | 64 GB or more |
| Several ISOs plus persistence | 128 GB or more |
Allow room not only for the ISO but for the writable persistence area and free working space for packages, updates, and temporary files. For example, Kali’s guide uses an 8 GB-or-larger device in its documented example; that is not a universal size rule for other distributions or uses (Kali persistence guide).
#1 Best Overall
- ✅For beginners, refer image-7, its a video boot instruction, and image-6 is "boot menu Hot Key list"
- ✅16-IN-1, 64GB Bootable USB Drive 3.2 , Can Run Linux On USB Drive Without Install, All Latest versions.
- ✅Including Windows 11 64Bit & Linux Mint 22.3 (Cinnamon)、Kali 2026.02、Ubuntu 26.04、Zorin Pro 18、Tails 7.8.1、Debian 13.5.0、Garuda 2026.03、Fedora Workstation 44、Manjaro 25.06、Pop!_OS 22.04、Solus 2026.04、Archcraft 26.05、Neon 2026.06、Fossapup 9.5、Sparkylinux 8.3, All ISO has been Tested
- ✅Supported UEFI and Legacy, Compatibility any PC/Laptop, Any boot issue only needs to disable "Secure Boot"
Before you write or partition the device
- Back up the removable device. Writing an ISO usually erases the selected target. Ubuntu’s boot-media instructions explicitly warn that existing data on the selected device is destroyed (Ubuntu bootable USB instructions).
- Download the ISO from the distribution’s official source and verify it. On Linux or macOS, calculate its SHA-256 hash with
sha256sum linux-distribution.iso. On Windows PowerShell, useGet-FileHash .linux-distribution.iso -Algorithm SHA256. Compare the result with the checksum published by the distribution. If signed checksums are offered, follow the distribution’s verification instructions as well. Kali documents checksum verification and advises obtaining a fresh image if verification fails (Kali image verification). - Identify the target by model and capacity, not just its device name. On Linux, run
lsblk -o NAME,SIZE,MODEL,TRAN,FSTYPE,MOUNTPOINTSbefore and after inserting the drive. Confirm which device appeared and check its model and size. - Check boot support. The computer must support booting from USB or SD. UEFI and legacy BIOS modes can behave differently. Secure Boot requirements vary by distribution, bootloader, and hardware; disabling it is not always necessary.
Use the computer’s one-time boot menu where possible instead of permanently changing boot order. Menu keys and wording differ by manufacturer. Back up important computer data before changing firmware settings.
Device-path warning: examples such as /dev/sdX are placeholders, not commands to paste unchanged. A whole-disk operation may use a path such as /dev/sdb; formatting or mounting a partition may use /dev/sdb3. Device names can change between boots. Recheck lsblk immediately before any destructive command. A mistaken format or partition command can erase the computer’s internal drive.
Method 1: Use Ventoy for multiple live ISOs
Ventoy lets you copy ISO files to a drive rather than re-imaging it every time you add a distribution. Its persistence plugin associates an ISO with a writable backend image file. It is a useful option for a multi-ISO drive, but it does not make every ISO persistent automatically: distribution and release support, labels, and configuration matter (Ventoy persistence documentation).
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Install Ventoy to the intended removable device, following the project’s current instructions. Installing it can repartition or erase that device, so verify the target and back it up first.
- Copy the Linux ISO or ISOs to Ventoy’s data partition.
- Create or obtain a persistence backend image compatible with the distribution. Ventoy documents a script named
CreatePersistentImg.sh; its default example creates a 1 GB ext4 image labeledcasper-rw. Examples includesh CreatePersistentImg.sh -s 2048for a specified size, andsh CreatePersistentImg.sh -l persistence -c persistence.conffor a different label and configuration. Use the instructions and configuration appropriate to your ISO. - Place the backend image on the Ventoy data partition and create
/ventoy/ventoy.jsonto map the ISO path to the backend. For example:
{
"persistence": [
{
"image": "/ISO/ubuntu.iso",
"backend": "/persistence/ubuntu_persistence.dat"
}
]
}The paths in the JSON must match the actual locations and names on your drive. Ventoy documents different persistence labels for different distributions: Ubuntu and Linux Mint commonly use casper-rw, while Kali uses persistence and requires a persistence.conf configuration. Those labels are not interchangeable. Check Ventoy’s current compatibility information for the specific ISO version you intend to boot.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
Boot the ISO from Ventoy and select its persistence option if offered. If you want to enlarge a backend image later, Ventoy documents ExtendPersistentImg.sh; for example, sudo bash ExtendPersistentImg.sh persistent.dat 2048 adds 2048 MB. Do not extend an image that is in active use, and back up its contents first. Avoid sharing one persistence file between unrelated distributions unless their documentation says that is supported.
Method 2: Create distribution-native persistence
For a single distribution, following its own live-USB instructions is often the clearest route. The example below follows Kali’s documented Debian-style approach. It is not a universal recipe: partition layouts, labels, boot options, and tools vary by distribution and ISO release.
Kali/Debian-style example
- Write the live ISO to the removable device with a trusted imaging tool that supports the distribution’s image. Writing the image can erase the device. Leave or create unallocated space for persistence if following a layout that adds a partition after the image.
- Boot a Linux system that is not currently using the persistence area. Use a partition editor to create an ext4 partition in the available space. Do not assume the new partition will be number 3; inspect the actual layout.
- Confirm the disk and partition paths with
lsblk -f. In the commands below, setusbto the verified whole-device path and replace the example partition number with the one you actually created. - Format the persistence partition, label it exactly as required, and create its configuration file. Kali’s documented example uses the label
persistenceand a file containing/ union:
usb=/dev/sdX
# Replace /dev/sdX and the partition number after verifying them.
sudo mkfs.ext4 -L persistence ${usb}3
sudo mkdir -p /mnt/my_usb
sudo mount ${usb}3 /mnt/my_usb
echo "/ union" | sudo tee /mnt/my_usb/persistence.conf
sudo umount /mnt/my_usbDo not paste the placeholder device or assume the partition number. The command formats the named partition and destroys data already on it. Verify the device and partition immediately beforehand. Kali’s instructions describe the ext4 filesystem, persistence label, persistence.conf, and / union configuration (Kali’s current persistence instructions).
- Reboot and select the persistence-enabled entry. Kali’s documented menu label is Live USB Persistence; labels can vary by release. Choose that entry each time you want the persistent layer active.
The partition number and layout are not fixed. Check the distribution’s current guide before applying the example to a new release. A persistence volume with the expected label but no valid configuration may be ignored; the live-boot reference describes the role of persistence.conf and volume labeling (persistence.conf reference).
Rank #3
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9+; Software download required for Mac, visit the SanDisk SecureAccess support page]
Optional: encrypted persistence
Kali also documents encrypted persistence using LUKS, followed by an ext4 filesystem and persistence configuration inside the unlocked mapping (Kali encrypted persistence guide). Encryption is worthwhile when the device may contain sensitive files, but it adds setup and boot complexity. A forgotten passphrase can make the data unrecoverable. Encryption of the writable persistence area is not automatically full-disk encryption: the ISO may remain readable, and the session is exposed while unlocked. It does not protect activity on an untrusted host computer or network.
Ubuntu and Ubuntu-based distributions
Ubuntu’s current desktop documentation describes Startup Disk Creator as a way to write Ubuntu images and Ubuntu-based flavors, and cautions that it may not work correctly with unrelated distributions (Ubuntu’s creation instructions). Do not treat it as a universal persistence tool or assume its controls and behavior are the same across releases. For Ubuntu-family persistence, use the workflow documented for the exact release and creation tool you have. Other distributions may use different boot parameters, labels, or persistence mechanisms.
Similarly, Rufus may offer a persistence control for compatible images, but support is not universal. Kali’s Windows instructions say its Rufus route is not the officially supported Kali method and does not work with every image, including Kali Everything Live (Kali’s Windows USB guide). Treat any tool-specific persistence slider as image-dependent, not as proof that arbitrary Linux ISOs will retain changes.
Method 3: Install Linux fully to an external drive
Choose a full installation if you want a conventional system with ordinary package management, kernel and bootloader updates, and broad customization. An external SSD is generally a more suitable target for frequent use than a basic thumb drive. This method is more involved than live persistence and can still fail to boot on different hardware.
Rank #4
- Lightweight and convenient: Lexar JumpDrive A30E (USB Type-A) boasts a slim, portable design for easy device compatibility; lightweight at 7.41 g
- Transfer speeds up to 100 MB/s: 10x faster than standard USB 2.0 drives; Based on internal testing, performance may vary depending upon the host device, interface, and usage conditions
- Wide compatibility: Compatible with tablets, laptops, Macs, and traditional Type-A devices, no software installation required; Reliably stores photos, videos & files
- Compact: Features a push-button retractor and a lanyard loop for on-the-go use
- Enhanced security: Lexar DataShield protects files, easily creates a password-protected safe with auto-encryption; Files deleted from the safe are securely erased and can't be recovered
- Prepare one removable device as the installer and a separate device as the installation target. Disconnect unrelated removable drives where practical.
- Boot the installer in the firmware mode you expect to use later, commonly UEFI.
- Choose custom or manual partitioning if you need to control exactly where the system is installed. Confirm the target by model and capacity, not only by a changing name like
/dev/sdb. - Create the required partitions on the external target. A common UEFI setup includes a FAT32 EFI System Partition and a Linux root partition; swap may be a partition or file, and a separate home partition is optional. Follow the distribution’s installer requirements.
- Ensure the bootloader’s EFI files and configuration are installed for the external target, not inadvertently on the computer’s internal drive. Installer screens differ, so do not rely on a single generic instruction for the bootloader field.
- When possible, disconnect or exclude the internal drive during installation. Afterward, test booting the external system with the internal drive disconnected or carefully excluded before reconnecting other drives.
An installer can identify disks differently from one boot to another. Installing the bootloader to the internal disk may change that computer’s boot setup or make the external installation depend on the internal drive. A full installation is more like a normal Linux system, but portability is not guaranteed: Secure Boot settings, firmware mode, architecture, graphics hardware, Wi-Fi firmware, and proprietary drivers can all affect whether it boots elsewhere.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Test that changes really persist
Do not stop after writing the ISO or creating a partition. Boot using the persistence-enabled option and run a simple test:
- Create a file in your home directory:
echo "persistence test" > ~/persistence-test.txt. - Change a harmless desktop setting. If appropriate for the distribution, install a small package such as
treeafter updating package lists. - Shut down cleanly. Do not pull the device while the system is running or writing.
- Boot again using the same persistence-enabled entry and check that the file, setting, and package remain.
- If useful, boot once without persistence and confirm that it behaves as a separate, non-persistent session.
For example, on a Debian-based live system, the package test could be sudo apt update followed by sudo apt install tree. Package operations can take space and generate writes, so skip this test if the storage is nearly full. Kali explicitly requires selecting its persistence boot option when saved changes are wanted (Kali persistence guide).
Troubleshooting
Files disappeared after reboot
The most common cause is booting the ordinary live entry instead of the persistence-enabled one. Other possibilities include a missing or incorrectly labeled persistence volume, a missing or malformed persistence.conf, an incorrect Ventoy mapping, or an ISO that does not support the chosen method. From a Linux session, inspect lsblk -f. For the Kali/Debian-style example, check that the intended filesystem is labeled persistence, that the configuration file is at the root of that filesystem, and that its contents are appropriate—for example, / union. Consult the distribution’s instructions before changing labels or files.
Best Value
- 1-Pack 128GB USB Flash Drive: Store, back up, and transfer photos, videos, music, documents, movies, manuals, and software with ease. Large-capacity portable storage for school, office, business, travel, and everyday use
- Plug and Play: No software installation required. Simply connect the USB flash drive to a USB port for quick access to your files. Ideal for file sharing, data storage, backup, and transferring digital content between devices
- Wide Compatibility: Compatible with Windows 11 / 10 / 8.1 / 8 / 7 / XP/ Vista / 2000 / ME / NT, Linux and Mac OS, and most USB-enabled devices. This USB drive works with desktop computers, laptops, TVs, car audio systems, speakers, and more. Supports USB 2.0 and is backward compatible with USB 1.1
- Portable Swivel Design: Features a 360° rotating metal cover that helps protect the USB connector when not in use. Built-in keyring loop allows easy attachment to keychains, backpacks, briefcases, or lanyards. Durable ABS plastic housing with LED activity indicator
- Tested for Quality: Each thumb drive undergoes quality testing and pre-formatting before shipment. Designed for dependable everyday use and convenient file storage across compatible devices
The USB or SD card no longer boots
Possible causes include a corrupted or incomplete ISO, a failed write, a damaged boot structure, using an unsupported firmware mode, or a bootloader installed to the wrong disk. Verify the ISO checksum, recreate the media if needed, try another USB port, and use the one-time firmware boot menu. If possible, test on another computer. For a full installation, inspect the external drive’s EFI and bootloader setup before reinstalling.
Persistence is full
The writable area can fill even if the physical device has unused space outside it. Use a larger persistence partition or backend image, move large personal data to a separate volume, or remove unneeded files and package caches. Back up first. Ventoy documents a tool to extend a persistence image; do not resize a backend while it is in use.
Updates break the live system
Overlay-based live systems are not always as robust for major upgrades as conventional installations. Back up persistence before major changes, avoid treating it as the only copy of important data, and consider recreating the live media for a new release if the distribution recommends that. For frequent kernel, bootloader, or release upgrades, a full installation is usually the more natural fit.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesIt works on one computer but not another
Removable boot depends on firmware mode, Secure Boot configuration, USB boot support, graphics and network hardware, and available firmware. An SD reader may not be exposed as bootable storage. A persistent layer can also contain hardware-specific settings. Compatibility across computers is possible, not guaranteed.
The persistence filesystem is read-only or reports errors
Unsafe removal, power loss, filesystem damage, flash wear, or device failure can cause errors. Copy off any readable data before attempting repair. Identify and unmount the affected partition, then check the verified partition path:
lsblk -f
sudo umount /dev/sdX3
sudo fsck -f /dev/sdX3Replace /dev/sdX3 only after verifying it, and do not run fsck on a mounted filesystem. If errors recur, replace the device and restore from backup.
Quick Recap
Backups, security, and safe removal
- Persistence is not a backup. Keep another copy of important documents, keys, and recovery information.
- Use a strong passphrase if you configure encrypted persistence, and store a recovery copy of anything you cannot afford to lose.
- Shut down cleanly before removing the drive; interruption during writes can corrupt a filesystem or persistence image.
- Treat unknown computers as potentially hostile. Encryption protects stored data while the device is locked, not a session after it is unlocked.
- A portable Linux session can still leave traces or expose data through the host computer, firmware logs, mounted internal drives, or network services. Do not assume that booting from removable storage makes a session anonymous or secure.
Which setup should you choose?
- Occasional testing or rescue: an ordinary live USB is simplest; add persistence only if you need changes to survive reboots.
- One portable live system: use the distribution’s supported persistence method and verify it with a reboot test.
- Several distributions: Ventoy can keep multiple ISOs and separate persistence backends, provided each ISO’s persistence support is configured correctly.
- Regular portable desktop use: install Linux fully to an external SSD, taking care to keep the bootloader on the external target.
- Raspberry Pi or embedded system: use supported SD or USB storage; select a high-endurance card for write-heavy use, or consider a USB SSD if the board supports it.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
