How to prepare a reference video for MP4 repair

When a recording is interrupted, the file loses its moov atom — the index that tells a player how the video is laid out. A reference clip is a healthy recording from the same device and the same settings, used as a template to rebuild that index. Getting this right is the single biggest factor in whether a repair succeeds.

Why a reference clip is needed at all

Repairing a headless MP4 is not about "reading" the video — the video data is already there. It's about rebuilding the index. To rebuild it, the tool needs to know the exact parameters the original recording used:

• the codec and its profile
• the resolution and frame rate
• the timebase and how samples are grouped
• the audio track layout

A reference clip supplies all of that in a form that is already valid. Without one, the tool has to guess — and guessing works sometimes, but far less often.

What must match

The reference does not need to be the same length, the same content, or the same file size. It does need to match on these:

• Same device — ideally the same camera or the same phone. Different models, even from one brand, often use different encoder settings.
• Same resolution — 1080p reference for a 1080p file, 4K for 4K. A mismatch is one of the most common reasons a repair fails.
• Same frame rate — 30 fps for 30 fps, 60 for 60.
• Same recording mode — if the broken file came from a slow-motion, HDR, log, or high-bitrate mode, record the reference in that same mode.
• Same container family — MP4 for MP4, MOV for MOV.

How to record a good reference clip

Phone

• Open the same camera app you used for the damaged video.
• Set the same resolution and frame rate (check the app's settings — many default to 1080p30 while the broken clip might be 4K60).
• Record 3–5 seconds. A clip of anything will do.
• Stop it cleanly and let the app finish saving before closing it.

Action camera (GoPro, DJI Osmo, Insta360)

• Use the same preset/mode as the damaged recording — presets often differ in codec and bitrate even at the same resolution.
• If the broken file was shot in a high-bitrate or log mode, record the reference in that same mode.
• Record a few seconds, then stop the recording with the button rather than removing power.

Drone

• Match the video resolution and frame rate exactly as configured in the flight app.
• If the damaged clip came from a specific camera mode (wide, zoom, night), use the same mode.
• The drone does not need to fly — recording on the ground is fine.

OBS or desktop recorder

• Use the same Output settings: encoder, resolution, frame rate, and bitrate.
• If the broken file was MP4, record the reference as MP4 too (not MKV).
• Record for a few seconds and stop the recording normally so the reference is properly finalised.

Common mistakes that make a repair fail

• Using a reference from a different device. This is the most frequent cause of a failed attempt.
• Using an edited or trimmed reference. Editing software rewrites the container and changes the very parameters you need to match. Use a clip straight off the camera.
• Using a reference at a different resolution or frame rate — for example, a 1080p clip against a 4K damaged file.
• Using a reference that is itself damaged. It must be playable from start to finish.
• Recording the reference in a different mode (slow-mo, HDR, log) than the damaged file.

What if you can't get a reference clip?

It's still worth trying. The tool attempts to recover what it can directly from the damaged file, and that succeeds in some cases. But be realistic about the odds — the reference is what turns "sometimes" into "usually".

Situations where no reference is realistically possible include: the device is gone or broken, the card is unreadable, or the recording was made on equipment you no longer have access to. In those cases, run the repair without a reference and judge the result from the free preview before paying anything.

FAQ