Uploaded Image Ads

Uploaded image ads are display ads you build outside Google Ads and then upload. Google Ads supports image files in GIF, JPG, or PNG format, AMPHTML, and HTML5, and an HTML5 ad goes up as a .zip file. Many advertisers design them in tools such as Google Web Designer. Unlike a responsive display ad, nothing is assembled for you: the ad renders as designed, with your layout, typography, and imagery, which is the whole reason to choose this route when brand control matters more than reach. Designers like the control, but the campaign pays for it in setup time, since each size is a separate piece of artwork.

The tradeoff is inventory. Google Ads Help states that uploaded ads will not be able to run in all parts of the Display inventory, unlike responsive display ads. A fixed-size image only serves where a slot of that size exists, so each size you upload opens a different slice of the network, and a small set of sizes means a small slice. HTML5 ads can be made responsive through rules set in a tool like Google Web Designer, so they resize across layouts, but that takes design effort that a simple image upload does not. Google points to a separate specifications article for exact dimensions and file limits, so check it before you commission artwork.

Several settings and changes sit around the format. You can combine uploaded ads with responsive display ads in the same campaign, which is the usual way to get both control and reach. Editing is awkward: to change an uploaded HTML5 ad you re-upload it as a new ad, which starts with its own reports, so you lose continuous history. And Display campaigns are moving into Demand Gen, where migrated ads are treated as new and must be re-approved, so expect a review step if you switch. Because uploaded ads and responsive ads can share a campaign, a simple split is to keep your best static banners and let responsive fill everything else.

The typical mistakes are running uploaded ads alone, uploading too few sizes, and treating a design file as the end of the job. With no responsive ads next to them, large parts of the network have nothing eligible to show, and spend concentrates in a narrow set of placements. Banners packed with tiny text become unreadable at small sizes. And without keeping your source files organized, a small price change turns into a full re-export, re-upload, and re-approval. Another trap is forgetting mobile: a banner designed for a wide desktop slot may be unreadable when scaled for a phone. It also helps to check that text stays legible at the smallest size you upload, since a headline that works at full size can turn into a smudge on a narrow mobile slot.

What to do this week: check how many sizes you have live in each ad group and whether a responsive display ad runs beside them. Review the placements report to see where your uploaded ads actually served, and compare cost per conversion between uploaded and responsive formats. Keep uploaded ads only where the creative control earns its cost, for example a regulated claim or a strict brand layout, and let responsive ads handle the rest of the network. Archive your source files with version names, so a promotion change takes minutes instead of a redesign. Finally, record which sizes drive conversions, so the next round of artwork focuses on the formats that actually earn their place.