PX to CM Converter
This PX to CM Converter is a fast, browser-based tool for converting pixel values to centimeters and back.
Designers and developers constantly deal with unit mismatches between screen and print. This tool bridges that gap instantly.
Key features:
-
Bidirectional conversion -- switch between PX to CM and CM to PX with one click
-
DPI presets for common environments: Screen (96), Print (72), HD (120), Retina (144), and 4K (192)
-
Custom DPI input for non-standard displays or print specs
-
Live formula display shows the exact calculation as you type
-
Reference table of common values, clickable to populate the input
-
Copy button to grab the result in one click
No installation. No signup. Just type a number and get your answer.
How to Use This PX to CM Converter
Enter a pixel value in the converter above, pick a DPI preset or type your own, and the centimeter result updates as you type.
The default DPI is 96, the standard for web browsers and Windows displays. Switch to PX → CM or CM → PX with the toggle, and use the copy button to grab the result.
A pixel is a relative unit tied to screen density. A centimeter is a fixed physical unit. Converting between them only works once you know the DPI (dots per inch) of the display or output device. Without DPI, the conversion is meaningless.
The PX to CM Conversion Formula
The math behind every px to cm converter is short:
cm = px ÷ DPI × 2.54
Divide the pixel value by the DPI to get inches, then multiply by 2.54 to get centimeters. At 96 DPI, 100px equals 2.646 cm.
Worked example, using a 480px value at 96 DPI:
- 480 ÷ 96 = 5 inches
- 5 × 2.54 = 12.7 centimeters
Change the DPI and the result changes completely: same pixel count, different physical size.
The 2.54 constant is not a rounded estimate. NIST documents the 1959 international agreement that fixed the inch at exactly 25.4mm (2.54cm) across the US, UK, Canada, and other English-speaking nations.
Anyone who needs the same pixel value expressed in inches instead of centimeters can run it through a dedicated px to inches converter, which drops the final multiplication step entirely.
Designers working in points rather than metric units have a similar shortcut in a px to pt converter, which swaps 2.54 for the point definition instead.
PX to CM Conversion Table
Quick reference at 96 DPI - the screen resolution standard for most displays.
| Pixels (PX) | Centimeters (CM) |
|---|---|
| 1 px | 0.02646 cm |
| 2 px | 0.05291 cm |
| 3 px | 0.07937 cm |
| 4 px | 0.10583 cm |
| 5 px | 0.13229 cm |
| 6 px | 0.15875 cm |
| 8 px | 0.21167 cm |
| 10 px | 0.26458 cm |
| 12 px | 0.31750 cm |
| 14 px | 0.37041 cm |
| 16 px | 0.42333 cm |
| 18 px | 0.47625 cm |
| 20 px | 0.52916 cm |
| 24 px | 0.63499 cm |
| 28 px | 0.74082 cm |
| 32 px | 0.84665 cm |
| 36 px | 0.95249 cm |
| 40 px | 1.05832 cm |
| 44 px | 1.16415 cm |
| 48 px | 1.26998 cm |
| 50 px | 1.32290 cm |
| 56 px | 1.48565 cm |
| 64 px | 1.69330 cm |
| 72 px | 1.90095 cm |
| 80 px | 2.10860 cm |
| 90 px | 2.37573 cm |
| 96 px | 2.540 cm |
| 100 px | 2.64583 cm |
| 128 px | 3.387 cm |
| 256 px | 6.773 cm |
| 512 px | 13.547 cm |
| 1024 px | 27.093 cm |
At 72 DPI, every value above increases by roughly 33%.
CM to PX Converter
Need the reverse? The formula flips:
px = cm × DPI ÷ 2.54
At 96 DPI, 1 cm equals approximately 37.8 pixels.
This comes up constantly when converting print dimensions into screen-ready pixel values - especially when moving specs from a physical mockup into a digital layout.
CM to PX Conversion Table
Quick reference at 96 DPI.
| Centimeters (CM) | Pixels (PX) |
|---|---|
| 0.1 cm | 3.77953 px |
| 0.2 cm | 7.55906 px |
| 0.3 cm | 11.33858 px |
| 0.4 cm | 15.11811 px |
| 0.5 cm | 18.89764 px |
| 0.6 cm | 22.67717 px |
| 0.8 cm | 30.23623 px |
| 1 cm | 37.79528 px |
| 1.2 cm | 45.35433 px |
| 1.4 cm | 52.91339 px |
| 1.5 cm | 56.69291 px |
| 1.6 cm | 60.47244 px |
| 1.8 cm | 68.03150 px |
| 2 cm | 75.59055 px |
| 2.4 cm | 90.70866 px |
| 2.8 cm | 105.82677 px |
| 3 cm | 113.38583 px |
| 3.2 cm | 120.94488 px |
| 3.6 cm | 136.06299 px |
| 4 cm | 151.18110 px |
| 4.4 cm | 166.29921 px |
| 4.8 cm | 181.41732 px |
| 5 cm | 188.97637 px |
| 5.6 cm | 211.02362 px |
| 6.4 cm | 241.88976 px |
| 7.2 cm | 272.75591 px |
| 8 cm | 303.62205 px |
| 9 cm | 340.15748 px |
| 10 cm | 377.95276 px |
| 15 cm | 567 px |
| 21 cm | 794 px |
| 29.7 cm | 1123 px |
These values map directly to standard paper sizes - A4 is 21 × 29.7 cm, or 794 × 1123 px at 96 DPI.
What Is a PX to CM Converter?
A px to cm converter is a small calculation tool that turns a pixel value into a physical centimeter measurement.
It works by running the pixel number through a density value, since a pixel on its own has no fixed size in the real world.
Two things go into the box every time:
- a pixel value, pulled from a screen, a design file, or a spec sheet
- a density value, expressed in dots per inch, that tells the tool how large each pixel should be treated as
Most people reach for this kind of converter in one of two situations: sizing something for a screen, or sizing something for print.
Change the density value and the centimeter output changes too, even with the exact same pixel count.
PX vs CM: What Is the Difference?
A centimeter is a fixed unit under the International System of Units.
One centimeter is one centimeter, on a ruler, on a wall, anywhere it gets measured.
A pixel is not fixed at all.
The word itself is shorthand for "picture element," and what a pixel actually represents changes depending on the screen or file rendering it.
Quick comparison:
- Centimeter: physical, constant, measurable with a ruler
- Pixel: digital, variable, only meaningful alongside a density value
That gap is the entire reason a converter exists in the first place.
What Is DPI and Why It Determines the PX to CM Result
DPI stands for dots per inch, and it sets how many pixels get packed into one inch of physical space.
Raise the DPI and the same pixel count produces a smaller printed or displayed size. Lower it, and that pixel count spreads out wider.
| DPI value | Typical context | Common use |
|---|---|---|
| 72 | Legacy screen default | Older Mac and web graphics |
| 96 | Standard screen reference | CSS pixel, Windows display |
| 150 | Draft or proof print | Internal review prints |
| 300 | High-quality print | Brochures, posters, photos |
PPI and DPI get used interchangeably in casual conversation, though they describe slightly different things. The distinction between the two matters more in print production than in everyday screen work.
What actually changes between devices is how tightly pixels are packed onto the physical panel, something a phone screen and a desktop monitor rarely share.
Real screens rarely match the reference value anyway.
Statcounter Global Stats data from June 2026 shows 1920x1080 remains the single largest desktop resolution worldwide, at 20.2% share. That one resolution spans monitors with very different physical sizes and pixel densities.
How the CSS Reference Pixel Affects PX to CM Conversion
The W3C's CSS Values and Units Module Level 3 defines the reference pixel as the visual angle of one pixel on a 96 DPI device, viewed from an arm's length of about 28 inches.
That works out to a viewing angle of roughly 0.0213 degrees, which the spec translates to about 0.26mm per pixel at ordinary reading distance.
This is why every browser treats 96 DPI as the baseline for pixel math, no matter what the screen's actual hardware density looks like.
A high-density phone screen or an Apple Retina display packs far more physical dots into that same reference pixel. The device pixel ratio setting exists to hide that gap from the styling layer.
Open Chrome DevTools on any page and the reported box dimensions stay in these reference pixels, not raw hardware pixels. That is what keeps px to cm math consistent across devices.
CSS pixel vs device pixel:
- CSS pixel: the logical unit written in stylesheets, always tied to the 96 DPI reference
- Device pixel: the actual hardware dot, which can outnumber CSS pixels 2 to 1 or more on dense screens
Anyone comparing px to a relative unit runs into a related question, covered in the px vs rem breakdown, since neither unit carries a fixed physical size on its own.
The reference pixel only exists because the CSS specification needed one fixed number to keep layouts predictable across wildly different screens.
Which DPI Should You Use: Screen vs Print
Screen work runs on 96 DPI, the same reference value CSS locks in for pixel math.
Print work runs on 300 DPI, which Adobe's own resolution documentation names as the industry standard for high-quality printed output.
Quick picks:
- 96 DPI - web and Windows screens (the converter's default)
- 72 DPI - older Mac screens and legacy files; still shows up in some print contexts
- 150 DPI - draft proofs and internal review prints
- 300 DPI - final print output
If you are designing for screen, use 96. For print, check the document settings first.
Screen context:
- Web pages, app interfaces, on-screen mockups
- 96 DPI keeps pixel values matched to CSS math
- Higher DPI values add nothing, since screens display in raw pixels regardless of the tag
Print context:
- Brochures, posters, packaging, photo prints
- 300 DPI avoids visible dot patterns at normal viewing distance
- Lower DPI values, 150 or under, work fine for draft proofs but not final output
Legacy files sometimes still carry a 72 DPI tag, a holdover from early screen defaults that has nothing to do with today's print requirements.
Professional print houses occasionally ask for values above the standard, though the 300 DPI benchmark covers nearly all commercial printing needs without added cost.
PX to CM at Common DPI Standards
These figures answer the lookup question directly, without running the formula by hand.
Key figures, calculated at standard DPI values:
- 100px at 96 DPI = 2.65cm
- 100px at 150 DPI = 1.69cm
- 100px at 300 DPI = 0.85cm
- 1920px at 96 DPI (a Full HD screen width) = 50.8cm
The gap between the first and third value shows exactly why a converter needs a DPI input, not just a pixel input.
Every one of these numbers traces back to how many pixels fit inside one inch at the chosen density, the same relationship the core formula relies on.
Converting PX to CM in Design Software
Every major design tool treats pixels differently once cm enters the picture.
Some switch units with one click. Others require the formula to be run by hand outside the program.
| Tool | Native unit | Converts to cm | Default DPI assumption |
|---|---|---|---|
| Photoshop | Pixels or physical units | Yes, via Image Size dialog | 72 or 300, set per document |
| Illustrator | Points or pixels | Yes, via unit preferences | Depends on document profile |
| Microsoft Word | Inches | Built in, no formula needed | Not resolution based |
| Figma | Pixels only | No, manual formula required | None, exports at fixed multiples |
Microsoft's own support documentation lists five selectable measurement units in Word: inches, centimeters, millimeters, points, and picas.
Pixels are not among them, since Word treats a page as a physical object from the start.
Figma runs the opposite way. Anyone who has gone through the basics of how to design a website in Figma knows every frame, spacing value, and text size stays in pixels, with no built-in physical unit at all.
Teams that need a printed piece out of Figma typically handle the jump at export time, following the same steps used to export a Figma file to PDF, then let the receiving print software apply the DPI.
How to Convert PX to CM Step by Step
The manual process takes a handful of steps to go from a raw pixel value to a number that means something on paper.
- Find the pixel value, from a design file, an image property panel, or a spec sheet
- Confirm the DPI the output needs, 96 for screen or 300 for print
- Divide the pixel value by that DPI to get inches
- Multiply the result by 2.54 to get centimeters
- Round to a sensible precision, usually one or two decimal places
- Check the result against the intended output size before finalizing
That last step catches more errors than any other.
A standard A4 page measures 21cm by 29.7cm under ISO 216, the international paper size standard. That gives a quick sanity check for anything meant to print at that size.
Checking the converted width against the converted height also protects the original aspect ratio. A rounding step applied to one dimension but not the other will visibly warp the output.
When PX to CM Conversion Does Not Apply
Not every pixel value has a centimeter answer worth trusting.
Vector formats break the entire premise. An SVG file carries no fixed pixel size at all, since its coordinates scale to whatever container or viewBox displays them.
A shape defined at 100 units wide can render at 10px or at 10,000px, and both are equally correct.
Cross-device consistency is the second failure point.
Android's own developer documentation groups screens into density buckets running from 160dpi at the low end (mdpi) up to 640dpi at the high end (xxxhdpi). That is a fourfold spread no single conversion can account for.
A px to cm result calculated for one phone in that range will not match the physical size on another, even when both report the same screen resolution.
Common mistakes:
- Wrong DPI assumed: using 72 for a print job that actually needs 300
- Mixing pixel types: treating device pixels and CSS pixels as interchangeable
- Skipping the DPI step entirely: converting a raw pixel count with no density value attached
FAQ on PX To CM Converter
What Does PX Stand For, and What Does CM Stand For?
PX shortens pixel, the smallest addressable unit on a digital display, itself short for picture element. CM shortens centimeter, a fixed metric unit equal to one hundredth of a meter, placing the two terms in entirely different measurement systems.
Is a Pixel a Fixed Unit or a Relative Unit?
CSS technically classifies px as an absolute length unit, alongside cm and inches, yet its physical size still depends on screen density. That classification is a naming convention inside the specification, not a guarantee of physical consistency across devices.
Why Does the Same Pixel Value Produce Different Centimeter Values on Different Screens?
Every physical screen has its own pixel pitch, the actual distance between two dots on the panel, set by the manufacturer. A converter assumes one DPI value, so a phone panel and a monitor panel translate the identical pixel count into different real-world sizes.
Does the Conversion Round the Result, and How Precise Is It?
Most calculators round to two decimal places, enough precision for design and print work. That rounding introduces a fractional millimeter of error, invisible at normal viewing distance but worth recalculating for high-precision manufacturing or engineering drawings.
Is It Better to Convert Manually or Use an Online Converter?
Manual math works fine for a single value. Repeated conversions across a full page layout or a print catalog invite arithmetic mistakes, and an online converter removes that risk while keeping the same underlying formula.
Do PX to CM Results Match Exactly Across Every Device?
No. The math produces one correct number for the DPI entered, but that number only matches physical reality on a device calibrated to that exact density, so treat the result as a planning figure rather than a guaranteed physical measurement.
When Does a PX to CM Converter Stop Being Accurate?
A PX to CM Converter stops being accurate the moment its single DPI assumption meets a screen or printer running a different density than the one entered into the formula, since the math stays correct while the physical output drifts.
Locking the calculation to one density value trades cross-device precision for a single repeatable number, useful for planning but not for pixel-perfect physical matching.
Three checks resolve most mismatches, in this order:
- Confirm the DPI entered against the target device or printer
- Check whether the source file carries a device pixel ratio above 1
- Verify the rounded output against the intended physical size
Moving from a fixed physical target to responsive sizing raises a related question, addressed directly in the comparison of em vs rem units.