How to Install Mac OS from USB in 2026
· macOS USB install, bootable macOS installer, createinstallmedia, Apple silicon installer, macOS clean install
Your Mac is stuck at the worst possible moment. The internal drive won't boot, Recovery feels flaky, and you need a clean reinstall or a repair path that doesn't depend on the system that just failed. That's when a bootable USB installer stops being “old-school” and becomes the fastest reliable way back in.
Apple still documents the same core workflow for creating and using a bootable installer, and that matters in 2026 because the boot path now splits in the middle depending on whether the machine is Apple silicon or Intel. The command to build the USB is familiar, the startup gesture is not, and most bad guides mix those two parts together. That's how people end up with USBs that never show up, or installers that boot on one Mac and fail on another.
Table of Contents
- Why a Bootable USB Installer Still Matters in 2026
- What You Need Before You Start
- Creating the Bootable USB With Terminal
- Booting From the USB on Apple Silicon vs Intel
- Erasing the Drive and Running the Installer
- Common Problems and How to Fix Them
- Post-Install Steps and Keeping Things Clean
Why a Bootable USB Installer Still Matters in 2026
The call usually comes in after the machine has already made the decision for you. The screen is black, the system volume is corrupted, or the internal SSD is brand new and empty, and now the only question is how to get macOS onto it without relying on the dead or half-dead install that was there before. In those moments, a USB installer is the path that still works when the built-in system doesn't.
Apple's own bootable-installer documentation makes the case plainly. The installer has to live on a USB flash drive or other external volume connected directly to the Mac, and the workflow uses the createinstallmedia tool inside the macOS installer app, not some separate imaging utility. Apple also separates the startup behavior for Apple silicon and Intel Macs, which is the 2026 reality you have to respect if you want the USB to boot reliably. See Apple's bootable-installer guide for the official sequence and the hardware split in startup behavior. Apple's bootable installer support document
A lot of published advice still treats this as a backup trick from the Intel era. That's wrong. The same installer concept has stayed relevant across modern macOS releases, and independent guides keep showing the same createinstallmedia workflow and the same boot-manager handoff on both older and newer Macs. MacWorld's macOS USB installer guide shows that continuity clearly, which is exactly why this remains the standard recovery path rather than a niche workaround.
Practical rule: if the Mac's internal disk is unreliable, assume Internet Recovery is a convenience, not a guarantee. A properly built USB installer gives you a local boot path you control.
That difference matters most when you're restoring a machine you can't afford to keep guessing with. A clean reinstall, a fresh SSD, or a batch of machines that all need the same macOS image is where the USB approach earns its keep, and it's still the method I reach for when I need the least drama.
What You Need Before You Start
Start with the drive, because everything else depends on it. The USB must be empty before you erase it, and it needs enough space for the installer. If you run into a capacity problem before you even begin, this disk space checklist is the faster fix than guessing your way through Terminal. Anything already on that flash drive is gone once you start the erase, so treat the first step as destructive, not reversible.
Next, download the full macOS installer, not a small updater or patch. The installer app is what contains createinstallmedia, and that app has to live in /Applications on the Mac that is creating the USB. In Finder, confirm the exact app name before you type a command, because the version in the filename has to match what you downloaded. A mismatch here usually turns into a failed command, not a useful error message.
Your target Mac's data matters too. If you plan to erase the startup disk, back up first. A USB installer is a reinstall path, not a rescue tool for files that were never saved. If you've already lost files on the target machine, handle recovery separately and use a proper recovery plan instead of hoping the reinstall will preserve anything. For that side of the workflow, this recovery guide is the safer place to start than a blunt erase.
Apple silicon adds one more physical rule. Plug the USB directly into the Mac, not through a hub or a chain of adapters, or the startup firmware may never see it at boot. That mistake shows up constantly in real setups, and it is easy to avoid if you treat the first boot as a hardware check, not just a software step.
Keep the Mac signed out of the App Store and iCloud if you're handing the machine off or doing a full reinstall for someone else. Skipping that cleanup can leave you dealing with Activation Lock and account surprises later.
Before opening Terminal, line up this checklist:
- USB drive. Empty, erased, and large enough for the installer.
- Full installer. In /Applications, with the exact macOS version you want.
- Working Mac. The target machine can be broken, the prep Mac has to boot.
- Backup. Anything important on the target should already be saved elsewhere.
- Direct connection. Especially on Apple silicon, no hub unless you're sure it is recognized.
Creating the Bootable USB With Terminal
The installer app does the heavy lifting, but Terminal is where the bootable media gets written. Open /Applications, confirm the app name, and look for something like Install macOS Tahoe.app, Install macOS Sequoia.app, or whatever version you downloaded. The exact filename matters because the command points into that app bundle, and a typo there is one of the fastest ways to trigger a dead-end “command not found” complaint.
The standard pattern looks like this:
sudo /Applications/Install\ macOS\ [Version].app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume --nointeraction
Here's what each piece does. sudo gives the tool permission to erase and write the USB. The path after it tells Terminal where the installer app lives. createinstallmedia is Apple's tool for making the drive bootable. --volume /Volumes/MyVolume tells it which erased USB volume to use, and --nointeraction lets the process run without stopping for extra prompts once you've already approved the destructive step.
Apple's support pages specifically instruct you to rename the USB volume to MyVolume so the command matches cleanly, and that isn't cosmetic. It keeps the volume name aligned with the command line, which saves you from quoting the wrong path or pointing the installer at the wrong device. Apple's documented workflow also shows the bootable-installer process is tied to the same command-line structure the Mac expects at startup.
After you press Return, Terminal asks for your admin password. Then you may get a prompt to approve access to the removable drive, and finally a confirmation to erase the volume. Type Y when asked, because that's the point of no return. MacWorld's installer guide shows the same basic pattern for the confirm-and-erase flow across releases. MacWorld's guide to creating bootable macOS USB installers
The copy phase is not instant. On a typical USB 3 drive, I expect roughly 10 to 30 minutes before the prompt comes back. Success is boring, which is what you want. Terminal returns to a normal prompt, Finder shows the USB renamed as Install macOS, and the drive is now a bootable installer instead of a plain storage device.
If the command fails immediately, re-check the installer path before anything else. Most failures I see are simple path mistakes, not bad hardware.
Booting From the USB on Apple Silicon vs Intel
Most guides fall apart here, because they blur two different boot systems into one set of instructions. The USB may be identical, but the startup gesture is not. On Apple silicon, the Mac listens for a long press on the power button. On Intel, it still uses the Option (Alt) key. Miss that split, and the USB installer will look broken even when it's fine.
| Step | Apple Silicon (M1 and later) | Intel Macs |
|---|---|---|
| Shut down | Fully shut down the Mac | Fully shut down the Mac |
| Startup gesture | Hold the power button until Loading startup options appears | Power on and immediately hold Option (Alt) |
| Boot picker | Choose the USB installer from startup options | Choose the USB installer from the boot picker |
| Continue | Click Continue after selecting the installer | Press Return or continue from the picker |
On Apple silicon, the USB needs to be connected directly to the Mac. The firmware is much pickier about external media during startup, and hubs are a frequent reason the drive never appears. That's not superstition, it's the nature of the sealed boot chain Apple uses on those machines. On Intel Macs, the firmware is more forgiving, but a hub can still hide the drive, especially if the adapter chain is cheap or flaky.
There's a small overlap worth calling out for late Intel hardware with the T2 security chip. Those Macs can behave more like Apple silicon when booting external media, which is why some people think the drive is dead when the core issue is security settings or an incomplete startup sequence. The external path still exists, but the Mac is more selective about what it accepts at boot time.
Simple rule: Apple silicon uses the power button. Intel uses Option. If you're pressing the wrong one, you're not “almost there,” you're on the wrong boot path.
A lot of boot failures come from timing, not from the installer itself. On Intel, the Option key has to be held immediately after power-on. On Apple silicon, the power button has to stay held long enough for startup options to load. If the USB doesn't appear, unplug it, reconnect it directly, power the Mac down again, and retry with the correct gesture for the machine in front of you. Setapp's install-from-USB walkthrough matches that split cleanly.
Erasing the Drive and Running the Installer
Once the installer boots, don't rush straight into the install button. If the goal is a clean system, the first real task is opening Disk Utility from the Utilities menu and erasing the top-level internal SSD, not just a container or volume nested underneath it. That distinction matters because choosing the wrong layer can leave macOS with a disk structure it can't install onto cleanly later.
Use APFS and GUID Partition Map when you erase the internal disk. Then close Disk Utility and return to the main installer. Select the freshly erased volume and proceed. If the installer later claims it can't install on the disk, the most common cause is that the wrong object was erased, or the partition map never got reset properly.
The installation phase usually includes more than one restart. That's normal. The machine may seem to boot back into the internal drive midway through the process, and that isn't a sign that the USB failed. The installer copies the system, reboots, then finishes the setup from the internal disk as part of the normal handoff. If you see the Apple logo again, give it time before touching anything.
The first boot setup follows the usual macOS sequence. Choose your region, join Wi-Fi, sign in with Apple ID if that's part of the workflow you want, and decide whether to migrate from a Time Machine backup or start clean. If you're rebuilding a damaged system and trying to recover data later, keep the reinstall and the file recovery mindset separate. A clean install is not the place to improvise with old files, especially if you still need to reconstruct what was lost. This restore guide is the safer companion if your goal is recovering deleted data rather than wiping the machine.
The practical mistake here is impatience. People assume the machine froze because the screen stayed on the Apple logo too long, then they force a restart and break a perfectly good install. Let the installer work, and only intervene if the Mac has clearly stopped changing state for a long stretch and you've already ruled out a bad USB.
Common Problems and How to Fix Them
The same three failures keep showing up, and they're usually easy to diagnose once you stop blaming the wrong part of the process. The USB installer rarely fails because macOS is mysterious. It fails because the drive wasn't built correctly, the Mac never saw it at startup, or the installer app was incomplete.
The USB does not appear at boot
If the USB never shows up in the boot picker, check the physical connection first. On Apple silicon, the drive should be plugged directly into the Mac, not through a hub. If it's already direct-connected, the next thing to question is whether you built the installer for the right macOS version and whether the USB was erased correctly before createinstallmedia wrote to it.
The installer says it is damaged
When the Mac throws a “this copy of the macOS installer is damaged” style message, think partial download before anything else. Redownload the full installer from Apple rather than trying to salvage a cached copy or an older app bundle. A bad download can still look complete in Finder, which is why this error catches people off guard.
The install hangs or loops
A grey Apple logo with no real progress, or a reboot loop back into the installer, usually means the USB is bad, the partition scheme was wrong, or the Mac is still trying to boot from the installer when it should be booting from the internal disk. Rebuild the USB, try a different port, and on the final restart remove the installer so the internal drive takes over. That's a common issue on Macs that appear to “finish” but never hand off cleanly.
If the internal disk isn't visible in Disk Utility, erase the physical parent disk, not just the APFS volume or container under it. That's the move people skip when they're in a hurry.
A few errors deserve a more deliberate read. “No packages were eligible for install” usually means the installer doesn't match the machine or the system environment is out of sync, and a bad date or an incompatible installer is often involved. In other words, don't keep clicking through the same broken media. Reset the inputs first.
If you're troubleshooting a machine that freezes during startup rather than during install, use the same discipline and don't guess. This frozen Mac guide is the better reference point when the problem is a stalled system, not the USB workflow itself.
Post-Install Steps and Keeping Things Clean
When macOS finally comes up, confirm the install in About This Mac and make sure the machine is showing the expected Apple silicon or Intel identity. Then run Software Update again. Fresh installs often land on a base build that still needs post-release fixes, and there's no reason to stop at “it boots” if Apple has already shipped corrections.
Sign back into iCloud and the App Store once you've verified the machine is stable. If you restored from a Time Machine backup, use Migration Assistant deliberately rather than dragging old files around by hand. That keeps the system and your data layers clearer, which pays off later when you're trying to figure out whether a problem came from the reinstall or from whatever was brought back afterward.
A clean reinstall also exposes how much clutter old apps leave behind. Preferences, caches, containers, logs, and saved state files often survive long after the app itself is gone, which is why a fresh macOS install can still feel oddly crowded. A focused cleanup pass after reinstalling is the right time to remove those leftovers instead of letting them sit under a new system.
For a practical post-install checklist, keep it simple:
- Confirm the system version in About This Mac.
- Run Software Update for any remaining patches.
- Sign into Apple services only after the machine is stable.
- Restore data carefully with Migration Assistant if you have a backup.
- Review leftover app files and clear the clutter that doesn't belong on the new install.
When the USB installer is the right tool, it gives you control back. It's the right choice when the internal disk won't boot, the recovery path is unreliable, or you need a repeatable reinstall method that works across generations. And when the machine is finally healthy again, the cleanup work should be just as deliberate as the reinstall itself.
If you've just rebuilt a Mac and want the leftovers gone without touching system files, visit Crufti. It finds the app debris that reinstalling leaves behind, then lets you review and remove it safely so the machine feels clean after the USB work is done.