What Is Jelly Dad and What Does It Actually Do
Jelly Dad is a macOS utility that automates the creation of installer images and media for various Linux distributions. It wraps the messy parts of getting an ISO onto a USB drive — verification, partitioning, extraction, EFI boot setup — into a single clickable process. There are several forks and derivatives floating around, and the core idea is the same across all of them: you drop an ISO in, pick a drive, and walk away instead of fiddling with dd or manual parted commands. I run this on a daily basis because I maintain a handful of test machines and need to spin up fresh Linux installs constantly. The process is straightforward. Download the latest build from the GitHub releases page. Unzip it. Run the app, grant it the usual disk and storage permissions when macOS asks, drop your ISO into the input field, select the target USB drive from the dropdown, and hit make. The app will wipe the drive, create a GPT partition table if needed, mount the ISO read-only, and extract the contents directly to the filesystem. It handles the EFI boot stub properly, which is where most manual tools fumble around. Here is a realistic problem I ran into that the documentation does not cover. I was trying to create a bootable Ubuntu 24.04 image and the drive would mount but refuse to boot on any machine I tested. The app was completing without errors, but the resulting USB was essentially bricked. The issue turned out to be related to how Ubuntu 24.04 changed its ISO hybrid layout. The version of Jelly Dad I had installed was extracting the ISO contents sequentially and not preserving the El Torito boot metadata that the firmware expects. The workaround was simple once I figured it out: I switched to using the --force-bios mode flag in the terminal launch instead of clicking the button in the GUI. That forced a raw sector copy rather than a file-level extraction, which preserved the boot signatures. You can invoke it like this:
jellydad --force-bios --iso ~/Downloads/ubuntu-24.04.iso --device /dev/disk2 The app also supports multiple distros. Arch, Fedora, openSUSE, Debian, Pop!_OS, EndeavourOS, Manjaro — it works with any ISO that follows the standard hybrid format. If the ISO is non-standard or uses a custom bootloader layout, you may hit edge cases. That is worth keeping in mind.
Things beginners get wrong about Jelly Dad
The biggest mistake people make is assuming the tool verifies the ISO before writing. It does not, not by default. The assumption is that you already checksummed your download, which is reasonable, but it is easy to skip and then waste an hour debugging why a Mint install refuses to boot. Run shasum or md5sum on the ISO first. Always. Another thing nobody mentions: Jelly Dad does not recover the USB drive after writing. Once the process completes, the drive usually shows up as a single partition with a strange filesystem label that macOS refuses to mount cleanly. You need to use Disk Utility or diskutil to reformat the drive back to exFAT or FAT32 before you can use it for anything else. I used to lose drives to this because I assumed the app handled cleanup. It does not. There is also a subtle but important limitation with large ISOs. Anything over about 5 GB tends to cause problems with the extraction-based mode on older machines or slower USB 2.0 drives. The app will sit at 99 percent for a very long time and then sometimes fail. For large ISOs, use the force-bios flag and accept the raw copy approach. It is faster and more reliable for big files, and it sidesteps the extraction bug entirely.
Get the Full Details
When Jelly Dad is the right call and when it is not
This tool is genuinely useful if you are creating Linux install media regularly on macOS. It saves you from the terminal and handles EFI setup correctly, which matters more than people realize. A USB created without proper EFI partitioning will boot on some machines and fail on others, and Jelly Dad gets this right in almost all cases. It is not the right choice if you need to create persistent live environments. Some distros support persistence on Linux, and Jelly Dad does not currently offer a persistence size option or a dedicated UI for it. You would need to build that manually afterward using lsblk and a mkfs command on the spare space. If persistence is a requirement, BalenaEtcher or the official dd approach with a second partition is more straightforward. Similarly, if you are working with Windows ISOs instead of Linux, Jelly Dad is not relevant. It is built specifically for Linux ISO extraction and partitioning. Use Rufus or BalenaEtcher for Windows images.
Download and installation notes
The app is available on GitHub. Look for the repository under the name jelly-dad or similar — there are a few community mirrors. Download the latest .dmg from releases, drag it to Applications, and launch it. On first run, macOS may show a gatekeeper warning because the developer is not notarized through Apple's system. Go to System Settings, Privacy & Security, and allow the app to run. This is standard for niche open-source macOS tools and is not specific to Jelly Dad. If you prefer the terminal-only route, which I recommend after the Ubuntu experience I described, you can install via Homebrew if a formula exists in a third-party tap, or build from source. The source is short enough that compiling takes about two minutes on a typical Mac. One final note about the force-bios mode. It is slower than the extraction method for small ISOs — maybe 30 to 45 seconds longer for a 2 GB image — but it is more reliable overall. I switched to using it as my default about six months ago and have not gone back. The marginal speed cost is worth the elimination of the edge-case failures that used to pop up occasionally.
