GOOGLE ADS IMAGE POLICY AND THE REQUIREMENTS THAT GET ASSETS REJECTED

Most write-ups on the google ads image policy read like a transcription of the help page. That is not what I learned from. What taught me was a few hundred image assets going to review and watching which ones came back disapproved, until the pattern was obvious enough that I can now predict a rejection before I upload. The policy itself is short. The useful knowledge is which clauses get enforced hard, which ones are tolerant in practice, and what a designer who has never touched the platform will get wrong every single time. This article goes straight to that, the requirements that matter and the disapprovals I read on sight, rather than a clause-by-clause restatement of the rules. If you only need the dimensions and weight limits, the image size reference covers those in isolation.

The google ads image requirements that actually matter

The technical specs are the part nobody argues with, because they are mechanical: either the file passes or it does not. For Search image assets the accepted formats are PNG and JPG, the maximum file size is 5120 KB, and the square (1x1) ratio is mandatory while landscape (1.91x1) is optional but recommended. The square minimum is 300 x 300 pixels with 1200 x 1200 recommended; landscape is 600 x 314 minimum with 1200 x 628 recommended. Those are the published google ads image requirements, and I treat the recommended sizes as the real floor rather than the minimums.

Here is the inference that took me a while to internalise: an image that clears the minimum resolution still fails the quality bar surprisingly often. Google crops and rescales the same asset across multiple surfaces, so a 300 x 300 image that looked acceptable on upload renders soft once it is resized for a different placement, and softness reads as "blurry or unclear" to the review system. Uploading at 1200 x 1200 is not about looking better, it is about surviving the downstream resizing without crossing into a quality disapproval. The other half of the google ads image policy that genuinely matters is the safe area: keep the meaningful content inside the center 80% of the frame, because anything Google crops off the edges is content you cannot rely on showing.

Relevance is a requirement, not a suggestion

The spec sheet stops at pixels, but the part that quietly costs performance is relevance. An asset has to match the queries and the landing page it serves alongside. I have seen technically perfect images underperform purely because they were generic stock that had nothing to do with the searcher's intent. Relevance does not usually trigger a hard disapproval, but it suppresses serving, which in practice is the same outcome as a rejection: the asset does not show.

The recurring disapprovals I read at a glance

After enough review cycles, the same handful of rejections account for the overwhelming majority of what I deal with. Five patterns cover almost everything, and I can spot four of them before an image is ever submitted.

1. Text or graphic overlay, the number one cause

This is the single most common rejection, and it is almost always self-inflicted. A designer treats the image asset like a display banner and adds a headline, a price burst, a discount badge, or drops the brand logo into a corner. The google ads image policy for Search assets disallows added text and graphic overlays, including a brand logo used as the image itself. The line the system draws is between what was captured in the original photograph and what was layered on afterward, a logo physically present on a product as it was shot is tolerated, a logo pasted on in post-production is not. When I receive creative from a brand team, the overlay check is the first thing I do, and it catches more rejections than every other rule combined. The same overlaid-text logic shows up in display creative too, where Google's vision system detects text baked into the image and penalises it.

2. Too much blank space

An image where the product sits small against a large empty background gets rejected because the offering becomes unrecognisable. This one is easy to read at a glance: if I have to look for the subject, so will the review system. The fix is always the same, tighten the crop until the subject dominates the frame and keep it centered in the safe area. As a bonus it improves performance, because an asset that reads clearly at thumbnail size converts better than one with a lost subject.

3. Blurry or unclear images

Covered above from the resolution angle, but worth separating because it also happens with high-resolution files that were upscaled, heavily compressed, or shot out of focus. The review system does not care why the image is soft, only that it is. I check sharpness at 100% before uploading rather than trusting the thumbnail.

4. Collages and combined images

Images stitched together in post-production are rejected. The tolerated exception is a naturally occurring collage, a scrapbook, a greeting card, a catalogue page, something that was photographed as a single real object. The distinction is again capture versus assembly: a real collage shot in one frame is fine, four product shots arranged in a grid is not. Brand teams that want to show a product range in one asset trip on this constantly.

5. Distorted or poorly cropped subjects

Images skewed, warped, or cropped so the subject is hard to make out get rejected for the same underlying reason as blank space and blur: the system cannot tell what it is looking at. Aspect-ratio stretching to force a square out of a landscape photo is the usual culprit. I crop to the target ratio instead of stretching, which preserves the subject and clears the rule.

The thread running through all five is consistent: the google ads image policy is built around whether a human, and the review model, can immediately recognise the product or service. Every recurring disapproval is a variation of "the subject is not clearly readable," and once that frame clicks, reading rejections at a glance becomes second nature. The full size and ratio breakdown across Performance Max and Display is worth keeping open when you prepare assets for multiple campaign types, because the overlay tolerance changes between them.

Account eligibility: the rejection that is not about the image

A category of "rejection" that confuses clients constantly is not a disapproval at all, it is the image asset option simply not appearing. Image assets are gated behind account history, and the google ads image requirements here are about the account, not the file. Per Google's image asset documentation, the account must have been open for at least 60 days, carry a good policy compliance history, run active campaigns, and have active text ads with Search spend greater than zero in the last 30 days. The account also has to sit in an eligible vertical, sensitive categories such as sexual content and gambling are excluded outright.

The structural detail, format rules, eligibility conditions, and the allowed-versus-not examples, is laid out in Google's official image assets format requirements. When a client asks why they cannot add images, I run down the eligibility list before I ever look at their creative, because nine times out of ten the answer is the 60-day window or zero recent Search spend, not the images.

How I read an asset before it goes to review

My pre-submission pass takes under a minute and removes most of the rejection risk. First, overlay: is there any text, badge, or logo that was not part of the original photo? If yes, it goes back. Second, subject size: can I identify the product instantly, or is it lost in blank space? Third, sharpness at full size, not at thumbnail. Fourth, assembly: is this one real photograph or a grid of several? Fifth, ratio: was it cropped to square, or stretched into it?

That sequence maps one-to-one onto the five recurring disapprovals, which is the point, the google ads image policy is not a long list to memorise but a small set of failure modes that repeat. The one rule that genuinely changes by campaign type is overlay tolerance: Performance Max accepts images with overlays while Search does not, so I keep a clean master version of every asset and only produce an overlay variant when a Performance Max creative specifically needs it. The clean image serves everywhere without friction; the overlay version is the exception, not the default. Treating the policy as five readable patterns rather than a wall of clauses is what turns a disapproval from a research task into a fix I make on sight.