Check More Than a Single DPI Number
A useful image DPI checker should not stop after displaying “72 DPI” or “300 DPI.” Those labels can be helpful, but they do not tell you whether the image contains enough pixel information for a real print.
The checker should read the file, report its pixel width and height, show any horizontal and vertical density metadata it can reliably detect, calculate megapixels and aspect ratio, and estimate physical print sizes at common PPI values. It should also tell the user when no absolute density metadata is present.
That last state is important. “No DPI metadata found” does not mean the image has no resolution. A 4000 × 3000 pixel image still contains twelve million pixels. It simply may not contain a usable field telling software how those pixels should map to physical units.
Embedded DPI vs Effective PPI
Embedded density metadata is a value stored in the image file. Effective PPI is a calculation based on actual pixels and intended physical size.
Suppose an image is 3600 × 2400 pixels and its metadata says 72 PPI. If you plan to print it 12 × 8 inches, its effective PPI is:
- 3600 ÷ 12 = 300 PPI
- 2400 ÷ 8 = 300 PPI
The “72” metadata label does not make that 12 × 8 print a 72 PPI print when the layout places all 3600 × 2400 pixels into 12 × 8 inches. This is why the checker should always show both the stored value and practical size-based calculations.
What the Checker Should Read
Horizontal and vertical density
JPEG, PNG and other image formats can store separate X and Y density values. A normal square-pixel photographic file commonly uses matching values, but the checker should preserve the distinction rather than silently collapsing them.
If the two values differ, show both and explain that users should verify the file in the destination application. A non-square interpretation, an unusual metadata block or conflicting metadata can create differences.
Pixel width and height
Pixel dimensions are among the most important values in the report. They tell you how much raster data exists before further cropping or resampling.
Megapixels
Megapixels are calculated as:
pixel width × pixel height ÷ 1,000,000
A 6000 × 4000 image contains 24,000,000 pixels, or 24 megapixels.
Megapixels are convenient for scale, but they do not replace aspect ratio or per-axis requirements. A printer cares about whether both width and height have enough pixels for the final dimensions.
Aspect ratio
Aspect ratio compares image width with height. Common ratios include 3:2, 4:3, 1:1 and 16:9. A mismatch between image ratio and print ratio can force cropping.
For example, a 3:2 photo fits 4 × 6 inches without ratio-based cropping. It does not fit 8 × 10 inches exactly because 8:10 simplifies to 4:5. Some of the long edge must be cropped or a border must be introduced.
File format and file size
The checker should display whether the image is JPG/JPEG, PNG, WebP or another supported format. File size in KB or MB is useful operational information but is not a reliable measure of print detail. A heavily compressed 24-megapixel JPEG can be smaller than a lower-resolution PNG.
What “No DPI Metadata” Means
A digital image can exist perfectly well without a declared physical density. Screen display is usually driven by pixel dimensions, layout rules, CSS, application zoom and device characteristics rather than by an image’s print PPI metadata.
For PNG, the pHYs chunk is optional. If it is absent, the PNG specification still defines the image pixels; the physical pixel size is unspecified. For JPEG, density information may appear in JFIF or EXIF metadata, but exporters can remove or rewrite those fields.
The checker should therefore use language such as:
No absolute density metadata was detected. The image is 4000 × 3000 pixels and can still be evaluated for printing by choosing a physical print size or target PPI.
Estimated Print Size at Common PPI Values
For an image that is 6000 × 4000 pixels:
| Target PPI | Maximum size using all pixels |
|---|---|
| 150 | 40 × 26.67 in |
| 200 | 30 × 20 in |
| 240 | 25 × 16.67 in |
| 300 | 20 × 13.33 in |
| 600 | 10 × 6.67 in |
These are mathematical sizes, not promises of visual quality. Focus, motion blur, noise reduction, sharpening, compression, subject detail, paper and viewing distance also influence the print.
Why Programs May Report Different Density Values
Different applications may read different metadata blocks or apply different defaults when metadata is absent. JPEG is a common example because JFIF can carry density information and EXIF can also include XResolution, YResolution and ResolutionUnit. If these values disagree, software behavior may vary.
Export workflows also matter. A web-oriented export may strip EXIF. A conversion to PNG may translate a density value into pixels per metre. A later optimization pipeline can remove ancillary metadata. This is why “the file says 72 in one app and 300 in another” should be investigated rather than treated as proof that one application changed the pixels.
How to Decide Whether an Image Is Large Enough to Print
Start with the final physical dimensions, not the stored DPI field.
- Find the final crop in pixels.
- Convert the intended print size to inches.
- Divide pixel width by print width.
- Divide pixel height by print height.
- Use the lower result as the limiting effective PPI.
- Compare that result with the print provider’s current requirement and the expected viewing distance.
Example: 4500 × 3000 pixels printed at 18 × 12 inches gives 250 PPI on both axes. The same image at 30 × 20 inches gives 150 PPI.
Neither result is automatically acceptable or unacceptable. The intended viewing condition and production requirement decide.
Checking DPI on Windows and macOS
On Windows, the shell exposes image properties for dimensions and horizontal and vertical resolution when the decoder and file provide them. In practice, users commonly open File Explorer properties and inspect the Details section.
On macOS, Apple Preview provides an Inspector for image information, including image resolution when available. The exact metadata shown depends on the file.
Mobile photo apps often emphasize dimensions, file size and camera information rather than a dedicated print-density field. This is one reason a browser-based checker can be useful across devices.
Common Mistakes
Do not assume that a file with missing DPI metadata is low resolution. Check its pixels.
Do not judge print readiness from megapixels alone. A crop can remove a large part of the available raster.
Do not treat file size as resolution. Compression can make two files with the same pixel dimensions very different sizes.
Do not assume 300 PPI guarantees a sharp print. A 300 PPI file can still be out of focus, over-compressed or badly enlarged before it reaches the checker.
Do not ignore aspect ratio. A “perfect” 2400 × 3000 file for an 8 × 10 print can lose pixels if you later crop it to a different shape.
Using the Checker With Other Site Tools
If the image has enough pixels but the embedded density does not match a required value, open the main Image DPI Converter and use metadata-only mode.
If you know a physical size and need to calculate required pixels, use the DPI Calculators page.
If you are choosing among common print sizes, use the Photo Printing Resolution Checker, which should account for effective PPI and cropping more directly.