Top Related Projects
Flash OS images to SD cards & USB drives, safely and easily.
A new bootable USB solution.
The Reliable USB Formatting Utility
UNetbootin installs Linux/BSD distributions to a partition or USB drive
Quick Overview
Fedora Media Writer is an open-source tool designed to create bootable USB drives for Fedora and other Linux distributions. It provides a user-friendly graphical interface for downloading Fedora images and writing them to USB drives, making it easier for users to create installation media for Fedora and other operating systems.
Pros
- Cross-platform support (Windows, macOS, and Linux)
- User-friendly graphical interface
- Automatic download of Fedora images
- Supports custom image writing
Cons
- Limited to creating bootable USB drives (no DVD support)
- Primarily focused on Fedora, with limited support for other distributions
- May require additional dependencies on some systems
- Limited customization options for advanced users
Getting Started
To use Fedora Media Writer:
- Download the appropriate version for your operating system from the releases page.
- Install the application following the instructions for your OS.
- Launch Fedora Media Writer.
- Select the Fedora version you want to download or choose a custom image.
- Insert a USB drive and select it as the target.
- Click "Write" to create the bootable USB drive.
Note: Fedora Media Writer is not a code library, so code examples and a quick start guide for developers are not applicable.
Competitor Comparisons
Flash OS images to SD cards & USB drives, safely and easily.
Pros of Etcher
- Cross-platform support (Windows, macOS, Linux)
- User-friendly interface with a simple, intuitive design
- Supports writing to multiple drives simultaneously
Cons of Etcher
- Larger file size and resource usage
- Slower write speeds compared to MediaWriter
- Less focused on Fedora-specific features
Code Comparison
MediaWriter (C++):
void WriterThread::run()
{
if (m_image->status() == Image::READY)
writeCompressedImage();
else
writeUncompressedImage();
}
Etcher (JavaScript):
function writeImage(drive, image, options) {
return new Promise((resolve, reject) => {
const writer = createWriter(drive, image, options);
writer.on('finish', resolve);
writer.on('error', reject);
});
}
MediaWriter is specifically designed for Fedora and uses C++, focusing on efficient image writing. Etcher, written in JavaScript, offers a more general-purpose solution with cross-platform compatibility. While MediaWriter excels in Fedora-specific tasks and performance, Etcher provides a more versatile and user-friendly experience across multiple operating systems.
A new bootable USB solution.
Pros of Ventoy
- Supports multiple ISO files on a single USB drive
- Works with a wide range of operating systems and bootable images
- Allows for easy updating and adding of ISO files without reformatting
Cons of Ventoy
- Requires initial setup and installation on the USB drive
- May not be as user-friendly for beginners compared to MediaWriter
- Lacks specific integration with Fedora or other distributions
Code Comparison
MediaWriter (C++):
void WriterThread::run()
{
if (!m_image->write(m_device)) {
emit error(m_image->errorString());
}
emit finished();
}
Ventoy (C):
int VentoyFillMBR(int fd, uint64_t DiskSizeInBytes)
{
int rc;
uint64_t Part1Start;
uint64_t Part1End;
uint64_t Part2Start;
uint64_t Part2End;
MediaWriter is focused on writing a single image to a device, while Ventoy manages multiple bootable images on a single device. MediaWriter's code is more straightforward for its specific task, whereas Ventoy's code handles more complex partitioning and multi-boot scenarios.
The Reliable USB Formatting Utility
Pros of Rufus
- Supports a wider range of operating systems and image formats
- Faster writing speeds and more efficient resource usage
- More advanced features like bad blocks check and custom partition schemes
Cons of Rufus
- Windows-only application, limiting cross-platform usage
- Less user-friendly interface for beginners
- Lacks integration with specific Linux distributions like Fedora
Code Comparison
MediaWriter (C++):
void WriterThread::run()
{
if (!m_image->write(m_device)) {
emit error(m_image->errorString());
return;
}
emit finished();
}
Rufus (C):
BOOL WriteImage(HANDLE hPhysicalDrive, HANDLE hSourceImage)
{
BOOL bRet = FALSE;
DWORD dwSize;
BYTE buffer[BUFFER_SIZE];
while (ReadFile(hSourceImage, buffer, BUFFER_SIZE, &dwSize, NULL) && dwSize > 0) {
if (!WriteFile(hPhysicalDrive, buffer, dwSize, &dwSize, NULL))
goto out;
}
bRet = TRUE;
out:
return bRet;
}
Both projects aim to create bootable USB drives, but Rufus offers more flexibility and features at the cost of platform limitations, while MediaWriter provides a simpler, cross-platform solution with tighter integration for Fedora and other Linux distributions.
UNetbootin installs Linux/BSD distributions to a partition or USB drive
Pros of UNetbootin
- Cross-platform support (Windows, macOS, Linux)
- Supports a wide range of Linux distributions and other operating systems
- Can create bootable USB drives from ISO files or download distributions directly
Cons of UNetbootin
- Less frequently updated compared to MediaWriter
- User interface may feel outdated
- Limited customization options for advanced users
Code Comparison
MediaWriter (C++):
void WriterWorker::work()
{
if (m_image->status() == Image::DOWNLOAD_FAILED) {
emit finished(WriterWorker::FAILED);
return;
}
// ... (rest of the code)
}
UNetbootin (C++):
void unetbootin::runinstusb()
{
if (!installType.startsWith("USB"))
return;
if (targetDrive == "")
return;
// ... (rest of the code)
}
Both projects use C++ for their core functionality. MediaWriter's code appears more modern and structured, with better error handling and status management. UNetbootin's code is simpler but may lack some of the robustness found in MediaWriter.
MediaWriter focuses specifically on creating Fedora live USB drives, while UNetbootin supports a broader range of distributions and operating systems. MediaWriter offers a more polished and up-to-date user interface, whereas UNetbootin provides greater flexibility in terms of supported systems.
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
Fedora Media Writer
Fedora Media Writer is a tool that helps users write Fedora images onto USB flash drives. It can automatically download the required image and write it in a dd-like fashion using direct device access. Because this overwrites the drive's partition layout, it also provides a Restore feature to reformat the drive back to a standard single-partition layout when you are done.
Fedora Media Writer runs on Linux, Windows, and macOS.

Table of Contents
Building
You can build Fedora Media Writer using the standard Qt cmake build system. For a detailed look at how releases are composed, see the GitHub Actions configuration.
Requirements
| Platform | Dependencies |
|---|---|
| Linux | udisks2 or storaged, xz-libs |
| Windows | xz-libs |
| macOS | xz-libs |
Linux
Specify the install prefix using the -DCMAKE_INSTALL_PREFIX cmake option (default is /usr/local):
cmake [OPTIONS] .
The main binary mediawriter will be installed to $PREFIX/bin and the helper binary to $PREFIX/libexec/mediawriter/helper.
Windows
Building on Windows is a matter of running cmake and make, as long as all dependencies are in your include path.
To create a standalone package, use the windeployqt tool included with your Qt installation. You will likely need to bundle some additional DLLs manually.
It is also possible to cross-compile using the MinGW compiler suite on Fedora and some other distributions.
macOS
Run cmake and make as usual. To create a standalone package, use the macdeployqt tool included with your Qt installation.
Translation
If you want to help translate Fedora Media Writer, please visit our Weblate project page.
Information about the individual Fedora flavors is retrieved from the Fedora websites and translated as a separate project.
Troubleshooting
If you experience any problem with the application, such as crashes or errors when writing to your drive, please open an issue here on GitHub.
Please attach the FedoraMediaWriter.log file from your Documents folder ($HOME/Documents on Linux and macOS, %USERPROFILE%\Documents on Windows). It contains some non-sensitive information about your system and a log of all events during the session.
My flash drive stopped working after writing
We understand how frustrating this can be, especially if it was a drive you relied on. We'd like to help explain what may have happened.
Fedora Media Writer writes the Fedora image sequentially to your drive and then reads it back in full to verify the result â much like a large file copy, just at the raw device level. From the hardware's perspective, there is nothing unusual about this. There are no special commands involved that could instruct a drive to misbehave, and the application has no ability to damage the physical flash memory.
Flash drives do have a limited number of write cycles before the memory naturally wears out, but that limit is typically in the tens of thousands for standard hardware. A single write-and-verify pass uses a tiny fraction of that budget, so ordinary use of Fedora Media Writer will not meaningfully shorten the life of a healthy drive.
If your drive is no longer recognized, here are the most likely explanations:
- The drive is in an inconsistent state. If the write process was interrupted, the drive's partition layout may be left in a state the operating system cannot recognize. This is recoverable â try using Fedora Media Writer's own Restore feature, or use Disk Management on Windows /
fdiskorgpartedon Linux to reformat it manually. - The drive uses low-quality components. Very cheap USB drives are often built with flash memory and controllers that cannot sustain the heat generated by continuous high-speed writing. Fedora Media Writer writes at full speed and then immediately reads the entire drive back to verify â this sustained workload can push such drives beyond what they were designed to handle.
- The drive was already near end of life. Flash memory can fail suddenly once it reaches its limit. If the failure coincided with writing a Fedora image, it is very likely the drive would have failed just the same had you been copying any other large file at the time.
If the drive shows up as read-only or containing no media, the flash memory controller has most likely detected an internal failure. This is a sign that the drive has reached the end of its life and will need to be replaced.
For a more in-depth explanation of how flash drives fail and how to detect a faulty drive, the Rufus FAQ covers this topic in great detail.
Security & Privacy
For details about cryptography, see CRYPTOGRAPHY.md.
For brief privacy information regarding User-Agent strings, see PRIVACY.md.
Top Related Projects
Flash OS images to SD cards & USB drives, safely and easily.
A new bootable USB solution.
The Reliable USB Formatting Utility
UNetbootin installs Linux/BSD distributions to a partition or USB drive
Convert
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot