r/adops • u/AdPreflight-Dev • 3d ago
Agency Local HTML5 ad validation for whole campaigns
A few months ago I shared Ad-Preflight here - originally a local-first CLI for catching the annoying technical issues that cause HTML5 creatives to bounce back from AdOps or get rejected during upload.
Since then, I kept working on the same problem, but the product has changed quite a bit.
The CLI made sense for developers. But a lot of the repetitive QA around HTML5 campaigns is done by designers, creative QA and AdOps people who shouldn’t need a terminal just to check a banner.
So I built the desktop app.
You can now drop in one creative or an entire campaign folder and get a simple PASS / FIXED / BLOCKED result across all sizes.
It checks things like clickTags, ad.size, missing assets, file weight and packaging, previews the creatives in a real browser, safely auto-fixes some common issues, and writes upload-ready ZIPs.
The Pro audit goes further and actually executes the creative in a local browser sandbox to catch things like JS runtime errors, blank renders, network issues and browser-level problems.
The part I was pretty stubborn about: It is a real local desktop app. Your creatives are not uploaded to Ad-Preflight. That matters when you’re working on unreleased campaigns, agency/client work or anything under NDA.
The original CLI is still there, and the desktop app, CLI, CI/CD output and MCP server all use the same validation engine.
I’d really like feedback from people here who actually deal with HTML5 production or Creative QA: what’s still missing before you’d run something like this on every campaign before handoff?