Local-first processing
Repairs run in your browser with WebAssembly, so the video itself does not need to be uploaded to a repair server.
How It Works / Trust
Understand how VideoRepair works before you trust it with a broken file
VideoRepair is built for MP4, MOV, AVI, and related files that fail because the playback structure is broken, not because the footage needs a full re-encode. This page explains what the tool actually does, where it works best, and where the limits are.
Structure-aware repair
The workflow targets container metadata and playback structure before resorting to blunt conversion or re-encoding.
Reference-assisted recovery
If a file lost critical codec details, you can add a healthy clip from the same device and settings to improve reconstruction.
How the repair flow works
1. Inspect the file container
VideoRepair checks whether the container still has a usable index, valid offsets, and enough metadata to map the audio and video streams.
2. Repair or rebuild missing metadata
If the moov atom, sample tables, or AVI playback index are damaged, the engine repairs offsets or reconstructs the playback structure needed for seeking and timeline recovery.
3. Use a reference file when needed
For severe corruption, a healthy clip from the same phone, dashcam, or action camera can supply matching codec settings and timing details.
4. Preview before you commit
You can inspect the repaired result in-browser first, then decide whether to export once playback, duration, and seeking look right.
What it is built for
- Interrupted recordings from phones, GoPro cameras, dashcams, and screen recorders
- Supported containers such as MP4, MOV, AVI, M4V, M4A, 3GP, and compatible 3G2
- Files that still have believable size but fail to play, seek, or report correct duration
- Cases where audio or video payload still exists but the container metadata or playback index is damaged
Current limits
- A true 0-byte file cannot be repaired because no media data was ever written
- If the video payload itself is physically missing, repair may only be partial
- MP4, MOV, M4V, M4A, 3GP, and 3G2 repair works best with H.264 video and AAC audio
- AVI repair currently focuses on classic AVI files rather than every OpenDML variant
- The in-browser workspace is designed for files up to 4GB per upload
Why the workflow is trustworthy
- The repair workflow is explicit about what it can and cannot fix
- The product lets you preview results before you decide to pay for export
- Support and contact paths are visible through the Help and Contact pages
- Brand and legal pages are published under Magic Leopard / MagicCat Technology Limited
Brand, support, and policies
VideoRepair is published under Magic Leopard by MagicCat Technology Limited. If you need more detail before using the workflow, you can review the Help, Privacy, Terms, and Contact pages directly from the product site.
Ready to test a damaged file?
If you already know the file is damaged, jump into the repair workspace. If you are still diagnosing the problem, the troubleshooting guides are the better next step.
Frequently Asked Questions
The repair process is designed to run locally in your browser with WebAssembly. That means the video file does not need to be uploaded to a remote repair queue for the core repair workflow.
It works best on files with damaged or missing container metadata, such as interrupted recordings, broken chunk offsets, missing moov atoms, and classic AVI index damage.
Use a reference file when the damaged clip came from the same device and settings as another healthy clip. That extra file can provide codec and timing details needed for more severe recovery cases.
No. A 0-byte file or a file with missing media payload cannot be fully restored. The best results come from files where the media data still exists and the main problem is broken metadata or container structure.
The trust model is based on local browser processing, visible legal and support pages, transparent file format limits, and the ability to preview the repaired result before export.