Image DPI Checker and Converter
See the DPI stored in any image, change it to 300 or any value without touching a single pixel, and check the print size.
or browse filesdrop an image here or paste
See the DPI stored in any image, change it to 300 or any value without touching a single pixel, and check the print size.
or browse filesdrop an image here or paste
Drop in a photo and its DPI appears immediately, read straight from the file's own metadata: the EXIF resolution tags and JFIF density of a JPG, or the pHYs chunk of a PNG. You also see where the value came from and what it means physically, because the panel converts it on the spot into a print size, the exact inches and centimeters the image would cover on paper at that resolution. When a file carries no resolution metadata at all, the tool says so honestly instead of inventing a number, and notes that most software will assume 72 in that case.
DPI is not part of the picture, it is a note attached to it, and this converter treats it that way. When you download with a new value, the tool rewrites only the metadata bytes: the JFIF density and the EXIF resolution tags of a JPG, or the pHYs chunk of a PNG. The compressed image data passes through bit for bit, so there is no re-encoding, no generation loss and no quality change of any kind. The file that comes out contains exactly the pixels that went in, now labeled with the resolution you chose. Formats without a standard DPI field are converted once to PNG and tagged there.
The most common reason to be here is a requirement like "images must be 300 DPI". Pick the 300 preset, or 72, 96, 150 and 600 for other targets, or type any custom value, and the live print-size line shows how large the image will print at that setting. That line is the honest check the requirement is really about: a 3000 × 2400 pixel photo at 300 DPI prints 10 × 8 inches, and if you need it bigger than that you need more pixels, not a bigger number in the metadata. Journals, print shops, passport photo services and book publishers all read exactly the value this tool writes.
DPI, dots per inch, only says how densely the pixels should be laid onto paper. Screens ignore it completely, which is why a 72 DPI and a 300 DPI copy of the same file look identical in a browser. It also says nothing about quality: a sharp 12 megapixel photo labeled 72 DPI has exactly as much detail as the same photo labeled 300. The label matters at print time, when layout software divides pixels by DPI to decide the physical size. That is why changing the metadata is legitimate when a workflow demands a specific value, and why this page pairs the change with the print-size math that actually determines how good the print will look.
Everything happens in your browser. The file is read locally, its metadata is parsed and rewritten on your device, and nothing is uploaded to any server. Because the conversion is a byte-level rewrite rather than a re-export, the tool is safe to use on final deliverables: contracts, artwork, ID photos and print-ready files come out with their pixels untouched, their compression intact and only the resolution label changed.
Open the image in the tool and the DPI shows immediately, read from the file's metadata: EXIF and JFIF for JPG, the pHYs chunk for PNG. If the file has no resolution metadata, the tool says "Not set", and most viewers will assume 72 for such files.
No. DPI is a metadata label, not image data. This tool rewrites only the resolution bytes and passes the compressed pixels through untouched, so quality is bit-identical and the file size changes by at most a few bytes. Only the intended print size changes.
Open the image, pick the 300 preset and download. The saved JPG or PNG carries 300 DPI in its metadata, which is what print services and layout software read. Check the print-size line first: pixels ÷ 300 is the size in inches it will print.
Screenshots and many exports simply do not write resolution metadata, and screens ignore DPI entirely, so nothing is wrong with the file. 72 is just the traditional assumed default. It says nothing about sharpness - the pixel dimensions do.
No. The file is read and rewritten entirely in your browser, and nothing is transmitted to any server. Print-ready client work and personal photos stay on your machine.