MM to PX Converter

The SynthQuery MM to PX Converter is a precision-focused, browser-side utility for turning millimetres into CSS pixels—and pixels back into millimetres—using the DPI (dots or pixels per inch) you actually care about. Print designers think in millimetres on paper; front-end developers think in CSS pixels on screens; export dialogs in Figma, Illustrator, InDesign, and Affinity often ask for both. This page unifies those worlds with an explicit formula, adjustable decimal display, presets for the CSS reference pixel density (96 px per inch), common print resolutions (72, 150, 300 DPI), and higher UI-scale densities (120, 144) you may see on Windows or HiDPI laptops. Nothing is uploaded: conversions run locally, settings persist in your browser, and you can copy a single-line summary or export a tab-separated batch table straight into Google Sheets or Excel. It sits in the Free tools series next to our PX to CM, PX to Inches, WebP, and HTML viewer utilities, with a clear path to the full SynthQuery catalogue at /tools when you need AI-assisted writing, detection, readability, or plagiarism workflows.

At the heart of every conversion is one constant: one international inch equals exactly 25.4 millimetres. Pixels enter the story only after you declare how many of them fit into that inch—your chosen DPI or PPI. The tool therefore implements the pair px = mm × (dpi ÷ 25.4) and mm = px × (25.4 ÷ dpi). When you pick 96 DPI, you align with the CSS Values and Units specification, which defines the reference pixel such that 1 in = 96 px for length conversion purposes in stylesheets. That is why 1 mm at 96 DPI is approximately 3.7795275591 px, not a round number: the millimetre is a rational fraction of an inch, while the CSS pixel is a convenient binary-friendly subdivision of the inch at the reference density. The interface is deliberately bidirectional. You may type millimetres when a European packaging brief lists flange widths in mm, or type pixels when a developer handoff specifies a 16 px border radius and you must report the physical size on a 300 DPI print proof. A swap control exchanges the numeric fields when you realize you started in the wrong box. Decimal-place control only affects formatting and copy output; internal arithmetic stays in double precision until the last rounding step, which matters when you chain conversions across spreadsheets. Preset buttons jump to everyday values: single millimetres for hairline checks, 25.4 mm for one inch, and ISO A4 sheet dimensions (210 × 297 mm) for layout sanity. The batch table lets you paste a column of measurements from a specification and receive the pixel column for the active DPI, then copy everything as TSV. A reference line translates the same millimetre length to CSS reference pixels (96 DPI) even when you are previewing another density—handy when you must explain to engineering how “10 mm in print” relates to “10 mm interpreted as CSS px,” which are different numbers. We also show typographic points derived from the selected DPI using the classic 72 points per inch relationship (pt = px × 72 ÷ dpi) so conversations with print vendors stay consistent. This does not replace a full prepress pipeline; it gives you a defensible on-page calculator journalists, students, and indie developers can trust without installing desktop software.

Product designers exporting icons from vector tools often receive millimetre dimensions for die-cut stickers or retail danglers but must implement shadows and padding in CSS pixels for the marketing site. They lock the export DPI to match production, convert critical mm tolerances to px, and drop the numbers into design tokens. Print-on-demand sellers reconcile millimetre bleed lines from PDF templates with pixel-based mockups in Shopify themes by running batch conversions for every trim and safe-zone line their supplier emailed. Front-end engineers collaborating with European mechanical teams translate mounting-hole spacing from mm drawings into pixel offsets only when building simulator or configurator UIs that still use CSS for layout; the tool makes the DPI assumption explicit so nobody silently mixes 96 px per inch with a 300 DPI print preview. Technical writers preparing figures for PDF manuals set 300 DPI to estimate how many pixels wide a screenshot must be to print at a requested physical width without upscaling blur. Educators teaching responsive design use the CSS 96 DPI preset alongside our HTML Online Viewer to show that logical pixels are not device hardware pixels; students can compare the same mm length at 96 versus 144 DPI to see how interpretation changes even when the phone’s hardware density is higher. Marketing analysts rebuilding ad creatives from European briefs convert column widths listed in mm into pixel grids for Meta or Google display specs when those platforms still think in px. Accessibility and UX researchers sometimes annotate prototypes with physical minimum touch targets (often discussed near 9 mm) and need to communicate equivalent CSS pixels to developers who work in rem and px. The converter bridges that gap with a documented DPI rather than a vague “multiply by 3.78.” When you finish sizing, you can open the Word Counter for adjacent copy, run SynthRead for readability, or jump to the AI Detector if generative drafts need policy review.

First, identify which DPI matches your task. For CSS layout and most “how many pixels is this mm on the web?” questions, keep 96 DPI selected—that is the spec reference, independent of whether the user’s monitor is Retina. For raster exports intended for a 300 DPI plate, switch to 300 so pixel counts reflect print pixels, not CSS pixels. If a vendor email only says “150 LPI” or “print resolution,” confirm the rasterization DPI they used before you lock numbers into a contract. Enter a millimetre value you can verify, such as 25.4 (one inch), and confirm the pixel readout matches your mental model at the chosen DPI. At 96 DPI you should see 96 px; at 300 DPI you should see 300 px. If those checks fail, re-read whether you accidentally typed in the pixel field first or left custom DPI blank. Use quick presets for A4 dimensions when checking spreadsheet templates or slide masters. For a list from a spec, switch to the batch table, paste one mm value per row, and copy TSV into Sheets—sorting and charting stay intact. Adjust decimal places to match your style guide: packaging may want three decimals; UI tokens may want integers or quarter pixels. When collaborating, paste the formula line from the tool into Slack or Jira so reviewers know which DPI produced the numbers. After mechanical sizing, open the Word Counter or Grammar Checker if accompanying copy ships in the same ticket. For full-funnel AI review, use the navigation link to /tools and pick detection, readability, or plagiarism as needed. Revisit the Free tools hub whenever SynthQuery adds utilities so your bookmark stays current.

This tool performs linear scaling only. It does not account for printer margins that clip artwork, non-square pixels on legacy video hardware, or physical dot gain on newsprint. Color management, ICC profiles, and soft-proofing live outside pure mm–px arithmetic. CSS lengths can also use rem, em, vw, and other units—do not assume every px in a stylesheet maps to a physical millimetre on screen without knowing viewport and root font size. HiDPI displays map multiple device pixels to one CSS pixel; choosing 144 DPI in the calculator models a logical scale factor, not a specific phone model. Always label which DPI you used when handing numbers to another team. If legal or medical dimensions are safety-critical, verify with calibrated measurement tools, not an online calculator alone. Rounding for display can hide tiny errors that accumulate across long spreadsheets—when in doubt, keep one extra decimal internally and round only at the presentation layer.