Fix it now
- Drop the file
- Repair runs locally
- Download the result
Samsung Galaxy phones record video as .mp4 files in the ISO base-media container — the same family as MOV, indexed by a moov atom. Under Camera › Settings › Advanced recording options you can switch on "High efficiency video" (HEVC/H.265), which is required for the heaviest modes — 8K at 30fps on the S-series and Note/Ultra line, 4K at 60fps, and the 960fps Super Slow-mo burst — while the compatibility default stays H.264/AVC. Whichever codec you shot, the file only becomes playable once the index is written when recording stops cleanly. Interrupt that and Gallery, Google Photos, VLC and everything else refuse it. Drop the file above and the tool checks for exactly that, in your browser, and rebuilds the container when the footage is recoverable.
What's actually inside a Galaxy recording
Every Galaxy video is an ISO base-media file: a large mdat box holding the compressed picture and sound, and a moov atom that indexes it — the sample tables listing each frame's byte offset, size, timing, and the codec parameters a decoder needs. The mdat is streamed to internal storage (the DCIM/Camera folder, files named like 20240115_143022.mp4) as you film. The moov is different: the camera pipeline builds it in memory and flushes it only when you press stop and the recording is finalized.
The codec inside depends on your settings. With High efficiency video enabled the stream is HEVC/H.265, which is why 8K and 4K60 footage takes so little space for its resolution; with it off you get H.264/AVC for maximum compatibility with Windows, older TVs and social apps. Super Steady mode quietly switches to the ultrawide sensor, and Pro Video mode can record to higher bit-depths — but all of them still write the same moov-indexed MP4. That single design fact is why an interrupted recording behaves identically no matter which mode produced it: a full mdat of HEVC or H.264 with no index, which Gallery shows as a grey or broken thumbnail and every player opens to an error.
The moments that break the index
Galaxy clips corrupt at the one point where the moov should be written — the end of recording — and there are four common ways to never reach it:
Thermal shutdown during a long take. This is the signature Galaxy failure. 8K and 4K60 push the Snapdragon or Exynos hard, and after several minutes the phone shows the overheating warning and closes the camera to cool down. The take ends without being finalized: the frames captured up to that instant are on storage, the index that would have closed the file is not.
The battery died mid-record. A phone that powers off during capture never runs the stop routine, so the container is left open-ended in exactly the same way.
The Camera app crashed or was force-stopped. A crash, an app kill by Android's low-memory manager, or tapping away and having the OS reclaim the app while it records all end the take without writing the index.
Storage filled up while filming. HEVC 8K writes hundreds of megabytes per minute; when internal storage or the microSD hits zero free space, the write fails partway and the file is truncated.
Each of these leaves valid frames behind an incomplete index — the repairable case. What can't be recovered is footage from after the interruption: it was never written to storage.
Why a clip from the same Galaxy helps
When the index is gone, it's rebuilt by scanning the surviving stream and reconstructing the sample tables the phone would have written. A healthy clip from the same Galaxy, shot in the same mode, makes that far more reliable: it carries the exact codec configuration the broken file is missing — the HEVC parameter sets (VPS/SPS/PPS) for a High-efficiency clip, or the H.264 ones for a standard clip — so the rebuild reproduces the original resolution and frame rate rather than guessing them.
Practically: shoot a few throwaway seconds on the same phone with the same Camera settings — same resolution, same frame rate, same HEVC-or-H.264 choice — and keep it handy. Match the codec to the broken file, and you'll only be prompted for it if the repair actually needs it. Generic MP4 samples from a different device usually won't help, because the parameter sets differ.
What this can and can't fix
Can fix
- A clip left unfinalized when the phone overheated and shut the camera down mid-record (missing moov)
- Recordings cut off by a dead battery or a Camera-app crash before the index was written
- 8K/4K HEVC and standard H.264 .mp4 files truncated when internal storage or the microSD filled up
- Galaxy .mp4 files that won't open in Gallery, Google Photos, VLC or an editor despite holding real frames
Can't fix
- Footage from after the interruption — those frames were never written to storage
- A file that reads as 0 bytes or mostly zeros after a failed copy off the phone
- Secure Folder / DRM-protected content
- A broken HEVC clip with no matching HEVC reference available from the same phone
If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.