APFS
Recover Deleted APFS Volume
What matters after an APFS volume is removed.
A deleted APFS volume removes the logical entry that macOS uses to mount it. Recovery depends on what metadata and file data remain after deletion. On SSDs, TRIM begins reclaiming freed blocks almost immediately, so the window for successful recovery narrows quickly.
First: do not make the source worse
Treat this as a recovery situation before you treat it as a repair task. The priority is to preserve readable data and avoid new writes to the affected device.
- Do not recreate the deleted APFS volume on the same container.
- Do not write new data to any volume sharing that container.
- Do not erase or repartition the disk after deleting the volume.
- Do not save recovered files back into the same container.
Scan and preview first
Refindo can scan a detectable APFS device for recoverable files. Results depend heavily on overwrite and TRIM activity after deletion.
Likely causes
- 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.
Read-only recovery workflow
- 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 to stop self-recovery
- 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.
Related recovery guides
What You Need to Know
Volume Deletion vs TRIM Race
When you delete an APFS volume, macOS removes the volume record from the container metadata. The file data blocks are not 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 do not 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 is no fixed time. TRIM scheduling depends on the SSD controller and macOS workload. Scanning within minutes gives the best results.