Does DPI Matter for Web Images? The 72 DPI Myth Explained

For normal web images, pixel dimensions and rendered CSS size matter more than a 72, 96 or 300 DPI metadata setting. Here’s what DPI/PPI actually changes.

On this page15 sections
  1. DPI and PPI are not exactly the same thing
  2. Where the 72 DPI idea came from
  3. What happens if you change only PPI metadata?
  4. CSS uses 96 px per CSS inch—but that does not mean “export at 96 DPI”
  5. CSS pixels vs physical device pixels
  6. Why 300 PPI matters in print
  7. What should web designers care about instead?
  8. Does removing resolution metadata change visual quality?
  9. What about 1x, 2x and Retina assets?
  10. Example: 1200×800 at 72 vs 300 PPI
  11. When a “DPI problem” is actually something else
  12. How to prepare web images without a DPI rule
  13. Resize actual pixels, not metadata
  14. Frequently asked questions
  15. Sources and further reading

You have probably heard one of these rules: “web images must be 72 DPI,” “screens are 96 DPI,” or “use 300 DPI for quality.” Each statement mixes together print concepts, CSS units and physical display density.

For normal images displayed in a browser, the practical web question is usually how many pixels does the image contain, and how large will the browser render it? A PPI/DPI metadata value does not magically add or remove those pixels.

Short version: a 1200×800 image remains 1200×800 whether its metadata says 72 PPI or 300 PPI. For web sharpness, focus on pixel dimensions, rendered CSS size, responsive source selection and device pixel ratio.

DPI and PPI are not exactly the same thing

PPI means pixels per inch and is relevant when mapping digital pixels to a physical size, especially in print preparation.

DPI means dots per inch and traditionally describes printer/output dot density. The terms are frequently used interchangeably in casual software interfaces, which is part of the confusion.

Where the 72 DPI idea came from

72 PPI became associated with early desktop publishing and screen conventions, then survived as a web-export rule long after modern display systems became far more diverse.

Today, phones, laptops and monitors can have very different physical densities. Browsers also use CSS pixels as an abstraction rather than exposing page layout directly in physical display dots.

What happens if you change only PPI metadata?

Suppose a JPEG is 1200×800 pixels at 72 PPI. In an image editor, change the metadata to 300 PPI without resampling.

The raster still contains 1200×800 pixels. The file may carry a different suggested print density, but the browser still has the same pixel grid available for normal rendering.

If you instead resample while changing print dimensions, then pixel dimensions can change. That is a different operation.

CSS uses 96 px per CSS inch—but that does not mean “export at 96 DPI”

CSS defines absolute length relationships such that 1in = 96px. MDN describes one CSS pixel as exactly 1/96 of a CSS inch.

This is a definition inside the CSS layout system. It helps browsers relate units such as inches, points and pixels. It does not instruct image editors to tag every raster file with 96 PPI metadata.

CSS pixels vs physical device pixels

A CSS pixel is not always one physical display pixel. On high-density screens, multiple device pixels can represent one CSS pixel. MDN’s devicePixelRatio API reports that relationship.

A 600 CSS-pixel-wide slot on a 2× display can make good use of a source around 1200 pixels wide. That is a pixel-density issue, not a file-metadata PPI rule.

Why 300 PPI matters in print

Printing introduces a physical size. If a 3000-pixel-wide image is printed at 10 inches, that is 300 pixels per inch of printed width. If the same file is printed at 20 inches, it provides only 150 pixels per inch.

The same raster can therefore have different effective print PPI depending on physical output size. That concept is meaningful because inches are real dimensions on paper.

Web layouts are different: an image can fluidly render at many CSS sizes, and screen density varies by device.

What should web designers care about instead?

1. Intrinsic pixel dimensions

Does the source contain enough pixels for the largest intended display slot?

2. Rendered CSS dimensions

How large is the image actually displayed by the layout?

3. Device pixel ratio

Would a higher-density display benefit from a larger candidate?

4. Responsive source selection

Can the browser choose a smaller or larger source instead of every visitor downloading the same file?

5. File size

How many bytes are transferred after dimensions, format and compression are considered?

Our Pixels vs Resolution vs File Size guide connects these measurements in one model.

Does removing resolution metadata change visual quality?

Not in the same way that resizing or recompressing the raster does. If pixel dimensions and pixel values stay the same, deleting a PPI metadata field does not remove visual detail from those pixels.

Other metadata can still matter for workflows, copyright information, orientation, color management or privacy, so “metadata never matters” would be too broad. The narrow point is that a PPI tag is not what gives a normal web image its screen sharpness.

What about 1x, 2x and Retina assets?

These labels describe source density relative to a CSS display size. A 300×200 image used as a 1× source and a 600×400 image used as a 2× source can represent the same visual size with different pixel density.

MDN’s responsive-image guidance supports density descriptors such as 1x and 2x, or width descriptors such as 600w and 1200w. These mechanisms are much more relevant to web sharpness than changing a Photoshop PPI field.

Example: 1200×800 at 72 vs 300 PPI

Take two files with identical pixel data and dimensions: both are 1200×800. One is tagged 72 PPI; the other 300 PPI.

Display both with:

img {
  width: 600px;
  height: auto;
}

For ordinary browser rendering, both have the same amount of source pixel detail for that 600 CSS-pixel slot. The metadata tag does not turn the 300-PPI file into a higher-resolution raster.

When a “DPI problem” is actually something else

If a web image looks blurry, investigate these before changing DPI metadata:

  • the delivered source is smaller than the rendered slot;
  • a CMS generated an unexpectedly small derivative;
  • CSS stretches the image beyond its natural size;
  • the browser selected a small srcset candidate;
  • compression is too aggressive;
  • the original is out of focus or low detail;
  • the image is being transformed or scaled by the layout.

How to prepare web images without a DPI rule

  1. Choose the required composition and aspect ratio.
  2. Measure the largest rendered CSS width.
  3. Create useful source widths, including a larger candidate for high-density displays where appropriate.
  4. Encode each candidate in a suitable web format.
  5. Set intrinsic width/height in markup.
  6. Use srcset/sizes for responsive selection.
  7. Check the actual downloaded resource in DevTools.

Resize actual pixels, not metadata

When your source is far larger than the website needs, use the browser image tool to change the actual width and height, then encode the delivery file. That operation has a direct effect on the raster and often on file size.

Frequently asked questions

Should web images be 72 DPI?

No fixed 72-DPI metadata value is required for normal web display. Pixel dimensions and rendered size are the more useful measurements.

Should web images be 96 DPI because CSS uses 96 px per inch?

No. The 96 relationship belongs to CSS absolute-length definitions. It is not a mandatory image-export metadata setting.

Will 300 DPI make my website image sharper?

Not if the file has the same pixel dimensions. To provide more screen detail, deliver enough source pixels for the rendered size and display density.

What DPI should I use for Retina displays?

Think in source pixels relative to CSS size, not a DPI tag. A 2× density source contains roughly twice the pixel width and height needed for the same CSS display size.

Sources and further reading

Continue the series8 parts

Image Resizing & Dimensions

A practical series on choosing, resizing, cropping, and delivering the right image dimensions for the web.

  1. Image Resizing: The Complete Guide to Dimensions, Resolution and Aspect Ratio
  2. How to Resize an Image Without Losing Visible Quality
  3. Crop vs Resize: What’s the Difference?
  4. Aspect Ratio Explained: How to Resize Images Without Stretching Them
  5. Best Image Size for a Website: Hero, Banner, Blog and Content Images
  6. Best Hero Image Size for Desktop and Mobile
  7. Pixels vs Resolution vs File Size: What Actually Matters on the Web?
  8. Does DPI Matter for Web Images? The 72 DPI Myth Explained