72 DPI to 300 DPI
Your image says 72 DPI — screens don't care, but the print shop does. Drop it here and the tag becomes 300 DPI in your browser. Pixels stay the same.
How to convert 72 DPI to 300 DPI in the browser
- Check what the file contains: Drop your screenshot, web image or AI export here and read its actual density and pixel dimensions.
- Compare the 300 result: Keep the 300 target and review the new print-size readout; a starting tag of 72 does not determine the available detail.
- Download without enlarging: Save the edited JPEG or PNG for a print workflow that needs a 300 density label.
The output keeps the original pixel grid. An absent or low density tag is a metadata issue only when the image already has enough pixels for the intended paper size. This tool neither invents extra detail nor guarantees that a printer's upload checks will accept the file.
Why images default to 72 DPI
72 is not a print density. It is a leftover screen convention from the original Macintosh, whose 72 pixels per inch matched the PostScript point so that 12-point type was 12 pixels tall. Browsers, Save for Web, most screenshot tools, and Photoshop’s New dialog often write 72 — or omit the tag, which many readers treat as 72. Screens never consult it. A 1920 × 1080 screenshot looks identical on a monitor whether it is tagged 72, 96, or 300.
That is why the file you just downloaded “says 72 DPI” even though you never chose 72. Three sources dump 72 files into print jobs every day:
Browsers and the web. Right-click Save Image, a screenshot of a landing page, a PNG exported from Canva or Figma for the web — the density field is 72 or blank. The picture looks sharp on a Retina display because the display is counting pixels, not inches. A print RIP does the opposite: it reads 72 and stretches those pixels across a claimed poster.
Photoshop and “new document” defaults. File → New still offers 72 PPI for screen/web presets. Save for Web and many “export for screens” paths strip or rewrite density to 72 even when the working file was 300. A designer who built an 8.5 × 11 in layout at 300, then exported a flattened JPEG for the printer, often hands over a 72-tagged file with the original pixels intact.
AI image tools. Web and AI exports may contain a 72 DPI tag, another density value, or no density metadata. Inspect the actual file before deciding whether its label needs changing. A low or missing density tag can tell a printer to stretch the existing pixels farther than a 300 DPI preflight expects. The honest fix is a tag rewrite when the pixels already cover the print, not a resample, unless the file needs more pixels than it already contains.
The print shop’s preflight does not know or care about that history. It sees 72 and rejects. If you are not sure what the file currently claims, check it on the DPI Checker first.
What actually changes when you convert 72 to 300
Only the density tag. Pixel width and height stay exactly the same. File size stays essentially identical. Quality is identical because the decoder never runs.
What does change is the claimed print size. Print inches = pixels ÷ DPI. Going from 72 to 300 shrinks the claimed inches by a factor of 300 ÷ 72 ≈ 4.17. A 1200 × 1800 px web image tagged 72 claims 16.7 × 25 in — a poster the pixels cannot support. Tagged 300, the same pixels claim 4 × 6 in, which is a real photo-lab size. That is the entire conversion.
| 72 DPI | 300 DPI | |
|---|---|---|
| Typical job | Screens, web, screenshots, AI default | Photo labs, journals, IDs, KDP, Etsy printables |
| 1200 × 1800 px prints | 16.7 × 25.0 in | 4.0 × 6.0 in |
| 2400 × 3000 px prints | 33.3 × 41.7 in | 8.0 × 10.0 in |
| On screen | Identical — monitors ignore the tag | Identical — monitors ignore the tag |
| What preflight sees | Screen-resolution — often rejected | Print-ready — the integer they check |
Rewriting 72 as 300 changes the scale instruction; resampling changes the grid itself. When the image is placed into a fixed-size box in a layout, that box can determine its effective resolution regardless of the tag. Check both the exported file and its final placement instead of using the number 300 as a substitute for a pixel-size check.
For the vocabulary gap between DPI and PPI, read DPI vs PPI. The lossless changer also lives on the homepage.
Check before you convert
Pixels decide the maximum print. The 72 tag does not. Before you send a screenshot or an AI download to a lab, divide each side by 300. If the inches you get are at least the inches you will print, rewrite 72 → 300 and stop. If they are not, you need a larger original.
| Pixel size | Print @ 72 DPI | Print @ 300 DPI | Typical fit at 300 |
|---|---|---|---|
| 1200 × 1800 | 16.7 × 25.0 in | 4.0 × 6.0 in | Standard lab print |
| 2400 × 3000 | 33.3 × 41.7 in | 8.0 × 10.0 in | Framed photo |
| 2550 × 3300 | 35.4 × 45.8 in | 8.5 × 11.0 in | US Letter / KDP page |
| 3000 × 4500 | 41.7 × 62.5 in | 10.0 × 15.0 in | 10 × 15 in print |
Formula again, because it is the only formula that matters: print inches = pixels ÷ DPI, and the centimetre column is inches × 2.54. The tool above computes it live for whatever target you have selected. A tiny readout at 300 DPI means the file is too small for that paper — raising the tag further will only make the claimed print smaller. If you need a different density, 200 DPI and 600 DPI are the same engine with those defaults.
A 1920 × 1080 pixel screenshot describes about 26.67 × 15 inches at 72 DPI, but only 6.4 × 3.6 inches at 300. The second size is smaller because the same pixels are placed more closely, not because the image lost pixels. If you need a 10 × 5.625 inch print at 300, the source must instead supply 3000 × about 1688 pixels after rounding each side to a whole pixel.
Inspect an AI image's actual metadata rather than assuming every generator writes 72. For example, a 1536 × 1024 pixel download covers about 5.12 × 3.41 inches at 300, whatever density label it started with. Decide whether that size is enough before changing the tag. If it is not, obtain a larger source or use a separate enlargement workflow and inspect the result.