Short answer: A CM360 backup image has been optional since Campaign Manager 360’s 16 May 2022 release. Optional is not the same as harmless. If a browser can’t run your HTML5 and there is no backup, CM360 serves nothing and DV360 serves a blank image. Upload one per size, as a separate file, never inside the ZIP.
This guide is for traffickers and ad ops teams who see the “(Optional)” label in Campaign Manager 360 and wonder whether to skip it. It covers what Google’s help pages say today, what happens when the backup is missing, how the DV360 backup image differs, and the setup mistakes we see in production. For every other platform’s rules, see our HTML5 backup image requirements by platform.
- CM360 dropped the backup requirement on 16 May 2022.
- No backup means CM360 serves nothing where HTML5 can’t run.
- DV360 serves a system-generated blank image instead.
- Both platforms forbid the backup inside the HTML5 ZIP.
- Multi-size creatives take one backup per size.
- A backup under 40 KB can also be your CM360 polite load image.
- Is a CM360 backup image required?
- What CM360 does when there is no backup
- CM360 and DV360 backup rules in one table
- Packaging the CM360 HTML5 backup: beside the ZIP, never in it
- The DV360 backup image: a blank instead of nothing
- Can the backup double as the CM360 polite load image?
- Setting up the backup in CM360
- 5 CM360 backup mistakes we see in production
- Should you upload one anyway?
Is a CM360 backup image required?
No. Google’s own help pages show the change step by step. In February 2021, CM360 still told users to add a backup image whenever the primary asset was HTML5.

| Date | What changed in CM360 |
|---|---|
| Feb 2021 | Backup listed for HTML5, with no “optional” label |
| 16 May 2022 | Release notes announce the backup is no longer required |
| Aug 2022 | Asset docs label the backup “(Optional)” |
| Today | “Create a display creative” says a backup is not required |
The live release-notes URL now redirects to the CM360 help home, so the archived copy is the one to bookmark.
What CM360 does when there is no backup
CM360 decides at serve time. When you upload an HTML5 asset, it lists the feature dependencies: the browser features it thinks your banner needs. If a browser lacks one of them, CM360 shows the backup. Without a backup, nothing is displayed.
An empty slot is still a served ad call. Google’s serving logic is plain: CM360 “serves your HTML5 asset whenever possible”, and if HTML5 is unsupported, nothing serves unless you added a backup image. The same page says the backup is not needed when an image is the primary asset.
You can edit the dependency list for assets you upload yourself. Google notes that with 0 feature dependencies the HTML5 asset is always delivered. Google suggests this for banners that handle old browsers on their own. If you remove dependencies a banner really needs, Google warns that users may see browser errors or oddly formatted media.
“Optional” describes the upload form. It says nothing about what a viewer with an unsupported browser will see.
CM360 and DV360 backup rules in one table
We checked each line below against Google’s live help pages today. DV360 is included because many campaigns run through both.
| Rule | Campaign Manager 360 | Display & Video 360 |
|---|---|---|
| Backup status | Optional | Optional |
| No backup, HTML5 unsupported | Nothing serves | System-generated blank image |
| Inside the HTML5 ZIP | Not allowed | Not allowed |
| Where to add it | Separate asset in Creative assets | “Backup images” section, under Advanced settings |
| Dimensions | Must match the HTML5 asset | Must match the creative |
| Multi-size or responsive | One backup per supported dimension | One backup per size |
| Backup settings | Landing page, target window, exit reporting label | Reporting label |
| Polite load image | Under 40 KB; can be the backup file | Separate upload; no weight stated |
Sources: CM360 asset guidelines and HTML5 asset prep; DV360 HTML5 creatives. For the wider spec picture, our banner ad specs cheat sheet covers each platform.
Packaging the CM360 HTML5 backup: beside the ZIP, never in it
CM360’s HTML5 prep guide is direct: the trafficker can upload a separate backup, and you should not include one in the HTML5 ZIP. DV360 says the same and points you to its “Backup images” section.

Yahoo wants the opposite, so a campaign on both needs two packages. Our platform-by-platform guide covers that split.
One thing to watch while you package. Google’s two CM360 pages disagree on the ZIP limit. The asset guidelines say up to 9.5 MB; the HTML5 prep guide says 10 MB. Build to 9.5 MB and both pages are satisfied. If you’re anywhere near that, our tips to reduce HTML5 banner size will help.
The DV360 backup image: a blank instead of nothing
DV360 treats backups as optional too. They serve only when the creative isn’t supported by the viewer’s browser or platform. Google’s example is Internet Explorer 8 with a banner that uses CSS animations.
The difference is what fills the slot. Per the DV360 help page, a missing backup means “a system-generated blank image is served instead.” The viewer sees an empty rectangle rather than nothing. Neither carries your message.
DV360 also uses the backup to read the creative’s size. Its FAQ says the size comes from the creative or the backup image. A backup at the wrong pixel size can make the creative show the wrong dimensions after upload.
Can the backup double as the CM360 polite load image?
Yes. CM360 asks for a polite load image under 40 KB and says it can be the same asset as your backup. Its dimensions should match the backup’s.
There is a catch. Google recommends a polite image that matches the first frame of the HTML5 ad, so there’s no jump when the banner starts. A good backup shows the final frame, with the full message and call to action. One file can’t be both.
We deliver two images per size for CM360: frame one as the polite load image and the end frame as the backup, both under 40 KB. It costs a few minutes and removes the jump.
Setting up the backup in CM360
The full upload flow is its own topic. These are the three backup-specific settings that traffickers most often leave on their defaults.

Assign each size
Upload the backup as a separate image asset. For a multi-size HTML5 asset, add one backup per supported dimension.
Set the click
Fill in the backup landing page and target window. The backup has its own landing page, separate from the HTML5 click tags.
Label it separately
Give the backup its own exit reporting label. If it matches a creative event label, CM360 can’t tell them apart in reports.
5 CM360 backup mistakes we see in production
- Skipping it because the field says “Optional”. The same creative may also run on The Trade Desk, where the backup image is required, or on publishers that ask for one.
- Zipping it with the HTML5 files. Both CM360 and DV360 say to keep it out of the ZIP.
- A retina file at double size. A 600×500 image for a 300×250 creative breaks the dimension match.
- One backup for a multi-size creative. CM360 and DV360 both key backups to size.
- Quoting the wrong Google page. The legacy Studio Help FAQ still says a backup “is still required for HTML5 ads”. Studio creatives traffic through CM360, so CM360’s rule is the one that applies.
Should you upload one anyway?
In our experience, yes. Agency delivery checklists still ask for backups, and the file is small. Upload one when any of these is true:
- The same banner set also goes to a DSP or publisher that requires a backup.
- CM360 lists feature dependencies for the asset.
- The client or agency spec sheet lists a backup per size.
- You want the image to double as the polite load file.
Making the files is the quick part. The free tool linked on this page turns an HTML5 ZIP into a backup image for every size. Before handover, run the set through our HTML5 banner delivery checklist and preview every size. If you’d rather not handle any of it, an HTML5 banner production studio can deliver CM360-ready packages with the backups included.
Frequently asked questions
When did CM360 stop requiring backup images?
With its 16 May 2022 release. By August 2022 the asset docs labelled the backup “(Optional)”.
If CM360 doesn’t require a backup, why do agencies still ask for one?
Because the same banners often run on platforms that do require one, such as The Trade Desk, Amazon DSP and many publishers. It’s also cheap insurance against CM360 serving nothing.
Does a CM360 backup image have its own click-through URL?
Yes. Set the backup landing page and target window in the backup image properties. It doesn’t use the HTML5 click tags.
If I remove all feature dependencies, do I still need a backup?
With 0 feature dependencies, CM360 always delivers the HTML5 asset, so the backup won’t serve through that check. Google suggests this only for banners that handle browser support themselves.
Why does DV360 show the wrong size after I upload a creative?
DV360 reads the size from the creative or the backup image. Make sure the backup matches the main creative, or pick the correct size in the Dimensions menu.
Sources
- Google CM360: Create a display creative
- Google CM360: Asset guidelines for display creatives
- Google CM360: How to prepare HTML5 display assets
- Google DV360: HTML5 creatives
- Google Studio Help: HTML5 FAQ (legacy)
- CM360 release notes, May 16, 2022 edition (archived)
- CM360 asset guidelines, February 2021 (archived)
- CM360 asset guidelines, August 2022 (archived)
Looking for a banner production company?
Digitaland has produced HTML5 banners for agencies and brands since 2011. See how we work, or send us the brief and we take it from there.


