PX to CM Converter
Enter a size in pixels and choose the resolution to get centimeters, or type centimeters to find the pixels you need. Presets show exactly how many pixels A4, Letter, photo and poster prints need at your DPI.
Last updated:
Step-by-step calculation
How to use the PX to CM Converter
- Type the pixels in the Pixels box. Centimeters appear instantly.
- Choose the DPI from the presets or type a custom value (96 for screens, 300 for print).
- Need pixels for a print? Pick a paper size in Print size presets and press Load width or Load height.
- Going the other way? Type in the Centimeters box, or press the ⇄ swap button.
- Copy the result or print the conversion tables.
Pixels to centimeters formula
- Divide the pixels by the DPI (dots or pixels per inch) to get inches.
- Multiply the inches by
2.54, the number of centimeters in an inch.
Worked example: a 1,800 px wide photo printed at 300 DPI → 1,800 ÷ 300 = 6 in, and 6 × 2.54 = 15.24 cm. The same file shown at 96 DPI on screen measures 1,800 × 2.54 ÷ 96 = 47.63 cm.
Reverse formula (centimeters to pixels): px = cm × DPI ÷ 2.54. Example: a 10 cm wide logo at 300 DPI needs 10 × 300 ÷ 2.54 = 1,181 px.
Pixels have no physical size on their own. The DPI (also called PPI for screens and images) decides how many of them fit in an inch, so always convert at the resolution you will print or display at. In CSS, 1 px is defined as 1/96 inch, so 96 DPI is the right choice for web layouts.
PX to CM conversion table
The tables follow the DPI you choose above. Click any row to load it, or print the tables.
Pixels to centimeters at 96 DPI
| Pixels | Centimeters |
|---|---|
| 1 px | 0.026 cm |
| 2 px | 0.053 cm |
| 5 px | 0.132 cm |
| 10 px | 0.265 cm |
| 16 px | 0.423 cm |
| 20 px | 0.529 cm |
| 24 px | 0.635 cm |
| 32 px | 0.847 cm |
| 38 px | 1.005 cm |
| 48 px | 1.27 cm |
| 50 px | 1.323 cm |
| 64 px | 1.693 cm |
| 72 px | 1.905 cm |
| 96 px | 2.54 cm |
| 100 px | 2.646 cm |
| 120 px | 3.175 cm |
| 128 px | 3.387 cm |
| 150 px | 3.969 cm |
| 200 px | 5.292 cm |
| 250 px | 6.615 cm |
| 256 px | 6.773 cm |
| 300 px | 7.938 cm |
| 400 px | 10.583 cm |
| 500 px | 13.229 cm |
| 512 px | 13.547 cm |
| 600 px | 15.875 cm |
| 640 px | 16.933 cm |
| 720 px | 19.05 cm |
| 768 px | 20.32 cm |
| 800 px | 21.167 cm |
| 1,000 px | 26.458 cm |
| 1,024 px | 27.093 cm |
| 1,080 px | 28.575 cm |
| 1,200 px | 31.75 cm |
| 1,280 px | 33.867 cm |
| 1,500 px | 39.688 cm |
| 1,920 px | 50.8 cm |
| 2,000 px | 52.917 cm |
| 2,400 px | 63.5 cm |
| 2,480 px | 65.617 cm |
| 3,000 px | 79.375 cm |
| 3,508 px | 92.816 cm |
| 3,840 px | 101.6 cm |
| 4,000 px | 105.833 cm |
| 5,000 px | 132.292 cm |
| 6,000 px | 158.75 cm |
Centimeters to pixels at 96 DPI
| Centimeters | Pixels |
|---|---|
| 0.1 cm | 4 px |
| 0.25 cm | 9 px |
| 0.5 cm | 19 px |
| 1 cm | 38 px |
| 1.5 cm | 57 px |
| 2 cm | 76 px |
| 2.5 cm | 94 px |
| 3 cm | 113 px |
| 4 cm | 151 px |
| 5 cm | 189 px |
| 6 cm | 227 px |
| 7 cm | 265 px |
| 8 cm | 302 px |
| 9 cm | 340 px |
| 10 cm | 378 px |
| 12 cm | 454 px |
| 15 cm | 567 px |
| 18 cm | 680 px |
| 20 cm | 756 px |
| 21 cm | 794 px |
| 25 cm | 945 px |
| 29.7 cm | 1,123 px |
| 30 cm | 1,134 px |
| 40 cm | 1,512 px |
| 50 cm | 1,890 px |
| 60 cm | 2,268 px |
| 70 cm | 2,646 px |
| 80 cm | 3,024 px |
| 90 cm | 3,402 px |
| 100 cm | 3,780 px |
Common pixel sizes at 96 DPI
| Pixels | Centimeters | Example |
|---|---|---|
| 16 px | 0.42 cm | Favicon / small icon |
| 96 px | 2.54 cm | Exactly 1 inch at 96 DPI |
| 300 px | 7.94 cm | Exactly 1 inch at 300 DPI |
| 1,080 px | 28.57 cm | Instagram post width |
| 1,280 px | 33.87 cm | HD video width |
| 1,920 px | 50.8 cm | Full HD width |
| 2,480 px | 65.62 cm | A4 width at 300 DPI |
| 3,508 px | 92.82 cm | A4 height at 300 DPI |
| 3,840 px | 101.6 cm | 4K UHD width |
| 6,000 px | 158.75 cm | 24 MP camera image width |
Pixels per centimeter at common resolutions
| DPI / PPI | Pixels per cm | Size of 1 px | 1,000 px is | Typical use |
|---|---|---|---|---|
| 72 | 28.35 | 0.353 mm | 35.28 cm | Web images, old Mac screens, PDF points |
| 96 | 37.80 | 0.265 mm | 26.46 cm | CSS pixels, Windows at 100% scaling |
| 150 | 59.06 | 0.169 mm | 16.93 cm | Posters and banners viewed from a distance |
| 300 | 118.11 | 0.085 mm | 8.47 cm | Photo prints, magazines, brochures |
| 600 | 236.22 | 0.042 mm | 4.23 cm | Line art, scanned documents |
Tips for print-ready images
- Print at 300 DPI for anything viewed up close, such as photos, flyers and business cards. A 4 × 6 in photo needs 1,200 × 1,800 px; an A4 page needs 2,480 × 3,508 px.
- Changing the DPI tag alone does not add detail. A 600 px image tagged at 300 DPI prints 5.08 cm wide; at 72 DPI it prints 21.17 cm wide but looks soft. To print larger and sharp you need more pixels.
- Large prints can use lower DPI. Posters and banners are seen from farther away, so 150 DPI (or even less for billboards) is common.
- Add bleed for full-page designs. Printers usually ask for an extra 3 mm on each edge, which is about 35 px at 300 DPI.
Frequently asked questions
How do you convert pixels to centimeters?
Divide the pixels by the DPI to get inches, then multiply by 2.54. For example, 600 px at 300 DPI = 2 in = 5.08 cm.
How many pixels are in a centimeter?
It depends on the resolution: 37.8 px per cm at 96 DPI, 28.35 at 72 DPI and 118.11 at 300 DPI. The formula is DPI ÷ 2.54.
What is 1080 pixels in cm?
At 96 DPI (screen), 1080 px is 28.58 cm. At 300 DPI (print), it is 9.14 cm.
How many pixels do I need for an A4 print?
An A4 page (21 × 29.7 cm) needs 2,480 × 3,508 px at 300 DPI, or 1,240 × 1,754 px at 150 DPI.
Which DPI should I use?
Use 96 DPI for web and CSS layouts, since a CSS pixel is 1/96 inch. Use 300 DPI for photos and documents printed and viewed up close, and around 150 DPI for posters.
Why does my image show a different size on screen?
Screens ignore the DPI stored in the file and display one image pixel per screen pixel (adjusted by your display scaling), so physical size on screen depends on the monitor's pixel density, not the file's DPI tag.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.