Your Screen Recording Won't Play: How to Fix Unplayable Video Files

A screen recording that won't open, shows no picture, or gets rejected on upload. Diagnose which failure you have and get a file that plays anywhere.

You finished the recording, exported it, sent it to a colleague — and it won’t open. Maybe the player shows an error. Maybe it opens to a black rectangle with a timeline that never moves. Maybe the upload form rejects it before you even find out whether it plays.

“Won’t play” is not one problem. It’s at least six, and each has a different fix. The fastest way through is to identify which failure you’re actually looking at before you start re-exporting things at random.

Start With the Symptom, Not the Fix

Match what you see to the likely cause before you touch anything:

What you seeMost likely cause
File is 0 KB, or far smaller than expectedExport was interrupted
”Unsupported format” / “codec not found”Player lacks the codec, or the extension is wrong
Audio plays, picture is blackDecoder or GPU driver problem on the playback machine
Picture plays, no audio at allNo audio track was recorded, or the file is a GIF
Plays locally, rejected on uploadFile size or resolution limit on the destination
Plays, but stutters or runs in slow motionPlayback hardware can’t keep up with the resolution

The rest of this guide works through those in order of how often they turn out to be the real cause.

1. The Export Never Finished

This is the most common cause and the least suspected one, because the file exists. A file existing is not the same as a file being complete.

An MP4 needs its index written at the end of the export. If the app quit, the machine slept, or you closed the window while the progress bar was still moving, you get a file with video data inside but no usable index — and most players refuse it outright.

How to confirm: check the file size. A one-minute 1080p export is typically in the tens of megabytes. If you see 0 KB, or a few hundred kilobytes for a long recording, the export didn’t complete.

The fix: export again and let it run to the end. Don’t put the machine to sleep mid-export, and don’t close the editor window until the export reports completion.

In Recorded, the export panel shows separate stages — encoding, muxing, and (for GIF) a palette pass. Every one of those stages must finish. If your machine tends to sleep during long jobs, export in shorter pieces, or see why video exports take so long for ways to shorten the window where it can go wrong.

2. The Player Doesn’t Support the Codec

A .mp4 extension says almost nothing about what’s inside. MP4 is a container; the video and audio inside it are encoded separately, and a player that can open one MP4 can choke on another.

Recorded exports MP4 as H.264 video with AAC audio. That combination is about as widely supported as video gets: browsers, phones, smart TVs, Slack, Google Drive previews, presentation software, and every mainstream editor read it. The GIF export is the other option — it plays anywhere images do, but it has no audio track at all and gets large quickly.

So if a file exported from Recorded won’t decode somewhere, the codec is rarely the real problem. Check these instead:

  • Open it in a second player. VLC and mpv carry their own decoders and ignore the operating system’s codec list. If the file plays in VLC but not in your default player, the file is fine and the player is the problem.
  • Check the actual extension. Renaming a .gif to .mp4 does not convert it, and the reverse is just as broken. Make sure the file name matches what you actually exported.
  • Update the player. Very old media players on Windows, and some TV or set-top firmware, predate hardware H.264 decoding for high-resolution profiles.

If the file came from somewhere else — a conference room recorder, a phone, a different capture tool — then the codec genuinely could be exotic (HEVC, VP9, ProRes). In that case the fix is to re-encode it with a general-purpose converter before sharing. Recorded exports MP4 and GIF only; it isn’t a format converter for other people’s files.

3. The Resolution Is Higher Than the Playback Device Can Handle

A 4K file can be perfectly valid and still be unwatchable on an old laptop, a budget tablet, or a meeting-room display. What you see looks like a broken file: the first frame appears, then it freezes, or it plays at a crawl with the audio running ahead.

This is a decoding budget problem, not a corruption problem. The giveaway is that the same file plays fine on a newer machine.

The fix: re-export smaller. In Recorded’s export panel, MP4 offers 720p, 1080p, 1440p, 4K, Original, and Retina. Original is the recording’s logical resolution; Retina multiplies that by the capture scale factor to match physical pixels on a high-density display. Both of those can land well above 4K if you recorded a large Retina screen.

1080p is the right default for anything you’re sending to someone else. It’s the resolution every device decodes comfortably, and for screen content — text, UI, flat colors — the visual difference against 4K is far smaller than it is for camera footage. Reach for 1440p or 4K only when fine text has to stay legible on a large display.

There’s also a hard ceiling worth knowing about: the exporter caps output at 4096 pixels per side and roughly 8.9 megapixels total, and scales anything larger down proportionally. So an export from a very large Retina display won’t match the raw pixel dimensions of the screen you captured. If text looks softer than you expected after that downscale, why your screen recording looks blurry covers how to recover sharpness.

4. The Upload Was Rejected, Not the File

If the failure happens in a browser upload form, a chat client, or an email client, the file is probably fine. Destinations impose their own limits — on size, sometimes on duration, occasionally on resolution — and the error messages rarely say which one you hit.

Three things to try, in order:

  1. Re-export at a lower resolution. Dropping 4K to 1080p cuts pixel count by about three quarters, and file size follows.
  2. Turn on the compress option. Recorded’s export panel has a “Compress Video” toggle for MP4 that runs the finished file through a second hardware-encoder pass — VideoToolbox on macOS, Media Foundation on Windows — while copying the audio track through untouched. It costs extra export time and buys a noticeably smaller file.
  3. Trim harder. The cheapest megabytes are the seconds you cut. Most screen recordings have a slow start and a trailing few seconds that nobody needs.

For a systematic pass at this, see reducing screen recording file size.

If you exported a GIF and the upload failed on size, that’s expected behavior rather than a bug. GIF stores every frame as a palette-quantized image with no inter-frame video compression, so size grows roughly with pixel count and duration. That’s why Recorded limits GIF to 480p, 720p, Original, and Retina, offers 10, 15, and 24 fps, and warns you when a GIF export runs past 30 seconds. For anything longer than a short loop, MP4 at 1080p will be smaller and better looking.

5. The Picture Plays but There’s No Sound

Work backwards from the file to the recording:

  • Is it a GIF? Then there is no audio, and there never was. GIF has no audio track. Re-export as MP4.
  • Was a microphone or system audio enabled when you recorded? If neither source was on during capture, the export has nothing to mux and will be silent no matter how you export it.
  • Is the player muted, or is the output device wrong? Trivially common, worth ten seconds of checking before you re-export anything.
  • Does it have sound in a different player? Some players default to the first audio track or mishandle multi-track files.

If the audio exists but is unusable — one source drowning out the other — that’s a mixing problem rather than a playback problem.

6. It Plays, but Something Is Visibly Wrong

A file that opens and runs but looks wrong is a different class of problem:

  • Stuttering or uneven motion: usually playback-side decoding load (see section 3), or a capture-side problem that was baked in while recording. Reducing lag when screen recording covers the capture side.
  • Audio drifting out of sync: a sync problem, not a container problem — re-exporting the same source usually reproduces it.
  • Wrong aspect ratio / black bars on all four sides: the export aspect ratio didn’t match the source framing. Re-export with the correct ratio rather than letting the player stretch it.
  • A “by recorded.app” watermark you didn’t expect: that’s the free-plan export mark. Exports under 25 seconds are free and carry the watermark; longer exports require signing in with Pro. Nothing is wrong with the file.

How to Produce a File That Plays Everywhere

When you don’t know what will open the video — a client’s laptop, a conference room display, an embed on someone’s site — pick for compatibility rather than for maximum quality:

  • Format: MP4. H.264 and AAC are the safest pair available.
  • Resolution: 1080p. It decodes everywhere and keeps screen text readable.
  • Duration: trimmed as tight as the content allows.
  • Compression: on, if the file is going over email, chat, or an upload form with limits.
  • Verification: open the exported file yourself, in a player you didn’t export it from, before you send it.

That last step takes fifteen seconds and catches nearly everything in this guide. For more on choosing between MP4 and GIF in the first place, see choosing the right video format. Recorded’s export pipeline and quality settings are covered on the high-quality export feature page.

When the Source Recording Itself Is Damaged

Everything above assumes the recording in your library opens normally in the editor and only the export is broken. If the recording itself won’t load — the editor shows an error, or the timeline comes up empty — then the problem happened during capture, not export.

The usual causes are the machine running out of disk space mid-recording, or the app being force-quit while capture was running. Check free space first: screen recordings consume it faster than people expect, and a disk that fills during a long session truncates whatever was being written.

A Short Prevention Checklist

  • Watch the export through to completion instead of switching away from it.
  • Keep enough free disk space for the recording and the export.
  • Export at 1080p MP4 unless you have a specific reason not to.
  • Play the finished file once yourself before sharing it.
  • Name files with their real extension — never rename to “convert.”
  • Send a link where you can, rather than attaching large files to email.

Most unplayable recordings aren’t corrupted at all. They’re incomplete exports, oversized files, or perfectly good videos handed to a player or an upload form that couldn’t take them. Working through the symptoms in order gets you to the real cause faster than re-exporting and hoping.

Ready to record something that plays on the first try? Download Recorded for macOS or Windows and export to MP4 or GIF in a couple of clicks.