🦉 UnitOwl

Points to Pixels

1 Point (pt) = 1.33333Pixel (px)

By KAMP Inc. / UnitOwl · Last reviewed:

Result
1.33333 px
1 pt = 1.33333 px
Ad Slot (horizontal)

How to Convert Points to Pixels?

One point equals approximately 1.333 pixels at the standard 96 DPI screen resolution. To convert points to pixels, multiply the point value by 1.333 (or equivalently, multiply by 96/72). This conversion is essential when translating print design specifications to screen. If a brand style guide specifies headings at 24pt, the web developer needs to set them at 32px (24 x 1.333) to achieve the same logical size. Word processor documents, PDF specifications, and email templates often use points, while CSS and web frameworks use pixels. Understanding this conversion ensures that screen layouts match print designs accurately and that cross-platform typography remains visually consistent. It also helps during design handoff, where specs may come from PDFs, pitch decks, or desktop publishing files that were never intended for CSS. The exact decimal result is often more useful than a rough whole-number estimate because modern browsers can handle fractional values, and even when designers round, they usually want to know how far the rounded web size drifts from the original print specification. That makes pt-to-px conversion a routine QA step when a web build has to mirror a signed-off PDF.

How to Convert Point to Pixel

  1. Start with your size in points (pt).
  2. Multiply the point value by 1.333 (or 96/72) to get pixels (px).
  3. The result is your size in pixels.
  4. For common sizes: 12pt = 16px, 14pt = 18.67px, 18pt = 24px, 24pt = 32px.
  5. For reverse conversion, multiply pixels by 0.75 to get points.

Real-World Examples

A brand guide specifies body text at 10pt. What CSS pixel size should you use?
10 x 1.333 = 13.33px. Round to 13px, or consider using 14px for better screen readability.
A Word document heading is 18pt. What is the equivalent in CSS?
18 x 1.333 = 24px. A common heading size for H2 or H3 elements.
A PDF form specifies 9pt for fine print.
9 x 1.333 = 12px. This is the minimum readable size on most screens without zooming.
A client wants their email headlines at 36pt to match their print letterhead.
36 x 1.333 = 48px. A bold headline size that works well for email headers.
A PDF style guide calls for 27pt section titles. What is the closest CSS pixel size?
27 x 1.333 = 36px. Using 36px keeps the web title aligned with the print spec while landing on a clean whole-number CSS value.

Quick Reference

Point (pt)Pixel (px)
11.33333
22.66667
34
56.66667
1013.3333
1520
2026.6667
2533.3333
5066.6667
75100
100133.333
250333.333
500666.667
1,0001333.33

History of Point and Pixel

The typographic point has its origins in the 18th century French type-founding system. Pierre Simon Fournier proposed a point system in 1737, which was later refined by François-Ambroise Didot. The modern "PostScript point" (exactly 1/72 of an inch) was standardized by Adobe for desktop publishing in 1984. When the web emerged in the 1990s, CSS needed a screen-native unit and chose the pixel at 1/96 inch. The 96/72 conversion factor between these units is now an immutable part of web standards and will not change, even as physical display technology evolves.

Common Mistakes to Avoid

  • Rounding point values to the nearest pixel prematurely. CSS supports fractional pixels (e.g., font-size: 13.33px), though browsers round to whole pixels for rendering. For layout calculations, keep the decimal precision until the final value.
  • Assuming point sizes in Word will look identical in CSS. Word uses points at the operating system DPI, while CSS pixels are resolution-independent reference units. Text may appear slightly different due to font rendering and antialiasing differences between platforms.
  • Using the wrong conversion direction. Points to pixels multiplies by 1.333 (numbers get larger). Pixels to points multiplies by 0.75 (numbers get smaller). If your pixel value is smaller than the point value, you went the wrong way.
  • Rounding every converted value to a convenient design token without checking the result. Jumping from 18.67px to 20px may simplify a scale, but it also changes the typographic hierarchy more than many teams realize.
Ad Slot (auto)

Frequently Asked Questions

Why is the common body text exactly 12pt / 16px?
The 12pt body text convention dates back to metal type and was carried forward into desktop publishing. When the web standardized on 16px as the default browser font size, it was chosen to be exactly 12pt (16 x 0.75 = 12). This was a deliberate alignment between print and screen standards.
Can I use pt in CSS instead of converting to px?
Technically yes, but it is not recommended for screen design. Browsers convert pt to px internally using the 96/72 ratio. Using px (or em/rem for accessibility) is the standard practice for web. Reserve pt for @media print stylesheets.
How does this conversion work on mobile devices with high DPI?
CSS pixels on mobile are "device-independent pixels" (DIPs). A 16px font on a 3x Retina display is rendered using 48 physical pixels, but the CSS math remains the same: 16px = 12pt. The conversion is between logical units, not physical screen dots.
Should I round point conversions to whole pixels in CSS?
Usually yes for simpler handoff, but not always. Browsers accept decimal values like 18.67px, and keeping the decimal can preserve the original typographic ratio more accurately. In design systems, teams often round to the nearest whole or half pixel for consistency, then verify the result visually.
What is 9pt in pixels?
Multiply by 1.333 (or 96/72). A 9pt value converts to 12px. That is a common minimum readable size for captions and fine print on screen.
Quick Tip

For web developers receiving designs in points: create a quick reference table for your project. The most common conversions are 9pt=12px, 10pt=13.3px, 11pt=14.7px, 12pt=16px, 14pt=18.7px, 16pt=21.3px, 18pt=24px, 24pt=32px, 36pt=48px. Pin this to your project documentation to avoid recalculating during implementation.

Sources & References