Screen recording checker

Screen Recording Checker

QUICK ANSWER

Drop in a recording that won't play, won't seek, or looks wrong in some app, and this tool reads its actual container and codec bytes (not just the file extension) to tell you what's really wrong: a mismatched extension, an invalid duration (the classic MediaRecorder WebM bug), a missing audio or video stream, a non-faststart MP4, or a codec a target app doesn't support. Everything runs in your browser — the file is inspected locally and never uploaded.

  • Reads container/codec bytes directly
  • Flags the Infinity/NaN duration bug
  • Checks faststart and seekability
  • Compatibility matrix per platform
  • Nothing uploaded
  • No signup
Clipy
Your next step

Mic works. Camera works. Now what?

Record and share free with Clipy. No watermark, no viewer signup.

  • Make your first recording in one click
  • Share a link the second you stop
  • Agent-readable links: AI summary, key moments, transcript
  • Free forever, no watermark, no install
Record my first video free

No credit card. Viewers never need an account.

Why this tool exists

  • Runs in your browser. Files never reach our servers.
  • No signup. No watermark. No usage cap.
  • Works offline once the page is loaded.
Trusted by creators at startups, agencies, and Fortune 500 teams.
Free forever, no signup, no watermark.

How it works

  1. 1

    Drop in the file that's misbehaving

    MP4 or WebM. The check reads the first several megabytes of the file's binary structure directly, so it works even on files the browser itself struggles to play.

  2. 2

    Read the diagnostics

    Each check gets a pass, warning, or fail: container/extension match, file size, duration, seekability, dimensions, faststart (MP4), and whether video and audio streams are actually present.

  3. 3

    Check the compatibility matrix

    See at a glance whether the file is likely to play in Chrome, Safari/iOS, and preview correctly in Slack, Gmail, and PowerPoint, based on its actual container and codec.

  4. 4

    Follow the suggested fix

    Each failing check links to the specific Clipy tool that fixes it — WebM to MP4 for the duration bug, the video converter for a container mismatch, rotate/flip for orientation issues, or the audio fixer for a missing/broken audio track.

Why won't my screen recording play?

The three most common reasons, in order of frequency: an invalid duration written by MediaRecorder (fix with WebM to MP4), a container the target app doesn't support like WebM in Safari or PowerPoint (fix with the video converter), or a codec the target app can't decode. Drop your file in above to see exactly which one applies.

Skip the diagnostics entirely

None of this matters if you record and share with Clipy: recordings stream to the server as you record, get transcoded into a broadly compatible MP4 automatically, and viewers get an instant link instead of a file with its own container quirks.

The Infinity/NaN duration bug, explained

Chrome's MediaRecorder writes WebM files without a valid duration in the header while recording, because it doesn't know the final length until you stop. Many players read that missing value as Infinity or NaN, which breaks the seek bar and can make some apps refuse the file entirely. The fix isn't re-encoding the video — it's re-muxing the container so the correct duration gets written into the header. The WebM to MP4 converter does exactly that as part of the conversion.

Why the file extension can lie

A video's extension is just a filename convention; the actual format is determined by the first few bytes of the file (a WebM starts with an EBML signature, an MP4 starts with an ftyp box near the top). Renaming a .webm to .mp4 doesn't convert it — it just makes some apps trust the wrong player logic and either refuse the file or play it incorrectly. This checker reads the real bytes, so it catches that mismatch even when the filename looks correct.

Faststart and why it matters

An MP4 file is internally split into a `moov` atom (the index: where every frame lives) and an `mdat` atom (the actual frame data). If `moov` comes after `mdat`, a browser or streaming player has to download the whole file before it can start playing, because it doesn't know where anything is yet. "Faststart" means `moov` was moved to the front, so playback (and scrubbing) can begin immediately. Screen recorders and some export tools sometimes skip this step.

Common questions

My video's duration shows as Infinity or NaN. How do I fix it?

This is almost always the MediaRecorder WebM duration bug. Run it through the WebM to MP4 converter, which re-muxes the file with a correct duration written into the header. It's a fast remux, not a re-encode, so quality is unaffected.

Why won't my recording play on iPhone or in Safari?

Safari doesn't support WebM playback at all. If this checker reports a WebM container, convert it to MP4/H.264 with the video converter — that's the most broadly compatible combination across Safari, iOS, and every other modern browser.

The checker says my file has no audio track. Did I lose my narration?

If the check says 'not found' but you know audio was recorded, it may be that recording capture failed at the source (a common cause: the wrong input device was selected, or a browser tab was shared without ticking 'share tab audio'). If the file genuinely never captured audio, there's no audio to recover. If audio exists but sounds wrong once you play it (too quiet, one channel silent, clipping), use the audio fixer instead — this checker only confirms whether a track exists, not how it sounds.

What does 'faststart' mean and why does it matter for sharing?

It means the MP4's index (moov atom) is positioned before the frame data (mdat atom), so a browser or streaming player can start playback immediately instead of downloading the whole file first. Non-faststart files still play fine once fully downloaded (e.g. after opening in a desktop video player), but stream poorly when shared as a link or embedded on a web page.

Does this tool upload my video anywhere?

No. Only the first several megabytes of the file's bytes are read locally in your browser to inspect its container structure, and a hidden <video> element checks playback metadata. Nothing is sent to a server. You can verify this in your browser's Network tab.

Can this tool check MOV, AVI, or MKV files?

It reliably reads MP4 and WebM container structure. Other containers (MOV shares MP4's box structure and often gets read correctly; AVI and MKV are not currently parsed) will show as 'unknown' for the container-specific checks, though duration/dimension/playback checks via the browser's own video element still run.

Tool not working the way you expect?

Tell us what broke. We resolve every report within 24 hours.

Send feedback →

More free tools

Doing this for an AI workflow?

Clipy recordings are agent-readable out of the box. One link carries the video, keyframes, and transcript.

Clipy for AI agents