Free PX to CM Converter

The SynthQuery Free PX to CM Converter is a browser-based utility for translating pixel counts into centimeters—and centimeters back into pixels—using a DPI or PPI assumption you control explicitly. Unlike a static table that pretends every screen matches one magic density, this tool acknowledges that pixels are samples on a digital grid while centimeters are physical lengths on a ruler, and the only honest bridge between them is “how many pixels span one inch” for the medium you care about: ninety-six pixels per inch for the classic CSS reference, three hundred pixels per inch for many commercial print workflows, or a custom value that matches your Figma export preset, Photoshop resolution field, or large-format RIP. Alongside centimeters you get millimeters for EU mechanical drawings, inches for US print vendors, and typographic points derived from seventy-two points per inch so font discussions stay aligned with layout dimensions. Batch mode converts whole lists with optional tab-separated export, the reference table adds a pt column for quick scanning, and a paper-size panel estimates full-page raster dimensions for ISO A4, A3, US Letter, and common business-card formats at your current DPI. Everything runs locally in your tab without uploading measurements to SynthQuery servers for the arithmetic, which makes the page suitable for confidential product dimensions on locked-down laptops. The converter belongs to our Free tools series—discoverable from /free-tools alongside the HTML Online Viewer, Word Counter, Dictionary, Grammar Checker, WebP Converter, and related utilities—while the complete product map for AI detection, SynthRead readability, plagiarism scanning, humanization, and more lives at https://synthquery.com/tools, also linked from the site footer under “All tools.”

The mathematics rest on the international inch definition: one inch equals exactly 2.54 centimeters. Given a pixel count and a chosen DPI (pixels per inch), physical inches equal pixels divided by DPI, and centimeters equal inches multiplied by 2.54. Equivalently, cm = (px ÷ DPI) × 2.54, and the inverse px = (cm ÷ 2.54) × DPI. Millimeters are centimeters times ten. Typographic points use the classic 72 pt per inch relationship, so pt = (px ÷ DPI) × 72 for the length of a line segment measured along the pixel grid at your stated density. The interface shows these formulas beside the live numbers so auditors, students, and skeptical engineers can verify that nothing is hidden inside a black box. SynthQuery ships named presets for seventy-two (legacy PostScript and Mac typography history), ninety-six (W3C CSS reference pixel density for mapping absolute units), one hundred twenty, one hundred forty-four, one hundred fifty, and three hundred (common photo and print starting points). A custom DPI field accepts other values within a clamped range to prevent divide-by-zero mistakes from typos. Decimal precision for centimeter readouts is selectable because packaging tolerances sometimes require four or more significant figures while executive summaries read cleaner with two. The conversion table lists dozens of practical pixel stops—from single-digit icon sizes through eight, sixteen, twenty-four, thirty-two, breakpoints such as three hundred seventy-five and seven hundred sixty-eight, up to high-definition and ultra-HD widths—each row now includes centimeters, millimeters, inches, and points so you can copy a full TSV into Google Sheets or Excel without re-deriving columns. Batch conversion provides two columns: paste pixel values to see centimeters (plus millimeters and points inline in the preview list), or paste centimeter values to see pixels. Each side offers its own “Copy batch TSV” action with headers so procurement spreadsheets and Jira tickets inherit structured data instead of screenshots. The paper-size card answers questions like “How many pixels wide is A4 at three hundred DPI?” by recomputing width and height whenever you change DPI, and a print control sends the section to the system print dialog for markup meetings. Local storage remembers your last DPI and decimal preference between visits on the same browser profile. Swap values reconciles odd intermediate states when you flip mental models; reset sample restores a compact teaching example. None of these capabilities require signing in: they exist to shorten the path between design tokens, vendor emails, and production CSS. We emphasize the difference between CSS logical pixels and hardware device pixels. A CSS pixel on a high-DPI phone is not the same as one physical OLED subpixel; devicePixelRatio scales sharpness without rewriting the ninety-six-px reference inch inside stylesheets. When your question is “how many centimeters wide is my 375 CSS-pixel artboard,” ninety-six DPI is usually the right educational preset. When your question is “how wide will this 3600-pixel TIFF print at 300 DPI,” three hundred is the right preset. Mixing those contexts silently is how teams ship banners at the wrong physical scale—this page forces the assumption into the open.

Product designers translate spacing tokens from eight-point grids into centimeter callouts on packaging die-lines where factories still measure with calipers. Marketing operations teams resize hero photography for out-of-home boards: knowing pixel counts at the printer’s native resolution prevents upscaling softening before files leave the studio. Front-end engineers reconcile Figma export settings with CSS max-width rules, then explain to executives how many centimeters a twelve-eighty layout spans on a ninety-six-DPI conference projector versus a Retina laptop—without rebuilding a spreadsheet every sprint. Educators teaching responsive design demonstrate that identical pixel widths occupy different physical space on projectors, tablets, and phones, reinforcing why responsive units and accessibility zoom matter beyond memorizing breakpoints. Graphic arts students batch-convert homework tables from pixels to centimeters before plotting guides in Illustrator or InDesign with correct document units. Photographers verify that a three-thousand-pixel file at three hundred DPI yields a predictable centimeter height on the long edge before paying lab fees for a gallery wrap. Localization engineers juggling US Letter and A4 templates convert margin specifications between imperial and metric teams using inches and millimeters side by side. Researchers preparing journal figures double-check minimum line-weight rules stated in centimeters even when plots were authored in pixel-based tools. Accessibility specialists relate typographic sizes to physical legibility discussions, remembering that readability formulas in SynthRead measure linguistic complexity—not ruler length—so pairing language tools with dimensional estimates covers both semantics and presentation. Agencies bookmark SynthQuery utilities instead of ad-heavy single-purpose sites that round silently or log inputs to unknown third parties.

Decide which DPI meaning applies before typing numbers. For CSS discussions that assume the ninety-six-pixels-per-inch reference, keep ninety-six selected unless your design system documents otherwise. For raster assets bound for commercial print, match the embedded resolution in your PSD, TIFF, or PDF placement—three hundred is a frequent default, but large-format inkjet may use lower effective DPI at viewing distance. Enter pixels in the left field or centimeters in the right; the counterpart updates as you type. Adjust decimal precision when stakeholders need cleaner rounding. Read millimeters, inches, and points in the summary block when briefs mix units. Use Swap values if you switched mental models mid-edit and want both fields normalized from your latest coherent entry. Use Reset sample to return to a small teaching example when demoing in class. Open batch mode when you have a column of values from Excel: paste pixel lines on the left or centimeter lines on the right, skim the preview list, then click Copy batch TSV to move structured data into tickets or sheets. Scroll the conversion table to compare familiar breakpoints at your DPI, and use Copy as TSV to grab the entire matrix including the pt column. Check the paper-size section before exporting full-page backgrounds so A4 and US Letter pixel dimensions match the printer’s expectations, and use Print if you want a paper handout for a review. When surrounding copy still needs polish, follow internal links to Grammar or SynthRead; when assets are finalized but prose might be AI-assisted, run the AI Detector per policy. Bookmark /free-tools for the utilities grid and https://synthquery.com/tools for the full catalog.

This calculator cannot see your operating system zoom, browser zoom, or actual LCD pitch, so it does not guarantee how large an element looks on a stranger’s desk. CSS absolute units and hardware pixels diverge on mobile; validate touch targets with real devices and WCAG guidance, not ruler math alone. For color-critical print, trust ICC profiles and vendor proofs over generic scaling. Round only at pipeline boundaries when regulations require it; intermediate rounding stacks error. If two teams disagree, align on the named export preset in your design system rather than debating abstract “true DPI.”