---
title: Image DPI Checker
description: A free in-browser image DPI checker — drop in JPEG, PNG, WebP, or TIFF files and read their stored DPI, where that reading comes from, their pixel dimensions, and the largest print they can make. Images never leave the browser.
canonical: https://batchrelay.com/image-dpi-checker/
last-updated: 2026-09-05
---

# Image DPI Checker

Image DPI Checker is a free tool on batchrelay.com that reads the print-resolution metadata out of image files. Drop in one image or a hundred; each one comes back with its format, pixel dimensions, the DPI value stored in the file, which tag that value came from, and the largest print it can make at 300 and 150 DPI. There is no account, no upload, and no file-size limit beyond what the device can hold.

It reports what a file already says. It does not change files. Rewriting density metadata is a job for Photoshop, Affinity Photo, or ExifTool; the FAQ on the page explains how to do it without resampling.

Canonical page: <https://batchrelay.com/image-dpi-checker/>

## What it reads

| Format | DPI source | Reported as |
| --- | --- | --- |
| JPEG | EXIF `XResolution` / `YResolution` with `ResolutionUnit` | from EXIF metadata |
| JPEG | JFIF APP0 density fields | from JFIF header |
| PNG | `pHYs` chunk, pixels per metre converted to inches | from PNG pHYs chunk |
| TIFF | `XResolution` / `YResolution` IFD tags | from TIFF resolution tags |
| WebP | Container dimensions; WebP carries no density field of its own | no DPI metadata |
| Any | No usable density tag | no DPI metadata — most software assumes 72 |

EXIF wins over JFIF when a JPEG carries both, because that is the order editors write and read them in. Pixel dimensions come from the container; when a container does not declare them where the parser looks, the browser's own decoder supplies them instead.

Horizontal and vertical density are read separately and shown as a pair only when they differ.

## Print-readiness thresholds

The chip on each card grades the DPI value stored in the file, using the same thresholds Batch Relay applies to prints everywhere else on the site:

| Stored DPI | Status | Meaning |
| --- | --- | --- |
| 300 or higher | Print-ready | Matches the standard photographic print target. |
| 150 to 299 | OK for large prints viewed at a distance | Banners, posters, and large wall pieces hold up; small prints will look soft. |
| Under 150 | Too low for print | Below the floor Batch Relay accepts for a print. |
| None stored | Neutral | The file carries no density tag; most software assumes 72. |

The DPI value is metadata, not a measurement of quality. Real print quality is pixels divided by printed inches, which is why every card also states the maximum print size at 300 DPI and at 150 DPI computed from the pixel count alone. A 6000 × 4000 file tagged 72 DPI still prints cleanly at 20 × 13 inches.

## Accepted files

JPEG, PNG, WebP, and TIFF, by drag-and-drop, by click, or through the file picker, several at a time. Dropping more files appends them to the grid rather than replacing it.

HEIC files from an iPhone cannot be decoded in a browser; the tool says so and asks for a JPEG export from Photos instead of failing quietly. TIFF thumbnails do not render in most browsers, so a TIFF card shows a neutral file-type tile in place of a preview; its metadata is read normally.

## Images never leave the browser

Every file is read with `file.arrayBuffer()` and parsed on the device. Thumbnails are object URLs, revoked when a card is removed or the page is left. No image is uploaded, posted, or sent to Batch Relay or to any third party, nothing about a file is stored on a server, and nothing is written to local storage.

## Where to go next

- [Image DPI Checker](https://batchrelay.com/image-dpi-checker/)
- [Memory Mate Maker](https://batchrelay.com/memory-mate-maker/)
- [How Batch Relay works](https://batchrelay.com/how-it-works/)
- [Sports photography workflow guides](https://batchrelay.com/guides/)
- [Site index for agents](https://batchrelay.com/llms.txt)