Best Image Size for Websites: A Practical 2026 Guide

Illustration of a browser window with a hero image, a content column and a thumbnail slot at different sizes

"What size should my website images be?" has no single answer, but it has a reliable method: an image should be as wide as the largest slot it will ever fill - times two for sharp screens - and not one pixel wider. Everything beyond that is weight your visitors download for nothing. This guide gives the concrete numbers for the slots nearly every site has, and the workflow that keeps them honest.

The two numbers that decide everything

Display size is the width, in CSS pixels, of the slot: a blog column is often 720-800 px, a full-width hero is the visitor's screen, a thumbnail might be 300. Device pixel ratio is how many physical pixels each CSS pixel contains - 2 on most modern phones and laptops. Multiply display width by the ratio (cap it at 2; 3x files are almost never worth their weight) and you have the file width that looks perfectly sharp. A hero shown at 1600 CSS px deserves a 2400-3200 px file; a 4000 px camera original is still oversized for it.

The slot-by-slot cheat sheet

Dimensions are only half the story

A right-sized image can still be overweight if the format and quality are wrong. Photos belong in WebP (or JPG as fallback) at quality 78-85; a 1600 px photo treated this way usually lands between 150 and 400 KB. Graphics with transparency want PNG or lossless WebP. Before uploading anything, run the numbers through the Image Size Calculator: it estimates the file size of given dimensions in each format, so you can plan rather than discover. And if the destination is a social platform rather than your own site, skip the arithmetic - the Social Media Resizer holds the exact presets.

The workflow that keeps sizes right

Sizes drift when every upload is improvised. Fix it with a habit: decide the slot, resize to slot width times two with Resize Image (aspect locked, never stretched), convert to the right format, then compress once - for a whole folder, the Bulk Image Compressor applies one setting to everything and returns a ZIP. Check the busiest detail at 100% zoom, keep the original in an archive, and publish. Five ordered minutes per batch beats any amount of rescuing an oversized library later.

What about responsive images?

Modern sites can serve several sizes of the same picture and let the browser choose (the srcset mechanism), which is the fully correct answer for heroes and product shots. It does not change the arithmetic above - it multiplies it: generate two or three widths (for example 800, 1400 and 2200) instead of one, each properly compressed. Start with the single right size; add responsive variants for the images that carry the page.

Weight budgets: give every slot a KB ceiling too

Pixel dimensions are half the discipline; the other half is a weight budget per slot, because a correctly sized image can still be saved badly. Workable ceilings for most sites: heroes under 350 KB, content images under 200 KB, thumbnails under 60 KB, and product images under 300 KB even with zoom headroom. When an image busts its budget, the fix order is format first (WebP before JPG), then quality (drop five points and compare at 100% - you will rarely see the difference), and only then smaller dimensions. Budgets sound strict until you batch them: a folder run through one consistent pipeline comes in under budget almost automatically, which is the real reason professionals obsess over workflow rather than individual files.

There is no magic number, but there is a magic habit: match the file to the slot, double it for sharp screens, and not a pixel more.

Related tools

Resize ImageImage Size CalculatorSocial Media ResizerBulk Image Compressor