DPI Checker - Find the DPI and True Print Size of Any Image

Drop an image and see the DPI actually written in the file, every place it is written, and exactly how big it prints. Nothing is uploaded and nothing is changed. The bytes are read in your browser and the file never leaves your device.

Plenty of files carry no DPI at all, and that is normal. DPI is only a note attached to the file: it never changes a single pixel. The pixel count is what decides how large a print can be, and that is shown below whether the tag is there or not.

Drag & Drop your images here

or

From my Computer
By URL
From Google Drive
From Dropbox

Import from your computer, a public URL, Google Drive, or Dropbox.

JPG, PNG, WebP, TIFF, HEIC, AVIF, BMP, GIF - up to 100 MB per file

🔒 100% processed on your device ⚡ No upload, no network calls 🗑 Files are never stored on a server
Options

Every print size in your results is shown in the unit you pick here. The paper names on the cards below keep the units those sizes are defined in. Switching this re-renders what is already on screen and never re-reads your files.

A4
210 x 297 mm
A3
297 x 420 mm
A5
148 x 210 mm
Letter
8.5 x 11 in
4 x 6 photo
4 x 6 in
5 x 7 photo
5 x 7 in
8 x 10 photo
8 x 10 in
Passport photo
35 x 45 mm
Custom
Set your own
Custom print size

Width and height in the unit selected above. Anything from 0.1 to 1000 is accepted.

The paper is turned to match each image, so a landscape photo is fitted to A4 landscape and a portrait one to A4 portrait. That is what a print dialog does by default, and each result says which way round it used.

The JFIF density in a JPEG header, the EXIF resolution tags, the Photoshop resolution block, the PNG pHYs chunk and the BMP header, straight from the raw bytes. Where a file carries more than one and they disagree, every one of them is shown.

This page changes nothing and writes no file. To set the DPI rather than read it, use the DPI changer. For the full tag list behind these numbers, use the EXIF viewer.

DPI is a note attached to the file. It does not change a single pixel. A 3000 x 2000 photo is 3000 x 2000 whether it is tagged 72 or 300. The tag only tells a printer how big to make the print.

Because of that, raising the DPI tag never adds detail. It makes the print smaller, not sharper. Anything promising to raise DPI to improve quality is selling you a resize. If you genuinely need more pixels, that is the image resizer, and it cannot invent detail either.

A JPEG can carry two different resolution values, one in the JFIF header and one in the EXIF block, and they often disagree. Photoshop files can carry a third in their own resolution block. Different software reads different ones, so when they conflict there is no single right answer. Every one found is shown above rather than resolved for you.

72 DPI is what most encoders write when nobody sets a value. It usually means the field was never filled in rather than that someone chose 72.

What counts as enough DPI depends on viewing distance. 300 is the standard for something held in your hand. Posters are fine at 150 and billboards are printed at 20 to 40 DPI and look perfect from across a road.

Horizontal and vertical DPI can differ, usually on scans. Where they do, the print comes out stretched unless the software corrects it, and both figures are shown separately above.

Sensor resolution tags such as FocalPlaneXResolution describe the camera, not the print. They are listed where present and are never reported as the DPI. To see every tag in the file rather than the density ones, use the EXIF viewer.

GIF has no resolution field and never had one. WebP has none of its own and carries a value only inside an EXIF chunk. PNG stores its density in pixels per metre, so converting it back to inches can land a whole number off by a fraction.

Everything is processed locally in your browser. Nothing is uploaded to our servers.

This DPI checker reads the resolution actually written inside your image file, every place it is written, and works out how big the picture really prints. It reads the JFIF density in a JPEG header, the EXIF resolution tags, the Photoshop resolution block, the PNG pHYs chunk and the BMP header, straight from the raw bytes in your browser. Nothing is uploaded and nothing is changed. It sits in the image metadata tools group with the EXIF viewer, the EXIF remover and the image info reader.

Two things this page does that almost nothing else does. A JPEG can hold two different resolution values that disagree, one in the JFIF header and one in the EXIF block, and a Photoshop file can hold a third. Every other tool shows a single number, which means it picked one for you without saying so. This one shows all of them and flags the conflict. Second, a header with the units byte set to zero means there is no density recorded at all, not one dot per inch, and getting that wrong is how competing tools end up printing "1 DPI" on perfectly normal files. When you want to set the tag rather than read it, that is the DPI changer, and when you genuinely need more pixels it is the image resizer. The rest of the image tools sit alongside, including the government photo tools for forms that specify a DPI outright.

5
Places DPI can hide in a file
8
Print size presets, plus custom
0
Files written or uploaded
100 MB
Per file, read in slices
🔍

Every Value, Not One

JFIF, EXIF, Photoshop, PNG pHYs and the BMP header are all read and listed separately. Where they disagree, the conflict is shown rather than quietly resolved on your behalf.

📏

The Print Size, Not Just a Number

Pick A4, A3, a 4 by 6 or your own size and see the DPI the photo actually achieves at that size, with the sheet turned to match the way a print dialog turns it.

⚠️

It Knows When There Is No DPI

A units byte of zero means no density was recorded, not one dot per inch. That distinction is why other tools report "1 DPI" on ordinary files and this one does not.

🔒

Read Only, In Your Browser

No file is written and nothing is uploaded. The tool opens the header, does the arithmetic and stops. It never even decodes the picture.

How to Check the DPI of an Image

Four steps, and there is no button to press. The file is read the moment it arrives, because a reader that makes you click Check is friction for nothing.

📤

1. Add the Image

Drag it in, browse, or import from a URL, Google Drive or Dropbox. Several files at once is fine and each gets its own result.

2. Read the Recorded DPI

The headline shows what the file says, or that it says nothing. Every density field found is listed underneath with its raw value and unit code.

📄

3. Pick a Print Size

A4, A3, A5, Letter, 4 by 6, 5 by 7, 8 by 10, passport, or your own. The result updates from data already read, never a second pass over the file.

💾

4. Read the Verdict

See the DPI the photo achieves at that size and whether it is sharp, everyday, poster only or soft. Copy it, or download the whole batch as text.

Check an Image DPI Now

Where This DPI Checker Looks, and What Trips Other Tools

There is no before-and-after picture here because nothing about your file changes, and the tool never even decodes the image. What matters instead is where the resolution is hiding and which unit code it is hiding behind. Every row below is a code path in the tool on this page.

Where it lives Format Unit codes The trap Read here What the tool shows
JFIF APP0 JPEG 0 none, 1 inch, 2 per cm Units 0 with density 1 x 1 means no density, not 1 DPI Yes The raw pair, the unit code, and the converted DPI or a plain no density recorded
EXIF resolution tags JPEG, TIFF, WebP, HEIC, AVIF 1 none, 2 inch, 3 per cm ResolutionUnit 1 means the numbers are a ratio, not a density Yes XResolution and YResolution separately, converted from centimetres where needed
Photoshop 8BIM 0x03ED JPEG, TIFF, PSD-derived Fixed point, plus display units Photoshop reads its own block first, so it can disagree with EXIF Yes A third value where present, which is the one most tools never look for
PNG pHYs chunk PNG 0 unknown, 1 metre Unit 0 is an aspect ratio only, and metres convert back imprecisely Yes Pixels per metre as stored, converted to whole DPI rather than a false decimal
BITMAPINFOHEADER BMP Pixels per metre, signed Zero means unset, and plenty of writers leave it at zero Yes The stored pixels per metre and the DPI it works out to
No density field at all GIF, WebP with no EXIF None exists Absent is not the same as stripped, and neither is 72 Reported A plain statement that the format has no resolution field, plus the full print size table

The "trap" column is not theoretical. Each one is a real defect in tools currently ranking for this term: reporting 1 DPI from an aspect ratio, treating a ratio as a density, missing the Photoshop block entirely, and calling an absent field 72. A file can also carry sensor tags such as FocalPlaneXResolution, which describe the camera and not the print, and are listed where present but never reported as the DPI. To see every tag rather than the density ones, use the EXIF viewer, and to set the value rather than read it, the DPI changer.

DPI Checker: What the Number Means and Why Your File Has Three of Them

DPI is a note attached to a file, not a property of the picture. A 3000 by 2000 photo is 3000 by 2000 whether it is tagged 72 or 300, and the tag changes nothing you can see on a screen. All it does is tell a printer how large to make the print. That single fact explains almost every confusion around the term, including why raising the number never makes a photo sharper: it makes the print smaller, and nothing else.

What makes checking it harder than it sounds is that the number lives in several places at once. A JPEG can carry a JFIF density in its opening header and an entirely separate pair of EXIF resolution tags further in, and a file that has been through Photoshop can carry a third value in its own 8BIM resolution block. Photoshop reads its own block first. Other software reads EXIF. Older software reads JFIF. When those disagree, and they frequently do, there is no single correct answer, so this page lists every value it finds instead of picking one and hoping. The W3C PNG specification is a good example of how carefully these fields are actually defined: its pHYs chunk stores density in pixels per metre with a one byte unit specifier, and a unit specifier of zero means the numbers describe a pixel aspect ratio and not a physical size at all.

That unit byte is where most competing tools fall over. A JFIF header with units set to zero and a density of one by one is extremely common, and it means no density was recorded. Read it naively and you print "1 DPI" on an ordinary photograph. This checker reports it as no density recorded, and still shows the full print size table underneath, because the pixel count is what actually decides how large you can print. To change the tag rather than read it, use the DPI changer. For every other tag in the file, use the EXIF viewer, and for format, colour depth and file integrity there is image info.

⚖️How This Compares to the Other Ways to Check DPI

Method Shows every value What it misses
This DPI checker Yes Nothing. All five sources, unit codes shown, conflicts flagged.
Windows File Properties No One figure only, and it silently prefers a single source.
macOS Preview inspector Partly Good on EXIF, no JFIF, no Photoshop block, no unit codes.
Photoshop Image Size dialog No Shows Photoshop's own value, which is often not the EXIF one.
Most online DPI checkers No One number, and many report 1 DPI from a units-zero header.
Desktop ExifTool command line Yes Nothing, but no print size maths and a terminal to learn.
Guessing from the file size No File size has no relationship to DPI whatsoever.

The Photoshop row is the interesting one. If a designer tells you a file is 300 DPI and your software says 72, neither of you is lying: Photoshop wrote its value into its own resource block and something else wrote 72 into the JFIF header. Seeing both at once ends that argument in about four seconds, which is most of the reason this page exists. If what you actually need is a file at a particular pixel size or a particular weight, that is the image resizer or resize to KB, not a DPI tag.


🖨️When Checking the DPI Is the Right Move

📄

A Form Specifies a DPI

Exam applications, visa forms and government uploads routinely ask for 200 or 300 DPI alongside a pixel size and a file weight. Check the tag before you submit rather than after a rejection.

🖶️

A Printer Says the File Is Low Resolution

Usually they mean the pixel count is too small for the size you asked for, not that a tag is wrong. The print size table tells you which of the two problems you actually have.

🖼️

Two Programs Disagree

One says 300, another says 72, and the file has not changed. That is two different fields, not a bug. Seeing every value at once settles it immediately.

📐

Planning a Print Before You Order

Pick the paper size and read the DPI the photo achieves at it. That tells you whether an A3 enlargement will hold up before you pay for one.


💻When the DPI Tag Does Not Matter at All

🌐

Anything Going on a Screen

Websites, apps, social posts and email all work in pixels and ignore the tag completely. A 72 DPI web image and a 300 DPI one at the same pixel size are identical files in every way that matters.

📶

Trying to Improve Quality

Raising the tag adds no detail, because there is no detail in a tag. It shrinks the print. If the print looks soft you need more pixels, and no metadata edit will produce them.

📦

Trying to Reduce File Size

The DPI field is a few bytes. Changing it moves the file size by nothing at all. For that job use compress JPG or the resize to KB tool.

🗺️

Printing Something Big

DPI requirements are really about viewing distance. Billboards are printed at 20 to 40 DPI and look perfect from across a road. A poster at 150 is fine, and a tool calling that low quality is wrong.


Why Check DPI Here Rather Than Anywhere Else

🔑

Conflicts Are Shown, Not Hidden

Where JFIF, EXIF and the Photoshop block disagree, all three appear with their raw values and unit codes. No tool that shows a single number can tell you a conflict even exists.

🔢

The Maths Is Stated, Not Implied

The DPI a photo achieves at a chosen size is shown to one decimal, and the verdict word is derived from that same number, so the figure and the word beside it can never come from different bands.

🔄

The Sheet Turns to Match the Photo

A landscape photo is fitted to A4 landscape, which is what a print dialog does. Each result names the orientation it used, so the numbers and the sentence beside them agree.

🚫

It Never Invents a Number

No density recorded says exactly that. A units byte of zero is reported as an aspect ratio, sensor tags are never passed off as print DPI, and no fallback default is presented as though it came from the file.


What the DPI Checker Actually Does

  • Reads the JFIF APP0 density, the EXIF XResolution and YResolution tags, the Photoshop 8BIM 0x03ED resolution block, the PNG pHYs chunk and the BMP header.
  • Identifies the real format from the file's first bytes, so a PNG renamed to .jpg is still read correctly.
  • Handles every unit code properly: inches, dots per centimetre, pixels per metre, and the "no units" cases that mean an aspect ratio rather than a density.
  • Shows horizontal and vertical resolution separately, because scanners sometimes record different values and the print comes out stretched.
  • Flags a conflict when two or three sources disagree, and refuses to pick a winner for you.
  • Offers A4, A3, A5, Letter, 4 by 6, 5 by 7, 8 by 10 and passport presets, plus a custom size with an aspect lock.
  • Turns the paper to match each image and says which way round it used, the same way a print dialog fits to page.
  • Rounds a required DPI up rather than down, because rounding a requirement down is a promise the print cannot keep.
  • Reads several files at once and exports one combined plain text report, in the units and print size you have selected.
  • Writes no file and makes no network call after the page loads. It does not even decode the picture.

🔢How to Use the DPI Checker

  1. Add one image or several Drag files in, or import from your computer, a URL, Google Drive or Dropbox. JPG, PNG, WebP, TIFF, HEIC, AVIF, BMP and GIF are all accepted, up to 100 MB each.
  2. Read the recorded DPI first The headline says what the file records, or that it records nothing, or that two sources conflict. The table under it lists every density field found with its raw value and unit code.
  3. Choose the print size you care about Pick a preset or set a custom width and height with the aspect lock. Switch between inches and centimetres at any time. Everything re-renders from data already read.
  4. Act on the verdict Sharp, everyday print, posters only or soft in print, worked out from the DPI the photo actually achieves at that size. Copy the result, or download the whole batch as a text report.

⚙️Technical Notes and Honest Limits

The limit worth stating plainly is that this page reads and never writes. It will tell you the tag is wrong for the print you want, and it will not fix it, because fixing it is a different job that belongs to the DPI changer. Keeping those two apart is deliberate. A reader that quietly re-tags your file is a tool you cannot trust to report honestly, and a page that tries to do both ends up doing neither well.

🔢 Why 72 DPI shows up on almost everything

Most encoders write 72 into the density field when nobody has chosen a value, so it is far more often a default than a decision. It is a real recorded value and it is reported as one, but seeing 72 usually means the field was never filled in rather than that someone wanted 72. It is also the reason so many people believe screens are 72 DPI, which stopped being true decades ago and was never a property of the image file in the first place.

📏 Why horizontal and vertical DPI can differ

Flatbed scanners sometimes sample at different rates along and across the sensor, and some capture software records that faithfully. When the two figures differ, a print made without correcting for it comes out stretched in one direction. Both values are always shown separately here rather than averaged into a single figure, because averaging them would hide exactly the problem you would want to know about. PNG makes this slightly worse by storing density in pixels per metre, so converting back to inches can land a fraction off a whole number.

📷 Sensor resolution is not print resolution

EXIF carries a tag called FocalPlaneXResolution, which describes how densely the camera's sensor samples the image circle. It is a camera specification and has no relationship at all to how large a print should be. It appears in the tag list where present, clearly labelled, and it is never reported as the DPI. Tools that confuse the two produce spectacular numbers, which is how a perfectly ordinary photo occasionally gets described as being several thousand DPI.

🗎 How large files are read without loading them

Density fields live in a small region of a file, but not always near the front. Many TIFF writers, scanner software in particular, append the tag table after the image data, so a 90 MB scan can keep its resolution figures right at the end. The reader takes a small opening slice, finds the offset it needs and then reads a window at that position, so peak memory stays roughly constant whatever the file size. A large scan answers about as quickly as a phone snapshot.


💡Real Situations This Page Handles

01

A student's exam portal demands a 200 DPI photograph. The checker shows what the file records and what it achieves at the required print size, and the presets in the government photo tools produce a compliant file if it falls short.

02

A designer insists a file is 300 DPI and the client's software reports 72. Both values appear side by side, one from the Photoshop resource block and one from the JFIF header, and the disagreement stops being an argument.

03

Someone wants an A3 enlargement of a phone photo. The verdict shows the DPI it actually achieves at A3 in landscape, so the decision gets made before the money is spent rather than after the print arrives.

04

An old scan reports different horizontal and vertical figures. The two are shown separately with a note, which explains why every print from that scan has come out subtly stretched.


- WHO USES THIS -

Built for Everyone in India

Anyone about to print something, upload to a form that specifies a DPI, or send artwork to a press that will ask awkward questions about resolution.

Print Shops and Presses Designers and Studios Students Filling Exam Forms Photographers Publishers and Editors Scanning and Archiving Teams Small Business Owners Web and App Developers

FAQs - DPI Checker

It is a note stored in the file saying how many dots per inch a printer should use. It is not a property of the picture and it changes nothing on a screen. A 3000 by 2000 photo is 3000 by 2000 whether it is tagged 72 or 300; only the size of the resulting print differs. The pixel count is what limits how large you can print, not the tag.

Drop the file in and the answer appears immediately, with no button to press. The headline shows what the file records, and the table underneath lists every density field found, with its raw value and unit code. Pick a paper size and you also get the DPI the photo actually achieves at that size. Nothing is uploaded and no file is written.

Because a file can hold more than one resolution value. A JPEG can carry a JFIF density in its opening header and separate EXIF resolution tags further in, and a Photoshop-edited file can carry a third in its own resource block. Different software reads different fields, so neither program is wrong. This page shows every value it finds and flags the conflict rather than choosing for you.

No. There is no detail stored in the tag, so raising it adds none. What it does is make the print smaller, because the same pixels are being packed more tightly. Anything advertising a DPI increase as a quality improvement is really offering you a resize. If a print looks soft you need more pixels, and the image resizer is the honest tool for that.

Because 72 is what most encoders write when nobody chooses a value. It is a genuine recorded number and is reported as one, but in practice it usually means the field was left at its default. It is also where the old belief that screens are 72 DPI comes from, which stopped being true decades ago and was never a property of the file anyway.

300 is the standard for something held in your hand. Between 200 and 299 is fine for most everyday printing and for the exam and government forms that specify 200. Between 150 and 199 works for posters and anything viewed from a metre away. Below 150 looks soft up close. It is really a question about viewing distance: billboards print at 20 to 40 DPI and look perfect.

Because the file genuinely has none. A JFIF header with its units byte set to zero, EXIF with ResolutionUnit set to 1, or a PNG pHYs chunk with unit zero all mean the numbers are an aspect ratio rather than a density. Reading those naively is how other tools end up reporting one dot per inch on ordinary photos. The print size table still appears, because the pixel count is the real answer.

No, and that is deliberate. This page reads and reports; it writes no file at all. Setting the tag is a separate job for the DPI changer, which is a different tool in the resize and DPI group. Keeping the two apart matters, because a reader that quietly re-tags your file is one you cannot trust to report honestly in the first place.

JPEG, PNG, WebP, TIFF, HEIC, AVIF and BMP are all read, each from whichever field that format uses. GIF has no resolution field and never had one, and WebP has none of its own and carries a value only inside an EXIF chunk. Where a format cannot store a density, the tool says so rather than reporting the value as missing or stripped.

Some flatbed scanners sample at different rates along and across the sensor, and the capture software records that faithfully. A print made without correcting for it comes out stretched in one direction. Both figures are always shown separately here rather than averaged, because averaging them would hide exactly the problem worth knowing about.

Not at all. The field is a handful of bytes, so changing it moves the file size by nothing measurable, and websites, apps and email work in pixels and ignore it completely. If the goal is a smaller file, that is a compression or resizing job. The DPI tag only ever matters at the moment something is printed.

Find Out What Your Image Really Prints At

Every resolution value in the file, the conflicts between them, and the true print size on A4, A3, a photo print or a size of your own. Read in your browser, nothing uploaded, nothing changed.

Open the DPI Checker