Free Online Image DPI Converter and JPG DPI Converter

Change Image DPI Without Confusing Metadata With Image Detail

Use the Image DPI Converter when a printer, publisher, marketplace, photo workflow or document submission process asks for a particular image density such as 150, 300 or 600 DPI. The tool should support JPG, PNG and WebP, show the image’s real pixel dimensions, display any readable density metadata, and let the user choose between two very different operations: changing density metadata only or resampling the image to maintain a chosen physical print size.

That distinction matters. A digital photo is fundamentally a grid of pixels. If a file is 3000 × 2000 pixels, changing a resolution field from 72 to 300 does not manufacture extra camera detail. It changes how software may interpret those existing pixels when a physical size is involved. Resampling is different because it actually creates or removes pixels.

The safest workflow is therefore simple: first decide the final print size, then determine how many pixels are required, then decide whether a metadata update is enough or whether the pixel dimensions must change.

Free Online PNG DPI Converter and WebP DPI Converter

The same core idea applies across JPG, PNG and WebP, but the formats do not store density information in exactly the same way.

JPEG files can contain density information in JFIF metadata and can also carry EXIF resolution fields. PNG uses an optional pHYs chunk that stores pixels per unit, with metres as the defined absolute unit. WebP can contain EXIF and XMP metadata inside its RIFF container, but it does not have a PNG-style dedicated pHYs density chunk. Because applications differ in which metadata they preserve or read, the tool should verify its own output after conversion and display the detected value to the user.

A conversion result should therefore say what changed, not merely “success.” For example:

• Pixel dimensions: unchanged at 3000 × 2000
• Density metadata: updated to 300 PPI
• Estimated print size at 300 PPI: 10 × 6.67 inches
• Resampling: not used

That result is much more useful than pretending the image became “higher quality.”

What Image DPI Actually Means

In everyday search language, people often say an image is “300 DPI.” Technically, the raster image is better described in pixels per inch when those pixels are mapped to a physical print size. DPI, or dots per inch, is more properly associated with printer output dots. The terminology overlaps in real workflows, so this site can use the familiar phrase “image DPI” while teaching the more accurate relationship.

The basic print relationship is:

print width in inches = pixel width ÷ PPI

and:

required pixel width = print width in inches × target PPI

For a 3000-pixel-wide image:

Nothing in the pixel grid changes in this example. Only the intended density and resulting physical size change.

DPI vs PPI in Practical Use

PPI describes image pixels mapped per inch. DPI describes printer dots per inch. A printer may use several microscopic ink dots to represent color and tone for one image pixel, so a printer advertised at a high hardware DPI does not mean the image itself must contain the same number of pixels per inch.

For photo preparation, the user normally needs to answer a PPI question: how many source pixels will be available for each printed inch? This is why 300 PPI is a common high-detail planning target for close-viewed photographic printing, while large work viewed from farther away can often use a lower image PPI. The printer or print lab’s own specification remains the final requirement.

Metadata Only Mode

Choose metadata only mode when the image already has enough pixels and a workflow simply needs a different declared density.

Example: an image is 1800 × 1200 pixels.

At 150 PPI, its interpreted print size is:

• 1800 ÷ 150 = 12 inches
• 1200 ÷ 150 = 8 inches

If the same pixels are tagged as 300 PPI, the interpreted print size becomes:

• 1800 ÷ 300 = 6 inches
• 1200 ÷ 300 = 4 inches

The image still contains exactly 2.16 megapixels. No detail was added or removed. For this reason, metadata only mode should preserve the pixel dimensions and, where the format permits, write the requested density fields.

Maintain Print Size Mode

Choose maintain print size mode only when the user wants to keep the physical print dimensions while changing the target PPI. That requires a new pixel count.

Suppose a 1200 × 1800 image is treated as 8 × 12 inches at 150 PPI. To keep an 8 × 12 inch output at 300 PPI, the image would need:

• 8 × 300 = 2400 pixels
• 12 × 300 = 3600 pixels

The tool therefore has to resample from 1200 × 1800 to 2400 × 3600. Interpolation can make an enlargement smoother and can satisfy a required pixel dimension, but it cannot recreate fine detail that the original never captured. The result should be described as an upsampled image, not as newly captured high-resolution detail.

Change Image to 150 DPI

A 150 PPI target is often useful for large pieces that are not examined at very close range, or for workflows that explicitly request 150. Do not choose it because it is automatically “good” or “bad.” Calculate the required pixels for the finished size.

A 20 × 30 inch print at 150 PPI needs 3000 × 4500 pixels. If the image already has those pixels, metadata alone may be enough for a workflow that reads density metadata. If the source is only 1500 × 2250, maintaining 20 × 30 inches at 150 PPI would require upsampling by 2× in each dimension.

Change Image to 300 DPI

Three hundred PPI is a common planning target for detailed prints viewed at close range. A 4 × 6 inch photo requires about 1200 × 1800 pixels at 300 PPI. An 8 × 10 inch print requires 2400 × 3000 pixels.

Before converting, compare the final crop with those requirements. A camera file may have enough total pixels, yet an aggressive crop can leave too few pixels for the intended print size.

Change Image to 600 DPI

A 600 PPI request should be treated as a workflow-specific requirement, not as a universal photo-quality upgrade. At 600 PPI, an 8 × 10 inch image would require 4800 × 6000 pixels, or 28.8 megapixels.

Higher sampling densities can be useful in specialized scanning, archival capture, fine line work, small text rendered as raster imagery, or production systems that explicitly request them. For many ordinary photographic prints, simply doubling a 300 PPI file to 600 PPI through interpolation creates a much larger file without doubling real captured detail.

Resize Image for 300 DPI

If the physical print size is known, calculate the pixels rather than guessing.

For inches:

pixels = inches × 300

For centimetres:

pixels = (centimetres ÷ 2.54) × 300

For millimetres:

pixels = (millimetres ÷ 25.4) × 300

A 10 × 15 cm photo at 300 PPI needs approximately:

• Width: 10 ÷ 2.54 × 300 ≈ 1181 pixels
• Height: 15 ÷ 2.54 × 300 ≈ 1772 pixels

If the image’s aspect ratio does not match 10:15, it must either be cropped, fit with unused space, or printed at a slightly different size. Stretching one axis independently would distort the image.

JPG DPI Conversion

JPG and JPEG are the same common image format naming convention. A JPEG can contain a JFIF header with density units and horizontal and vertical density values. It can also contain EXIF metadata with resolution fields. Because different software may read or preserve these fields differently, a robust converter should write a consistent value where technically appropriate and then read the result back for verification.

Compression is a separate issue. Re-encoding a JPEG at a low quality setting can introduce artifacts even if its PPI metadata is correct. A DPI conversion workflow should therefore avoid unnecessary recompression when possible and use a sensible quality setting when re-encoding is required.

PNG DPI Conversion

PNG does not store a simple “DPI” field in the same form as JFIF. Its optional pHYs chunk stores pixels per unit on the X and Y axes. When the unit is metres, a 300 PPI target is approximately 11,811 pixels per metre because one inch is exactly 0.0254 metres.

Useful approximate conversions are:

If no pHYs chunk exists, the PNG still has perfectly valid pixel dimensions. Its physical pixel size is simply unspecified by that mechanism.

WebP DPI Conversion

WebP supports EXIF and XMP metadata in its container, so density-related EXIF fields can be carried. Compatibility is less predictable than with established print-oriented JPEG workflows because some encoders, editors or web pipelines may strip metadata and some applications ignore a density value entirely.

For that reason, a WebP DPI result should include a compatibility note. If a print service specifically requires embedded image density and has inconsistent WebP support, exporting an accepted JPEG or PNG may be the safer production choice.

Supported Image Information to Show

After upload, the tool should display:

• file format
• pixel width and height
• megapixels
• aspect ratio
• file size
• detected horizontal and vertical density when present
• estimated physical print dimensions at the detected density
• estimated print sizes at 150, 200, 240, 300 and 600 PPI
• whether the requested operation is metadata only or resampling

This turns a converter into a decision tool instead of a single number changer.

How to Use the Free Online DPI Converter

1. Upload a supported JPG, PNG or WebP image.
2. Review the current pixel dimensions and any detected density metadata.
3. Choose 150, 300, 600 or enter a custom DPI/PPI value.
4. Select metadata only if you want to preserve the exact pixel grid.
5. Select maintain print size only if you understand that the image must be resampled.
6. If maintaining print size, review the new pixel dimensions before processing.
7. Convert the image.
8. Verify the output summary.
9. Download the converted image and, for important print work, check the file in the application or print-service workflow that will actually use it.

Privacy and Temporary Processing

The planned production implementation should process uploaded images only for the requested operation and should not intentionally keep the files after processing. Because the final architecture may use a Next.js backend for formats or metadata operations that are not reliable in the browser, the public privacy copy must not claim that every image always remains on the user’s device unless the final implementation genuinely works that way.

Before launch, verify the actual upload path, temporary-file behavior, logs, hosting-provider behavior and retention policy, then make the privacy statement match the implementation exactly.

Common Mistakes to Avoid

The first mistake is changing 72 to 300 and assuming the file gained detail. It did not unless the pixel dimensions also changed, and even then new pixels came from interpolation rather than new capture information.

The second mistake is ignoring print size. A 3000-pixel-wide image can be 300 PPI at 10 inches or 150 PPI at 20 inches.

The third mistake is trusting one metadata label more than the actual pixel dimensions. For print decisions, calculate effective PPI from the pixels that remain after editing and the final physical size.

The fourth mistake is treating 300 PPI as a universal acceptance rule. It is a useful common target, but viewing distance, print process, image content and supplier requirements matter.