Why does a photo that looks crisp on your phone turn into a blurry mess on a banner — and why does a print shop reject a file your website happily displays? It almost always comes down to image resolution, the most misunderstood spec in the whole process. Get it wrong and you either publish soft, pixelated images or bog your site down with files ten times bigger than they need to be. This guide makes resolution make sense for both web and print, in plain terms.
Pixels: what resolution really means
A digital image is a grid of coloured dots — pixels. Its resolution is how many pixels it contains, written as width × height, e.g. 4000 × 3000. More pixels means more detail and more flexibility to display or print large.
That pixel count is the single most important number. Everything else — DPI, file size, “high-res” — flows from it. A 6000-pixel-wide image is genuinely high resolution; a 600-pixel one is not, no matter what label it’s given. When someone asks if a photo is “big enough”, they’re really asking how many pixels it has relative to where it’s going.
DPI and PPI: where most confusion lives
DPI (dots per inch) and PPI (pixels per inch) describe how densely those pixels are packed when displayed or printed — not how many there are. This is where people tie themselves in knots.
- For screens, DPI is irrelevant. A screen shows an image by its pixel dimensions, full stop. A “72 DPI” tag on a web image is a leftover myth — what matters is the pixel count.
- For print, DPI matters a lot. Printing spreads your pixels over a physical size. The standard for sharp print is around 300 DPI. So a 3000-pixel-wide image prints sharply at about 10 inches wide (3000 ÷ 300).
The practical takeaway: changing the DPI number alone does nothing to a screen image. To print bigger and stay sharp, you need more actual pixels.
Resolution for the web
On the web, you want enough pixels to look crisp on modern high-density screens, but not so many that the file is bloated and slow. Sensible starting points:
- Full-width hero / banner: around 1920–2560 pixels wide.
- Standard content image: roughly 1200–1600 pixels wide.
- Product thumbnail: 400–800 pixels wide.
- Social posts: commonly around 1080 pixels on the relevant side, though platforms vary.
Because today’s phones and laptops have high-density (Retina-style) screens, it’s wise to supply images at roughly double the displayed size, then compress. That keeps them sharp without serving needlessly huge files. Note that resolution and file weight are linked but separate concerns — a big image still needs compressing, which is its own topic.
Resolution for print
Print is where under-resolution shows up brutally, because there’s no screen to hide behind. Working at ~300 DPI, here’s roughly what you need:
- Business card / small flyer: a couple of thousand pixels is plenty.
- A4 brochure page: around 2500 × 3500 pixels.
- A1 poster: several thousand pixels on the long edge.
- Large-format banner / backdrop: very large pixel dimensions — though viewing distance helps, so banners seen from metres away tolerate lower DPI.
The honest rule: you can always make a big image smaller, but you cannot conjure real detail when enlarging a small one. AI upscaling has improved, but it invents detail rather than recovering it, and it shows on close inspection. Shooting at high resolution from the start is the only reliable insurance.
Why “bigger isn’t always better”
It’s tempting to think maximum resolution everywhere is safest. It isn’t. Oversized images on a website slow page loads, hurt the experience and can drag on search performance — a real concern for Singapore sites competing on speed. The smart approach is to capture and archive at high resolution, then export the right size for each use: large for print, optimised for web. One master, many fit-for-purpose versions. Setting up that asset structure is part of how our photography and content team delivers shoots, so you get files sized for every channel rather than one giant file you have to wrangle. You can see the range of formats across our portfolio.
A quick checklist before you publish or print
- For web: is the image roughly the right pixel width for its slot (and ideally compressed)? Not a 6000-pixel original dumped straight in.
- For print: does the pixel count divided by the print width in inches land near 300? If it’s well below, it’ll look soft.
- Always keep the high-res master so you can re-export any size later.
- Never enlarge a small image and expect new detail — go back to the original or reshoot.
Frequently asked questions
What resolution do I need for a website image?
Match the pixel width to where it’ll display — roughly 1920–2560px for full-width heroes, 1200–1600px for content images, 400–800px for thumbnails. Supplying around double the displayed size handles high-density screens; then compress for speed.
What does 300 DPI mean and do I always need it?
300 DPI is the print-sharpness standard — 300 pixels packed into each printed inch. You need it for close-viewed print like brochures and cards. Large banners viewed from a distance can use less. For screens, DPI doesn’t apply at all; only pixel dimensions matter.
Can I enlarge a small photo to print it big?
Not without quality loss. Enlarging stretches existing pixels, and AI upscaling invents detail rather than recovering real information. For sharp large prints, shoot at high resolution from the start or go back to the original file.
Need images that work for both web and print? Tell us how you’ll use them and we’ll capture and deliver them at the right resolution for every channel.
