Google Ads HTML5 upload troubleshooting
Google Ads HTML5 ad rejected? Check the ZIP before you upload
Catch common Google Ads HTML5 upload failures involving file size, unsupported files, missing ad.size metadata, and malformed creative packaging before the ad reaches review.
The short version
Google Ads reports that the HTML5 ad is too large, contains an unsupported file, or is missing the primary HTML file and Ad Size tag.
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
- ✓Supported file types and file signatures inside the ZIP
- ✓Total creative size against the configured Google Ads rule
- ✓Primary HTML file and meta name="ad.size" declaration
- ✓Missing assets, insecure references, and click handling
- ✓Google Ads rules in the desktop app, with a verdict next to DV360, CM360, CM360 Studio and Google Ad Manager
What it cannot guarantee
- !Google Ads limits vary by ad format and campaign context
- !The tool does not validate account eligibility for HTML5 ads
- !Policy, landing-page, and manual review decisions remain outside the local audit
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.Point the CLI at the creative folder, not a ZIP nested inside another ZIP.
- 2.Run the standard package command to see the failing rule.
- 3.Apply --fix only for supported safe repairs, then inspect the generated ZIP.
- 4.Upload the resulting package after checking the report.
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 usPlatform reference: Google Ads: fix error messages with uploaded HTML5 ads