How big should images on a website be?
Updated
Make every image no wider than it's shown, at most twice that for sharp screens, then compress it until going further would show. For the largest image near the top of the page, aim for it to finish loading fast enough that Largest Contentful Paint stays at 2.5 seconds or less, which is what Google's web.dev calls good. In practice that usually means a hero image of a few hundred kilobytes at most, and content images well under that.
Why image size matters
Images are often the heaviest thing on a page, and the largest image near the top is often the element that Largest Contentful Paint (LCP) measures. Web.dev counts an LCP of 2.5 seconds or less as good, measured at the 75th percentile of page loads, on phones and computers separately. Every extra kilobyte of that image is time your visitors on slow connections wait.
Core Web Vitals are part of how Google looks at page experience (Google Search Central), so image size is not only about patience: it's part of how your pages are judged.
Step 1: the right number of pixels
An image shown 800 pixels wide on a computer screen needs at most 1,600 pixels for high-density (Retina) screens; any more is downloaded and thrown away. This is where the biggest savings are: a phone or camera photo is often 4,000 pixels wide or more, so resizing it to the size it's shown at removes most of the data before compression even starts.
If the same image is shown at different widths on phones and computers, offer several sizes with srcset and let the browser pick (responsive images on web.dev).
Step 2: compress until it would show
After resizing, compress each image to the point just before the difference becomes visible. Our engine aims for a quality score of 80 by default, where an average person can't tell the result from the original side by side. On our 204 test images, that brought the total down to 35.6% of the original size with PNG and JPEG, and 26.6% with WebP. For your own site, WebP is the easy win: every current major browser shows it.
Practical targets
These are our rules of thumb, not standards. The real test is your LCP on real devices.
| Image | Width (for sharp screens) | Aim for |
|---|---|---|
| Full-width hero | 1,920–2,560 px | under 200–300 KB |
| Image in an article | 1,200–1,600 px | under 100–150 KB |
| Product photo | 1,000–1,500 px | under 100 KB |
| Thumbnail | 300–600 px | under 30 KB |
| Logo or icon | its display size × 2 | a few KB; SVG if you have it |
If an image won't get under its target without looking worse, it's usually too wide for its spot, or it's a photo saved as PNG.
Step 3: load them well
- Give every image its
widthandheight, so the page doesn't jump while it loads (Cumulative Layout Shift). - Add
loading="lazy"to images further down the page (lazy loading on web.dev), but not to the hero: it should load first. - Photos as JPEG or WebP, screenshots and graphics as PNG or WebP. See JPEG vs PNG vs WebP.
Doing it with PicPinch
- Open Resize images and set the maximum width, or use the settings on any page.
- Choose Smallest to allow WebP for your own site.
- Drop in a whole folder. Each image gets the right format and the smallest file that still looks the same, and nothing is uploaded.
Questions
- Is there one right file size for website images?
- No. It depends on how wide the image is shown and what's in it. A detailed photo needs more bytes than a flat graphic at the same width. Start from the display width, then compress until any more would show.
- Should I use WebP on my website?
- Usually yes. All current major browsers show it, and it was the smallest format for most images in our tests.
- Does image size affect Google rankings?
- Not by itself, but Core Web Vitals such as LCP are part of how Google looks at page experience, and large images are a common reason for a slow LCP.
- What about images in emails?
- Keep them small and in JPEG or PNG, because not every email app shows WebP.
Get started: compress images, resize images, PNG to WebP.