Solid state
An SSD erases deleted files on its own.
The drive does it in the background, within minutes, whether or not anyone touches the machine. That single fact sorts SSD losses into two groups: deletions, which are mostly beyond anyone once the drive has done its housekeeping, and failures, where the data is often intact. This page is for telling one from the other, before anything makes either worse.
Why deleted files on an SSD are different
On a hard drive, deletion removes the entry pointing to a file and the contents sit untouched until something reuses the space, which can take years. An SSD adds a step. The operating system tells the drive which blocks are now free, the TRIM command, and the drive’s controller then erases those blocks in the background so future writes stay fast. On a modern internal drive under Windows, macOS or Linux, that happens automatically, and usually within minutes of the deletion.
Once it has, the data is gone in the strongest sense available: the flash cells hold nothing. No software, no lab and no amount of money reads back what the controller has erased. We say this before you spend anything, because a fair share of SSD deletion enquiries end at this paragraph, and they should end free.
When TRIM has not done its work
The erase-on-delete behaviour has conditions, and the exceptions are where deletion recovery on solid state still succeeds.
- External drives over USB. Many enclosures and portable drives never pass the TRIM command through, so a deletion on an external SSD often behaves like one on a hard drive: recoverable until something overwrites it.
- A corrupted filesystem keeps its data allocated. When a partition table breaks, a volume stops mounting, or the drive shows as RAW, nothing has told the controller those blocks are free, so its housekeeping leaves them alone. These cases recover well.
- The machine was powered off fast. TRIM marks blocks; the physical erase is housekeeping the controller gets to shortly after. Cutting power early sometimes beats it, but many drives answer with blanks for marked blocks either way. Treat this as a reason to power off now, never as a reassurance.
The failing SSD, and why hours matter
A failing SSD rarely announces itself. There is no click and no grind. The signs are quieter: read errors climbing, the machine stalling on certain files, a drive that disappears under load and returns after a power cycle, capacity reporting as zero, or the drive locking itself into read-only.
If any of that is happening and the drive still detects, it is a recoverable case with a countdown attached. The correct move is one careful, error-aware imaging pass onto stable storage, healthy regions first, before the drive is asked to do anything else. Every reboot and every browsing session spends reads the drive may not have. All recovery then happens on the image; the original is read once and set aside.
Dead external SSDs, and the board in between
A portable SSD that no longer detects has two suspects: the drive itself, and the USB bridge board between it and the world. The bridge fails far more often. Behind it there is usually an ordinary SATA or NVMe drive that reads perfectly once connected directly, which turns a dead drive into a routine job.
Some portables are built as one board, with a USB controller native to it, and some encrypt on the bridge, tying the data to the failed part. Which type yours is decides everything, and it is established at the free assessment rather than guessed over the phone.
Where it ends
Two verdicts are final, and you will get either one plainly and early.
Deleted and erased is gone. Once the controller has cleared the flash, there is nothing on the drive to recover, for us or for anyone. A quote to attempt it would be a quote to bill you for the discovery.
A dead controller on an encrypting drive is usually gone too. Many modern SSDs scramble everything written to flash with keys that live in the controller. When the controller dies, the flash chips still hold data, and nobody can unscramble it. This is the same wall a dead iPhone hits, and it does not move for money.
Common questions
Can deleted files be recovered from an SSD?
From a modern internal SSD, usually no. TRIM tells the drive the space is free and the controller erases it in the background, typically within minutes, whether or not you do anything afterwards. From external SSDs over USB, and in any case where the filesystem broke rather than files being deleted, the answer is frequently yes. The assessment is free, and it starts with working out which of those you have.
My external SSD is not detected. Is the data gone?
Often not. The USB bridge board in the enclosure fails more often than the drive behind it, and in that case the drive reads normally once connected directly. The exceptions are portables built as a single board, or ones that encrypt on the bridge, where a dead board can mean the end. Which kind you own is established at the free assessment, before any quote.
Windows says I need to format the drive. Should I?
No. That message reports an unreadable filesystem, and an unreadable filesystem on an SSD is one of the better cases: the files are still allocated, so the drive's own housekeeping leaves them alone. Formatting replaces the damaged structures a recovery would work from. Power the machine down and have the drive assessed as it is.
What does SSD recovery cost?
SSD and NVMe work starts at $399, after a free assessment and a fixed quote you agree to first. No recovery, no fee applies, and what counts as a recovery is agreed in writing at quote time. Where the answer is that the drive has already erased the deleted data, you hear it at the assessment and pay nothing.