Why Deleted Files Usually Can't Be Recovered on an SSD
Undeleting a file on a hard drive and undeleting one on an SSD look like the same task from the outside, but the SSD has usually already done something a hard drive never does — actively erased the data, not just forgotten where it was.
What's actually happening
On a hard drive, deleting a file just removes its entry from the file system's index; the actual data stays physically on the platter, untouched, until something else happens to be written over that same spot. SSDs work differently. Because flash memory has to be erased in large blocks before it can be rewritten, the operating system sends the drive a TRIM command as soon as a file is deleted, telling the controller which blocks are no longer in use. Many SSDs act on that almost immediately, and some perform idle-time garbage collection that clears the marked blocks within seconds to minutes — well before anyone has a chance to notice the deletion was a mistake.
How recoverable this really is
Once TRIM has actually executed against a block, the data isn't merely hard to find — it's electrically gone from that flash cell, and no software technique or forensic process gets it back. That makes this a fundamentally different problem from a hard drive, where recoverability is mostly a race against being overwritten. What's actually recoverable depends on whether TRIM ran at all: some setups don't pass TRIM through, including many external USB enclosures, some RAID configurations, and older systems or drives without TRIM support, and in those cases an SSD behaves much more like a hard drive for recovery purposes.
The general approach
Because the window, if one exists at all, is measured in seconds to minutes rather than the days or weeks a hard drive often allows, stop using the drive and try recovery software immediately rather than researching options first. It's just as important to check other copies — a cloud sync trash bin, a backup, a shared copy on another device — since those are frequently the faster and more reliable path once TRIM is even a possibility.
Don't keep using the drive, install recovery software onto it, or run anything that writes to it while investigating — every write is a chance to trigger garbage collection on blocks that hadn't been cleared yet. If the system was off when the deletion happened, TRIM may not have executed yet at all, which makes leaving the drive untouched until it's imaged more valuable here than on almost any other case in this catalog.
This is a different problem from a dead or undetected SSD covered in SSD Controller Failure — that one is about the controller failing outright, this one is about normal deletion behavior on a working drive. For the underlying mechanics of how SSDs manage data differently from hard drives, see HDD vs. SSD vs. NVMe. A real backup, covered in Backup Drive Picks, is the only reliable defense against this scenario specifically.
This page describes the general situation, not a guaranteed fix for your specific case. If you'd rather have someone experienced take a look before you try anything, see what a hands-on evaluation looks like.