Why Deleted Files Usually Can't Be Recovered on an SSD
Undeleting a file on an SSD is fundamentally less predictable than undeleting one on a hard drive. TRIM can cause the SSD to stop returning the old data through its normal logical interface, and later internal garbage collection may physically erase the underlying flash pages.
What's actually happening
On a hard drive, deletion normally marks file-system space as available while the old sectors remain readable until they are overwritten. On a TRIM-capable SSD, the operating system may also issue a TRIM/deallocate command for logical blocks that are no longer needed. What happens next is controller- and interface-dependent: the SSD may stop exposing the previous contents immediately, may return zeros or other deterministic data for trimmed ranges, and may physically erase the corresponding flash later during garbage collection. The timing is not reliably predictable from outside the drive.
How recoverable this really is
Once a trimmed range no longer returns its previous contents through the SSD's normal logical interface, ordinary undelete software cannot recover those old blocks. If the controller has also erased the underlying flash, recovery becomes harder still. The important question is whether TRIM/deallocation was issued and propagated through the actual storage stack. USB bridges, RAID layers, virtualization, operating-system settings, file systems, and drive firmware can all affect that behavior, so apparently similar SSD deletion cases can have very different outcomes.
The general approach
Stop using the affected storage as soon as practical, but don't assume there is a universal seconds-long countdown or keep booting the same system just to test recovery tools. 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.