Best Image Size for Mobile: A Complete Guide
Are your images killing your mobile speed? Learn how to size images correctly for iPhone and Android devices using srcsets.
TL;DR (Mobile Best Practices)
Last updated: Jan 2026
- Max Width: Serve ~1200px images for high-density phones.
- Format: Use WebP or AVIF (smaller & faster).
- Tech: Use
srcsetto let the browser pick the best size.- Don't: Rely on CSS resizing alone.
More than 60% of web traffic comes from mobile devices. Yet, many websites still serve 3000px wide desktop wallpapers to 360px wide iPhone screens.
This is a disaster for performance.
The Golden Rule of Dimensions
Never serve an image larger than the effective display size required by the device.
Google recommends responsive images to avoid serving unnecessarily large files on mobile devices.
Mobile Size Reference Table
| Use Case | CSS Width | DPR | Recommended Image Width |
|---|---|---|---|
| Mobile Content | 360px | 2x-3x | 720px - 1080px |
| Mobile Hero | 390px | 3x | 1200px |
| Tablet | 768px | 2x | 1536px |
| Desktop Hero | 1200px | 2x | 2400px |
For a modern smartphone:
- Logical Width: ~390px (iPhone 14)
- Pixel Density (Retina): 3x
- Ideal Image Width: ~1200px max.
Why "Resizing in CSS" Isn't Enough
You might think: "I set width: 100% in CSS, so it fits!"
Visually, yes. But the browser still had to download the full 5MB file just to shrink it down.
Performance Impact (Core Web Vitals)
- LCP: Oversized hero images delay paint significantly.
- INP: Large decode cost blocks main thread interactivity.
- CLS: Incorrect sizes cause layout shifts if aspect-ratio is missing.
The Solution: Responsive Images with srcset
The srcset attribute allows you to provide multiple files, and the browser picks the winner.
<img src="small.jpg"
srcset="small.jpg 500w,
medium.jpg 1000w,
large.jpg 2000w"
sizes="(max-width: 600px) 100vw, 50vw"
alt="Responsive image">
Before vs After: Mobile Image Sizing
| Scenario | Dimensions | File Size | LCP Score |
|---|---|---|---|
| Before | 3000px JPG | 520 KB | 🐢 3.1s |
| After | 1200px WebP (srcset) |
130 KB | ⚡ 1.9s |
Common Mistakes to Avoid
- Desktop Images on Mobile: Serving a 3000px hero image to a phone wastes huge data.
- CSS-Only Resizing:
width: 100%scales the image visually but still downloads the full file size. - Missing
sizes: Without thesizesattribute, the browser defaults to 100vw, defeating the purpose ofsrcset.
Recommended Breakpoints for 2026
If you are generating image variants, aim for these widths:
- 600px: For standard mobile screens.
- 1200px: For tablets and high-density mobile.
- 1920px: For desktop hero images.
Tools to Automate This
- Next.js Image: Automatically generates these variants.
- WordPress: Native support by default.
- Manual: Use our Image Resizer to create a mobile-optimized copy manually if you have a static site.
Conclusion
Mobile speed is a significant ranking factor, especially through Core Web Vitals. Sending 4K images to a phone is the easiest way to lose rankings. Resize your assets.
Rule of Thumb (2026): Never serve images larger than 1200px wide to mobile devices. Use srcset so browsers choose smaller files automatically.