Image Resolution Guide

A digital image is made of pixels. An image that is 1200x800 pixels has 1200 pixels across and 800 pixels down. This is the practical size that matters for websites, screens, thumbnails, and social media.

More pixels can hold more detail, but they also increase file size. The right resolution is the one that fits the display need without being unnecessarily large.

DPI means dots per inch and is mainly relevant when printing. A 1200x800 image is still 1200x800 pixels whether the metadata says 72 DPI or 300 DPI. The DPI value can affect print size, but it does not magically change the number of pixels.

For websites, focus on pixel dimensions. If a site asks for 1000x1000 pixels, changing DPI alone will not satisfy that requirement.

An image looks sharp when it has enough pixels for the space where it appears. If a 400 pixel image is stretched across a 1200 pixel container, it will look soft. If a 3000 pixel image is displayed at 600 pixels, it may look sharp but waste bandwidth.

High-density screens can benefit from slightly larger images, but that does not mean every image should be uploaded at full camera size.

Resolution is not only about total pixels. The shape of the image matters. A 1200x1200 square image and a 1200x675 wide image both have useful roles, but they fit different layouts.

Before resizing, identify both the needed dimensions and the needed aspect ratio. This prevents stretching and awkward cropping.

Resolution decisions should happen before editing and exporting. If you crop an image too tightly and then enlarge it later, the result may look soft. If you keep a larger source version, you can create several exports for thumbnails, banners, and social posts without losing flexibility.

For websites, resolution also affects performance. A high-resolution original is useful for editing, but the published version should match the layout. This is why many teams keep source images separately from optimized web exports.

A 400x400 image may be enough for a small avatar, but it is not enough for a large website banner. A 1280x720 image works well for many video thumbnails, but it may not be the right shape for a vertical story. A 3000 pixel photo may be useful as a source file, but it is often too large to publish directly in a blog post.

Resolution should always be paired with purpose. If the image is decorative, smaller dimensions and stronger compression may be acceptable. If it is a product photo or portfolio image, more detail may be needed. If it contains text, readability matters more than file size alone.

When creating multiple versions, name them clearly so the purpose is obvious. For example, keep a source image, a web image, a thumbnail, and a social image as separate files. This avoids confusion and makes it easier to update assets later without losing the original quality.

Avoid judging resolution only by file size. A large file can still be blurry if the source was low quality, and a small file can look sharp if it has the right pixel dimensions for its display size. Check the actual dimensions and preview the image where it will be used.

When working with clients or collaborators, specify resolution in pixels instead of vague terms like high quality or web size. A request for 1200x800 pixels is clear, while high quality can mean different things to different people. Clear dimensions reduce revisions and make it easier to prepare images for websites, ads, forms, and social media.

If an image must work in more than one layout, start with the largest practical source and create separate exports for each use case. This is better than stretching one small file across every design.

Preview the final placement too.