An EtchDroid alternative, and when you don't need one
An honest comparison of EtchDroid and BootForge for writing bootable USB drives from Android, including the cases where EtchDroid is still the better choice.
We’ll start with the part most comparison pages leave out: EtchDroid is good, and for a lot of people it is the right answer. It is free, open source, available on F-Droid, has no ads, and does the one thing it sets out to do well. If it’s working for you, there is no reason to switch, and this page will tell you so rather than talk you out of it.
There are specific jobs it doesn’t cover, though, and they’re the reason people come looking. Here is what’s actually different, so you can tell which group you’re in.
Stay with EtchDroid if
- Open source matters to you as a requirement rather than a preference. EtchDroid is fully open source and on F-Droid. BootForge is not open source, and we’re not going to pretend otherwise.
- You’re flashing Raspberry Pi images, which it handles well and has years of proof doing.
BootForge accepts raw
.imgfiles too (more on that below), but the feature is newer and we won’t claim territory it hasn’t earned yet.
If either of those describes you, close this page. You already have the right tool.
(An earlier version of this page also listed “writing a single Linux ISO” here, because BootForge couldn’t do that. Since the 0.1.9 release it can, so that difference is gone — the comparison below reflects the current apps.)
Where EtchDroid stops
Three limits are documented by the project itself, and none of them are bugs. They follow from how it works.
Official Windows ISOs aren’t supported. EtchDroid’s FAQ explains that Windows ISOs “use the UDF filesystem, which most BIOSes don’t support on USB drives”, and to work they “must first be converted to a different filesystem”. Converting an ISO isn’t something you can practically do on a phone. This is the single most common reason people go looking for something else.
One drive holds one system. Writing an image replaces the entire contents of the drive. If you want a Linux installer and a rescue tool on the same stick, that isn’t a setting you’re missing, it’s a consequence of raw writing.
DMG support was removed. The project states that “writing DMG images is a very uncommon use case and maintaining support for them is a lot of work”, and that it was dropped “in order to focus on stability and performance”. That’s a reasonable call, but if DMGs are what you need, neither app serves you. BootForge doesn’t write them either.
One limit worth clearing up because it gets blamed on the app: neither app can write to your phone’s internal SD card slot. As EtchDroid puts it, “Android does not allow apps to write to the internal SD card slot in the way that is required in order to write disk images. Only USB devices can ever be supported.” That’s an Android platform restriction and it applies to every app in this category.
What BootForge does differently
BootForge’s signature mode sets the drive up as a Ventoy multiboot drive: a small bootloader is installed once, the rest of the drive stays ordinary storage, and adding an operating system means copying its ISO file across. A menu at boot lets you choose.
Since version 0.1.9 it also writes single images directly, the way EtchDroid does. Pick an ISO, pick
the drive, and it’s written byte for byte, then read back and verified. Raw .img files are accepted
on the same path, with one honest caveat the app shows you up front: writing a .img is verified, but
whether the result boots depends on the image and the target device, and BootForge doesn’t claim
otherwise.
For Windows there’s a third route: a dedicated installer mode that builds the drive the way Windows setup expects it (GPT with a FAT32 partition, with the large install file split to fit), from Microsoft’s official ISO, unmodified. It’s made for UEFI machines, which is every PC that meets Windows 11’s requirements anyway.
Here is where that leaves the comparison:
| EtchDroid | BootForge | |
|---|---|---|
| Single-image write | Yes | Yes, with read-back verification |
| Official Windows ISOs | Not supported | Supported: multiboot copy, or a dedicated installer drive |
| Systems per drive | One | One, or as many as fit in multiboot |
| Adding another OS later | Rewrite the whole drive | Copy a file (multiboot) |
| Removing one | Rewrite the whole drive | Delete a file (multiboot) |
Raspberry Pi .img files | Yes, well proven | Accepted; write verified, boot not claimed |
| Root required | No | No |
| Open source | Yes | No |
| Price | Free | Free core, optional one-time Pro |
All three BootForge modes are free; the drive-making engine has never been part of the paid tier. BootForge also adds a curated catalog of images with checksums and links to official sources, checksum verification for files you supply, and a way to reset a drive back to a plain USB stick when you’re done.
The honest trade
Switching costs you something, and you should weigh it:
- You give up open source. EtchDroid’s code is public and auditable. BootForge’s isn’t. If that’s a dealbreaker, it’s a legitimate one.
- You give up F-Droid. BootForge is distributed through Google Play only.
- BootForge is freemium. The entire drive-making engine is free with no ads and no coins, and nothing safety-critical is locked. But there is a paid tier, and EtchDroid has no paid tier at all.
- In multiboot mode, Ventoy adds a layer. Your PC boots Ventoy, which then boots your image. On machines with Secure Boot enabled that means a one-time key enrollment step a direct write doesn’t have. This only applies to the multiboot mode; BootForge’s single-image write has no Ventoy layer. See Troubleshooting boot problems.
What you gain is Windows support, several systems on one drive, and file-copy management instead of reflashing. If those aren’t things you need, the trade isn’t worth making.
Using both
These aren’t mutually exclusive and plenty of people keep both installed, though with BootForge now covering the single-image case too, the reason to reach for EtchDroid is the one it has always owned: it’s open source, and it’s proven. They don’t conflict.
Where to go next
- Make a bootable USB from your Android phone, which covers both methods without assuming either.
- Make a Windows 11 install USB from an Android phone, if that’s the limit that brought you here.
- What is BootForge for the full picture.
Legal notes
EtchDroid is an independent open-source project with no affiliation to BootForge or ByteHaven Studios. It is described here on the basis of its own published documentation, linked above, and we’ve tried to represent it fairly. If something on this page is out of date or wrong, tell us at support@bytehavenstudios.com and we’ll correct it.
BootForge is an independent application, not affiliated with or endorsed by the Ventoy project, and uses Ventoy under that project’s licence.