How to Find the DPI of an Image on Android (3 Methods, No App)

How do you find the DPI of an image on Android?

You read it from the file with a browser — because no Android gallery app displays it. Chrome (or any modern browser) can open a DPI checker that parses the photo's metadata on your phone and prints the stored DPI, the pixel dimensions, and the size the file would cover on paper. The whole job takes about a minute.

• Google Photos does not have a DPI field. Its details panel lists file name, size, resolution, and camera details — the redesign that moved those lines to the bottom of the panel rolled out in November 2019 (9to5Google, 11 Nov 2019). Guides published in 2026 still report the same gap (techplayguide, 8 Jun 2026).
• The DPI is not missing — it is just not displayed. JPEGs carry it in a JFIF header or EXIF tags (XResolution / YResolution); PNGs carry it in a pHYs chunk measured in pixels per metre (convert.town DPI checker, accessed November 2026). Android's own ExifInterface API exposes those tags to any app that asks (developer.android.com, accessed November 2026).
• Most Android camera photos report 72 DPI. The EXIF standard says to designate 72 whenever the image resolution is unknown — and a camera never knows your print size (AOSP ExifInterface source, quoting JEITA CP-3451C Exif 2.3 Section 3-8).
• The stored tag is not the print result. Real print DPI = pixel width ÷ print width in inches. A 4,032-pixel photo printed 8 inches wide delivers 4,032 ÷ 8 = 504 PPI, whatever the tag says. Arithmetic, not opinion.

Why doesn't Android show DPI anywhere?

Because Android treats photos as pictures, not as print files. The platform's gallery apps are built for browsing, cropping, and sharing. Print metadata — DPI, resolution tags, density fields — sits in a layer Android has never surfaced in its standard UI. Independent 2026 guides state it directly: "Android does not include a built-in DPI checker in its gallery apps" (techplayguide, 8 Jun 2026).

• Google Photos shows a curated summary. Date, map, file name, size, resolution, camera, exposure settings. No density field.
• Files by Google shows no EXIF at all. File info gives name, size, modified time, and folder path — "No EXIF fields at all" (metadata-editor.com, updated 7 Oct 2026).
• Manufacturer galleries vary. Samsung's Gallery panel mirrors Google Photos when you swipe up or open More options > Details (metadata-editor.com, 7 Oct 2026). Whether a DPI line appears depends on the manufacturer, the Android version, and the app build — exposure is "inconsistent" across Android devices (YesDPI device guide, accessed November 2026).
• The API exists; the UI does not. Android ships ExifInterface.TAG_X_RESOLUTION, TAG_Y_RESOLUTION, and TAG_RESOLUTION_UNIT for developers (developer.android.com, accessed November 2026). Apps can read the number. The stock viewers choose not to show it.

The practical consequence: hunting for a hidden settings screen wastes your time. There is no toggle. The number has to be read from the file by something that parses metadata — a browser tool, an EXIF app, or a desktop program.

What does the Google Photos details panel actually show?

File name, file size, resolution, device, and camera settings — but never DPI. Swipe up on an open photo (or tap the info icon) and the panel slides up. Since the 2019 redesign, "Details" like file name, size, resolution, and megapixel count sit at the very bottom of that sheet (9to5Google, 11 Nov 2019).

One trap worth knowing: for a backed-up photo, the panel can be describing Google's copy rather than the file on your phone. Google's Storage saver setting resizes any photo larger than 16 MP down to 16 MP (Google Photos Help, accessed November 2026). Check the local original — or the file you actually intend to print.

Which method should you use to find DPI on Android?

Method 1 — the browser — for almost everyone. Method 2, an EXIF app, if you inspect photos daily. Method 3, a computer, only when a desktop workflow demands it.

Method 1: how do you check DPI on Android in Chrome (no install)?

Open Chrome, load a browser-based DPI checker, choose the photo, read the result. The file is parsed inside the browser tab; nothing installs and nothing needs an account.

1. Open Chrome on the phone that holds the photo. Any modern browser works; Chrome ships on nearly every Android device and handles file pickers predictably.
2. Load the free image DPI checker. It reads the same metadata a desktop app would — JFIF and EXIF for JPEG, the pHYs chunk for PNG — directly from the file (convert.town, accessed November 2026).
3. Pick your photo. Choose it from Gallery, Files, or Downloads. The system file picker hands the file to the page.
4. Read the report. You get the stored DPI, the pixel dimensions, and the print size the tag assumes. If the file carries no density field, an honest tool says so instead of printing a made-up 72.
5. Convert the stored number into the real one. Divide pixel width by your intended print width in inches. Use the Real Print DPI Calculator below, or the full DPI calculator on this site.
6. If the lab demands a specific tag value: run the file through the DPI converter, set 300 (or whatever number the lab asked for), and re-check the result. Changing the tag rewrites a label; it adds zero pixels.

Method 2: what about an EXIF app from the Play Store?

It works, and it shows more fields — at the cost of installing an app and granting it photo access. EXIF metadata apps display the full tag list, including resolution values that gallery apps skip (techplayguide, 8 Jun 2026).

• When it is worth it: you inspect photos constantly, you need GPS or camera settings alongside DPI, or you work offline in the field.
• When it is not: you have one photo and a print deadline. Installing an app to read four bytes of metadata is overhead.
• The privacy trade: an EXIF app needs library access to every photo you point it at. A browser tool reads only the single file you select. Pick based on how often you will use it.

Recommendation: keep Method 1 as your default. Add an EXIF app only if you find yourself needing full tag dumps weekly.

Method 3: how do you find DPI by moving the photo to a computer?

Send the file to a PC or Mac, then read it with the operating system's own inspector. This is the route print shops recognize, and it doubles as verification that the file you send is the file you checked.

1. Get the original off the phone. USB transfer, your cloud drive, or email it to yourself. Downloading a re-compressed copy from a chat app defeats the purpose — see the missing-DPI section.
2. On Windows: right-click the file → Properties → Details → look under Image for Horizontal resolution and Vertical resolution (pixotter, 17 Mar 2026).
3. On Mac: open the file in Preview → Tools → Show Inspector → the General tab shows resolution in pixels/inch when the metadata exists (YesDPI device guide, accessed November 2026).
4. Compare with the phone reading. If the numbers differ, you are comparing two different files — the local original versus a backed-up or re-shared copy.

Is the DPI you find the real print DPI?

No. The stored DPI is a label the file carries; the real print DPI is pixels divided by inches, and you control the inches. Both numbers matter, for different reasons.

Worked example, all arithmetic: a standard 12 MP Android photo is 4,032 × 3,024 pixels.

• Tagged 72 DPI, software assumes 4,032 ÷ 72 = 56 inches wide.
• Printed 8 inches wide, it delivers 4,032 ÷ 8 = 504 PPI — sharp at any lab standard.
• Printed 20 inches wide, it delivers 4,032 ÷ 20 = 201.6 PPI — fine on a wall, soft in your hands.

So finding the DPI is step one. Deciding the print size is step two — and step two is the one that decides sharpness. Our 300 DPI size chart lists the pixel dimensions per paper format if you need them.

Where is DPI stored inside an Android photo?

In one of three structures, depending on the file format: a JFIF header segment, EXIF resolution tags, or a PNG pHYs chunk. None of them live in the pixels — they sit in the metadata wrapper around them.

The JFIF byte layout, if you ever need to read it by hand: after the SOI marker and segment length, 13 bytes in sits the density-unit byte — 0 for none specified, 1 for PPI, 2 for pixels per centimetre — followed by two bytes of X density and two bytes of Y density, big-endian (Stack Overflow, 9 May 2013; follow-up, 19 Feb 2014). That is the whole header. A hex editor can read it; so does every checker on this page.

Android's API side: TAG_X_RESOLUTION is documented as "The number of pixels per TAG_RESOLUTION_UNIT in the TAG_IMAGE_WIDTH direction," type rational (developer.android.com, accessed November 2026). The platform knows exactly where the number is. It simply does not render it in any stock viewer.

What if the image shows no DPI at all?

Then the file never had a density field — which is normal for screenshots, web images, and anything that passed through a social platform or messaging app. An empty field is not corruption. It means no writer ever set one.

• Viewers fill the gap with guesses. When no tag exists, Photoshop and most web/Mac tools assume 72; Windows Explorer's Horizontal resolution field assumes 96 (convert.town, accessed November 2026; pixotter, 17 Mar 2026). Neither number is stored in your file. Both are display conveniences.
• Screenshots never carry one. A screenshot is a dump of your display buffer, not a camera capture — no camera, no EXIF, no density.
• Messaging and social apps rewrite files. Files that "came through a chat, a social feed, or a web download" commonly arrive without density metadata (setdpi.com, accessed November 2026). Check the original on the phone that shot it, not the copy you received.
• Backed-up copies may differ from local originals. Google's Storage saver resizes photos larger than 16 MP to 16 MP (Google Photos Help, accessed November 2026). The file you downloaded from the cloud is not necessarily the file the camera wrote.

What to do about it: if a print form demands a value, write one. Relabel the file to 300 with the DPI converter — the label changes, the pixels do not. If the file also lacks pixels for the print size you need, no tag will fix that; resize or print smaller with the image resizer.

Why does my Android photo say 72 DPI?

Because the EXIF standard tells cameras to write 72 whenever the resolution is unknown — and print resolution is always unknown at capture time. A camera cannot know your print size; you have not picked it yet.

• The standard's own wording: "When the image resolution is unknown, 72 [dpi] shall be designated" — tag 282, XResolution, default 72, per the AOSP ExifInterface source quoting JEITA CP-3451C (Exif 2.3) Section 3-8.
• Phones follow it. Android's own API documentation carries the same tag definitions (developer.android.com, accessed November 2026). Public EXIF readouts of Samsung phone photos list horizontal and vertical resolution as 72 dpi (Wikimedia Commons file data for a Galaxy S2 photo; Ipernity EXIF for a Galaxy S24 FE photo — both cited in our 72 DPI explainer).
• 72 is not a quality verdict. Sony states the rating "is a print setting assigned to the pictures by the software; it is not associated with how the camera takes the pictures" (Sony support, accessed November 2026).
• The pixels are untouched. Your 12 MP photo still holds 12 million pixels at 72 or at 300. Only the label moves.

How do you change DPI on Android after you find it?

With a browser-based converter — Android has no native field for editing it, the same way it has no native field for reading it. The workflow mirrors Method 1: Chrome does the work, no app install.

1. Check first. Run the photo through the DPI checker and write down the current tag and pixel dimensions.
2. Open the DPI converter in Chrome. Select the photo, enter the target value (300 is the common print-lab standard), keep dimensions unchanged.
3. Convert and save. The finished JPEG downloads to your phone.
4. Verify. Run the new file through the checker. It should report the new value with identical pixel dimensions. If the pixels changed, something went wrong — a DPI rewrite should never resize.

Read the full walkthrough in our change-DPI-without-an-app guide — the steps are the same on Android, and the desktop routes cover Windows and Mac.

Who is this guide not for?

Skip it if you need screen-only numbers, batch forensics, or a lab certification — this is a read-the-tag guide, not a print audit.

• Anyone checking an image that never prints. Web and app layouts ignore DPI entirely; pixels are the only currency. See DPI vs PPI for why.
• Anyone inspecting a file received over chat or social. The copy you got may have been resized and stripped. Find the original first, then read it.
• Anyone who needs every tag on 500 files. A one-file browser check does not scale. Use a desktop batch tool or exiftool on your computer.
• Anyone hoping a tag change adds pixels. It does not. If the print size exceeds your pixel budget, the fix is fewer inches or a better original — our minimum print resolution guide has the pixel chart.
• Anyone who wants a lab's formal sign-off. This reads metadata; it does not certify a file. Only your lab can do that.

First-hand: what we checked ourselves

We build DPI tools, so we verified every claim that reduces to arithmetic or to our own code — and left the phone screenshots marked for capture. Here is exactly what is confirmed and what still needs a dated screenshot.

1. Check 1 — the arithmetic holds. 4,032 ÷ 72 = 56.0 inches. 4,032 ÷ 300 = 13.44 inches. 4,032 ÷ 8 = 504 PPI. All three recompute in the calculator below, on your numbers, in your browser.
2. Check 2 — the reader reads the same fields. Our checker parses JFIF density, EXIF XResolution/YResolution with unit conversion, and PNG pHYs in pixels per metre — the same structures documented by convert.town (accessed November 2026). Files with no density field return an explicit "not set," never a fabricated 72.
3. Check 3 — relabeling preserves pixels. Push a photo through the DPI converter at 300. Pixel dimensions come out identical to the input. Only the tag moves. Reproducible in one click, on any file you own.
4. Check 4 — the API names exist. TAG_X_RESOLUTION, TAG_Y_RESOLUTION, TAG_RESOLUTION_UNIT are present in Android's ExifInterface reference, with documented types and meanings (accessed November 2026).

What broke when we pushed it: documented failure modes, not guesses. Files downloaded from messaging and social flows arrive without density fields — an honest checker reports "not set" (setdpi.com documents the same behavior, accessed November 2026). And a re-download from Storage saver may not match the local original, because Google resizes photos above 16 MP in that mode (Google Photos Help, accessed November 2026).

Who it is not for: this section covers arithmetic and our own tool behavior, both verifiable free in your browser. It is not a substitute for inspecting your actual file — or for your lab's requirements.

[AUTHOR EXPERIENCE / NEEDS SOURCE before publish: four dated screenshots — (1) Google Photos details panel on the test phone showing file name, size, resolution and camera rows with no DPI line, (2) the DPI checker result for that same file showing the stored tag, (3) Files by Google "File info" showing no EXIF fields, (4) Windows Properties > Details on the transferred copy. Add phone model, Android version, and capture date to each caption.]

Free tool: Real Print DPI Calculator

Watch: finding the DPI of an image on Android

Video embed placeholder — replace VIDEO_ID with the published YouTube ID before launch.

Video transcript summary: The video opens by saying the keyword aloud — "how to find the DPI of an image on Android" — and answers in the first minute: no gallery app shows it, read it in Chrome instead. It walks through the browser checker on a real phone photo, shows the Google Photos details panel missing the DPI line, then reads the same file's JFIF bytes to prove the number was always there. The final chapter runs the stored tag against the real print DPI in the calculator on this page.

FAQ

Next steps: a one-day plan

1. Today, 2 minutes: open the image DPI checker in Chrome and inspect one photo from your camera roll. Write down the stored DPI and the pixel dimensions. Screenshot the result — that is your before-picture.
2. Today, 1 minute: run those numbers through the Real Print DPI Calculator with your actual print width. Note the effective PPI next to the tag.
3. Today, 1 minute: open Google Photos, swipe up on the same photo, and confirm the panel shows size and resolution but no DPI line. You have now verified the gap with your own eyes.
4. Before your next print order, 5 minutes: read your lab's file-requirements page. If it demands a tag value, convert the file with the DPI converter, re-check it, and send the converted copy — never the messaging-app original.
5. This week, optional, 10 minutes: film or screenshot the three panels (Google Photos, Files by Google, browser checker) for your own reference — or to answer the next person who asks you the same question.

Sources

1. 9to5Google. "Google Photos for Android rolls out 'Info' menu redesign." Quote: "'Details' like file name, size, resolution, and megapixel count — along with device details — is now at the very bottom." 9to5google.com. 11 Nov 2019.
2. Android Developers. ExifInterface API reference. Quotes: TAG_X_RESOLUTION — "The number of pixels per TAG_RESOLUTION_UNIT in the TAG_IMAGE_WIDTH direction"; TAG_RESOLUTION_UNIT — "The unit for measuring TAG_X_RESOLUTION and TAG_Y_RESOLUTION." developer.android.com. Accessed Nov 2026.
3. Android Open Source Project. ExifInterface.java — tag definitions quoting "JEITA CP-3451C specifications (Exif 2.3) Section 3-8": XResolution / YResolution "Default = 72" and "When the image resolution is unknown, 72 [dpi] shall be designated." android.googlesource.com. Accessed Nov 2026.
4. Google Photos Help. "Choose the backup quality of your photos & videos." Quote: "If a photo is larger than 16 MP, it'll be resized to 16 MP" (Storage saver). support.google.com. Accessed Nov 2026.
5. TechPlayGuide. "How to Check DPI of an Image: The Amazing Complete Guide." Quotes: "Android does not include a built-in DPI checker in its gallery apps"; Google Photos "typically does not show DPI directly." techplayguide.com. 8 Jun 2026.
6. YesDPI. "How to Check Image DPI on Windows, Mac, iPhone and Android." Quotes: Android built-in apps show "pixel dimensions" while "explicit DPI/PPI metadata is inconsistently exposed"; effective DPI = "pixel width ÷ print width in inches." yesdpi.com. Accessed Nov 2026.
7. metadata-editor.com. "How to view photo metadata on Android phones." Quotes: Files by Google File info — "No EXIF fields at all"; Samsung Gallery panel "when you swipe up or open More options > Details." metadata-editor.com. Updated 7 Oct 2026.
8. convert.town. "DPI Checker." Quotes: JPEG stores DPI "in a small JFIF header or in EXIF tags"; PNG stores it "in an optional pHYs chunk (in pixels per metre)"; TIFF in "IFD tags 282 and 283"; "Windows ... assumes 96 DPI; Photoshop and most web/Mac tools assume 72." convert.town. Accessed Nov 2026.
9. setdpi.com. "DPI Checker." Quotes: EXIF preference order XResolution with ResolutionUnit conversion then JFIF fallback; PNG pHYs "× 0.0254"; "No DPI metadata found" is the honest result for screenshots and social exports; 72 "is the old Macintosh screen convention," 96 "the old Windows screen convention." setdpi.com. Accessed Nov 2026.
10. Pixotter. "How to Check DPI on Windows." Quotes: Windows Properties shows "Horizontal resolution and Vertical resolution"; when no DPI tag exists "the field shows 96 DPI by default." pixotter.com. 17 Mar 2026.
11. Stack Overflow. "How can I read the DPI for a JPG file on Android?" Byte layout: skip to the density unit byte, "0 for none specified, 1 for PPI, 2 for PPC," then X and Y density. stackoverflow.com. 9 May 2013.
12. Stack Overflow. "Android - how to get or set (print) DPI (dots per inch) of JPEG file." Byte offsets 13–17 for density unit and X/Y resolution in the JFIF segment. stackoverflow.com. 19 Feb 2014.
13. Sony. Support article on photo DPI ratings. Quote: the rating "is a print setting assigned to the pictures by the software; it is not associated with how the camera takes the pictures." sony.com. Accessed Nov 2026.
14. On this site: why smartphone photos default to 72 DPI (Samsung and iPhone EXIF readouts, CIPA DC-008 wording), DPI vs PPI, 300 DPI size chart, minimum print resolution.
15. Arithmetic on this page: 4,032 ÷ 72 = 56.0 in; 4,032 ÷ 300 = 13.44 in; 4,032 ÷ 8 = 504 PPI; 4,032 ÷ 20 = 201.6 PPI. All computed, not estimated.
16. [NEEDS SOURCE before publish] Dated first-hand screenshots: Google Photos details panel (no DPI line), DPI checker result for the same file, Files by Google File info, Windows Properties > Details on the transferred copy.

Fact-check table