ShareX screen recording corrupted or won't play? How to recover it

By the FixMP4 engineering team · · 7 min read

ShareX records your screen by launching FFmpeg in the background and telling it to stop when you end the recording. If FFmpeg is stopped any other way, by a crash, a forced shutdown, a power cut or killing the process, the MP4 it was writing is left without its index and will not open. That is the most common reason a ShareX recording is "corrupted", and it is usually recoverable. This article explains how ShareX produces its videos, where to find them, how to recover a broken one, and how to set things up so long recordings are safe.

How ShareX records video

When you choose Screen recording, ShareX builds an FFmpeg command from your settings (capture source, video codec, audio device, frame rate) and runs it. FFmpeg writes video frames and audio into an MP4 as they come in. When you press Stop, ShareX asks FFmpeg to finish cleanly, and FFmpeg writes the moov index at the end of the file. Only then is the MP4 playable.

The GIF option works similarly: ShareX first records a video, then converts it to GIF. If the recording stage fails, the GIF step has nothing to work from.

Where to look for the file

  1. Open ShareX and go to History (or Image history); recent captures are listed with their paths.
  2. Check the default capture folder: Documents\ShareX\Screenshots, inside a folder for the current month.
  3. If you changed the location, look under Application settings, Paths.
  4. If you use an upload destination, check whether the upload failed: the local file is usually still there even if the upload did not finish.

Copy the file somewhere safe before trying to open or fix it.

Diagnose the failure

What you seeLikely cause
File missing or 0 KBFFmpeg never started or failed instantly
Large file, won't open, shows no durationRecording interrupted before FFmpeg finished
Plays but ends earlyThe capture or encoder stopped while ShareX kept running
Plays with frozen or green framesHardware encoder or driver problem during capture
Plays but no soundAudio source missing or wrong device selected

The second row is the one this guide focuses on, since it is the one where the footage exists but cannot be played.

Recover an interrupted ShareX MP4

The broken file contains all the frames and audio recorded up to the interruption. What is missing is the index that tells a player where they are and how to decode them. Rebuilding it takes two files:

  1. The damaged recording, unmodified.
  2. A short reference recording: open ShareX on the same PC, with the same screen recording settings (same codec, same capture area or a similar one, same frame rate and audio source), record ten seconds and stop it normally.

Open the FixMP4 repair tool, add the damaged file and the reference. The repair runs in your browser, so a long recording of your screen never leaves your computer, which matters when it contains private work, chats or passwords. FixMP4 supports H.264 and HEVC video with AAC audio, which covers ShareX's x264 and x265 options and the hardware H.264/HEVC encoders. It shows a free preview of the recovered video before you pay for the full export.

If you prefer the command line, untrunc is the classic open-source tool for the same job; see our untrunc online alternative guide for how the two approaches compare.

When the recording plays but ends early

If the file opens but stops before the point where you pressed Stop, the capture itself stalled. Common reasons:

  • Hardware encoder errors: GPU encoders can fail after driver updates, when switching displays, or when a game takes exclusive control of the GPU. Try the software x264 encoder to compare.
  • Disk full: FFmpeg stops writing when the drive fills up. Check free space on the drive holding the Screenshots folder.
  • Display changes: unplugging a monitor or changing resolution mid-recording can end the capture.

Nothing after the stall was recorded, so repair cannot add it, but the part before it is fine.

Fix FFmpeg problems before the next recording

ShareX depends on FFmpeg being present and compatible:

  • In the screen recording options, ShareX can download FFmpeg for you or point to an existing ffmpeg.exe. Make sure the path is valid.
  • After updating ShareX or FFmpeg, run a short test recording before a long one.
  • If ShareX shows an FFmpeg error dialog, the text includes FFmpeg's own error message. Searching that exact line usually points to the cause, such as a missing audio device or an encoder your GPU does not support.

Make long ShareX recordings safer

  • Stop recordings with the hotkey or the tray menu, never by closing ShareX or ending the process.
  • Keep the PC from sleeping during a long recording; sleep often terminates FFmpeg abruptly.
  • Record important sessions in shorter segments so an interruption costs minutes rather than an hour.
  • Prefer a dedicated recorder for very long sessions: tools like OBS can record to MKV or fragmented MP4, which survive crashes, and remux to MP4 afterwards. Our article on fragmented MP4 explains why that format is crash-safe.

For other Windows screen recorders, see Xbox Game Bar recordings, Bandicam recordings and OBS recordings.

Recording with Loom instead? Loom recording failed to upload or won't play explains where those recordings live while they upload.

Frequently asked questions

Where does ShareX save screen recordings?

By default ShareX stores captures in its Screenshots folder inside Documents\ShareX, organised into monthly subfolders. You can check or change this under Application settings, Paths, and the After capture tasks decide whether the file is also uploaded or copied.

Why is my ShareX recording 0 KB or very small?

If FFmpeg could not start (wrong capture device, unsupported encoder, missing FFmpeg), nothing was written. A tiny file means recording never really began, so there is nothing to repair. Check the FFmpeg output in ShareX's recording options to see the error.

Can I recover a recording if ShareX crashed?

Often, yes. ShareX records through FFmpeg, and an MP4 that FFmpeg could not finish has its frames but no index. Rebuilding the index with a short healthy recording made with the same settings usually restores the video up to the point of the crash.

Does ShareX have a crash-safe recording format?

ShareX lets you choose different codecs and FFmpeg options. A crash-safe container is not the default, so the most reliable protection is to stop recordings properly, keep FFmpeg up to date, and test your settings with a short clip first.

Have a broken recording right now?

Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.

Open the repair tool
  • ShareX
  • screen recording
  • FFmpeg
  • Windows
  • MP4