HFS+ or APFS for a Hackintosh: Choose by macOS Version
Check the HFS+ and APFS requirements for older macOS releases, plus Hackintosh bootloader, Disk Utility, conversion, and recovery considerations.
A Sierra installer cannot boot from an APFS system volume. A Catalina installation, meanwhile, needs an APFS layout rather than an HFS+ startup volume. On a Hackintosh, choose the file system for the exact OS X or macOS release you intend to run—not simply by whether the drive is an SSD. Before erasing or converting anything, make a restorable backup and check that the installer, bootloader, firmware path, and hardware support that release.
The version boundary matters most
Mac OS Extended (Journaled), usually called HFS+, is the native system-volume format for older OS X releases through macOS Sierra. APFS arrived with High Sierra. High Sierra can run from either format in supported installation scenarios, though its installer normally converts qualifying SSD startup volumes to APFS. Mechanical disks were generally left on HFS+ unless converted separately.
With Mojave, plan on APFS: the installer converts HFS+ startup volumes. Catalina uses an APFS volume group, separating the system and data volumes while presenting them together in macOS. Its installer and updates expect that arrangement. Later releases rely on APFS for still more system-volume behavior, including sealed system volumes in Big Sur and newer versions. For these releases, APFS is not an optional performance setting.
| Target release | System-volume decision | Hackintosh check |
|---|---|---|
| OS X through macOS Sierra | Use HFS+ for the startup volume | Keep a boot path that can read the HFS+ installer and system |
| macOS High Sierra | HFS+ or APFS, subject to installer behavior | Expect APFS conversion on a qualifying SSD; verify bootloader APFS access |
| macOS Mojave | Plan for APFS | Verify APFS boot support before allowing conversion |
| macOS Catalina and later | Use the APFS layout required by that release | Check installer, volume-group, and update boot entries |
Those choices concern the system volume, not every disk connected to the machine. A newer macOS installation can generally read an older HFS+ data disk. An older OS without APFS support, however, cannot be assumed to mount an APFS volume. Test the specific pairing before relying on a shared disk for backup or migration.

What each format changes—and what it does not
HFS+ on a legacy build
HFS+ is the straightforward choice for a Mountain Lion, El Capitan, or Sierra build: those systems were designed to start from it. Its journaling helps recover file-system metadata after an interrupted write, but it cannot make an interrupted installation safe or replace a backup. If a machine is kept solely for older software and hardware, converting its working system disk to APFS offers little benefit. The older OS may not understand the converted volume at all.
Even a correctly formatted HFS+ volume needs a valid boot path. The disk's GUID Partition Map, EFI System Partition where applicable, bootloader configuration, and installer support are separate concerns. Formatting as HFS+ will not fix incompatible graphics, a missing storage controller driver, or incorrect ACPI configuration.
APFS on High Sierra and newer systems
APFS provides copy-on-write metadata, clones, and snapshots. Snapshots can help with some recovery and update workflows, but they remain on the same physical device unless copied elsewhere. APFS also puts volumes in a container so they can share available space. In Disk Utility, keep the physical drive, its partitions, the APFS container, and its volumes distinct. Erasing one level is not the same as erasing another.
On a Hackintosh, the bootloader must be able to find the relevant APFS volumes or macOS boot entries. Depending on the age and configuration of Clover or OpenCore, that may require an appropriate APFS driver or the bootloader's APFS support. The requirement depends on the setup. If a volume is missing from the picker, do not drop random drivers into a working EFI folder. Check first that the volume exists, the installer completed, and the bootloader can enumerate it.
APFS will not fix slow hardware. Performance on a particular hard disk or older SSD depends on the workload, drive health, controller, and macOS release. If a High Sierra installation on an HFS+ hard disk already works, APFS availability alone is no reason to convert it. For Mojave or later, though, keeping HFS+ as the system format is not a sound workaround for installation or boot trouble.
Choose a format before opening Disk Utility
- Preserving an older OS X installation: leave its HFS+ startup disk intact. Test APFS on a separate target.
- Installing High Sierra on an SSD: prepare for APFS conversion even if you initially erase the target as HFS+. Verify that the bootloader can start the converted installation before retiring the previous disk.
- Installing High Sierra on a hard disk: HFS+ may be simpler if the installer permits it and you do not plan to put a later macOS release on that volume.
- Installing Mojave or Catalina: plan the disk and EFI boot path around APFS rather than relying on an unsupported HFS+ system-volume workaround.
- Keeping several macOS releases: consider separate physical disks or clearly identified partitions. Sierra cannot start from an APFS volume, and an older recovery environment should not be assumed to maintain a newer APFS installation.
For an installation drive, use GUID Partition Map unless you have a specific, verified legacy configuration that calls for another scheme. GUID describes how the drive is partitioned; HFS+ and APFS describe the macOS storage within it. Choosing “APFS” in Disk Utility does not correct the wrong partition scheme.
Some installer versions initially show only volumes in Disk Utility. Enable the device view before deciding what to erase, then check the capacity and device name twice. If the drive holds a working OS or unrelated data, do not erase the entire physical device just to change one target volume. Test that your full backup is readable before repartitioning, converting, or installing.

When an APFS installation disappears from the boot menu
A missing boot-picker entry does not prove the disk was formatted incorrectly. Start from a known-working installer or recovery environment appropriate for the target macOS release. Check whether Disk Utility sees the physical drive, APFS container, and expected volumes. If the physical drive is missing, investigate the cable, port, controller mode, and storage support before touching the file system.
If the container is visible but Clover or OpenCore shows no entry, compare the EFI configuration with that bootloader version's APFS requirements. Save the original EFI folder on a separate, bootable device before editing it. During installation, you may need to select temporary installer or update entries before the finished system entry appears. Make sure you are not selecting an unrelated older macOS volume.
If the machine reaches the Apple logo or verbose output and then stalls, APFS may already have been read successfully. Graphics initialization, USB mapping, ACPI, or a macOS version unsupported by the platform can all stop booting at that point. Do not erase and reinstall solely because the last visible message mentioned an APFS volume.
Conversion and recovery without risking the only copy
HFS+-to-APFS conversion is not a casual reversible switch. Even when a tool supports conversion in one direction, returning to HFS+ generally means erasing the target and restoring a compatible backup or reinstalling. Back up user data separately from the installer, save the working EFI configuration, and record the macOS and bootloader versions used with that backup. An older recovery environment may not inspect a newer APFS layout reliably.
Treat encryption as a separate decision. FileVault support depends on the macOS release, bootloader setup, and ability to show the password prompt at startup; choosing APFS does not, by itself, establish that an encrypted Hackintosh can boot. Get an unencrypted installation and recovery method working first, then keep the recovery key somewhere secure if you enable encryption.
For a High Sierra test on a spare SSD, boot the installer and install macOS before changing the everyday boot drive. Inspect the target in the installer's Disk Utility: confirm the SSD uses GUID Partition Map and has the expected APFS container and macOS volume. Then check that the saved EFI configuration can display and start that volume. Move personal data only after that boot test succeeds.
