APFS
Recover Deleted APFS Volume
What matters after an APFS volume is removed.
Written by the Refindo Recovery Team · Published · Updated
Deleting an APFS volume removes the logical entry macOS uses to mount it, but deletion and erasure aren't the same thing. The file data isn't wiped on the spot; whether you can get it back depends on what metadata survives and, critically, how fast the SSD reclaims the freed space. On SSDs, TRIM starts releasing those blocks almost immediately, so the recovery window can be measured in minutes rather than days. Speed is the whole game here.
Quick answer
Deletion freed the space but hasn't necessarily reused it yet. Keep every volume in that container read-only and scan immediately, because on an SSD the window closes in minutes.
Keep the container read-only
- Do not recreate the deleted volume on the same container.
- Do not write new data to any volume that shares that container. They compete for the same freed space.
- Do not erase or repartition the disk after the deletion.
- Recover to a separate drive, not back into the same container.
What happens when an APFS volume is deleted
- Accidental volume deletion in Disk Utility.
- Container cleanup after removing a volume group.
- New writes to the same APFS container overwriting old records.
- TRIM on SSDs clearing deleted blocks quickly.
How to scan for a deleted APFS volume
Refindo can scan a detectable APFS device for recoverable files. Results depend heavily on overwrite and TRIM activity after deletion.
- Connect the APFS device immediately and grant Refindo disk access.
- Open Refindo and select the container that held the deleted volume.
- Run Quick Scan, then Deep Scan to locate the deleted volume structure and files.
- Preview recoverable files and save them to a separate drive.
When TRIM has likely won
- The volume was deleted on an SSD where TRIM may have already cleared blocks.
- The deleted volume held the only copy of critical work.
- Disk Utility reports hardware errors or the device disappears during scans.
- Other volumes in the container have been written to since the deletion.
Volume deletion, TRIM, and shared space
Volume Deletion vs TRIM Race
When you delete an APFS volume, macOS removes the volume record from the container metadata. The file data blocks aren't immediately zeroed, but the SSD controller receives TRIM commands for the freed space. How quickly the controller processes those commands determines the recovery window, which can range from seconds to hours depending on the drive firmware.
Container Space Reallocation After Deletion
APFS containers dynamically share space among volumes. After a volume is deleted, its freed space becomes available to remaining volumes. If other volumes in the same container write new data, those writes may land on blocks that previously belonged to the deleted volume, overwriting recoverable content even without TRIM involvement.
Frequently Asked Questions
Can a deleted APFS volume always be restored?
No. Recoverability depends on remaining metadata, file data, overwrite activity, and TRIM.
Should I recreate the deleted volume?
No. Recreating it writes new metadata to the same container and can reduce recovery chances.
What scan should I run?
Start with Quick Scan, then run Deep Scan if the deleted volume structure is incomplete.
Does it matter if the deleted volume was on an HDD or SSD?
Yes. HDDs don't use TRIM, so deleted data persists until physically overwritten. SSDs with TRIM can clear blocks in the background, making recovery harder.
How long do I have before a deleted APFS volume becomes unrecoverable on an SSD?
There's no fixed time. TRIM scheduling depends on the SSD controller and macOS workload. Scanning within minutes gives the best results.
Scan before you repair
Run a read-only scan first, preview what is recoverable, then save selected files to a different drive.