DPI is a print-density instruction stored inside a JPEG or PNG file, not a measure of image detail or sharpness. Changing a number in the 72 to 600 range rewrites one small metadata field, JFIF density for JPEG or pHYs for PNG, and leaves the actual pixel grid exactly as it was. A 3000 by 2400 pixel image stays a 3000 by 2400 pixel image after the change; only the suggested print size calculated by a layout program or printer driver shifts. This distinction matters because anyone searching how to change image DPI in GIMP usually has one of two goals: keep the pixels intact and just update the print label, or genuinely produce more or fewer pixels. Those are different operations and they should be treated differently, because Image > Print Size in GIMP performs the first when resampling is disabled and Image > Scale Image performs the second. Choosing the wrong one can quietly enlarge or shrink the pixel grid, alter print sharpness in unintended ways, or duplicate a JPEG encode the image did not need.
What "Changing DPI" Really Does in a File
A JPEG stores DPI inside a JFIF APP0 header segment as two 16-bit integers plus a unit byte, as defined in the W3C JFIF 1.02 specification. The PNG specification places the equivalent value inside a pHYs chunk as a single 32-bit pixels-per-metre count. Both formats carry the same idea: for each physical inch the output device should lay down roughly N pixels taken from the existing pixel grid. The pixels themselves are untouched, the compressed image bitstream is untouched, and the file structure stays valid because only a single small header field is being replaced.
Raising the DPI from 72 to 300 does not invent new pixels, sharpen a blurry photo, make a web browser render the image more crisply, or rescue a low-resolution scan. Lowering the value does not delete pixels either. A printer, layout application, or export workflow may consult the metadata to compute a physical size; a website, by contrast, normally displays an image according to its CSS width or container size and ignores the print field completely.
GIMP's Two DPI Paths: Print Size vs Scale Image
GIMP exposes DPI in two menus that behave very differently. Image > Print Size opens a dialog where you can change the resolution entry; with resampling disabled it writes the new DPI into the file header while keeping the pixel dimensions unchanged. Image > Scale Image is the opposite: it multiplies the canvas by an integer or fractional factor, which means the actual pixel grid shrinks or grows and detail is either added by interpolation or lost to decimation. The single most common mistake is to use Scale Image when Print Size was the intent.
| Operation in GIMP or a browser | Pixel dimensions | Metadata DPI | What the output looks like |
|---|---|---|---|
| Image > Scale Image | Changes (resampled) | Recalculated by GIMP | A new file with the requested pixel count and a fresh DPI label |
| Image > Print Size (resampling off) | Unchanged | Updated to the typed value | The same file with the DPI header rewritten |
| Image DPI Changer | Unchanged | Updated in JFIF or pHYs only | A local copy, no re-encode, no upload |
If GIMP is open and the workflow is comfortable, Print Size is a perfectly valid answer to the question. If the goal is to avoid a re-encode, skip the dialog, or work on a machine without GIMP installed, a metadata-only path produces the same outcome with less risk.
When You Only Want to Change the Metadata
Several situations make a metadata-only path useful. A photographer who already exported a print-ready JPEG and only needs a different DPI label does not want a second lossy encode. A designer who must deliver a file with a print shop's required 300 DPI value does not want the pixel grid quietly doubled. A user on a locked-down work laptop without admin rights cannot install GIMP at all. And anyone handling a sensitive original may prefer a process that runs in the browser without uploading the file. The Image DPI Changer is built for exactly this case: it accepts a single JPEG or PNG up to 25 MiB, reads any existing JFIF or pHYs value, writes a new whole-number DPI, and returns a local copy.
How to Update Image DPI Locally With the Image DPI Changer
- Choose one JPEG or PNG image up to 25 MiB and review any detected print-density metadata the page displays.
- Enter a whole-number target DPI, such as 72, 150, 300, or 600; this value changes the JFIF or pHYs print-density field, not the pixel dimensions.
- Select Update image DPI, download the copy, and verify the intended size in the destination layout application or printer workflow.
The tool runs entirely in the browser. Nothing is uploaded, the compressed image bytes are copied as-is, and the operation does not require a canvas or a second JPEG encode. A failed operation clears its old result link rather than presenting a previous file as though it had just been updated, so the downloaded file always corresponds to the most recent action.
Verifying the Downloaded File
After the download, open the file in any metadata viewer or in the destination layout program to confirm the value landed where that program reads it. A JPEG can carry several kinds of resolution information, including the JFIF density fields in the APP0 segment and optional EXIF resolution tags in the APP1 segment; applications may choose which one they trust. The Image DPI Changer reads and writes the JFIF density fields, dynamically inspects standard EXIF resolution fields after selection, and reports whether it found a usable existing JFIF or pHYs density. It does not attempt to merge or rewrite every possible EXIF, XMP, ICC, IPTC, camera, GPS, or vendor extension.
For a PNG, the W3C PNG Specification Third Edition defines the pHYs chunk as a single integer count of pixels per metre. A DPI like 300 is encoded as 300 ÷ 0.0254 ≈ 11811 pixels per metre, rounded to the nearest integer. Reading the file back may show a DPI value that differs from the request by a fraction of a unit. That small rounding step is a storage precision limit of the PNG format, not a change in the actual image pixels. The round-trip will still fall within rounding error and will not affect the printed size in any visible way.
A Print-Size Calculation You Can Repeat
For one concrete example, take a 3000 by 2400 pixel image and set the DPI to 300. Divide the pixel count by the DPI to get the physical print size:
3000 pixels ÷ 300 DPI = 10 inches wide
2400 pixels ÷ 300 DPI = 8 inches tall
The same 3000 by 2400 pixels at 150 DPI produces:
3000 pixels ÷ 150 DPI = 20 inches wide
2400 pixels ÷ 150 DPI = 16 inches tall
Notice the pixels never change; the only thing that changes is how many of those existing pixels the printer is told to fit into each inch. For more elaborate calculations across unusual paper sizes, the DPI Converter can work out the physical dimensions without ever touching a file.
Common Mistakes With DPI
Reading DPI as a quality number rather than a print-density instruction leads to most of the wrong decisions. A low-resolution scan will not gain detail from a label change, because the source pixels are fixed and the printer has nothing extra to work with. Saving out of GIMP with the Quality interpolation box checked in Scale Image silently enlarges the file and replaces pixels with smoothed approximations, which can actually look softer at print size. Submitting a JPEG with a 300 DPI label to a print shop that also requires a minimum pixel count or a specific export format is incomplete; the label alone never satisfies a pixel-count requirement.
It is also worth remembering that not every program reads the same metadata family. A JPEG can store JFIF density, EXIF resolution, XMP, and ICC data, and a printer driver or layout application may pick any one of them. For a deeper discussion of what DPI actually does and the difference between print density and image detail, the guide on changing DPI without losing quality walks through the same idea with a slightly different framing.
When DPI Metadata Is Not Enough
If the goal is to produce more pixels, changing DPI metadata will not help. An image that needs to grow from 2000 to 4000 pixels on its long side has to be resampled by an actual image editor. The Image Resizer can set exact pixel dimensions in the browser without uploading the file. If the question is purely about the physical size a print layout should reserve, the DPI Converter calculates inches and centimetres from the current pixel grid and the intended DPI. If a metadata field other than DPI needs editing, the EXIF Editor handles a focused set of JPEG EXIF credit fields. None of these tools overwrite pixels unless that is their explicit job, which is why separating metadata changes from pixel changes keeps a print workflow predictable.