PX to MM Converter
Convert pixels to millimeters instantly based on your screen or print DPI.
| Pixels (px) | Millimeters (mm) | Centimeters (cm) | Inches (in) |
|---|
What Is a PX to MM Converter?
A PX to MM Converter is a digital unit conversion tool that turns pixel values into millimeters using a defined resolution setting.
It solves a problem most people don't notice until a design gets printed and the size comes out wrong.
Pixels started as a screen-only concept, and the term itself traces back to "picture element," a single dot of light on a display.
Millimeters describe a fixed physical length under the International System of Units, unrelated to any screen.
Pixels only became relevant to layout work once CSS adopted them as a length unit for web pages.
PX vs MM: Why They Are Not the Same Kind of Unit
Two different categories:
- Millimeter: a fixed physical length, identical everywhere on Earth
- Pixel: a resolution-dependent unit that changes size based on screen density
- No universal ratio connects the two without a dots per inch value attached
A flat 1:1 ratio between px and mm does not exist anywhere in the spec.
The conversion always runs through a chosen DPI figure, which is why a bare "px to mm" question has no single correct answer on its own.
How to Convert PX to MM (Formula and Key Values)
The formula is mm = px ÷ DPI × 25.4.
Divide the pixel count by the resolution setting, then multiply by 25.4, since one inch always equals 25.4 millimeters.
The PX to MM Formula
Worked example at 96 DPI:
- Take 32 px
- Divide by 96, the resolution
- Multiply the result by 25.4
- Answer: 8.47 mm
Change the DPI value and the millimeter result shifts even though the pixel count stays exactly the same.
This is the part that trips people up.
The formula is simple. The variable inside it is not.
Key Figures at Common DPI Values
The W3C CSS specification anchors the whole system to one reference point.
- 1 px at 96 DPI equals 0.26 mm, based on the CSS reference pixel definition (W3C, CSS Values and Units Module)
- 1 px at 72 DPI equals roughly 0.35 mm
- 1 px at 300 DPI equals roughly 0.08 mm
- 1 inch always equals exactly 25.4 mm, the fixed constant behind every row above
Notice how the same 1 px produces three different millimeter values.
The pixel never changes. Only the resolution assumption does.
Why CSS Pixels Are Not the Same as Physical Pixels
A CSS pixel is not a physical dot on a screen.
It's a fixed reference measurement that browsers use so the same layout looks consistent across wildly different displays.
The CSS Reference Pixel
The W3C defines the reference pixel as the visual angle of one pixel on a 96 DPI device, viewed from an arm's length away, about 28 inches.
At that distance the angle works out to roughly 0.0213 degrees, which is exactly where the 1 px equals 0.26 mm figure comes from.
Why this matters: a CSS pixel is defined by geometry and viewing distance, not by the actual dot pitch of any specific monitor.
That's why a pixel density reading from one monitor can't be assumed to match another.
Device Pixel Ratio and Screen Scaling
Modern screens pack multiple physical dots into the space of a single CSS pixel.
MDN documentation states that a devicePixelRatio of 1 indicates a classic 96 DPI display, while a ratio of 2 is expected on Retina or HiDPI screens.
| Device Pixel Ratio | Screen Type | Physical Pixels per CSS Pixel |
|---|---|---|
| 1 | Standard 96 DPI display | 1 |
| 2 | Retina / HiDPI | 4 (a 2x2 grid) |
| 3+ | High-density mobile screens | 9 or more |
Actual screen resolution in the field varies enormously, which is exactly why one px to mm output can't be trusted across devices without checking the ratio first.
StatCounter data puts 1920x1080 as the most common desktop resolution worldwide, holding a 20.2% share as of June 2026, with dozens of other resolutions splitting the remainder.
PX to MM at 96 DPI vs 300 DPI: Which Standard to Use
Use 96 DPI for anything staying on a screen, and 300 DPI for anything headed to a printer.
Mixing the two up is the single most common mistake in this entire conversion process.
Web Design: 96 DPI
96 DPI is the accepted web standard, matching the CSS reference pixel definition used by every modern browser.
- Replaced the older 72 DPI assumption carried over from early Mac displays
- Keeps layout math consistent with relative CSS units like rem and em
- Works fine for on-screen mockups, wireframes, and browser rendering
It falls apart the moment the file gets sent to a printer.
Print Design: 300 DPI
Print professionals settled on a much higher resolution standard for one simple reason: dot visibility at close range.
At 300 DPI, the human eye can't resolve individual dots from normal reading distance.
A standard ID-1 payment card under ISO/IEC 7810 measures 85.60 by 53.98 mm, and print shops check card-sized files like this against their resolution before anything goes to press.
Pros of the print standard:
- Sharp text and fine detail at close viewing range
- Consistent output across most commercial printers
Cons of the print standard:
- Produces oversized file sizes if applied to web assets
- Wastes rendering time in a browser, where 300 DPI serves no purpose
PX to MM Conversion Chart for Common Values
Below are the millimeter equivalents for pixel values that come up constantly in web and print work.
Figures are rounded to two decimal places for practical use.
| Pixels (px) | MM at 96 DPI | MM at 300 DPI |
|---|---|---|
| 1 px | 0.26 mm | 0.08 mm |
| 8 px | 2.12 mm | 0.68 mm |
| 16 px | 4.23 mm | 1.35 mm |
| 32 px | 8.47 mm | 2.71 mm |
| 50 px | 13.23 mm | 4.23 mm |
| 100 px | 26.46 mm | 8.47 mm |
| 500 px | 132.29 mm | 42.33 mm |
An A4 sheet measures 210 by 297 mm under the ISO 216 paper standard, which puts the 500 px row at roughly two thirds of an A4 page's width at 96 DPI.
That comparison is a handy sanity check whenever a converted value looks suspiciously large or small.
Converting PX to CM, Inches, and Points
The same formula that produces millimeters extends to centimeters, inches, and points with a different final multiplier.
Divide by 10 for centimeters, divide by the DPI value alone for inches, and multiply by 0.75 for points.
| Pixels (96 DPI) | Millimeters | Centimeters | Inches | Points |
|---|---|---|---|---|
| 16 px | 4.23 mm | 0.42 cm | 0.17 in | 12 pt |
| 32 px | 8.47 mm | 0.85 cm | 0.33 in | 24 pt |
| 96 px | 25.4 mm | 2.54 cm | 1 in | 72 pt |
The 96 px row lines up perfectly with 1 full inch, which is exactly why 96 became the reference resolution in the first place.
For layout work in centimeters, the same DPI dependency covered earlier applies without exception.
Converting PX to Points for Typography
Points matter most for text sizing rather than shape dimensions.
The CSS specification fixes the relationship at exactly 1 px equals 0.75 pt, a ratio that never changes regardless of screen or print context.
- 16 px body text equals 12 pt, a common baseline in print-style typography
- Font size scaling in design software often works backward from a target point size to a pixel value using this same ratio
Anyone jumping between a browser's pixel-based type scale and a print layout's point-based type scale is really just applying this fixed multiplier.
Tools That Convert PX to MM
Two categories handle this conversion in practice.
Standalone calculators built for a single conversion, and unit settings buried inside design software that already knows the document's resolution.
Online Calculators
Built for speed, not for long-term precision workflows:
- Accept a single px value and a DPI setting, then return the mm result instantly
- Some support batch lists, converting dozens of values in one pass
- Most run entirely in the browser using JavaScript, recalculating as the input changes
They're useful for a quick check. They're not built for tracking a document's resolution setting across a whole project.
Built-in Software Converters
Design applications like Photoshop, Illustrator, and Figma keep unit conversion tied directly to the document's own resolution setting.
What changes automatically:
- Every existing pixel value recalculates its millimeter equivalent the moment the DPI setting changes
- Rulers and guides update to match the new resolution instantly
The catch: the DPI setting has to be correct from the moment the file is created, not fixed after the fact.
How to Convert PX to MM in Photoshop, Illustrator, Figma, and InDesign
Every major design tool handles this conversion differently, and none of them do it automatically without a nudge.
Changing the unit label on screen never changes the DPI value stored underneath it, which is exactly where most workflow mistakes start.
Photoshop
Photoshop keeps resolution and canvas size in the same dialog, which makes the DPI setting hard to miss once you know where to look.
- Open Image, then Image Size
- Uncheck Resample so the pixel count stays fixed
- Change the Resolution field to 300, or whatever DPI the job requires
- Read the width and height fields, now shown in the chosen physical unit
Key setting: unchecking Resample is what locks the pixel count in place while the physical dimensions recalculate around it, according to discussions in Adobe's own community forum.
Skip that step and Photoshop resamples the image instead, changing the actual pixel data rather than just relabeling it.
Illustrator
Illustrator ties its default unit to the intent chosen in the New Document dialog, not to a single global setting.
Preset categories and their defaults:
- Mobile and Web presets default to pixels
- Print and Art & Illustration presets default to points or millimeters
- Each preset also loads a matching color mode and resolution
Adobe's own documentation confirms these presets exist specifically to set dimensions, color mode, and resolution together for different design categories and devices.
Switching a document's units manually afterward, through File, then Document Setup, overrides the display without changing the resolution the preset originally loaded.
For a quick reference on the inch side of that same field, a PX to Inches Converter handles the math Illustrator's own dialog performs internally.
Figma
Figma has no native millimeter unit at all.
Designers working on print layouts inside Figma commonly build a 210 by 297 pixel frame to stand in for an A4 page, a workaround documented directly on Figma's own community forum.
Why that workaround is risky: a 210 px frame is not the same as 210 mm once a real DPI value gets applied, since 210 mm at 96 DPI actually works out to roughly 794 px.
- The px-as-mm trick only holds up as a rough visual proxy, not a print-accurate measurement
- Exporting at a specified DPI is the step that makes the physical size correct on paper
InDesign
- Open Edit, then Preferences, then Units & Increments on Windows, or InDesign, then Preferences on macOS
- Set the Horizontal and Vertical fields under Ruler Units to Millimeters
- Confirm the change, which updates ruler and panel display only
Adobe's InDesign documentation notes that changing ruler units this way never touches existing guides, grids, or object positions, only how the numbers are displayed.
InDesign also accepts a shorthand override: typing a value like 48mm directly into any measurement field, regardless of the ruler's current unit.
Common Mistakes When Converting PX to MM
Most px to mm errors trace back to one of four habits, and all four are easy to avoid once you know to look for them.
| Mistake | Why It Happens | Consequence |
|---|---|---|
| Using 96 DPI on a print file | Carrying over the web default without checking | Printed size comes out roughly a third of what was intended |
| Assuming a fixed px-to-mm ratio | Treating one memorized number as universal | Values are wrong the moment DPI changes |
| Ignoring device pixel ratio | Measuring a mockup screenshot at face value | On-screen measurement doesn't match the CSS layout |
| Rounding too early in a multi-step conversion | Rounding each intermediate value before the final multiply | Small errors compound across a full layout |
Confusing DPI and PPI falls into the same category, since the two terms get used interchangeably in casual conversation but describe different mediums.
One more habit worth flagging: resizing an image without locking the aspect ratio distorts both the pixel dimensions and the physical size at the same time.
- A 32 px square resized unevenly to 40 by 28 px is no longer a square in either pixels or millimeters
- Design software usually offers a lock icon next to width and height fields for exactly this reason
None of these mistakes are complicated once named.
They just aren't obvious until a printed piece or a broken layout points them out.
When PX to MM Conversion Does Not Apply
Not every file has a resolution to convert against in the first place.
A vector file only gains a fixed relationship between px and mm at the moment it gets exported to a raster format or placed into a specific print layout.
The W3C's own SVG specification describes the format as stylable and scalable to different display resolutions, which is precisely why a vector icon has no single px to mm answer until export.
- A 16 px SVG icon scaled up to fill a 1600 px canvas loses no sharpness, since there was never a fixed pixel grid to begin with
- The same operation on a raster PNG would produce a blurry, pixelated result at that scale
Resizing a raster image after the fact breaks any conversion calculated before the resize.
A value worked out for a 500 px wide image no longer applies once that image gets scaled down to 250 px, since the pixel count itself has changed.
Responsive layouts create a similar problem from the opposite direction.
A page that reflows with the viewport doesn't hold one fixed px value for an element across screen sizes, so a millimeter conversion calculated at one breakpoint stops matching reality at another.
The practical limit: a px to mm conversion is only ever correct for one specific device, one specific DPI, and one specific moment in a layout's life, not as a permanent property of the design.
Anyone building fully fluid, responsive design around fixed millimeter targets is fighting the format instead of working with it.
FAQ on PX to MM Converter
Why Does the Same PX Value Look Like a Different Physical Size on Different Screens?
A px is a resolution-dependent unit, not a fixed physical length. Pixel density and device pixel ratio vary by device, so the same 16 px element spans a different number of millimeters on a phone than on a desktop monitor.
Can PX to MM Conversion Be Used Reliably in Responsive Web Design?
Not reliably. Responsive layouts resize elements across breakpoints, so a px value converted to millimeters at one viewport width stops matching physical reality at another. Treat any result as valid for one screen size only.
What Is the Difference Between PX and DP in Mobile Design?
A px is a raw screen pixel, while dp (density-independent pixels) scales automatically with a device's pixel density. Android's UI framework uses dp so a button looks the same physical size across phones with very different screen resolutions.
Does PX to MM Conversion Apply to Exported Image Files Like JPEG or PNG?
Yes, once a resolution value is embedded. A JPEG (in its JFIF or EXIF header) or a PNG (in its pHYs chunk) can carry a DPI tag, and that stored figure, combined with the pixel count, sets the millimeter size in a print layout.
How Do You Verify a PX to MM Converter Result Before You Trust It?
A PX to MM Converter result deserves a quick check against the resolution setting it assumed, the device pixel ratio of the screen involved, and one physical reference measurement before that figure gets built into a layout or sent to print.
Three checks catch most errors early.
- Resolution setting used in the calculation
- Device pixel ratio of the target screen
- One physical reference measurement, such as a ruler
Since 1920x1080 leads global desktop resolution at 20.2 percent (StatCounter, June 2026) and typically pairs with a device pixel ratio of 1, most desktop checks can trust the 96 DPI assumption without measuring the ratio.
Skipping that step leaves Retina and mobile exports unverified, where the shortcut produces a confidently wrong number rather than an obvious one. Checking how many pixels make up an inch on the target device is the logical next comparison to run.