How to Change Image DPI to 300 for Print and Visa Forms

What DPI Says About Your File

DPI (dots per inch) is a print instruction. Inside a digital image the stored value is really a pixels-per-inch density: it tells a printer or a layout program how large to lay the pixels out on paper. The pixel count itself never changes when the density changes, so the same file is either a small tight print or a large loose one.

Work the division the other way and the number stops being mysterious. A 413 x 531 pixel portrait printed at 300 DPI measures 35 x 45 millimetres, which is a passport-sized photo. Read that identical file as 72 DPI and it measures 145 x 187 millimetres — nearly A5. Nothing about the photograph changed; only the instruction attached to it did.

Screens ignore the field completely. A 413-pixel-wide image occupies 413 CSS pixels on a phone or a monitor no matter whether its header says 72, 300 or 1200. That is why the resolution arguments in design tools are so often about print, and why a web image with a 300 DPI tag is not sharper than one with no tag at all.

• Print width in inches = pixel width / DPI, with the same division for height.
• 2480 x 3508 pixels at 300 DPI is exactly A4 (210 x 297 mm).
• 600 x 600 pixels at 300 DPI is exactly 2 x 2 inches.
• Changing the density field cannot add detail that the sensor never captured.

A Metadata Change Is Not Resampling

There are two different operations hiding behind the phrase increase the DPI, and they have opposite effects on quality. The first rewrites the density value in the file header and leaves the image data exactly as it was: same pixel grid, same JPEG entropy-coded data, byte size almost identical, and zero visual loss. That is the operation a submission form is asking for.

The second is resampling, where software recalculates the picture at a different pixel count. Interpolation invents intermediate pixels, so enlarging softens edges and shrinking discards detail. It is a real edit to the image and it can be useful, but it is not what a 300 DPI requirement means.

The honest limit: a 500 x 700 pixel scan told to be 300 DPI will print at 1.67 x 2.33 inches, which is a small and genuinely sharp stamp. If the same file must fill a 4 x 6 inch print it needs roughly 1200 x 1800 pixels, and getting there is interpolation. No density change can turn a small scan into a large sharp print.

Note: If a portal rejects the file for resolution, check which of the two it actually validated: many forms reject on pixel dimensions, on file size in KB, or on both, and only some read the density tag.

Read the DPI Your File Carries Now

1. Windows Explorer — Select the file and look at the Details pane, or right-click, choose Properties and open the Details tab. Horizontal resolution and Vertical resolution show the stored density. Where the field is blank the file carries no density value at all.
2. macOS Preview — Open the image, press Command-I (Tools, then Show Inspector) and read the General tab, which reports the current dpi alongside the pixel dimensions.
3. A desktop raster editor — GIMP and the other layer-aware editors put the same reading one menu away: open Image Size, switch Resample off, and the document resolution becomes editable without touching the pixel count, which is the cleanest way to see what the label alone will do.
4. In the browser — Drop the file onto the DPI converter. It parses the binary rather than trusting the viewer, shows the existing density and prints the physical size the file would produce at the target DPI.

Note: A JPEG with no JFIF APP0 block and a PNG with no pHYs chunk have no DPI at all. Windows, macOS and browsers then substitute an assumption, usually 72 or 96, which is why the same file can be reported as two different resolutions on two machines.

Set a JPEG or PNG to 300 DPI in the Browser

The converter offers 72, 96, 150, 300 and 600 DPI as one-tap presets and accepts any custom number. 300 is the value print shops, scanned-document rules and most government uploads ask for; 600 is for fine-art or archival output and roughly quadruples the ink coverage a rasteriser has to resolve, not the file's own detail.

For a JPEG the tool writes the Xdensity and Ydensity fields of the existing JFIF header. For a PNG it writes the pHYs chunk, converting the requested density to pixels per metre by dividing by 0.0254 and rounding, because PNG stores metric density rather than imperial. In both cases the pixel payload is copied through untouched, which is why the output weighs almost the same as the input.

WebP is the exception. Lossy WebP has no equivalent density field, so the tool draws the decoded image onto a canvas and exports it as JPEG at 95 percent quality with the density written into the new file. That is a genuine re-encode, so expect the byte size to shift and one generation of compression to be added — convert a fresh copy, not an already-travelled one.

• The download keeps your filename and adds the density: photo.jpg becomes photo-300dpi.jpg.
• Nothing is uploaded. The buffer is read, edited and re-served from local memory.
• Verify after the fact: reopen the result in the same inspector and confirm the value moved while the pixel dimensions did not.

Pixel Counts for the Sizes That Get Asked For

Use pixels = millimetres / 25.4 x DPI, or inches x DPI. The table below is that arithmetic at 300 DPI, the density most submission portals and print shops specify.

Note: Round to whole pixels and keep the aspect ratio. A portal that also caps the file at a few hundred kilobytes will need the compression pass afterwards, not before: resize, then set density, then compress.