What it checks
Media facts that matter in an editing workflow
ClipCompat reads the actual stream metadata instead of relying on the filename extension. The checker focuses on the attributes that frequently change compatibility or editing behavior.
Video Compatibility Checker
Drop a video file, choose your editing environment, and get a structured explanation of the media characteristics that may affect import, decode or timeline behavior.
MP4, MOV, MKV, WebM and other formats MediaInfo can read.
Your file is analyzed locally in your browser.No video ready? Choose a tiny synthetic file to run through the local analyzer.
Samples download from ClipCompat. Your own selected video is never uploaded.Editing environment
Choose a video file to begin.
What it checks
ClipCompat reads the actual stream metadata instead of relying on the filename extension. The checker focuses on the attributes that frequently change compatibility or editing behavior.
How it works
The checker uses MediaInfo compiled to WebAssembly. A Web Worker reads the file in chunks through the browser File API, normalizes the reported media properties, then applies conservative compatibility rules for the selected editing environment.
The browser gives ClipCompat local access only to the file you choose.
The analyzer reads chunks as needed rather than uploading the video to a server.
Media facts are separated from documented support conditions and heuristic editing risks.
Supported, Conditional, Editing Risk, Unsupported, Known Issue or Test Required.
Why the verdict is useful
A generic codec list cannot tell you whether a particular file is VFR, 10-bit 4:2:2, wrapped in an unusual container or being checked for a different editor edition. ClipCompat shows the detected facts first, then the matching rule and its evidence level, so you can see why the verdict changed.
Privacy
ClipCompat does not upload or store the selected video for analysis, and the checker does not require an account. Media inspection happens in your browser. The checker does not send filenames or extracted media facts to a dedicated application analytics integration.
Limitations
Hardware decoding, GPU drivers, operating-system media components, plug-ins and specific editor versions can affect real-world behavior. ClipCompat therefore uses conditional and test-required states instead of claiming that every file will definitely work or fail.
Related Lab Cases
ClipCompat Lab Cases use tiny synthetic files so compatibility logic can be checked without relying on private user footage.
A small synthetic MP4 that represents a conventional H.264 editing baseline.
Open case →Synthetic H.264 MP4 with irregular frame timing to test VFR detection and verdict priority.
Open case →A synthetic HEVC source that exercises environment-dependent bit-depth and chroma rules.
Open case →A synthetic VP9-in-WebM file that tests a less universal editing path.
Open case →A synthetic AV1-in-MKV source that intentionally produces different target guidance.
Open case →