The demand is usually the tag itself. A portal may reject a picture that already has enough pixels because the embedded number still says 72, or a shop form may ask for 300. SetDPI is that tag change and nothing broader: no print bureau, no account, and no separate company behind the name on this card.
SetDPI rewrites density metadata that a JPEG or a PNG already carries. In a JPEG the number sits in a JFIF density field or an EXIF resolution tag. In a PNG it sits in the pHYs chunk. The tool writes a new DPI or PPI value into that field. It does not resample, so the pixel width and pixel height stay as they were, and a blurry photo stays blurry. This is not an AI enlarger and it does not add detail that was never captured.
Pixel dimensions, the DPI label, and the printed size are three different things. Dimensions count the samples in the file. The label is only metadata, such as 300. Printed size is the dimensions divided by that label. A shop that says 300 DPI may mean the label, a physical size, or both. The DPI calculator and the 300 DPI in pixels page keep those questions apart. JPEG and PNG are the formats in scope. TIFF, WebP, HEIC, and RAW are outside this tool.
This repository has no automated image-regression suite. The evidence folder contains traffic screenshots, not before-and-after picture fixtures, so this page does not claim that every JPEG or PNG variant was tested.
The A4 calculator rows and the matching FAQ follow one formula. A4 paper is 210 mm by 297 mm. At 300 DPI, round(210 / 25.4 × 300) is 2480 and round(297 / 25.4 × 300) is 3508. The same steps give 1240 by 1754 at 150 DPI and 4961 by 7016 at 600 DPI. You can repeat that arithmetic on a calculator.
You can check a file yourself. Record the pixel width and height, set a new DPI, and save. Confirm elsewhere that the pixel dimensions are unchanged and that the density label matches. Compare the byte count too: rewriting JFIF, EXIF, or pHYs data can change the file size without resampling. After the page loads, turn networking off and repeat. If the new label still saves, that step did not use a conversion server. These are checks for you to run. They are not a completed test log. This About page was revised on 17 October 2026, and that date is not a site-wide retest.
The image step runs in the browser on the file you choose. There is no upload form for that conversion, and the rewrite does not send the picture to a server. Loading the site is a separate matter. The pages request their own files, and they include analytics scripts from Google Analytics and Microsoft Clarity plus an advertising script. Those scripts can store cookies and send browser data to their providers. The privacy policy describes that activity. This page does not promise a visit with no cookies and no analytics.
Mail is a different channel. A message to support@setdpi.com sends what you typed, because you chose to send it. Do not attach the private photo. Use the contact page for the field list.
SetDPI is an independent project. It is not affiliated with, endorsed by, or sponsored by Adobe, Apple, Microsoft, Google, Canon, Epson, or any printer maker. Product names appear only to describe a task a reader might be doing. All writing on this site is original. There is no paid plan on this site, and this page does not promise that later changes will stay free.
Send corrections to support@setdpi.com. A useful note names the page URL, the browser and operating system, the file type, the pixel dimensions, the original DPI, the target DPI, and the expected result next to the actual result. No reply time is promised.