15 Questions About Pixel Converter Answered

A pixel converter looks like a simple input box, but underneath it sits a stack of concepts that trip people up — DPI versus PPI, CSS pixels versus device pixels, what auto-detection actually does, and why two converters can give different answers for the same input. This FAQ answers the 15 questions we see most often.

Open the Screen Ruler Pixel Converter alongside this page if you want to try the answers as you read.

1. What is a pixel converter?

A pixel converter is a tool that converts a count of pixels to a physical length (millimeters, centimeters, or inches), or vice versa, at a given DPI or PPI. You give it a number and a resolution, and it returns the size that number represents in the real world.

The formula is:

• inches = pixels / DPI
• mm = inches × 25.4

The converter just runs that formula for you, in both directions, with sensible presets and device PPI auto-detection.

2. What's the difference between DPI and PPI?

DPI (dots per inch) historically describes printer output: how many ink dots a printer lays down per linear inch of paper. PPI (pixels per inch) describes a display: how many pixels per linear inch of screen.

In practice the two terms are used interchangeably for the purposes of unit conversion, because the math is identical. The pixel converter accepts either as the "resolution" input.

Where it matters:

• For print output, use DPI of the printer or document (typically 300 or 600).
• For on-screen size, use the device's PPI (varies — see below).

3. What is "device PPI auto-detection"?

The pixel converter detects what device you are currently viewing on (iPhone 15, Galaxy S24, MacBook Pro 14, etc.) and looks up its real screen PPI. It uses screen dimensions, devicePixelRatio, and a device database to identify the device.

This matters because a "100 px" image looks 24% bigger on a 326 PPI iPhone than a 401 PPI iPhone Pro Max — auto-detection gives you the real on-device physical size, not a generic 96 DPI assumption.

4. Why does my converter give a different answer than another converter?

Three common reasons:

1. Different DPI assumption: one tool assumes 96 DPI (web default), another 72 DPI (legacy print/screen), a third 300 DPI (print). For 100 px, that is 26.5 mm vs 35.3 mm vs 8.5 mm — all "correct" at their respective DPIs.
2. CSS pixel vs device pixel: on a Retina screen the browser reports CSS pixels (logical), but the actual hardware fires at 2× or 3× density. A converter that does not account for devicePixelRatio will mismatch.
3. Rounding: some converters round at intermediate steps; the Screen Ruler converter keeps full precision until the final display.

To get the right answer, pick the DPI/PPI that matches your medium and the converter's pixel mode that matches your input.

5. What's the default DPI for the web?

96 DPI by historical convention. The W3C CSS specification anchors 1 inch = 96 px for "reference" rendering. Modern displays with devicePixelRatio > 1 still expose CSS as 96 DPI for layout purposes, but render at higher density.

6. What DPI should I use for print?

• Standard photo / document print: 300 DPI.
• Newspaper / low-quality: 150 DPI.
• Large-format / poster: 150 DPI is often enough because viewing distance is greater.
• Fine-art / billboard up close: 600 DPI.
• Billboard from far away: 30–72 DPI is fine.

Match the converter's DPI input to the printer's output DPI for the most accurate physical size.

7. Why is my image blurry when I print it?

Almost always because the image's pixel count is too low for the print size at 300 DPI. A 1000 px image at 300 DPI prints sharp at 3.33 inches (≈85 mm). Print it at 6 inches and the effective DPI drops to 167, which the eye reads as soft. Use the converter to check: pixel_count / target_inches = effective DPI. If the result is below 200, the image will look soft.

8. What's the smallest pixel I can see on my screen?

At typical viewing distance (50 cm for desktop, 30 cm for phone) the human eye can resolve about 60 pixels per degree of visual angle. For a 326 PPI phone at 30 cm that is roughly 1 px — the so-called "Retina threshold". For a 110 PPI desktop monitor at 50 cm it is also around 1 px. Below that and the eye blends adjacent pixels.

The pixel converter does not directly compute visual acuity, but you can use it: convert "1 arcminute at 30 cm" → about 0.087 mm → at 326 PPI = 1 px. That confirms the threshold.

9. Does the pixel converter work on mobile?

Yes. The interface is mobile-optimized — no zooming required, large tap targets, and on-screen keyboard inputs are numeric. The device PPI auto-detection works on iOS and Android browsers.

10. Does devicePixelRatio (DPR) matter?

DPR matters when you are converting between CSS pixels (what your code emits) and device pixels (what the hardware lights up). On a Retina iPhone with DPR = 3, a 100 CSS-px-wide element is rendered with 300 device pixels horizontally.

For physical-size conversion:

• Use CSS pixels when you want to know how big an element appears in browser layout.
• Use device pixels when you are matching to a hardware-level pixel grid (e.g. embedded UI, e-ink, retro display).

The Screen Ruler pixel converter defaults to CSS pixels but exposes a device-pixel mode.

11. Can I convert from physical size back to pixels?

Yes — the converter is bidirectional. Enter "8 mm" and the device PPI input field, and it returns the corresponding pixel count. This is the right direction when you have a physical design requirement (button must be at least 8 mm tall for thumb tap) and need to know how many pixels to allocate.

12. Is there a difference between "px" and "rem" / "em"?

Yes, big one. rem and em are CSS units relative to font size, not to physical length. A 1 rem element is 16 CSS px at default settings but becomes 24 px if the root font is 150%. The pixel converter does not convert rem directly — first resolve rem to px in your stylesheet (document.documentElement.style.fontSize), then convert px to physical units.

13. What about "viewport units" (vw, vh)?

Also dynamic. 1 vw = 1% of viewport width, in CSS px. Resolve to px first based on the viewport size of your target device, then run the conversion. The pixel converter accepts CSS px directly.

14. How accurate is the converter?

The math is exact to floating-point precision. The accuracy bottleneck is the input:

• DPI / PPI input: if you mis-specify the DPI, the answer is wrong proportionally. Auto-detection mitigates this for the current device.
• Device PPI lookup: the Screen Ruler device database has 50+ devices with manufacturer-specified PPI. For listed devices the lookup is exact. For unlisted devices, the converter falls back to a screen-dimension-based estimate (less accurate, typically ±2%).
• Print DPI: assumes the printer hits the specified DPI exactly. Real printers vary by 1–2% from spec.

For most practical purposes — sizing a button, checking print clarity, comparing devices — the converter is well within the tolerance that matters.

15. Why not just use a tape measure?

You can — that is what the Screen Ruler on-screen ruler is for, with a calibration step against a known reference object. The pixel converter is for the inverse problem: you have a pixel count (from a Figma spec, a CSS value, a print job), and you want to know what physical size it corresponds to, without rendering it first. Use the on-screen ruler for "how big is this thing", use the pixel converter for "how many pixels do I need".

Bonus: rapid-fire micro answers

A few more questions we hear regularly that don't need a full section:

• Does monitor brand matter? No — only its physical PPI matters. Two 27" monitors with the same resolution have the same PPI regardless of brand.
• Why does the same PNG look bigger in Photoshop than in the browser? Photoshop reads the file's embedded DPI; the browser ignores it and uses CSS px. Photoshop at 72 DPI displays "larger" simply because it scales the image at 1 image-px-per-screen-px.
• Can I convert SVG sizes? Yes — SVG dimensions are expressed in CSS px by default (with viewBox controlling scaling). Treat them like any other CSS px input.
• Why does iOS report a smaller screen.width than my phone's actual resolution? Because iOS exposes CSS pixels, not device pixels. Multiply by devicePixelRatio to get the hardware count.
• Is there a "right" DPI for a 4K monitor? Depends on the diagonal. A 27" 4K display is about 163 PPI; a 32" 4K is about 138 PPI; a 43" 4K is about 103 PPI. The pixel converter knows these for listed monitors.
• Why does scaling my browser to 200% change layout but not PPI? Browser zoom multiplies CSS px values for layout but does not change the underlying physical PPI. The converter uses unzoomed reference values internally.
• Can I use the converter offline? The page caches after first load, and the math runs entirely client-side, so once loaded it works offline.
• Does the converter respect dark mode and accessibility settings? Yes — the UI follows the system theme and supports keyboard-only operation, screen readers, and high-contrast modes.

Try it

Most of these questions are answered in one input on the Screen Ruler Pixel Converter. Open it, pick your DPI or let the converter auto-detect your device, and the answer is one keystroke away.

If your question is not here, the Pixel Converter user guide walks through the full workflow with screenshots, and the Pixel Converter technical deep-dive covers the math and engineering choices.