Cm to Px: Convert Centimetres to Pixels Correctly (Free Tool)

CodexFuse Team · 2026-10-27T09:53:58.597Z · 9 min read min read

Cm to px depends on DPI: learn the formula, the right DPI for web and print, and a worked designer example using the free converter.

Cm to px is the conversion of a length in centimetres into pixels, using the formula pixels = centimetres divided by 2.54, multiplied by the DPI (dots per inch) of the output. Unlike a fixed unit conversion, cm to px has no single answer until you know the DPI, because the same 10 cm becomes 283 pixels at 72 DPI and 1,181 pixels at 300 DPI. The free cm to px converter applies that formula for you, so you enter the centimetres, choose the DPI, and read the pixel result.

What does cm to px actually mean?

Cm to px means translating a physical length into a number of screen or print dots, and the translation depends entirely on how many dots are packed into each inch. At 96 DPI, the standard for most screens, 1 cm equals about 38 pixels; at 300 DPI, the standard for quality print, the same centimetre equals about 118 pixels. Without stating the DPI, a pixel figure is incomplete.

The formula is worth memorising, even if you normally use a converter:

Pixels = (centimetres ÷ 2.54) × DPI

For example, 10 cm at 96 DPI gives (10 ÷ 2.54) × 96 = 378 pixels. The same 10 cm at 300 DPI gives 1,181 pixels. Neither answer is wrong — they answer different questions, for screen and for print.

Why does DPI change the answer so much?

DPI changes the answer so much because it multiplies the whole result: doubling the DPI doubles the pixel count, and moving from screen resolution (96 DPI) to print resolution (300 DPI) more than triples it. That is why a web graphic that looks perfect on screen can print as a small, soft rectangle, and why a print file can be needlessly huge when uploaded to a website.

Worked example: a freelance designer sizing a hero image

The scenario (fictional): A freelance designer, Ayesha, is building a landing page for a small bakery. The client hands her a printed menu and says the hero photograph should span 30 cm wide on the page layout she is mocking up, and the final website banner must be sharp on a standard screen.

Step 1 — Set the DPI first. Because the banner is for a website, not print, Ayesha chooses 96 DPI, the common screen standard. Choosing 300 DPI here would have produced a file more than three times wider than the site needs.

Step 2 — Convert with the tool. She opens the cm to px converter, enters 30 in the centimetres field, selects 96 DPI, and reads the result: 1,134 pixels wide. The tool also shows the equivalents in millimetres, inches, and points, which she checks against the layout brief.

Step 3 — Check the height the same way. The layout calls for a 12 cm tall banner. The same conversion gives 453 pixels (12 ÷ 2.54 × 96 = 453.5, rounded to 453). Her export target is therefore 1,134 × 453 pixels.

Step 4 — Export once, correctly. She exports the photograph at exactly 1,134 × 453 pixels instead of exporting a large print file and letting the browser shrink it. The page loads faster, the image stays sharp, and there is no surprise cropping on mobile.

The result: one conversion, one export, no rework. If the same banner were later needed for a printed flyer, Ayesha would repeat the conversion at 300 DPI and get 3,543 × 1,417 pixels — a different file for a different job, not a stretched version of the web file.

Which DPI should you use: 72, 96, 150, or 300?

Pick the DPI by asking where the image will actually be seen. The wrong choice here is the single most common cause of blurry prints and bloated web pages.

• 72 DPI — older screen standard: still quoted in many design tools, but most modern screens and browsers assume 96 DPI; use 72 only when a specific platform asks for it.
• 96 DPI — websites and screens: the default choice for web graphics, social images, and anything viewed on a monitor or phone.
• 150 DPI — good-quality everyday print: suitable for internal documents, drafts, and large posters viewed from a distance, where file size matters more than fine detail.
• 300 DPI — quality print: the standard for brochures, product packaging, magazines, and anything a customer will hold close and inspect.

What cm to px cannot do for you?

A converter answers one question — how many pixels equal this many centimetres at this DPI — and it is honest to name what it leaves out. Knowing the limits stops a correct conversion from becoming a wrong design decision.

• It does not resize your image: the tool converts a measurement; it does not crop, compress, or resample a photo. For that, use an image resizer, or a bulk image resizer when you have a whole set to process.
• It does not know your platform's rules: a social platform, printer, or website theme may cap file size, aspect ratio, or dimensions. Check those requirements first, then convert to meet them.
• It does not fix a low-resolution original: converting a small image's centimetre size at a higher DPI only restates the same pixels; detail must come from the source file.
• It does not set print bleed or margins: printers typically need extra bleed beyond the trim size, so add that to your centimetre measurement before converting.

Related conversions help when the brief arrives in another unit. If a client gives you inches instead of centimetres, the cm to inches converter guide covers that direction, and a clothing size converter is the right tool when the measurement is a garment rather than a graphic.

From a converted size to a live website, without the server work

For many readers, the conversion is only the first step: the sized image still has to live on a website that loads quickly, stays online, and does not demand weekly maintenance. That is where a managed platform changes the shape of the job.

On CodexFuse, the workflow is concrete. First, create an account and add credits — you pay as you go, with no subscription tying you to a plan you may not need next month. Next, set up managed hosting for the site and point the domain to it; the platform handles the server side, including updates and monitoring, rather than leaving you to babysit it. Then upload the correctly sized images, business email, and backups under the same account, instead of juggling a separate provider for each piece.

The decision rule is simple: if you want to spend your time on the design and the business, and not on server updates, security patches, and backup checks, a fully managed setup fits. If you genuinely enjoy tuning servers yourself and want root-level control over every setting, a self-managed server may suit you better — and that trade-off is worth stating plainly rather than pretending one option fits everyone.

Frequently Asked Questions

How many pixels is 1 cm?

At 96 DPI, 1 cm is about 38 pixels; at 300 DPI, it is about 118 pixels. There is no single answer without the DPI, so always state the DPI alongside the pixel figure.

Is cm to px the same at every DPI?

No. The centimetre value stays the same, but the pixel result scales directly with DPI. Doubling the DPI doubles the pixel count, which is why screen and print conversions differ so sharply.

What DPI should I use for a website?

Use 96 DPI for most web graphics. It matches how browsers and screens typically interpret pixel dimensions, and it keeps file sizes reasonable for fast loading.

What DPI should I use for printing?

Use 300 DPI for quality print work such as brochures and packaging. For large posters viewed from a distance, 150 DPI is often acceptable and produces smaller files.

Can I convert cm to px without a tool?

Yes, with the formula pixels = (cm ÷ 2.54) × DPI. For 10 cm at 96 DPI, that is 378 pixels. A converter is faster and removes arithmetic slips, especially across many sizes.

Does changing DPI in a converter change my photo?

No. The converter only calculates a measurement. To actually change an image's pixel dimensions, you must export or resize the file itself at the new size.

Get your sizes right, then put them to work

Start with the DPI, convert with the free cm to px tool, export at the exact pixel size, and check the result on a real phone and a real screen. That short routine removes the most common sizing mistakes in design and publishing.

And if the website those images live on is still eating your time with hosting, email, and backup chores, move it to CodexFuse today: set up fully managed hosting on pay-as-you-go credits, upload your correctly sized work, and let the platform handle the server side while you get back to the work itself.