Insta360 Corrupted Video — Recover the Recording

Insta360 cameras (the X5 (April 2025, the current 8K 360° flagship with replaceable lenses, $549.99), X4 (2024), X3, Ace Pro 2 (Oct 2024, 8K action), Ace Pro, GO Ultra (2026, the current compact-action flagship), GO 3S, GO 3, One RS, and the modular One R) record .insv, .mp4, and .lrv files. The mix is unusual: standard MP4 / HEVC for the playable preview, plus dual-lens-fish-eye source files (the .insv containers) that Insta360 Studio reads to produce the final 360 / reframed output. When something goes wrong with a recording, you can lose the standard MP4, the source .insv, or both.

This page covers all three.

What's actually in an Insta360 file

• .mp4: standard MP4 with H.264 or H.265 video. Plays in any player. Same MOOV-finalisation behaviour as any MP4.
• .insv: Insta360's container holding the dual-lens (front + rear fisheye) source data. Insta360 Studio reads this to do the 360 reframing. Container layout is MP4-like with proprietary metadata.
• .lrv: low-resolution preview, basically a small MP4. If broken, easy to ignore — Studio regenerates from the .insv source.

The MOOV-atom-not-finalised failure pattern applies to all three.

Why Insta360 files corrupt

• Battery exhaustion mid-record (especially the small GO models).
• microSD card pulled before recording stops.
• Physical impact / drop / dunk that interrupts the recording.
• Camera firmware crash (rare on current firmware; happens on older revisions).
• Sub-spec microSD card unable to sustain the dual-lens write rate (8K-equivalent for X4 needs a properly rated card).

What you should try first

1. Re-insert the card into the camera and let it boot. Insta360 firmware sometimes detects an incomplete recording and finalises it.
2. Insta360 Studio. Always test the file in Studio before paying for recovery. Studio is more permissive of partial .insv files than QuickTime is for .mp4.
3. Try the .lrv preview. If the .lrv plays, the camera was at least partway through writing the file — a good sign for recovery.
4. For standard .mp4 files: try VLC, then untrunc if you have a reference clip.

How our recovery handles Insta360 files

• .mp4 files: standard MP4 recovery path. H.264 / H.265 detection from frame markers, MOOV rebuild, audio recovery, co64 for files over 4 GB.
• .insv files: structural recovery. We rebuild the container index from frame markers, producing a file Insta360 Studio can mount. The proprietary metadata header is preserved when present; if it's been damaged, Studio may need the metadata reset manually before processing.
• No reference clip required for .mp4. For .insv, a healthy reference clip from the same camera improves outcomes — upload it alongside the broken file if possible.

What you do

1. Upload the file. Drag and drop. If you have multiple files (e.g. an .insv plus an .lrv), upload them together.
2. ~1 minute later you get a diagnostic + free 5-second preview where applicable.
3. Pay if it works. Adjust or escalate if not.

FAQ

Does this work on the X5 (April 2025), X4, X3, Ace Pro 2 (Oct 2024), Ace Pro, GO Ultra (2026), GO 3S, GO 3, One R, and One RS? Yes. All Insta360 cameras share the general container family, with codec/format variations we detect automatically. The X5's 8K 360° recording with replaceable lenses uses the same .insv container layout as the X4 — same recovery path. Ace Pro 2's Leica-tuned colour science and the GO Ultra's compact-action footage are preserved through structural recovery.

Will the recovered .insv work in Insta360 Studio? For structural recoveries (missing MOOV / index), yes. Studio mounts the rebuilt file and the 360 / reframe pipeline runs as normal. For deeper proprietary-metadata damage, sometimes we can recover the file enough to play but not enough for full Studio functionality. The diagnostic tells us which case.

Can you reframe a recovered file the way Insta360 Studio does? No, that's Studio's job. We hand back a file Studio understands; you reframe in Studio.

My X4 recording was 8K 30p — does that affect recovery? Resolution and frame rate are detected from the codec parameters. We have no fixed list of supported configs.

What about the Insta360 Pro / Pro 2 (the older 6-lens 8K rig)? Different file format (multiple synchronised streams). Recovery is harder and more case-specific. Upload and we'll diagnose; honest expectations.

Is my footage safe? Server in France, auto-deleted after 48 hours, never used to train anything or shared. Privacy policy.

Related

• DJI Osmo Action 4 corrupted
• GoPro Hero 12 truncated file
• How our recovery engine works

Upload your Insta360 file →