Recovering .insv files gives you a file that no ordinary player will display, and the first conclusion most people draw from that is wrong. The recovery is not the problem. An .insv file is pre-stitch spherical data — two fisheye streams, one per lens, written side by side in a single container — and there is nothing broken about it. It simply is not a finished video, and it will stay unviewable until it is stitched.
The practical rule: do not judge an Insta360 recovery by whether the file plays. Judge it by whether both lens streams are intact and whether the camera’s own software will accept them. Stitching is the second half of the job, and it is a normal step rather than a repair.
Why Recovered insv Files Will Not Play
A 360 camera records two wide fisheye views that together cover the sphere, plus the gyroscope and orientation data needed to project the result into an equirectangular frame. Stitching is the process that combines them, corrects the overlap, and produces the flat 360 video that viewers and editors recognize.
That stitching normally happens on export, not at capture. The camera writes the raw dual-fisheye data to the card, which is why the files are larger than the finished video and why the first frame of an .insv looks like two distorted circles or a heavily warped double image. Every playback application that is not Insta360-aware will either refuse the file, show a broken thumbnail, or display exactly that unstitched view.
This is the counterintuitive part of 360 recovery, and it is worth stating plainly: a file that shows two circles is not a corrupted file. It is a healthy raw file. Files that are genuinely damaged behave differently — they fail to open at all, report 0 bytes, or stop partway through stitching with a specific error.
How Insta360 Splits Footage Across Files
Insta360 writes its sphere data in one container per recording, with the two lens streams inside it. Depending on the model and mode, you may also see separate per-lens files, low-resolution proxy files for fast preview, and photo files alongside the video ones. The naming conventions vary by generation, but the structural logic does not: a complete recording is a matched set, and a broken set is missing one of its parts.
Three file types matter during recovery.
The .insv file is the recording itself and the one that carries the usable data. The .lrv file is a low-resolution proxy written alongside it, useful for quick preview and for confirming what a missing recording contained, but not a deliverable — it is also unstitched and roughly 480p. The .insp file is a still image in the same spherical format, and it goes through the same stitching step.
Because the two lens streams share a timestamp and a naming pattern, matching them up after a recovery is normally automatic. The case where it is not automatic is when only one stream was recovered, which changes what is possible rather than whether anything is possible.
What a Recovery Actually Returns
The table below maps the common outcomes to what they mean and what to do next.
| What you find | What it means | What to do |
|---|---|---|
| Both lens streams present, file will not play in a normal player | Expected; pre-stitch data is not a viewable format | Import into Insta360 Studio and export |
| Both streams present, stitching fails with an error | Structural damage to the container or one stream | Try the other lens order; re-export; if it still fails, the file is genuinely damaged |
| One lens stream present, the other missing | Half the sphere is lost | Export a flat single-lens video from the surviving stream |
| Files absent from the folder entirely | Deletion, format, or an interrupted write | Scan the raw card before writing anything else to it |
| Only a .lrv proxy present | Low-resolution unstitched preview | Use it to confirm content; recover the .insv for delivery |
| File size looks normal but duration shows 0:00 | Index atom missing, not payload loss | Repair the container index, then stitch |
The last two rows are where 360 recovery differs most from ordinary video recovery, and where the right sequence matters: fix the container first, then stitch. Attempting to stitch a file with no index will fail, and that failure says nothing about whether the footage is recoverable. The distinction is explained under missing video index repair.
Re-Stitching: From Raw Sphere Data to Finished Video
Insta360’s own desktop application, Insta360 Studio, is the reference tool for this step, and it accepts .insv files directly. The workflow is short.
- Copy the recovered files to a local working drive, in their own folder, and leave the card untouched.
- Launch Insta360 Studio and import the .insv files. The application groups the lens streams automatically if their names and timestamps match.
- Confirm the model setting. Studio sometimes needs the source camera model selected manually for recovered files, because the metadata that normally identifies the camera may be part of what was lost.
- Choose the export type. A 360 export produces an equirectangular video; a reframe export produces a conventional flat video following a chosen direction, which is often what a client actually wants.
- Check the stabilization and gyroscope-dependent options. If the gyro track was recovered, stabilization works normally. If it was not, the footage still stitches but loses the smooth horizon, and Studio may report that the metadata is absent.
- Export to a drive that is not the source card, and verify the result before deleting anything.
The stitching step is computationally heavy, so a 10-minute sphere recording can take substantially longer than real time to export, and the load scales with resolution and frame rate. A failed export is more often a resource problem than a file problem: close other applications, ensure the working drive has space for several times the source size, and retry before concluding the file is unrecoverable.
Where the recovered material has to be rebuilt across a set of related files rather than stitched from one, the sequence is covered in re-stitching 360 footage, and the platform-level picture, including how Insta360 cameras write and split data, is in Insta360 camera recovery.
When One Lens Stream Is Missing
If only one of the two streams survived, the sphere is incomplete, and no stitching tool can invent the missing half. That does not make the recording worthless, and it is where the single-lens fallback applies.
Studio can export a flat video from a single fisheye stream. The result is a wide-angle conventional clip rather than a 360 video: no sphere, no reframing after the fact, but real footage with usable resolution. For many purposes — confirming that an event was captured, delivering proof of a run, pulling a moment for a highlight — that is enough.
Two details make the difference between a usable fallback and wasted effort. The surviving stream must be selected explicitly, since Studio may not offer the flat option until the missing counterpart is deselected. And the exported frame will be heavily distorted near the edges, so cropping the central portion usually produces a cleaner result than trying to correct the whole image.
The loss of one stream is also diagnostic. If the two streams for one recording are written sequentially, an interruption during the second stream’s write leaves the first intact and the second missing or truncated — the signature of a power loss or battery pull mid-recording rather than of a card fault. Broader patterns of action-camera loss are collected under action camera data recovery.
Telling a Stitch Failure Apart From a Lost File
Confusing these two wastes more time than any other mistake in 360 recovery, because they look identical from the outside: an import that does not produce a video.
A lost file is a file that is not there. The folder shows fewer items than the shoot should have produced, the missing pair has no counterpart, and scanning the raw card is the correct response. A stitch failure is a file that is there but cannot be processed. The file exists at close to its expected size, Studio lists it, and the export fails or produces a result that is visibly wrong — misaligned seams, one hemisphere black, or a horizon that rolls uncontrollably.
The distinction matters because the responses are opposite. A lost file needs a scan of the card before anything writes to it. A stitch failure needs a different tool or a different setting, and running a scan changes nothing. If the file is present and listed, the problem is downstream of the data; if it is absent, the problem is upstream and the card is the place to look.
One further case deserves its own name: a file that stitches but shows a black or heavily distorted hemisphere usually means one lens stream was recovered only partially. The file is structurally valid, so no error is raised, but the second stream’s samples are incomplete. That is a recovery outcome rather than a tool problem, and the fallback above is the practical answer.
Verifying the Result
Verification for 360 output is a different checklist than for ordinary video, because several failure modes produce a file that plays.
Check the duration against the expected recording length, since a stitched export that is much shorter than the source usually means one stream ended early. Scrub the full sphere, not just the front view, and look at the seam where the two lenses overlap — misalignment there is the most common visible symptom of a partial stream recovery. Confirm audio, and confirm that any reframed deliverable still covers the direction the shot was planned around. A general checklist that applies to the stitched output as well is in verifying recovered video files.
If you are on Windows and the card is still detected by a computer, a purpose-built recovery tool such as XRecovery (xappset.com) can scan SD, microSD, and other memory cards for deleted or formatted photos and videos. As with any recovery tool, stop writing to the card first and always save recovered files to a different drive.
One expectation to hold on to: recovering an .insv file is only half the job, and the second half is a routine export. Files that reach Insta360 Studio intact will stitch. Files that do not are missing data, and no amount of re-exporting will add it back. The related case of a container that is broken rather than missing is covered in Insta360 video recovery.
Frequently Asked Questions
Why won’t my recovered insv file open?
Because pre-stitch files are not viewable video. An .insv file holds two fisheye streams that must be combined before a normal player can show anything, which is why a healthy recovered file looks like two distorted circles. Import it into Insta360 Studio and export to get a playable result.
Can I recover a 360 video if only one lens file survived?
Partially. The sphere cannot be rebuilt without both streams, so a 360 export is impossible. You can still export a flat video from the surviving fisheye stream, which gives a wide-angle conventional clip with no reframing options. That is often enough for review or proof purposes.
Does stitching a recovered file reduce quality?
Stitching is a projection step rather than a re-encode of the original capture, but the export does encode to a new file, so you should export at the highest quality setting available and keep the original .insv files as the archive copy. Never delete the raw files after a successful stitch.
How long does stitching take?
Longer than real time, and it scales with resolution and frame rate. A short 5.3K sphere clip can export in a few minutes on a capable machine, while longer recordings can take considerably more. If an export fails, check available disk space and system memory before assuming the file is damaged.