iPhone ProRes recovery begins with a single question most guides skip: did the file land in the phone’s internal storage, or on an external SSD connected over USB-C? The answer determines what is possible, and the two outcomes are far apart. Internal storage is hardware-encrypted with keys held in the device’s secure element, so recovery depends on the phone still powering on. An external SSD is easier to reach but often harder to recover from than an SD card.
Check one thing before either path: the Photos app’s Recently Deleted album, which holds deleted media for 30 days. A surprising share of “lost” clips are queued for deletion and restore with two taps.
Where Phone Camera Media Actually Lives
The boundary between a camera and a phone has largely dissolved, and storage is where that shows.
Apple logs ProRes 422 HQ into the same DCIM tree that stills use, as .MOV files with 10-bit 4:2:2 sampling. The bitrate is serious: roughly 220 Mbps at 1080p30 and around 880 Mbps at 4K30, which is about 110 MB/s and 6.6 GB per minute at the higher setting. On devices with 128 GB of storage, 4K ProRes requires recording to an external drive; higher-capacity models can write internally but fill fast. Apple Log clips follow the same path — a log tone curve inside a ProRes MOV, with the same recovery profile as any other ProRes file.
Android covers similar ground differently. Most flagship cameras offer a RAW+ mode that writes a DNG and a JPEG with a shared base name, plus HEIF stills and 10-bit video. Some camera apps now record directly to a USB-C SSD, which turns a phone into a recorder with a tethered drive.
| Workflow | Where the file lives | Typical failure | Recovery outlook |
|---|---|---|---|
| ProRes 422 HQ to internal storage | Phone NAND, hardware-encrypted | Clip missing after an app crash or a full-storage stop | Good while the phone boots; keys are held by the device |
| ProRes or HEVC to a USB-C SSD | External SSD, often exFAT | Cable pulled mid-take; SSD unplugged before the write finished | Strong if the index is missing; weak if blocks were trimmed |
| Direct-to-SSD recording app | External SSD | App terminated; drive unmounted uncleanly | Depends on whether the drive was ever mounted read-write afterward |
| HEIF stills, internal | Phone NAND | Photos vanished after a sync or storage error | Recoverable while the device works, and often recoverable from iCloud |
| Android RAW+ (DNG + JPEG) | Internal or SD card | One half of the pair recovered, the other missing | High — the DNG and JPEG are separate files |
| Field offload through a USB-C reader | SD card or SSD | Interrupted copy reported as complete | Re-run the copy; the source is usually intact |
The Counterintuitive Part: An SSD Is Worse Than a Card
Conventional advice says solid-state storage is more reliable than removable flash. That is true for hardware failure and false for recoverability, and the reason is one command.
SD and microSD cards have no TRIM support. When you delete a file from a camera card, the file system simply marks those clusters as available; the underlying flash cells keep their charge until the controller needs the space. That is the entire reason deleted photos can be recovered from a card at all. An SSD in the same workflow behaves differently. Modern SSDs implement TRIM, and once the operating system tells the drive that a block is no longer in use, the controller is free to erase and unmap it immediately. On some drives this happens within seconds. Recovering deleted files from a trimmed SSD is often impossible, not because the data was overwritten with new information, but because the drive was instructed to discard it.
Three practical consequences follow for anyone recording to a USB-C SSD:
Never mount a problem SSD on a desktop OS before you image it. Windows, macOS, and Android all issue filesystem housekeeping when they mount a volume, and that housekeeping can include TRIM. A write blocker or a Linux live environment with automount disabled is the safer path.
A missing index is a different problem from a deleted file. If a take was interrupted — cable pulled, battery drained, app crashed — the file may exist with no completed index. That is a container problem, repaired by rebuilding the index rather than a deleted-data problem, and TRIM never came into play. The external SSD and professional media recovery guide covers both cases for CFexpress and tethered drives.
Self-encrypting drives add a second wall. Many portable SSDs ship with hardware encryption enabled by default, sometimes with the key derived from a software companion. A drive whose encryption layer is active cannot be read by a generic recovery tool even when its blocks are intact.
HEIF, ProRAW, and the Still Side of the Same Problem
Phone stills have their own containers, and the terminology gets muddled quickly.
HEIF is a container, and on an iPhone the payload is almost always HEVC-encoded at 10 bits. Familiar extensions include .heic. The format compresses well, which is why it is the default, and it is also why a partially recovered HEIC can look far worse than a partially recovered JPEG — the codec has fewer code values to work with when a slice is missing. If a recovered .heic refuses to open on Windows, that is usually a decoder problem rather than a data problem, and is covered in the HEIC repair guide.
Apple’s ProRAW is a DNG file with an additional gain map and computational metadata. Android’s RAW+ mode writes a plain DNG next to a JPEG. In both cases the two files are independent, so a recovery that returns the JPEG but not the DNG — or the reverse — is telling you about cluster adjacency, not about a coded pairing. Re-scan and look for the missing half by file name rather than by size. The comparison of RAW, JPEG, and HEIF containers explains what each format stores internally and why recovery success rates differ between them.
The First Fifteen Minutes With a Phone-First Workflow
The steps are short and the order matters.
- Stop recording and put the phone down. Do not delete anything to free space, and do not let a second app write over the storage that held the clip. Freeing space is the single most destructive action available.
- Check Recently Deleted and any cloud trash. Photos, Files, and third-party editing apps each keep their own recently-deleted area. This costs a minute and resolves a real percentage of cases.
- Turn off syncing before it propagates. If the loss was caused by a sync conflict, letting iCloud or Google Photos reconcile again can overwrite the local copy. Take the device offline.
- For an external SSD, eject properly and then leave it alone. Do not reformat, do not run a “repair” utility, and do not let a desktop OS mount it read-write more than necessary.
- Image the storage before scanning. For a card, a byte-level image is standard practice. For a USB-C SSD, image it from a write-blocked or read-only connection if you have one.
- Recover to a different drive. Never write recovered files back to the source.
Why Internal-Storage Recovery Depends on the Device Itself
Apple’s data protection architecture encrypts stored files with keys managed by the device’s secure element, and those keys are bound to that specific hardware. This produces a clean dividing line:
- The phone powers on and mounts. Internal-storage recovery is realistic. Files can be scanned through a recovery tool or recovered from a backup, and the encryption layer is transparent because the device itself can unlock it.
- The phone does not power on, and the logic board is dead. The keys are gone with the hardware. No software, and no laboratory, can decrypt the volume without them. This is a case where the honest answer is that the data is unrecoverable, and where a backup or an iCloud copy is the only remaining route.
The same principle applies to Android devices with file-based encryption, and to the increasing number of hybrid and cinema cameras that encrypt their internal storage. The camera internal storage recovery overview and the guide to recovering files from camera internal memory cover the general mechanics of working with non-removable storage.
If you are on Windows and the card or drive is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, CFexpress, and external drives for deleted or formatted photos and videos. As with any recovery tool, stop writing to the media first and always save recovered files to a different drive.
Verifying Phone Footage Before It Reaches the Timeline
Phone-origin ProRes has three properties worth checking every time, because they fail quietly rather than loudly.
Confirm the duration against the take length. ProRes clips are long-GOP-free, so a recovered clip whose duration matches is almost certainly complete in frame count as well. Check that the audio track exists — many direct-to-SSD apps write audio into a separate stream, and a recovery that grabs only the video leaves a silent clip. Finally, open the file in a grading application before delivery, because ProRes is frequently recorded in a log or wide-gamut profile whose appearance in a consumer player is not evidence of correctness. The verification routine for recovered files walks through the checks in the right order.
Frequently Asked Questions
Can deleted ProRes clips be recovered from an iPhone’s internal storage?
Often yes, if the phone still powers on and the storage has not been reused. The device can unlock its own encryption, which makes the files readable. If the phone is dead, the encryption keys are tied to that hardware and the data cannot be recovered by any method.
Why is a USB-C SSD harder to recover from than an SD card?
Because SSDs support TRIM. Deleting a file instructs the drive to discard those blocks, and the controller may erase them within seconds. Camera cards do not support TRIM, so deleted files stay intact until they are physically overwritten.
My clip disappeared after the app crashed. Is it gone?
Usually not. An app crash or a pulled cable typically interrupts the index write rather than destroying video samples, leaving a file that is complete in size but will not open. Rebuilding the container index restores playback of everything that reached the drive.
Should I keep shooting ProRes on the phone at all?
If the workflow fits, yes — with external recording for 4K and a copy made before the original is deleted. ProRes 422 HQ is far more resilient per frame than a long-GOP delivery codec, and it holds up well to recovery. The exposure is operational: fast fills, tethered drives, and syncing that runs before you have verified the originals.