Runway Gen-3 and Gen-4 clips look flawless in the preview, then betray their origin on the timeline: hands sprout a sixth finger, faces morph mid-pan, a background character clones into two, textures shimmer and warp between frames, and the audio drifts out of sync on longer generations. UploadCheck watches and listens to every export before you publish — flagging the temporal warps, cloned subjects, frozen loop seams, and audio desync that make a clip read as "AI slop" — and hands your agent the exact timestamps to re-roll or trim.
broken videos published. Every Runway generation gets one final pass, so a frozen frame or dropped word never reaches your audience.
instead of re-watching a 20-minute export. UploadCheck finds the one bad moment with its exact timestamp — no more scrubbing to hunt for it.
saved off every delivery. No re-export → re-upload → "why is there a black frame at 0:14" from a client after it went live.
It doesn't replace Runway — it's the automated final QC pass on the finished export, the thing an editor can't reliably do by eye.
Same engine every way. The free scan runs 35 automated checks; a paid plan adds the AI gates (garbled speech, on-screen continuity, narration match) and lifts the hourly limit.
Use Claude Code, Codex, Cursor, or any LLM for production? Paste our one-time setup prompt and it wires a /check command. Then just say "check my Runway generation" — the AI runs UploadCheck and reads back the findings. Free needs no key.
Export your video or audio from Runway, then drop the file into the free scan. No account, no tools — a real PASS / BLOCK verdict with timestamps in seconds.
Start free →On a paid plan, upload the Runway generation straight into your UploadCheck dashboard — same engine as the free scan, with every AI gate on and no hourly throttle. Paste a link or choose a file.
See paid plans →You generate and export your generation in Runway as usual, then run the finished file through UploadCheck — from the web, the CLI, or your AI assistant. UploadCheck scans it for problems Runway can't check, returns timestamped flags and fixes, and you re-check until it passes.
Morphing and warped motion, temporal flicker, frozen/looped frames, cloned or duplicated subjects across a shot, audio that drifts out of sync with the video, off-target loudness, and wrong resolution/codec/frame-rate — each with the exact timestamp and a fix.
No. UploadCheck is the last step after your Runway generation — one check before you publish. It doesn't touch your Runway project; it inspects the finished file and hands you (or your AI) a repair list.
Yes — Runway artifacts are exactly what the AI oracle gates are built for. twins catches a character that clones or morphs into a duplicate across a scene, while omni_watch and gemini_watch actually watch and listen to the full clip and report the warps, flicker, and "this doesn't look real" moments a frame-by-frame check misses. On the deterministic side, loop_freeze catches frozen frames and bad loop seams, av_sync catches audio drifting out of sync on longer generations, and canvas_fill catches off-center or letterboxed framing — all with the exact timestamps your agent needs to re-roll or trim.
Instead of re-watching a clip to hunt for the one bad moment — or worse, finding it after you've published — UploadCheck flags it in one pass with the exact timestamp. Catching one bad generation before publish saves the re-generate/re-export, re-upload, and the reputational hit of a broken clip going live.
Free with your email — 35 gates, unlimited. Add the AI gates when you're ready, from $0.025/min.