STATIC DISPLAY BANNER CHECK
Google Display Ad Size Checker
Check your finished banners before handoff: dimensions, file sizes, duplicate files and the sizes still missing from your set.
What this check covers
This tool reads actual decoded pixel dimensions and file signatures, not dimensions written in filenames. It compares static PNG and JPEG files with Google's main uploaded-display size table and uses a conservative ceiling of 150,000 bytes. Original files are never resized or recompressed here.
A passed check means only that the supported technical checks passed. Content policies, landing pages, account eligibility, regional inventory and ad approval still require review. Selecting a size above is your campaign checklist, not a requirement to supply every listed size.
Animated GIF, APNG and WebP files are not approved by this checker. GIF animation length and frame rate need separate validation; WebP needs conversion to an accepted format. Region-specific additional sizes are outside this first version. Exact duplicate files are identified by SHA-256, not visual similarity.
ZIP exports contain the unchanged files that passed, with exact duplicates omitted. The CSV includes every inspected file and missing campaign sizes. This ZIP is a handoff package, not an HTML5 ad or an assurance that Google will accept a bulk upload.
Specifications checked September 11, 2026: Google uploaded display ad specifications. Responsive display assets follow different requirements, including a 5120 KB file limit.
Questions
Why is my 1200 x 628 image flagged?
That may be an appropriate responsive display asset, but this page checks finished, fixed-size uploaded banners. These are different ad workflows. Do not shrink a responsive asset just to pass this checker.
Can I fix an oversized banner?
Use the image compressor with the original pixel dimensions and a target below 150 KB. Review small text and edges after compression, then check the exported file here. JPEG does not preserve transparency.
Are these files uploaded?
No. File inspection, hashing, previews, CSV and ZIP generation run locally in this browser. Reloading the page clears the batch.