Repair a Zoom local recording

A Zoom local recording lives in two stages: a proprietary in-progress file that Zoom turns into an MP4 when the meeting ends. Understanding which stage yours is stuck at tells you exactly what can be recovered — and where an in-browser MP4 rebuild fits in.

Your file never leaves your device — repair runs in your browser. 0 bytes uploaded.

Your data is the big block — usually intact. What breaks is the small index. Repair rebuilds it.

Drop a file here or browseTap to choose a file

ZIP · Office · PDF · video · JPG · PNG · RAR/7z · SQLite — repaired right here in your browser. Nothing is uploaded

0 bytes uploadedFree: 3 repairs/day — up to 500 MB video, 100 MB docs & archives, 50 MB photos. Free download. Single repair €5.90. No account required.

Fix it now

  1. Drop the file
  2. Repair runs locally
  3. Download the result

When you record a Zoom meeting to this computer, Zoom doesn't write an MP4 in real time. It streams to proprietary intermediate files in a per-meeting folder under your Documents/Zoom directory — typically named double_click_to_convert_*.zoom for video plus separate audio — and only converts them into a finished zoom_0.mp4 (H.264 video, AAC audio) when the meeting ends cleanly. A crash, force-quit, or a full disk before that step leaves you stuck. This page explains the two failure points and where a browser-based MP4 rebuild helps: after Zoom's own converter has produced an MP4 that itself won't play.

The two stages — and which tool owns each

Stage one: the raw .zoom file. This is Zoom's own proprietary intermediate format, not an MP4. The only software that can read and convert it is Zoom itself — so if you still have double_click_to_convert_*.zoom files, your first and best move is Zoom's built-in converter: open the desktop client, go to Meetings → Recorded, and choose Convert. (A widely reported trick when it stalls: copy only the .zoom files into an empty folder and convert from there.) We are honest about this: an in-browser tool cannot decode Zoom's undocumented .zoom container — that is not one of the formats our engines rebuild.

Stage two: the MP4. Once Zoom's converter runs, it outputs a standard MP4. If that conversion was interrupted — Zoom crashed mid-convert, the disk filled, or the machine shut down — the MP4 it left behind can be unfinalized: valid H.264 frames with no moov index. That is a normal broken-MP4 problem, and it is exactly what an in-browser rebuild fixes.

When the converted MP4 won't play

A finished Zoom MP4 is an ordinary ISO base-media file: the audio and video payload (mdat) followed by the moov index that maps every frame. If Zoom's conversion was cut short, the moov may be missing or truncated — the player then reports the MP4 as corrupt, zero-length, or refuses to open it. Drop that MP4 above and the tool scans the surviving frames and rebuilds the sample tables Zoom would have written, reconstructing a playable container.

For a faithful rebuild it helps to have a healthy Zoom MP4 from the same client version — for example, a good recording from another meeting — because it carries the exact codec configuration the broken file is missing. You'll only be asked for one if the file needs it. What we cannot do is finish a conversion Zoom never completed at the .zoom stage; run Zoom's converter first, and bring us the MP4 when the MP4 is the thing that's broken.

What this can and can't fix

Can fix

  • A converted Zoom MP4 left unfinalized because the conversion crashed or the disk filled (missing/truncated moov)
  • A zoom_0.mp4 that copied off the machine but won't play in any player
  • Container damage in a Zoom MP4: broken index, wrong offsets, zero duration
  • Zoom MP4s a recovery tool returned unplayable, when the H.264/AAC data survived

Can't fix

  • The proprietary .zoom intermediate file itself — only Zoom's own converter can read that format
  • A recording where the .zoom data was truncated by the crash before enough was written
  • Cloud recordings held on Zoom's servers (this is for local recordings on your disk)
  • Files that read as 0 bytes or mostly zeros

If a repair fails, we tell you why (missing data versus broken structure), and you are never charged for a failed repair.

FAQ

Zoom crashed and I only have double_click_to_convert files. Can you convert them?

No tool but Zoom can read the proprietary .zoom format. Run Zoom's own converter first (Meetings → Recorded → Convert; a common fix is to move only the .zoom files into an empty folder). If that produces an MP4 that then won't play, bring the MP4 here.

Zoom converted the recording but the MP4 won't open — now what?

That's the case we handle. An interrupted conversion can leave an MP4 with valid frames but no moov index. Drop it above and the tool rebuilds the container so the file plays again.

Does a healthy Zoom recording help the repair?

It can. If the index can't be rebuilt from the broken file alone, a good MP4 from the same Zoom client version supplies the exact codec settings for a faithful rebuild. You'll only be prompted if it's needed.

Is my meeting recording uploaded to fix it?

No. The MP4 is read from your disk and rebuilt in your browser tab; nothing is transmitted. You can confirm 0 bytes leave your machine in the Network tab — useful for meetings that may be confidential.

Related: Repair MP4 (any source) · Repair an OBS recording · "moov atom not found"