The 7 Best Pixel Converter Tools Compared (2026)

Pixel-to-physical-unit conversion is one of those workflow chores that keeps reappearing — sizing a print, sanity-checking a Figma spec, validating a CSS value against a physical button target. There are dozens of free tools that claim to do it, and a handful built into the design apps you already use. This guide compares the seven we think actually deserve to be on a designer / developer / photographer's bookmark bar in 2026.

We tested each tool on the same five conversions:

1. 100 px → mm at 96 DPI (web default)
2. 1000 px → inches at 300 DPI (print)
3. 8 mm → px at 326 PPI (iPhone 13/14)
4. 1920 px → cm at 460 PPI (iPhone 15 Pro Max)
5. Custom: 250 px → mm at 200 DPI (unusual)

A "good" tool gets the right answer for all five, in under 10 seconds each, on both desktop and mobile.

TL;DR ranking

Rank	Tool	Free	Custom DPI	Device PPI auto-detect	Mobile-friendly	Best for
1	Screen Ruler Pixel Converter	Yes	Yes	Yes	Yes	Default for everyone
2	Photoshop Image Size	No	Yes	No	No	Print workflow with open image
3	Figma Inspector + manual math	Yes (limited)	No	No	Yes	In-design comparison
4	Pixel Converter (Omni Calculator)	Yes	Yes	No	Yes	One-off conversions
5	RapidTables Pixel to mm	Yes	Limited	No	Yes	Quick lookups, English-only
6	DPI Calculator (sven.de)	Yes	Yes	No	Mediocre	Print pros familiar with the tool
7	CSS-Tricks pixel converter snippets	Yes	No	No	N/A	Devs who want to build their own

1. Screen Ruler Pixel Converter ⭐ recommended

URL: /pixel-converter

The full-featured option. Bidirectional conversion (px ↔ mm/cm/inch), custom DPI input, device PPI auto-detection from a 50+ device database, integrated with an on-screen ruler for calibration.

Test results:

• All 5 conversions: ✅ correct
• Average time: 4 seconds
• Mobile UX: clean

Why it ranks #1:

• Auto-detects your device's PPI so "how big will this look on my phone" is one tap, not three minutes of looking up specs.
• Custom DPI input for any non-standard print or display target.
• Bidirectional with a clean toggle — no need to manually rearrange the formula.
• Mobile-first layout that works without zooming.
• Free, no account, no install, no ads in the conversion flow.
• Calibrated mode: combines with the on-screen ruler to verify pixel size against a credit card, A4 paper, or coin.

Limitations:

• Does not export design assets — pure conversion only.
• No batch CSV upload (use a spreadsheet for that).
• Cannot read DPI metadata from an uploaded image file (use Photoshop for that).

2. Photoshop "Image Size" panel

Access: Image → Image Size in Photoshop / Affinity Photo / GIMP / Pixelmator Pro.

The classic answer for print designers. The Image Size panel has been in Photoshop since the early '90s and gives you px / cm / mm / inch dimensions linked to the image's stored DPI.

Test results:

• Conversions 1, 2, 5 (with manual DPI input): ✅ correct
• Conversions 3, 4 (device PPI): ❌ no concept of device PPI, only image DPI

Why it ranks #2:

• Exact for print workflows where you have an actual image file.
• Bidirectional: change px and physical units update, or vice versa.
• Tied to the actual asset: the conversion reflects what will physically print.
• Widely understood: anyone with print experience knows the panel.

Limitations:

• Requires an image to be open. You cannot do an abstract "how many px is 1 cm at 300 DPI" without making a dummy image.
• No device PPI: irrelevant for "how big on iPhone 15" questions.
• Subscription cost for Photoshop. GIMP / Pixelmator are alternatives but heavier than a web tool for a one-off check.
• Desktop only: there is no useful mobile equivalent.

3. Figma Inspector + manual math

Access: select object, look at the right-hand inspector panel in Figma / Sketch / Adobe XD.

Not really a pixel converter, but you end up using it as one when you are already inside the design file. Figma reports dimensions in CSS px; you do the px → physical math yourself.

Test results:

• Conversions 1–5: ✅ correct only if you also have a calculator and remember the formula.
• Average time including the math step: 30 seconds.

Why it ranks #3:

• Already in front of you if you're designing — no app switch.
• Pixel-exact within the design file.

Limitations:

• Pure CSS px: no physical-unit display.
• No DPI awareness: Figma assumes 72 DPI for its "1×" mode regardless of target medium.
• Manual math required: just multiply / divide externally.

4. Omni Calculator — Pixel Converter

URL: omnicalculator.com/conversion/pixel

A clean, well-explained web calculator that handles the basic conversion well.

Test results:

• Conversions 1, 2, 5: ✅ correct
• Conversion 3, 4: ✅ correct only if you manually look up and enter the device's PPI

Why it ranks #4:

• Free, no install.
• Clear input fields with labeled DPI.
• Math explanation below the calculator is good for learning.
• Mobile-friendly.

Limitations:

• No device PPI database: every device-specific question requires you to look up the PPI elsewhere.
• Single direction at a time (px → physical OR physical → px, switch the page).
• Ads in the page margin can be distracting on mobile.

5. RapidTables Pixel to mm

URL: rapidtables.com/convert/length/pixel-to-mm

Minimal, fast, no-frills.

Test results:

• Conversions 1, 2 (96 DPI defaults): ✅ correct in 3 seconds
• Conversion 5 (custom 200 DPI): partial — the tool offers a fixed dropdown of DPI options, no free text input
• Conversions 3, 4 (high-PPI devices): ❌ device PPIs not in the dropdown

Why it ranks #5:

• Extremely fast for common conversions.
• Light page weight: loads in under a second on mobile.

Limitations:

• DPI dropdown only — can't enter 326 or 460 for modern phones.
• English only.
• Single direction.

6. DPI Calculator (sven.de)

URL: dpi.lv

A long-time favourite of print pros. The tool's quirk is it accepts resolution × diagonal size and computes PPI from those, then converts.

Test results:

• Conversions 1, 2, 5: ✅ correct
• Conversions 3, 4: ✅ correct if you know the device's exact resolution and diagonal inches, which is more friction than a database lookup

Why it ranks #6:

• Two-step workflow (compute PPI, then convert) is rigorous and educational.
• Custom DPI fully supported.

Limitations:

• No device database: you supply resolution and diagonal manually.
• UI looks dated — functional but ugly.
• Desktop-oriented: mobile layout is awkward.

7. Custom code snippets (CSS-Tricks, MDN, Stack Overflow)

Not a tool but a pattern: a one-liner JavaScript function that does the conversion, copied into your project.

function pxToMm(px, dpi = 96) {
  return (px / dpi) * 25.4;
}

Test results:

• All 5: ✅ correct, with manually supplied DPI.

Why it ranks #7:

• Embeddable: you can build a conversion directly into your own design system, validator, or workflow tool.
• Zero dependencies.

Limitations:

• No UI by default.
• No device PPI lookup unless you write the database yourself.
• Only useful for developers, not designers or photographers.

Honourable mentions

• fromCharCode-style hacks in Excel / Google Sheets — covered in our pixel-converter-vs-alternatives article; useful for batches.
• Print software auto-fit (e.g. Lightroom Print module) — handles the conversion implicitly when you tell it the paper size and DPI. Not a converter you "use", but it does the work in the background.
• Native macOS Preview Print dialog — shows you the equivalent size in inches and cm when you set up a print job. Not interactive but useful as a sanity check.

Verdict

If you are a designer, developer, photographer, or anyone who needs pixel ↔ physical conversion more than once a month, the Screen Ruler Pixel Converter is the highest-leverage choice: it has the device PPI database, custom DPI, bidirectional input, and mobile UX that the alternatives miss. It is free, instant, and integrates with the on-screen ruler when you want to verify physically.

Use Photoshop's Image Size for actual print prep with an open image, Figma's inspector for in-design comparison, and Omni Calculator if you specifically prefer their UX.

Skip the rest unless you have a niche reason.

Try the Screen Ruler Pixel Converter — bookmark it and you have probably solved the conversion problem for the year.