You need a single drive that boots multiple Fedora releases
You just downloaded Fedora 41 Workstation, but your old USB stick still holds Fedora 39. You need to test a new kernel spin, and you do not want to erase the drive and reflash it from scratch. You plug in a fresh USB stick, but you realize you will need three different ISOs this week. Reflashing for each one wastes time and wears out flash memory. Ventoy solves this by turning the drive into a persistent boot menu that reads ISO files directly.
How the bootloader actually works
Traditional flashing tools carve the ISO contents directly onto disk sectors. They overwrite the partition table and filesystem every time you change images. Ventoy takes a different approach. It installs a lightweight bootloader onto the first partition and formats the remainder of the drive as a standard ExFAT volume. When you boot the drive, the bootloader scans the filesystem, finds files ending in .iso, and mounts them in memory as virtual optical drives. The ISO stays intact on the disk. You can copy, rename, or delete them like normal files.
The partition layout is simple. The first partition holds the EFI system files and the Ventoy bootloader binaries. The second partition is a large ExFAT data volume that any modern OS can read. ExFAT is chosen because it supports files larger than 4 GB and works across Windows, macOS, and Linux without extra drivers. The bootloader does not extract the ISO. It passes the raw file to the firmware, which treats it exactly like a physical DVD inserted into an optical drive.
Keep the data partition mounted only when copying files. Unmount it before booting to avoid filesystem state conflicts.
Install Ventoy to the USB drive
Identify the correct block device before running any installer. Running the wrong device path will erase your internal drive. Open a terminal and list all storage devices.
Here is how to list block devices and verify the USB stick size and mount points.
lsblk -f
# -f shows filesystem types and labels
# helps you distinguish the USB drive from internal disks
# look for the removable flag and correct capacity
Fedora convention favors lsblk over fdisk -l for quick overviews. The output shows device names, sizes, and mount points in a single tree. Find the device that matches your USB stick capacity. Note the exact path, such as /dev/sdb or /dev/nvme1n1. Do not use partition numbers like /dev/sdb1. The installer needs the whole disk.
Download the latest Ventoy release and extract the archive. The official site provides a Linux tarball that contains the Ventoy2Disk.sh script.
Here is how to fetch the latest release and extract the installer safely.
VER=$(curl -s https://api.github.com/repos/ventoy/Ventoy/releases/latest | grep tag_name | cut -d'"' -f4 | tr -d v)
# fetches the latest version string from GitHub API
# strips the leading 'v' character for clean variable usage
wget "https://github.com/ventoy/Ventoy/releases/download/v${VER}/ventoy-${VER}-linux.tar.gz"
# downloads the official Linux tarball
tar -xzf ventoy-${VER}-linux.tar.gz
# extracts the archive into a versioned directory
cd ventoy-${VER}
# moves into the extracted folder to run the installer
Run the installer script with sudo. The script will wipe the target disk, create the two partitions, format them, and install the bootloader files. Add the -g flag if your target machine only supports UEFI. GPT partition tables are required for UEFI booting. MBR works for older BIOS systems but is deprecated on modern hardware.
Here is how to install Ventoy to the USB drive with GPT partitioning.
sudo bash Ventoy2Disk.sh -i -g /dev/sdX
# -i triggers the installation routine
# -g forces GPT layout for UEFI compatibility
# /dev/sdX must be replaced with your actual device path
The script prints progress messages and asks for confirmation. Type y to proceed. The process takes a few seconds. When it finishes, the drive will appear as a mounted ExFAT volume named Ventoy.
Unmount the drive before testing. Leaving it mounted can confuse the bootloader during the first boot attempt.
Copy and verify your ISO files
Mount the large Ventoy data partition and copy your ISOs into it. You can place them in the root directory or organize them into subfolders. Ventoy scans recursively and lists every .iso file it finds.
Here is how to download a Fedora ISO and copy it to the mounted Ventoy partition.
wget https://download.fedoraproject.org/pub/fedora/linux/releases/41/Workstation/x86_64/iso/Fedora-Workstation-Live-41-1.4.x86_64.iso
# fetches the official Workstation live image
# verify the URL matches your target architecture
cp Fedora-Workstation-Live-41-1.4.x86_64.iso /run/media/$USER/Ventoy/
# copies the file to the mounted ExFAT volume
# adjust the mount path if your desktop environment auto-mounts elsewhere
Always verify ISO integrity before copying. Corrupted downloads cause silent boot failures or installer crashes. Fedora provides SHA256 checksums alongside every release. Run the checksum command against the downloaded file and compare it to the official value.
Here is how to verify the ISO checksum before copying it to the drive.
sha256sum Fedora-Workstation-Live-41-1.4.x86_64.iso
# computes the cryptographic hash of the downloaded file
# compare the output string with the official checksum page
# a mismatch means the file is corrupted and must be redownloaded
Copy multiple ISOs as needed. Fedora Server, KDE Spin, and a rescue image all fit on a single 16 GB stick. Ventoy does not care about the distribution. It only cares about the .iso extension and valid boot sectors inside the image.
Keep ISO names short and avoid special characters. Some older UEFI firmware parsers truncate long filenames or misread spaces.
Boot the drive and confirm the layout
Plug the USB drive into your target machine. Enter the boot menu during POST. The key varies by manufacturer. F10, F12, or Esc are common. Select the USB device from the list. Ventoy loads its menu and displays every ISO it found on the drive.
Select the Fedora ISO. The bootloader hands control to the Fedora installer or live environment. The system boots exactly as if you had flashed the ISO directly. You can test the live environment, run the installer, or boot into a rescue shell.
Verify the partition layout after installation. Run lsblk again to confirm the two-partition structure. The first partition should be FAT32 and labeled EFI-SYS or Ventoy. The second partition should be ExFAT and labeled Ventoy.
Here is how to confirm the partition layout matches Ventoy expectations.
lsblk -f /dev/sdX
# displays filesystem types and labels for the target disk
# confirms the first partition is FAT32 for EFI
# confirms the second partition is exFAT for data storage
If you see only one partition or an unexpected filesystem, the installer did not complete correctly. Re-run the installation script and check for permission errors.
Reboot before you debug. Half the time the symptom is gone.
Common pitfalls and what the errors look like
The installer refuses to run if the target disk is mounted. You will see this exact message:
Error: /dev/sdX is mounted. Please unmount it first.
Run sudo umount /dev/sdX* to detach all partitions on that device. Then retry the installation.
Secure Boot blocks unsigned bootloaders by default. Ventoy ships with a self-signed key. If your machine enforces Secure Boot, the firmware will drop you into a key enrollment prompt or show a Security Violation screen. You have two options. Enroll Ventoy's public key through the firmware setup, or disable Secure Boot temporarily for testing. Ventoy also offers a built-in Secure Boot support toggle in its boot menu. Navigate to Option > Secure Boot Support and enable it. The bootloader will sign itself on the fly using a preloaded certificate.
UEFI and Legacy BIOS modes do not mix. If you installed Ventoy with -g (GPT) but the target machine only supports Legacy BIOS, the drive will not appear in the boot menu. If you installed with MBR but the machine requires UEFI, the firmware will ignore the drive. Match the partition scheme to the firmware. Use GPT for UEFI. Use MBR for Legacy BIOS. Modern Fedora installs default to UEFI.
Corrupted ISOs produce vague installer errors. The Anaconda installer may hang at Starting storage configuration or drop to a shell with Failed to mount /run/install/repo. The issue is almost always a bad download or a failing USB controller. Verify the checksum again. Test the drive on a different machine.
Run journalctl first. Read the actual error before guessing.
When to use Ventoy versus other flashing tools
Use Ventoy when you maintain a collection of ISOs and want to swap images without reformatting. Use dd when you need a bit-for-bit exact copy of a raw disk image or a non-ISO bootable file. Use Fedora Media Writer when you want a guided, single-image flash that verifies automatically and requires zero terminal commands. Use Rufus when you are on Windows and need advanced NTFS/exFAT partition tweaks or DD-mode fallback for stubborn firmware. Stay on Ventoy if you only deviate from the defaults occasionally and value speed over strict verification.