Skip to content

Using the web app

How rsv.repair loads files, runs the repair in your browser, and what each step means.

  • Your .rsv file: the interrupted recording that will not open in a normal player. It’s the only file you need.
  • A save location: the tool writes a fixed .mp4 (you choose the name and folder).
  • Chrome or another Chromium-based browser like Edge or Brave — on macOS, Windows, Linux, or ChromeOS — with File System Access so you can pick files and save output.

When you open rsv.repair, the repair engine loads in your browser. You may see “Getting ready…” for a moment while it prepares.

Use a recent version of Chrome or another Chromium-based browser like Edge or Brave so the tool can run as intended.

Your .rsv (01)
Drop in (or browse to) the .rsv file that does not play. The file picker is limited to .rsv so you don’t accidentally pick the wrong type. This is the only input — the tool reads everything it needs (codec, resolution, frame rate, audio layout, timecode) from the file itself.

Save as (02)
Choose where to save the output .mp4. The browser asks for a path; nothing is uploaded to a server.

Tap Fix video. Recovery is fully automatic — there’s nothing to configure.

The UI shows roughly where the job is:

  • Recovering your footage… Your .rsv is being read and the recovered video is written to disk.
  • Finishing up… The browser is flushing the last bytes to disk. Large files can take minutes here.

Expand Output log to see detailed messages — the detected codec, resolution, frame rate, camera model, start timecode, and frame counts.

You should see Done, a one-line summary (codec · resolution · fps · frames), and a short preview of the recovered video. The file is on disk at the path you chose.

There are no settings to tune: the recovery is fully automatic and derives everything it needs from the .rsv itself.

Try refreshing the page, then use an up-to-date version of Chrome or another Chromium-based browser like Edge or Brave.

When recovery can’t complete, the app shows what happened and what you can do next:

  • “Needs a reference clip.” A few .rsv files don’t carry the small piece of codec setup the tool normally reads from the file. To fix it, give the tool a reference clip: any clip that recorded correctly from the same camera with the same settings (a normal .mp4/.mov). The tool reads only the codec setup from it, then recovers your .rsv as usual. Your reference clip is processed in your browser too — it isn’t uploaded.
  • Other failures. Some files fail for reasons we haven’t seen yet.

In any of these cases you can opt in to share a small sample so we can add support for your file — see below.

Whenever a file can’t be recovered, you can choose to upload a small sample for analysis. This sends the first 64 MB of your .rsv (and, if you picked one, a slice of your reference clip) — that includes the opening few seconds of footage. It’s the only thing rsv.repair ever uploads, it happens only when you click the upload button, and you can leave an email if you’d like us to tell you when it’s supported. Details: Privacy & your files.

Processing is local in your browser: your .rsv and output are not sent to our servers as part of the repair flow. The only exception is the opt-in sample upload above, which never runs unless you choose it. See Privacy & your files.