My Mac’s APFS drive suddenly won’t mount after a restart, and Disk Utility First Aid didn’t fix it. I need to recover important files before trying anything that could overwrite the data. What reliable Mac APFS data recovery software or tools have worked for you?
If this is APFS data loss, the main thing is to stop touching the drive. Don’t install apps on it, don’t copy files to it, and don’t run a bunch of “fixes” just to see what happens. New writes can overwrite the exact data you’re hoping to recover.
I went through this after deleting a whole project folder on my MacBook with no Time Machine backup. I thought it was gone, but I was able to get almost all of it back.
Before using recovery software, check the easy stuff first:
- Look in the Trash.
- Check Time Machine if you use it.
- Open Time Machine anyway, even if your backup drive was not connected. APFS can have local snapshots, and macOS may still have a recent one available. They’re usually only kept for about a day, depending on free space.
If that doesn’t turn anything up, I’d go straight to recovery software instead of trying to repair the disk first.
I used Disk Drill because it actually understands APFS and isn’t only doing file signature scanning.
What I did was pretty simple:
- Downloaded Disk Drill to a different drive, not the one I was recovering from.
- Went to System Settings > Privacy & Security > Full Disk Access and gave Disk Drill permission. Without that, it may not be able to fully scan APFS system volumes.
- Picked the affected APFS drive and ran a full Search for Lost Data scan.
- Let the scan finish instead of stopping it early.
- Used preview to check whether the files were actually readable.
- Recovered the files to an external SSD, not back onto the Mac.
The useful part was that most of the recovered folders still had their original names and folder structure. That matters a lot when you’re dealing with a big project, because sorting through thousands of randomly named files is miserable. Disk Drill also has SMART monitoring, which helps if you think the drive itself might be failing. If the drive seems unstable, make a disk image first and recover from that instead of repeatedly scanning the original.
If you lost an entire APFS partition, I’d still recover the important files before attempting any repair. TestDisk can sometimes rebuild damaged partition tables, but it’s text-based and easy to mess up if you don’t already know what you’re doing. My rule is recover first, repair second.
For SSD recovery, keep TRIM in mind. Modern Macs use it in the background to clear deleted blocks. Once those blocks are wiped, recovery software can’t bring them back. That’s why stopping use immediately matters so much. Traditional hard drives don’t work the same way, so accidental deletion recovery is often more forgiving on HDDs.
If Disk Drill can find the files and they preview correctly, that’s usually a good sign.
But if the Mac no longer detects the drive, it keeps disconnecting, you hear clicking, or the APFS container looks badly damaged, I wouldn’t keep poking at it with DIY tools. At that point a professional recovery lab is safer. Many reputable places offer a free evaluation and some work on a no data, no fee basis. It costs more than software, but physical drive problems are a different situation.
Hopefully it’s just deletion or a damaged partition. Those are the cases where software recovery usually has the best shot, especially if you stop using the drive right away.
A deleted folder is one case; an APFS volume that will not mount after reboot is a bit uglier, because the file system metadata may be damaged, not just missing files.
I’d avoid “repair” tools until you’ve made an image of the drive, especially if it is external or acting flaky. Disk Drill is fine to try if it sees the APFS container, but I’d judge it by whether previews work, not by how many files it claims it found.
Do not click “Initialize,” “Erase,” or “Partition” if macOS offers that when the drive shows up. That prompt only means macOS can’t make sense of the file system right now, not that the data is gone.
For an APFS volume that suddenly will not mount, I would separate “can the Mac see the device?” from “can Finder mount the volume?” Those are different problems. If Disk Utility still shows the physical drive or APFS container, recovery software has something to work with. If the physical drive itself disappears, reconnects, or shows the wrong size, that is when repeated scans become a bad idea.
A detail people often miss with APFS is encryption. If FileVault or an encrypted APFS volume is involved, the recovery app may need the password or recovery key before it can show anything useful. Without that, some tools will still scan and produce a pile of garbage-looking results, which can make you think the scan failed when really the volume is just locked. So before judging any app, make sure it is actually seeing the unlocked APFS container.
Disk Drill is reasonable for the “I need a Mac app with a GUI and previews” route. I would not treat it as magic, though. Preview matters more than the scan count. If it says it found 900,000 files but half of them don’t preview, that is noise, not recovery. Save a few sample files to another drive and open them before paying or committing hours to a full restore.
If you want alternatives, look at R-Studio for Mac or UFS Explorer. They are less friendly than Disk Drill, but they are common choices when the file system is more badly damaged. DMDE is another cheaper option, though it is not what I would hand to someone who gets nervous around partition maps. TestDisk is useful for some partition table problems, but for APFS file recovery I would not make it my first stop unless you already know what you are doing.
The safer order, in my opinion, is:
- Stop booting from or writing to the affected drive.
- Check whether the physical drive appears in Disk Utility, System Information, or Terminal with
diskutil list. - If it appears, make an image to another drive if you have enough space.
- Scan the image, not the original, if the drive seems unstable.
- Recover to a separate disk.
- Only after that, try repairs, reformatting, reinstalling macOS, or rebuilding partitions.
For an external drive, imaging is usually realistic. For an internal Apple silicon or T2 Mac, it can be more annoying because the SSD is tied into the machine and encryption is often involved. In that case, booting to macOS Recovery and using Share Disk/Target Disk Mode from another Mac can sometimes be cleaner than repeatedly booting the same Mac and letting background processes touch the volume.
A small warning about “First Aid didn’t fix it”: don’t keep running it over and over. Once is fine. Maybe twice if you got a different error after the first pass. After that, you are mostly just stressing the same damaged metadata and hoping for a different outcome.
If the files are business-critical, skip the software shopping and get a lab quote first. If they are important but not worth lab money, then Disk Drill is the easiest first try, with R-Studio or UFS Explorer as the more technical second try. The key is not which logo is on the app. The key is whether the original drive is kept read-only as much as possible and whether recovered files actually open.
A drive that shows a normal size and stable identifier in diskutil list is a very different problem from a drive that appears, vanishes, or reports as 0 bytes. In the first case, software recovery is a reasonable next move. In the second case, the recovery app is mostly being asked to read through a connection or hardware problem, and that can make things worse or at least waste a lot of time.
For an external APFS disk, I’d rule out the boring hardware layer before paying for anything: different USB-C cable, different port, no hub/dock, and ideally another Mac. Don’t run repairs while doing this. Just see whether the physical device and APFS container show consistently. A flaky enclosure can make APFS look “corrupt” when the actual issue is the bridge board dropping out under load.
If the disk is seen reliably, Disk Drill is fine as the friendlier first attempt, especially if you care about previews and original folder names. I’d still avoid installing it on the affected volume and I would recover only to a separate disk. If Disk Drill sees the container but gives you mostly unpreviewable junk, don’t assume the next five GUI apps will magically do better. That’s when R-Studio or UFS Explorer may be worth trying, or a lab if the files justify the cost.
The annoying detail with APFS is that “won’t mount” does not always mean “files are gone.” It can be a damaged volume role, bad snapshots, encryption weirdness, or container metadata trouble. So I’d spend my effort on getting one clean read or image of the device, then scan that. Repeated First Aid passes and random repair buttons are the part I’d avoid.