How to Create a Bootable Fedora USB Drive on Linux
You downloaded the Fedora ISO. You plugged in a USB stick. Now you need to get that image onto the drive so your machine will boot from it. You might be tempted to copy-paste the .iso file onto the USB like a document, but that will not work. The BIOS or UEFI firmware needs the ISO written as a raw disk image, not a file inside a filesystem. Writing the image correctly turns the USB drive into a bootable replica of the installation media.
What the ISO actually is
An ISO file is a container. It holds the filesystem structure, the bootloader, the kernel, and the installation payload. When you write an ISO to a USB drive, you are not copying a file into a folder. You are overwriting the entire drive structure with the contents of the ISO.
Think of the USB drive as a blank canvas. The ISO is the paint. You are not putting the paint can on the canvas. You are spreading the paint across the whole surface so the canvas itself becomes the image. The firmware reads the USB drive as if it were the optical disc the ISO represents. The ISO contains the EFI System Partition structure required for UEFI boot and the Master Boot Record required for legacy BIOS boot. Writing the ISO raw ensures both structures land on the drive in the exact layout the firmware expects.
Write the image with dd
The dd command is the standard tool for raw disk imaging on Linux. It copies data byte-for-byte without interpretation. This makes it fast, reliable, and compatible with every Fedora release. It also carries real risk. If you point dd at the wrong device, you will overwrite that device completely. There is no undo.
Identify your USB drive before you run any write command. The system assigns device names like /dev/sdb or /dev/nvme0n1p3. You need the whole disk device, not a partition.
Run lsblk to list block devices and find your USB stick.
lsblk -f # -f displays filesystem types to help distinguish the USB from your system drives
Look for the device that matches the size of your USB drive. It will likely be /dev/sdb or /dev/sdc. Your system drive is usually /dev/sda or /dev/nvme0n1. If you see partitions like sdb1 or sdb2, ignore them for now. You need the parent device sdb.
Check the device size in lsblk. If the size does not match your USB stick, you are targeting the wrong disk.
Once you have the correct device name, use dd to write the ISO. Replace /dev/sdX with your actual device and fedora.iso with the path to your downloaded file.
sudo dd if=fedora-workstation-40-1.10.x86_64.iso of=/dev/sdX bs=4M status=progress oflag=sync # if=input file path to the ISO image
# of=output device, must be the whole disk like /dev/sdb, never a partition like /dev/sdb1
# bs=4M sets block size to 4 megabytes for faster throughput than the default 512 bytes
# status=progress prints bytes copied and ETA so you know the command is running
# oflag=sync forces a physical write to the device before returning, preventing cache drops
The command will run silently except for the progress output. It may take several minutes depending on the USB speed and ISO size. Do not interrupt the process. If dd returns an error about read-only media, check the physical write-protect switch on the USB drive.
After dd finishes, you must eject the drive. The kernel caches writes, and the filesystem needs to be finalized. Unplugging the drive immediately can leave the filesystem in an inconsistent state.
sudo eject /dev/sdX # Unmounts any mounted partitions and sends a hardware eject signal to flush caches
Run lsblk before you run dd. One typo in the device name wipes your root partition.
Verify the drive
You can verify the write succeeded without rebooting. Plug the drive back in if you ejected it, or keep it connected if you used eject which just unmounts.
lsblk -f /dev/sdX # Verify the filesystem type matches the ISO structure, usually iso9660 or vfat
You should see the filesystem type reported. For Fedora Workstation, the root partition often shows iso9660 or vfat depending on the version. If lsblk shows no filesystem or the wrong size, the write failed. Re-run the dd command.
Boot the USB. If the screen stays black, check your BIOS boot order, not the USB.
Common pitfalls
Copying the ISO file to the USB creates a file named fedora.iso on the drive. The bootloader will not find it. The drive will not boot. You must write the image using dd or a dedicated tool.
Writing to a partition instead of the whole disk breaks the boot structure. If you specify /dev/sdX1, you overwrite the partition table and the EFI system partition layout. The drive becomes unbootable. Always target the whole disk /dev/sdX.
The dd method creates a read-only replica of the ISO. Any changes you make during a live session are lost when you reboot. This is the correct behavior for installation media. If you need to save files or install packages on the USB, dd is the wrong tool. Use fedora-media-writer for persistence.
Secure Boot is supported by Fedora. The ISO contains signed kernels and bootloaders. If your hardware has a custom Machine Owner Key, you may need to enroll Fedora's key during the first boot. The installer provides a prompt for MOK enrollment. Do not disable Secure Boot unless you have a specific reason. Fedora works with Secure Boot enabled.
If the USB does not appear in the boot menu, check your BIOS settings. Some systems have a "Fast Boot" option that skips USB devices. Disable Fast Boot to ensure the firmware scans all media. Some laptops require a specific key like F12 or F9 to open the boot menu. Consult your hardware manual.
Eject the drive before you unplug it. The kernel caches writes, and a sudden disconnect can corrupt the filesystem.
Choose the right tool
Fedora provides multiple ways to create bootable USB drives. Each tool serves a different workflow.
Use dd when you need maximum compatibility and a scriptable workflow for creating installation media that works on every UEFI and BIOS configuration.
Use GNOME Disks when you prefer a graphical interface and want a visual confirmation of the target drive before writing.
Use fedora-media-writer when you require a persistent live environment that retains documents and installed packages between sessions.
Install fedora-media-writer via DNF if you need persistence.
sudo dnf install fedora-media-writer # Installs the official Fedora tool for creating live USBs with optional persistence
Run the application, select your ISO, and toggle the persistence slider. The tool handles partitioning automatically. Persistence uses a separate partition on the USB for your home directory. This adds overhead and reduces write speed. Use persistence only when you need a portable workspace, not for installation.