Repair a corrupted Insta360 X4 .insv file

An .insv is a standard MP4 container underneath, so it obeys the same rule as any MP4: the index — the moov atom that maps every frame and describes the H.265 streams — is written only when the recording is finalized. Cut power to the X4 before that and you're left with a container full of real footage and no index. Insta360 Studio then reports that it can't recognise or import the media.

On a 360 action cam the interruption is usually one of these:

• The battery dies or is swapped while recording is still running.
• The card is pulled before the camera finished closing the file.
• An impact or a hot-shutdown ends an 8K recording early — the highest-bitrate mode is the most fragile.

One X4-specific wrinkle: because 5.7K+ footage keeps both fisheye tracks inside one main .insv, a single unfinalized file is the whole recording. Studio also expects the sidecars alongside it — the low-res .lrv proxy in particular — so don't rename or move the files; keep the set together in one folder.

The rebuild scans the surviving H.265 data in the .insv and reconstructs the sample tables and index the camera never wrote, producing a container that opens again. That's the part standard players and repair tools choke on. It is not a stitch: the file still holds dual-fisheye raw, so once it opens you take it back into Insta360 Studio to stitch, reframe, and export the flat video you actually share. Think of it as getting the door open — the editing room behind it is still Studio's.

Because the streams are H.265 with the X4's particular 360 layout, a healthy .insv from the same X4 in the same shooting mode (same resolution, same encoding) is the best possible reference: it carries the exact stream configuration the broken file is missing, which is the same principle Insta360's own File Repair tool uses when it asks for a reference from the same camera and settings. Grab any normal clip shot in the same mode and keep it ready — you'll be asked for it only if the file needs it.

360 capture is uniquely exposing — it records everything around the camera, in every direction, so a single .insv can hold far more of a place and the people in it than a framed shot ever would. X4 files are also large: 8K H.265 runs to gigabytes per clip, making an upload slow as well as revealing. Upload-based repair sites take a full copy onto servers you can't inspect, under terms you didn't write.

Here the container rebuild runs entirely in your browser: the .insv is read from your disk, rebuilt in the tab, and saved back. Nothing is transmitted, and you can verify it — open the Network tab and watch 0 bytes leave your machine. Then you finish the job locally in Insta360 Studio, so the footage never leaves your control at any stage.