HTML5 ad runtime troubleshooting
HTML5 ad is blank after upload? Static validation is not enough
A creative can have valid files and still render blank when its JavaScript executes in the ad environment. Deep Audit runs the creative in a local browser to expose runtime failures before upload.
The short version
The ZIP passes a markup or packaging check, but the platform preview or live placement shows a blank, partially rendered, or broken ad.
Check your creative now: ZIP, folder or ad tag
Your browser reads the ZIP or folder - no upload, no account. A result tells you what failed, which of those the free app repairs for you, and what to do with the rest.
LOCALYour browser reads the file. Nothing is uploaded.
Preflight check
Drop a creative ZIP or folder here
One creative at a time. The verdict appears right here.
Video asset check
Drop your video exports here
MP4, MOV, WebM or an animated GIF. One file or the whole set of cuts, up to 12 at once, each judged against the rules Meta, TikTok, YouTube, LinkedIn, Pinterest, Snapchat, DV360, CM360 and Ad Manager publish.
The example is a six-second 1080×1920 MP4 from this site, put through the same checker as your own file - not a canned result.
- Running calls the ad server, the same request a real impression makes. It may count one.
- An empty slot can be targeting (domain, region, frequency cap), not a broken tag.
What Ad-Preflight checks
- ✓Runtime JavaScript errors with file and line information
- ✓Failed asset requests and insecure network calls
- ✓Blank-render detection at each creative size
- ✓Overflow, animation, redirect, popup, and visual behavior signals
What it cannot guarantee
- !A local browser run cannot reproduce every platform sandbox or publisher wrapper
- !External services may behave differently at serving time
- !A passing runtime report is evidence of readiness, not a platform approval guarantee
Run it in the desktop app or CLI
Designers and AdOps can drop a campaign folder into the desktop app and follow the visual report. If you work in a terminal or CI pipeline, the same checks are available through the CLI.
- 1.Run the standard audit first to remove packaging and markup failures.
- 2.Activate Deep Audit and run the creative in a real local browser.
- 3.Open the report and fix the first runtime error before chasing downstream symptoms.
- 4.Re-run all sizes and attach the report to the handoff.
CLI equivalent
npx @ad-preflight/cli package ./my-ad --fixStill rejected? Send it to us
Send the rejection message and your free check result, and within 3 working days you get a written answer: what failed, on which platform, and the fix. No files, no call, no sign-up.
Send it to us