Use Image Kit while this guide is open
Compress, convert, and optimize the same image assets discussed in this guide.
Geographic Note: Google Ads specifications are global, though ad policies and availability vary by country and region.
Hundreds of Rejected Ad Images: Finally Understanding Google's Rules
Look, I messed this up more times than I want to admit. You spend an hour making the perfect ad image, upload it, and boom – rejected. No clear reason, just "doesn't meet requirements." So I went down the rabbit hole. Tested different formats, file sizes, dimensions. Made a lot of mistakes. Here's what I learned.
Look, I messed this up more times than I want to admit. You spend an hour making the perfect ad image, upload it, and boom – rejected. No clear reason, just "doesn't meet requirements."
So I went down the rabbit hole. Tested different formats, file sizes, dimensions. Made a lot of mistakes. Here's what I learned.
The Size Thing Nobody Tells You About
Google says "under 150KB" for display ads. But here's the thing – that's not always true anymore. I've had 180KB images get approved and 120KB images get rejected. The file size matters less than you think.
What matters more? The actual dimensions and aspect ratio. Google wants specific sizes now, and they're pickier about it than they used to be.
Image Sizes That Work
I keep these saved because I use them constantly:
Square formats:
- 1200×1200 (my go-to for most campaigns)
- 300×300 (still works, but looks dated on bigger screens)
Landscape:
- 1200×628 (this is the money shot for feed ads)
- 1200×600 (works better on mobile in my experience)
- 1200×300 (banner style, but doesn't get much love from the algorithm)
Portrait:
- 960×1200 (stories and mobile feed)
- 600×750 (backup option)
Here's something I noticed – if you upload an image that's too small, Google will auto-reject it. But if it's too big? Sometimes they let it slide, sometimes they don't. There's no pattern I could find.
Complete Google Ads Image Specifications (2025)
| Ad Format | Dimensions (Ratio) | Target Size | Use Case / Approval |
|---|---|---|---|
| Square | 1200×1200 (1:1) | 150-200KB JPG/WebP | Feed, sidebar - 95% approval |
| Landscape (Standard) | 1200×628 (1.91:1) | 150-200KB JPG/WebP | News feed, banners - 95% |
| Landscape (Wide) | 1200×600 (2:1) | 150-200KB JPG/WebP | Mobile feed - 90% |
| Landscape (Banner) | 1200×300 (4:1) | 100-150KB JPG/WebP | Leaderboard - 80% |
| Portrait (Standard) | 960×1200 (4:5) | 150-200KB JPG/WebP | Stories, mobile - 90% |
| Portrait (Tall) | 600×750 (4:5) | 100-150KB JPG/WebP | Stories backup - 85% |
| Small Square | 300×300 (1:1) | <150KB JPG/PNG | Sidebar, legacy - 70% |
| Skyscraper | 300×600 (1:2) | <150KB JPG/PNG | Sidebar vertical - 75% |
| Mobile Banner | 320×50 (6.4:1) | <150KB JPG/PNG | Mobile bottom - 70% |
| Leaderboard | 728×90 (8.09:1) | <150KB JPG/PNG | Desktop top - 75% |
Loading diagram...
File Size Reality Check:
- Google says <150KB, but accepts up to 5MB
- Sweet spot: 150-200KB for main formats
- Under 150KB for older/smaller formats
- Focus on quality over strict size limits
File Formats: JPEG vs PNG vs WebP
Everyone says "use PNG for quality" or "use JPEG for smaller files." Both are kinda right, kinda wrong.
JPEG works great for photos and anything with gradients. The compression is good enough that most people won't notice quality loss. I typically export at 85% quality – anything higher is just wasting bytes.
PNG is what you want for logos, text, or graphics with sharp edges. But man, those file sizes get huge fast. I usually only use PNG when I absolutely need transparency or have text that needs to stay crisp.
WebP is the new kid on the block. Google loves it (obviously, they made it). Smaller files, better quality. The problem? Some older browsers still don't support it great. For Google Ads specifically though? WebP is solid. I've been using it more in 2025.
File Format Comparison for Google Ads
| Format | File Size | Quality | When to Use | Rating |
|---|---|---|---|---|
| JPEG | Medium | Good | Photos, products (default) | ⭐ 9/10 |
| WebP | Small | Excellent | Modern ads, mobile-first | ⭐⭐ 10/10 |
| PNG | Large | Perfect | Logos, text, transparency | ⭐ 7/10 |
| GIF | Medium | Poor | Avoid for static ads | 4/10 |
| AVIF | Smallest | Excellent | Too new, not reliable yet | 5/10 |
Format Selection Guide:
- 90% of time: JPEG at 85% quality or WebP
- Need transparency: PNG or WebP
- Best performance 2025: WebP
- Universal compatibility: JPEG
- Logos with text: PNG
- Never use: GIF for static images
What Google Doesn't Want (And Why They'll Reject You)
This is where I learned some expensive lessons.
Text overlays: Google has this 20% text rule. Except it's not really 20% anymore. They eyeball it now. I had an image with three words get rejected, and another image with a paragraph get approved. My theory? It's about readability and whether the text looks "spammy."
Borders and frames: If your image has a border that's too thick or looks like a button, rejected. Google thinks you're trying to trick people into clicking. Even if you're not.
Stretched or weird ratios: Upload a 1000×1001 image? Rejected. They want clean ratios. 1:1, 16:9, 4:5, 9:16. Stick to those.
Blurry or pixelated images: This one's obvious but I see it all the time. If you're resizing an image, don't just stretch a small one bigger. Start with a high-res image and scale down. Quality matters.
Common Rejection Reasons & Solutions
| Rejection Reason | What Triggers It / How Common | Real Example / Solution | Prevention |
|---|---|---|---|
| Too much text | >20% text coverage (estimate) / Very common | Product label visible / Zoom in to hide text, use ad copy instead | Keep text to 2-3 words max |
| Thick borders | Border >5px or looks clickable / Common | Frame around image / Remove all borders | Use clean, borderless images |
| Wrong dimensions | Non-standard aspect ratio / Rare | 1000×1001 pixels / Use exact Google specs | Stick to standard ratios |
| Low quality | Pixelated or blurry / Common | Small image stretched / Start with 2x size, scale down | Never upscale images |
| Prohibited content | Alcohol, weapons, etc / Common | Beer bottle visible / Remove/blur item | Check Google policies |
| Misleading elements | Fake buttons, play icons / Common | Big "CLICK HERE" text / Remove UI elements | No fake CTAs |
| File too large | >5MB (theoretical limit) / Rare | Uncompressed PNG / Compress properly | Aim for <200KB |
| Trademark issues | Brand logos without permission / Rare | Nike logo visible / Remove logos | Use generic images |
| Sexual content | Even subtle suggestive / Occasional | Model in swimsuit / Use conservative images | When in doubt, don't |
| Poor quality design | Looks spammy / Occasional | Cluttered collage / Simplify design | Clean, professional look |
My Rejection Success Rate:
- First upload: 85% approval
- After tweaks: 95% approval
- After 3 tries: 99% approval (give up on that 1%)
The Compression Dance
Here's where it gets tricky. You want the file small enough to load fast but big enough that it doesn't look like garbage.
What I do now:
- Start with the highest quality image I have
- Resize to the exact dimensions Google wants (using the list above)
- Export at 80-85% quality for JPEG, or convert to WebP
- Check the file size – if it's over 200KB, I compress more
- Look at it on my phone to make sure it still looks good
The phone check is important. What looks fine on a 27-inch monitor can look like hot garbage on a phone screen.
Real Example: What I Did Wrong
Last month I was running ads for a client. Made this beautiful image – product photo, clean background, nice colors. 1200×1200 pixels, 140KB JPEG file. Perfect, right?
Rejected.
Reason? The product packaging had text on it that Google's algorithm thought was too much. Even though it was literally just the product label.
So I took the same photo, zoomed in tighter on the product so less of the label was visible. Same file format, similar size. Approved in 10 minutes.
The lesson? Sometimes Google's algorithm is just weird. Don't take it personally. Try small variations.
My Current Workflow
Since I do this a lot now, here's my exact process:
- Design the image at 2400×2400 if it's square (2x the final size)
- Use actual photos when possible, not stock images (Google seems to prefer real stuff)
- Keep text minimal – if I need text, I put it in the ad copy instead
- Export as JPEG at 85% quality
- Run it through a compressor if it's over 150KB
- Upload and pray
Yeah, "pray" is part of my workflow. Because even when you do everything right, sometimes Google just says no.
My Google Ads Image Upload Workflow
Loading diagram...
Tools I Actually Use
I'm not trying to sell you anything here. This is just what works for me:
- Figma for design (free tier is fine)
- Image Kit on this site for quick compression
- TinyPNG as a backup compressor
- Squoosh when I need to convert to WebP
The built-in export tools in Photoshop or Figma work fine too. Don't overcomplicate it.
What Changed in 2025
A few things are different this year:
WebP is more accepted: I'm seeing better performance with WebP files now. They load faster and Google's crawler seems to like them.
Mobile-first: More people see ads on phones now. So vertical images (like 960×1200) get better engagement than they used to.
Quality over size: I used to obsess over getting files under 100KB. Now I aim for under 200KB but focus more on quality. The internet is faster, people have better phones, and a crisp image converts better than a compressed mess.
What Changed: 2020 vs 2025
| Factor | 2020 | 2025 | Impact on Strategy |
|---|---|---|---|
| File Size Limit | Strict <150KB | Flexible <200KB recommended | Can prioritize quality more |
| WebP Support | 70% browsers | 97% browsers | Use WebP by default now |
| Mobile Traffic | 60% of ad views | 80% of ad views | Vertical formats more important |
| Text Rule | Strict 20% rule | Eyeball algorithm | Focus on readability, not percentage |
| Approval Speed | 24-48 hours | 10-30 minutes | Faster iteration possible |
| Quality Standards | Medium acceptable | High quality expected | Users expect sharp images |
| Aspect Ratios | Flexible | Strict standard ratios | Must use 1:1, 16:9, 4:5, 9:16 |
| Responsive Ads | Optional | Expected | Need multiple sizes |
| Average File Size | 80-120KB | 150-200KB | Bigger files acceptable |
| PNG Usage | 30% of ads | 10% of ads | JPEG/WebP dominate |
Key Strategy Shifts 2025:
- Prioritize WebP over JPEG
- Focus on mobile-first vertical formats (4:5 ratio)
- Don't stress about hitting exactly 150KB
- Quality > Size (within reason)
- Multiple aspect ratios required for responsive campaigns
When Nothing Works
Sometimes you'll do everything right and still get rejected. Here's what I do:
- Try a different aspect ratio
- Reduce text even more (even if it's already minimal)
- Change the file format
- Upload during different times of day (yeah, I tested this – doesn't matter, but I still do it)
If it's still rejected after three tries, I move on. Not worth the headache. Make a different image.
The Bottom Line
Google Ads image requirements aren't rocket science, but they're also not as simple as "under 150KB, any size." Pay attention to exact dimensions, keep your images clean and sharp, and don't try to be too clever with text overlays.
Start with the standard sizes I listed above. Export clean files. Check them on mobile. Most of the time, that's all you need.
And when it doesn't work? Don't stress. Even Google doesn't always know what Google wants.
Data Sources
This article is based on global best practices and standards:
- Google Ads Specs: Google Ads Help Center
- Image Requirements: Google Ads Creative Specifications
- Best Practices: Google Ads Learning Center
Note: Tool availability, features, and best practices may vary by region. Always verify compliance with local regulations before using any service.
Related Reading
Explore more image optimization articles to improve your ad performance:
- WebP vs JPEG vs PNG: Which One Should You Actually Use? - Image format comparison guide
- How I Compress Images Without Making Them Look Like Trash - Image compression best practices
- Batch Processing 500 Images: What I Learned the Hard Way - Efficient batch processing workflow
- Responsive Images with Srcset Guide: Stop Serving Wrong Sizes - Serve optimal images for different devices
Related guides worth indexing with this article
Batch Processing 500 Images: What I Learned the Hard Way
Had to process 500 product images last month. Did it wrong the first time and wasted 6 hours. Here is the right way to do it.
Lazy Loading: How Loading 100 Images Slower Made Page Load Faster
Blog had 100 images per page. Load time: 12 seconds. Added lazy loading. Load time: 2 seconds. Here is how it actually works.
Responsive Images: Why My 4K Photo Looked Terrible on Phones
Uploaded beautiful 4K photos to website. Looked perfect on desktop. Tiny and blurry on phones. Took me days to figure out responsive images.