Sony .RSV and .MP4 files that never finished writing.
One step before it starts: your email. I'll use it to tell you before early access ends and pricing begins, and to follow up about this recovery — checking it worked, or letting you know if I fix something that affects your file. Nothing else unless you tick the box. Details on the privacy page.
That doesn't look like an email address.
Add one normal clip from the same camera, shot with the same settings. It doesn’t need to be long — a few seconds is enough, and it isn’t uploaded either.
One payment for this file. You get a key by email, paste it here, and the recovery runs on your machine — straight to the drive you pick.
It worked? One line for people with the same problem — totally optional.
Thanks — you can see what others said on the reviews page.
If you’re on this page, I probably know exactly how you feel right now. I’ve had that feeling too. So I built this. I hope it helps.
I work as a DIT. A while back a PTZ camera on an observational show ran for eight hours straight and then just stopped writing. 191 GB sitting on the card and not one player would open it. The paid repair tools I tried either refused the file outright or handed back something where the audio had drifted a minute out of sync by the end. On a two-minute clip you’d never notice. On an eight-hour take it’s useless.
So I spent a day taking the file apart by hand. It turns out nothing was ever lost. Sony cameras write the clip index at the very end of a take — pull the power and every single frame is still sitting on the card, with nothing left to tell a player where they are. Rebuild that index and you get the whole take back, bit for bit, no re-encoding.
That’s all this page does. It runs entirely in your browser — your file never goes anywhere — so a 200 GB recovery takes about as long as copying the file would.
.RSV / .MP4FX30 · FX3 · FX6 · a7S III · a7 IV · a6700 · BRC-AM7 · AX / CX / PXW · full recovery.RSV / .MP4H.265 4K 10-bit · FX30 etc. · full recovery.mdtLUMIX GH5S etc. · full recovery · needs one normal clip from the same camera4:2:2 10-bit and 4-channel 24-bit audio are handled, and length isn’t a problem — multi-hour, hundred-gigabyte takes come out frame-accurate.
Layout is measured from the file rather than hard-coded — for Sony no reference clip is needed at all; everything the rebuild requires is already inside the recording.
These aren’t supported yet, but they’re what I’m working on. Drop your file anyway — it takes a second to find out and costs nothing. If it’s one I can’t handle yet, the first 50 MB is usually enough for me to work out the structure, so send it over and I’ll add it.
Not sure how to cut the first 50 MB? Do it here in one click →
Sony interleaves the card in a fixed cycle: a block of timed metadata, then fifteen video frames, then a block of uncompressed audio, over and over. The metadata block starts with an SMPTE key and the video frames carry their own length prefixes, so the whole file can be walked without guessing where anything begins.
That’s the part most tools get wrong on long recordings. If you estimate frame boundaries instead of reading them, the error accumulates and the audio slides. The codec parameters are tucked inside that metadata block too, which is why no reference clip is needed.
A day of unattended camera can be a couple of hundred gigabytes. Sending that anywhere would take longer than the shoot did, and broadcast material has no business sitting on a stranger’s server. So the work happens where the file already is. Close the tab and nothing remains.
Questions, a file that won’t go through, or you just want to tell me it worked — brian@footage.repair