Image DPI Checker in One Sentence
This tool reads an image’s physical resolution metadata so you can check DPI / PPI, identify where that value came from, compare it with the file’s pixel dimensions, and estimate the image’s intended print size without uploading anything.
What This Tool Helps You Check
If you have ever asked “What DPI is this image?” or “Will this file print at the size I expect?”, this tool gives you the answer in a practical way.
Use it to:
- Check image DPI or PPI metadata for JPEG, PNG, and WebP files
- Verify pixel dimensions alongside physical resolution information
- See where the value came from such as JFIF, PNG pHYs, or EXIF
- Estimate print size in inches and centimeters when physical resolution exists
- Confirm whether metadata is actually present instead of assuming every image has DPI stored
- Compare multiple files at once when reviewing exports, print assets, or uploads
- Spot conflicting metadata sources when a file contains more than one resolution entry
- Audit image assets before printing, publishing, or sending to clients
This makes the tool useful for designers, photographers, developers, print workflows, marketplaces, CMS uploads, and anyone who needs a reliable answer about image resolution metadata.
Workflow & Usage
1. Add one or more images
You can:
- Drag & drop files into the upload area
- Click to browse files from your device
- Paste an image from the clipboard when supported by your browser
Supported formats:
- JPEG / JPG
- PNG
- WebP
The tool supports multiple files in one session, so it works well for quick comparisons and batch checks.
2. Let the parser inspect the file
Each file is read locally in your browser. The checker then parses the image structure to find:
- file format
- pixel dimensions
- available physical resolution metadata
- the source of that metadata
- estimated print size when enough information exists
Because the tool reads metadata directly from the file, it can tell the difference between an image that truly has DPI metadata and one that only has pixel dimensions.
3. Review the result card
Each file card gives you a quick summary of the most useful information:
- file size
- format
- dimensions
- detected DPI
- metadata source
- estimated print size
- additional technical details when relevant
You also get a status badge so you can see immediately whether the file has physical resolution metadata or not.
4. Expand the metadata source table
If resolution metadata is found, you can open the detailed section to inspect every source the tool detected.
This helps when:
- a JPEG contains both JFIF and EXIF resolution values
- you want to confirm the tool used the expected source
- you need to understand why two apps report different DPI numbers for the same file
Understanding the Results
DPI / PPI
In everyday use, people often say DPI and PPI interchangeably.
Strictly speaking:
- PPI usually refers to image pixel density
- DPI usually refers to printer dot density
For most practical image workflows, the question is the same: what physical resolution metadata is stored in the file, and what print size does that imply?
This tool focuses on that practical answer.
Pixel dimensions
Pixel dimensions show how many pixels the file contains, such as:
- 1200 × 1800
- 2400 × 3000
- 4000 × 6000
These dimensions define the image’s actual pixel data.
They do not automatically tell you the intended print size unless physical resolution metadata is also available.
Source
The Source field tells you where the DPI or PPI value came from.
Typical sources include:
- JFIF for many JPEG files
- pHYs for PNG files
- EXIF when embedded metadata provides resolution information
Knowing the source matters because some files contain more than one resolution entry, and not every application chooses the same one.
Print size
When the file contains valid physical resolution metadata, the tool estimates the intended print size in:
- inches
- centimeters
This helps answer practical questions such as:
- Will this image print at 8 × 10 inches cleanly?
- Is this export large enough for an A4 layout?
- Did the design app save the correct print settings?
No DPI / Not set
A result like No DPI or Not set does not mean the image is broken.
It usually means:
- the file contains pixel data but no physical resolution metadata
- the exporting app did not write DPI information
- the metadata was removed during optimization, sharing, or conversion
This is common with screenshots, downloaded web graphics, social media images, and some image-processing pipelines.
Mismatch warning
If the tool detects multiple physical resolution sources that disagree, it flags that mismatch.
That warning is useful because it explains why:
- one app may report 72 DPI
- another may report 300 DPI
- the file may contain conflicting metadata written by different tools at different stages
Where the Tool Reads Resolution Metadata From
One of the most important parts of this checker is that it reads resolution data from the image structure itself whenever possible.
JPEG: JFIF first, EXIF fallback
For JPEG files, the tool checks JFIF header data first because that is one of the most common places where JPEG density is stored.
If needed, it can also read EXIF resolution metadata as a fallback.
This is useful because some JPEG workflows write:
- JFIF density only
- EXIF resolution only
- both JFIF and EXIF
PNG: pHYs chunk
PNG does not use JFIF or standard JPEG-style EXIF density storage.
Instead, physical resolution is commonly stored in the pHYs chunk. The tool reads that chunk directly and converts it into a more human-readable DPI value when possible.
WebP: usually EXIF fallback
WebP files do not have a simple dedicated DPI header equivalent to JPEG JFIF or PNG pHYs.
That means physical resolution for WebP is often only available when the file contains embedded EXIF metadata with resolution tags.
In practice, many WebP files have dimensions but no stored DPI at all.
Why DPI Matters — And When It Does Not
For print workflows
DPI matters most when the image is being placed into a physical layout or sent to print.
That includes:
- brochures
- posters
- flyers
- packaging
- photo prints
- magazines
- books
- product inserts
In those workflows, physical resolution metadata helps estimate how large the image can be printed before it starts to look soft.
For digital workflows
For screens, websites, apps, and social posts, the most important factor is usually pixel dimensions, not stored DPI metadata.
A 2000-pixel-wide image is still 2000 pixels wide on the web whether its metadata says 72 DPI, 96 DPI, or 300 DPI.
That is why changing DPI alone usually does not improve web image quality.
For file verification
Even when DPI does not affect the final use case, it can still be useful as a diagnostic clue.
For example, resolution metadata can help you verify:
- whether an export pipeline preserved print settings
- whether two files came from different apps or workflows
- whether a client delivered the intended version of an asset
- whether a CMS or editor stripped metadata during processing
Best Use Cases
Checking print-ready images
Before sending artwork or photos to print, it is useful to verify both:
- pixel dimensions
- physical resolution metadata
This helps avoid situations where a file looks large on screen but prints smaller or softer than expected.
Reviewing exports from design apps
Design tools and editors do not always write resolution metadata the same way. This checker helps confirm whether the final file contains the expected value.
Comparing files after conversion
If you convert an image from JPEG to PNG or WebP, the conversion process may keep, change, or remove physical resolution metadata. This tool helps you see what survived the conversion.
Troubleshooting upload pipelines
Site owners and developers can use it to inspect whether upload systems, optimizers, or CDNs strip metadata from files.
Auditing client assets
If a client says an image is “300 DPI,” you can check whether the file actually contains that value and whether the image dimensions support the intended print size.
Common Questions Explained
“Why does my image have dimensions but no DPI?” Because pixel dimensions and physical resolution metadata are separate things. An image can be 3000 × 2000 pixels and still contain no stored DPI value at all.
“Does 300 DPI always mean the image is high quality?” No. DPI metadata alone does not guarantee quality. The real limiting factor is still the number of pixels available for the intended print size.
“Why does one app say 72 DPI and another say 300 DPI?” Because some files contain multiple metadata sources, and different apps may prioritize different ones. That is why the source table is useful.
“If I change DPI metadata, do I gain more detail?” No. Changing DPI metadata without resampling the image does not add pixels or improve sharpness. It only changes the implied physical print size.
“Why can’t every WebP show DPI?” Because WebP often stores dimensions without storing physical resolution metadata. When EXIF resolution is missing, there may be no DPI value to report.
“Is 72 DPI bad for web images?” Not really. For the web, pixel dimensions matter much more than stored DPI. A web image can display perfectly well even if its metadata says 72 DPI or contains no DPI value at all.
Tips for More Accurate Checks
- Use the original exported file when possible, not a resaved screenshot or a messaging app download
- Check both dimensions and print size together instead of looking at DPI alone
- Review the source field if you need to understand where the value came from
- Watch for mismatch warnings when comparing reports from different software
- Do not treat missing DPI as an error unless your workflow specifically requires print metadata
- Remember that web optimization tools often strip metadata to reduce file size
How It Works
This tool runs entirely in your browser and performs a metadata-focused inspection of the image file.
- You load one or more images.
- The browser reads the file locally.
- The parser detects the format and extracts pixel dimensions.
- It then looks for physical resolution metadata in the most relevant place for that format:
- JPEG: JFIF first, then EXIF if needed
- PNG: pHYs chunk
- WebP: EXIF fallback when available
- If valid physical resolution exists, the tool converts it into a readable DPI value.
- It estimates print size from the combination of dimensions and physical resolution.
- If multiple sources exist, it surfaces them so you can compare them directly.
Because everything happens client-side, your images are not uploaded just to inspect their metadata.
Perfect For
- Designers checking print assets
- Photographers reviewing exported files
- Developers debugging image-processing pipelines
- Site owners auditing uploads and optimizers
- Marketplace sellers preparing product images
- Teams comparing converted assets across formats
- Anyone who wants a fast, private way to check image DPI or PPI metadata
If you need to know whether an image actually contains physical resolution metadata — and what that means in practical terms — this tool gives you a clear, reliable answer.
