HTML5 banner sizes, specs and size limits
HTML5 banner specs by platform: Google Ads takes 600 KB, DV360 counts 5 MB of downloads and Campaign Manager 360 takes a 10 MB ZIP. Where banners fail.
· Updated · 5 min read

The same HTML5 banner meets three different limits depending on where it goes: 600 KB in Google Ads, 5 MB of downloaded files in Display & Video 360, and a 10 MB ZIP in Campaign Manager 360. The size is only one of the checks, and the click tag rules differ more than the numbers do.
I built a set of six HTML5 banners and a checker that applies these rules in the browser. Unless noted, everything below comes from each platform's own help page, which I read on 18 October 2026.
The common HTML5 banner sizes#
Most campaigns are built from a handful of IAB sizes: 300×250 (Medium Rectangle), 728×90 (Leaderboard), 160×600 (Wide Skyscraper), 300×600 (Half Page), 336×280 (Large Rectangle), 970×250 (Billboard), 320×50 (Mobile Leaderboard) and 320×100 (Large Mobile Banner). The dimensions are the same for HTML5 and image banners; what differs by platform is the file weight, the click tag and the backup image below. My Banner Sizes tool lists every IAB, Google Ads and AdMob size with where it runs.
The numbers#
| Check | Google Ads (display) | Display & Video 360 | Campaign Manager 360 |
|---|---|---|---|
| Size | 600 KB or smaller | 5 MB of files the browser downloads | ZIP up to 10 MB (another page says 9.5 MB) |
| Files in the ZIP | No more than 40 | Up to 100, no size limit on the ZIP | Up to 100 |
| Click tag | The page does not mention one | Required, readable, not minified | At least one, readable, not minified |
| Storage APIs | Not stated | Not stated | localStorage, sessionStorage, indexedDB and openDatabase are rejected |
| Backup image | Not stated | Not stated | Keep it out of the ZIP |
Sources: Google Ads help, requirements for HTML5 ads, DV360 guidelines for HTML5 display creatives, CM360, how to prepare HTML5 display assets. The 9.5 MB figure is on a separate CM360 asset options page, which I found through a search and did not open in full.
"Not stated" means the page I read does not say, not that the platform allows it.
Google Ads is the strict one#
Google Ads takes a ZIP of HTML and optionally CSS, JS, GIF, PNG, JPG, JPEG and SVG, at 600 KB or less and 40 files or fewer. It also checks things the other platforms do not mention:
- The file starts with
<!DOCTYPE html>. - The
<head>has anad.sizemeta tag, for example<meta name="ad.size" content="width=300,height=250">. - Every reference is a relative path to a file inside the ZIP.
- Tags have explicit end tags, so
<path></path>passes and<path />does not. - External references are limited to Google Fonts and Google-hosted CreateJS, GreenSock and jQuery.
Google's list of accepted sizes has 20 entries. My Banner Sizes tool uses that list for its Google flag.
I also got a number wrong early on. My own project notes said the Google limit was 150 KB. The help page says 600 KB. The 150 KB figure probably comes from a different rule.
Where the 150 KB comes from#
The DV360 guidelines for mobile creatives, which I only saw through a search result, mention a 150 KB initial load, with further loads allowed after that. I did not open that page, and the search result looked dated, so treat it as a lead.
Some publishers set their own initial-load rule. I use 150 KB as a cap for my own banners, and npm run ads fails when a package goes over it. That cap is my choice, not a platform limit, and the checker labels it "150 KB publisher target" for that reason.
My six packages weigh between 67 KB and 105 KB each as raw files, including the backup image. The 970×250 is the largest at 105 KB, which is 17% of Google's 600 KB.
Click tags differ more than the sizes do#
DV360 says HTML5 display ads must use click tags. It wants the variable easy for the ad server to read, so no minifier on it, and the landing page must open in a new tab or window.
CM360 says the same about readability. It also says that a hard-coded URL stops it from tracking clicks and stops traffickers from updating the destination.
Google Ads' requirements page does not mention click tags at all. If you build one banner for all three, the click tag costs you nothing on Google Ads and is required on the other two, so I always include it.
<script>
var clickTag = "https://example.com/landing";
</script>
<a href="#" onclick="window.open(window.clickTag); return false;">Learn more</a>
Keep the variable named clickTag, leave it out of your minifier's rename list, and read it at click time rather than at load time.
The backup image trap#
Each of my packages ships an index.html and a backup image side by side. CM360 says not to put a backup image in the HTML5 ZIP, and to upload it separately in the interface. So for CM360 I would zip the HTML alone. DV360 and Google Ads do not say the same on the pages I read.
Check before you traffic#
A ZIP that fails after upload costs you a round trip with the ad ops person. The HTML5 Banner Checker runs this list on a ZIP in your browser, so nothing is uploaded. It has a profile for each platform above, plus the 150 KB publisher target, and it also flags the entry file location, the ad.size meta tag, the missing click tag, external requests, files that nothing references and a missing backup image.
Where the sources disagree#
DV360 pages disagree on whether a ZIP has a size limit: one says no size limit, another puts the weight limit at 5 MB of downloads. I read the 5 MB as the weight of what the browser downloads when the ad serves. Help pages also change without notice, so check the three source pages before a big campaign.