Here’s a scenario that happens more often than it should: a title gets delivered, passes an eyeball check, and gets rejected anyway — because somewhere in the conform, a frame ended up with an unintended letterbox, or the active picture area doesn’t actually match the aspect ratio the metadata claims.
Black borders happen for boring, unglamorous reasons. A source pulled from an older format doesn’t get re-cropped properly. A conform step introduces pillarboxing that nobody catches because the player’s own UI was covering the edges of frame during review. A file gets flagged as 16:9 in its metadata but the actual active picture is something else entirely, because a previous pass never adjusted it. None of these are dramatic mistakes — they’re the kind of thing that’s genuinely hard to catch by eye, especially across a large batch of files where nobody has time to frame-step through every title.
What the Aspect Detector does
Drop in a JPEG frame and it automatically detects the active picture area by analysing which pixels aren’t black — no manual measuring, no guessing where the border starts. It shows you a bounding box overlay directly over the frame so you can see exactly what it found, and then crops to that active region so you have a clean reference of what the “real” frame actually is versus what the container claims.
Why this matters more than it seems
Aspect ratio and black-border issues are exactly the category of fault that’s invisible in a quick review and obvious the moment a platform’s automated QC catches it — which means it’s also exactly the category worth catching yourself, before it costs you a delivery cycle. Running a handful of representative frames through this tool before you ship a title is a two-minute check against a problem that otherwise surfaces days later as a rejection.
For full pipeline coverage — checking every title in a batch rather than spot-checking frames — this is the same category of check we run as automated frame analysis within QC & Compliance, just wired into the pipeline rather than done one frame at a time. But for a fast, no-signup sanity check before you send something out the door, this does the job.
All FooEngine tools run locally in your browser. No files are uploaded to any server.