Skip to main content

Em to Pixels (em to px)

Last updated:

Em-to-pixels conversions translate CSS-relative em-unit specifications into absolute pixel values for design-mockup verification, design-system documentation, and cross-tool design-handoff work. A 1 em font-size translates to 16 px under the 16-px-default browser convention; a 1.5 em heading translates to 24 px; a 0.875 em small-text translates to 14 px; a 2 em display-heading translates to 32 px. The factor is the multiplicative ratio between the em (computed-current-font-size) and the pixel under the standard 16-px-default browser font-size, with 1 em = 16 px when the current element's computed font-size equals the browser default. The conversion assumes the standard 16-px-default browser font-size on the html-and-body root and no nested font-size overrides — designers should document this assumption explicitly when sharing conversion results.

How to convert Em to Pixels

Formula

px = em × 16

To convert em to pixels, multiply the em figure by 16 — the standard browser-default font-size in pixels under the 16-px-default convention. For mental math, "em × 16" is straightforward integer arithmetic for common em values: 1 em = 16 px, 1.5 em = 24 px, 2 em = 32 px, 0.5 em = 8 px, 0.75 em = 12 px, 0.875 em = 14 px, 1.125 em = 18 px, 1.25 em = 20 px. The conversion runs at every CSS-em-source to design-mockup-pixel-destination handoff boundary in modern design-system work, with the factor exact under the standard convention. The conversion assumes no nested font-size overrides between the html root and the element being measured — em cascades, so deeply-nested elements with multiple font-size overrides may have different effective em-to-px ratios.

Worked examples

Example 11 em

One em equals 16 CSS pixels under the standard 16-px-default browser font-size on the html-and-body root elements. The relationship holds when the current element's computed font-size equals the browser default — em is element-relative, so nested font-size overrides shift the conversion.

Example 21.5 em

One point five em — a typical web-page heading font-size — converts to 24 CSS pixels on the design-mockup verification value. The em-figure is the CSS-cascading-relative source; the px-figure is the absolute design-mockup reference under the standard 16-px-default browser convention.

Example 30.875 em

Zero point eight seven five em — a typical small-text or caption font-size — converts to 14 CSS pixels on the design-mockup verification value. The fractional em-value preserves accessibility-zoom adaptation while specifying a precise design-pixel target.

em to px conversion table

empx
1 em16 px
2 em32 px
3 em48 px
4 em64 px
5 em80 px
6 em96 px
7 em112 px
8 em128 px
9 em144 px
10 em160 px
15 em240 px
20 em320 px
25 em400 px
30 em480 px
40 em640 px
50 em800 px
75 em1200 px
100 em1600 px
150 em2400 px
200 em3200 px
250 em4000 px
500 em8000 px
750 em12000 px
1000 em16000 px
2500 em40000 px
5000 em80000 px

Common em to px conversions

  • 0.5 em=8 px
  • 0.75 em=12 px
  • 0.875 em=14 px
  • 1 em=16 px
  • 1.125 em=18 px
  • 1.25 em=20 px
  • 1.5 em=24 px
  • 2 em=32 px
  • 2.5 em=40 px
  • 3 em=48 px

What is a Em?

In modern CSS the em (em) is a relative-typography unit equal to the computed font-size of the current element. Under the standard 16-px-default browser font-size on the html-and-body root elements, 1 em = 16 px in the document body context. But the unit is element-relative: a child element with font-size: 14px has 1 em equal to 14 px in that element's context, with em-units in nested padding-margin-line-height specifications scaling relative to that 14 px. The cascading-relative behaviour distinguishes em from rem (root em, fixed to the root html font-size). Under typical 16-px-default browser conventions, 1 em ≈ 16 px and 1 px = 0.0625 em, but the relationship varies with the locally-computed font-size. The 16-px-default convention is the universal modern web reference: every major browser (Chrome, Firefox, Safari, Edge) defaults to 16 px html font-size unless overridden by user accessibility-and-zoom settings or page-specific CSS reset. The em-and-rem distinction is critical in modern CSS: em cascades, rem is absolute (relative-to-root).

The em as a typographic unit traces to traditional metal-type printing, where one em was the width of the metal block holding the capital letter "M" in the typeface — typically equal to the type's nominal point-size (so a 12-point font had a 12-point em width). The unit became the natural relative-typography reference, with em-dashes (typographic dashes the width of an em), em-spaces (spaces the width of an em), and em-quads all defined relative to the type-size. CSS adopted the em as a relative-typography unit in CSS1 (1996), defining 1 em as the computed font-size of the current element. Under the standard 16-px-default browser font-size, 1 em equals 16 px in the document body context, but the relationship is element-relative: a child element with font-size: 14px has 1 em equal to 14 px in that element's context. The relative-em-unit cascades through the CSS document tree, scaling padding-and-margins-and-line-heights proportionally to the local font-size. CSS3 formalised the rem (root em) unit, defined as the font-size of the root html element, providing a non-cascading absolute-relative unit for application-wide scaling. The em-and-rem pairing is the universal modern responsive-typography pattern in CSS, with em for component-internal scaling and rem for application-wide scaling.

Modern responsive-and-fluid web-typography globally — CSS components and design-systems use em for component-internal scaling that should adapt to the local font-size context. Padding, margin, line-height, border-radius, and component-dimension specifications scale proportionally to the local font-size when expressed in em, supporting accessibility-and-zoom adaptation and component-template-reusability across different parent-context font-sizes. Typography-component design (heading-paragraph-link-button-card) uses em for internal proportions: a button with 0.5em vertical-padding scales the padding proportionally to the button's font-size, supporting both small-action-button and large-CTA-button use cases from the same component code. CSS frameworks (Tailwind, Bootstrap, Material-UI) use em selectively for relative-spacing alongside px-or-rem for absolute-spacing. Email-template typography occasionally uses em for cross-client font-size scaling, though px-and-pt remain more universally compatible. Modern design-systems (Tailwind, Material Design, Carbon Design System) document em-versus-rem decision-trees for responsive-typography work, with em recommended for component-internal scaling and rem recommended for application-wide scaling. The em unit is not used in print-typography (where points are the canonical unit) — it is web-and-screen-typography specific.

What is a Pixel?

In modern web typography under CSS specifications, the pixel (px) is the CSS reference pixel — a logical unit nominally equal to 1/96 inch (about 0.2646 mm) at the CSS reference viewing distance. The unit scales by device-pixel-ratio for high-DPI displays: a "Retina" display with 2x device-pixel-ratio renders one CSS pixel as a 2×2 grid of physical hardware pixels, preserving the visual size while doubling the rendering resolution. The CSS pixel relationship to other typography units is fixed under the 96-dpi convention: 1 inch = 96 px, 1 cm = 37.795 px, 1 mm = 3.7795 px, 1 pt = 4/3 px ≈ 1.3333 px, 1 pc = 16 px (with the pica equal to 12 points). The 96-dpi convention is the universal reference across modern web browsers (Chrome, Firefox, Safari, Edge), CSS specifications, and screen-typography work. Print-typography traditionally uses points (1 pt = 1/72 inch), and the 96-dpi-versus-72-dpi distinction explains the 4/3 factor between web pixels and print points. Modern operating systems may override the 96-dpi default through display-scaling settings, but CSS reference pixel calculations remain anchored to the 96-dpi reference.

The pixel (a portmanteau of "picture element") emerged in 1960s digital-image-processing research at JPL, Bell Labs, and similar laboratories as the discrete addressable unit of a raster-scanned digital image. The term was coined by JPL researcher Frederic C. Billingsley in 1965 in connection with the Mariner mission imaging-systems work. As digital displays evolved through the 1970s and 1980s — from monochrome CRT terminals through colour CRTs and into early LCD displays — the pixel became the fundamental unit of screen-based typography and graphics. The CSS Working Group standardised the CSS reference pixel in 1996 as part of CSS1, with the original definition tied to a 96-dpi reference viewing-distance of an arm's length from a desktop monitor. The 2010 CSS3 spec formalised the reference-pixel abstraction: 1 CSS pixel ≈ 1/96 inch at the reference viewing distance, scaled by device-pixel-ratio for high-DPI ("Retina") displays. Modern web typography overwhelmingly uses pixels (px) as the base unit for font-sizes, line-heights, padding, margins, and component dimensions, with em-and-rem relative units providing scale-relative-to-parent and scale-relative-to-root respectively. The 96-dpi reference convention also drives the conversion between pixels and traditional print-typography points (1 pt = 4/3 px at 96 dpi).

Web typography globally — CSS font-size, line-height, padding, margin, border-radius, border-width, and component-dimension specifications all use pixels as the base unit on every modern web browser. CSS frameworks (Tailwind CSS, Bootstrap, Material-UI, Ant Design) all use px as the primary spacing-and-typography unit, with em-and-rem relative units providing scale-relative-to-parent and scale-relative-to-root flexibility. Mobile-app typography on iOS uses points (which on iOS are implementation-detail-equivalent to CSS pixels at the reference scale, scaled by device-pixel-ratio), Android uses density-independent-pixels (dp/dip) which are similarly reference-scaled. Digital-image-processing and computer-graphics: image dimensions, sprite-sheet layouts, texture-coordinate-mapping all use pixels. Screen-typography: every modern operating-system font-rendering pipeline computes glyph dimensions in pixel-equivalent units. Game-development and game-engine frameworks (Unity, Unreal, Godot) use pixels as the canonical 2D-coordinate unit. Email-template typography uses pixels heavily for cross-client compatibility (Outlook, Gmail, Apple Mail all render pixel-based dimensions consistently). Print-design software (Adobe InDesign, Affinity Publisher) supports both pixel-and-point input with automatic 96-versus-72-dpi conversion at the print-output boundary.

Real-world uses for Em to Pixels

CSS em-unit design specifications translated to pixel design-mockup values for design-handoff

CSS em-unit specifications in design-system documentation routinely translate to pixel values for design-mockup verification, design-handoff to development teams, and cross-tool design-asset production in Figma, Sketch, Adobe XD, and similar design tools that work primarily in pixel-based dimensions. A 1 em CSS body-text translates to 16 px Figma frame; a 1.5 em CSS heading translates to 24 px design-mockup; a 0.875 em CSS small-text translates to 14 px caption. The conversion runs at every CSS-em-source to design-tool-pixel-destination handoff step in modern design-system work.

Component-design em-based padding-and-margin specifications translated to pixel verification values

Component-design work uses em for component-internal proportional padding-and-margin specifications, with conversion to pixel values for design-mockup verification and cross-component-comparison. A 0.5 em vertical-padding translates to 8 px under the 16-px-default; a 1 em horizontal-padding translates to 16 px; a 1.5 em card-padding translates to 24 px. The conversion runs at every em-based component-design specification to pixel-mockup-verification step, with the em-figure on the CSS-cascading-relative source and the px-figure on the absolute design-mockup reference.

Design-system typography-scale em values translated to pixel design-tokens for tool-import

Design-system typography-scales expressed in em (h1: 2.5em, h2: 2em, h3: 1.5em, body: 1em, small: 0.875em, etc.) translate to pixel values for design-token import into Figma, Sketch, Adobe XD, and similar tools that consume pixel-based design-tokens. A 2.5 em h1 translates to 40 px; a 2 em h2 translates to 32 px; a 1.5 em h3 translates to 24 px; a 0.875 em small translates to 14 px. The conversion runs at every CSS-em-design-system-source to design-tool-pixel-token-import step.

Email-template em specifications translated to pixel-based email-client-rendering values

Email-template em-based typography specifications translate to pixel-based values for cross-email-client-rendering verification, especially in Outlook-bound mailings where the Word-rendering-engine handles em-based specifications inconsistently across legacy Outlook versions. A 1 em email-body translates to 16 px; a 1.5 em email-heading translates to 24 px; a 0.875 em email-disclaimer translates to 14 px; a 0.75 em fine-print translates to 12 px. The conversion runs at every CSS-em-email-source to pixel-rendering-verification step in enterprise-email-marketing work across Outlook-and-Gmail-and-Apple-Mail compatibility-testing pipelines.

When to use Pixels instead of Em

Use pixels whenever the destination is design-mockup verification, design-handoff to development teams, design-tool-import (Figma, Sketch, Adobe XD), email-client-rendering verification, or any context requiring absolute pixel-based values rather than CSS-relative units. The pixel is the universal absolute design-mockup unit. Stay in em when the destination is CSS specifications for component-internal proportional scaling, design-system documentation for relative-typography hierarchies, or any context where cascading-relative-to-current-font-size scaling is desired (responsive components that adapt to local font-size context). The conversion is the CSS-relative-to-absolute-pixel scale-shift between em-based CSS source and pixel-based design-tool destination work, applied at every design-handoff and design-token-export boundary in modern design-system practice across Tailwind-and-Material-and-Bootstrap-and-Carbon design-system pipelines.

Common mistakes converting em to px

  • Assuming "1 em = 16 px" universally without verifying the 16-px-default browser font-size assumption. The relationship holds only when the html root font-size is 16 px (the universal modern browser default), and the current element has no font-size override. User accessibility settings (browser-zoom, larger-text features) can shift the root font-size, with em-based designs adapting accordingly.
  • Forgetting that em cascades through nested font-size overrides. A "1 em" specification in a deeply-nested element with multiple parent font-size overrides multiplies the effective scaling at each level — what was meant as "16 px" might end up as 24 px or larger after several nested cascades. Use rem (root em) for application-wide consistent absolute scaling, em for component-internal proportional scaling.

Frequently asked questions

How many pixels in 1 em?

One em equals 16 CSS pixels under the standard 16-px-default browser font-size on the html-and-body root elements. The relationship is element-relative — the actual conversion depends on the computed font-size of the current element. Under typical browser-default conditions and with no nested font-size overrides, 1 em = 16 px universally across the document, but user accessibility settings or page-specific CSS reset can shift this.

How many pixels in 1.5 em (web heading)?

One point five em equals 24 CSS pixels under the standard 16-px-default browser convention. That is a typical web-page heading font-size translated to design-mockup pixel reference. The em-figure sits on the CSS-cascading-relative source and the px-figure sits on the absolute design-mockup reference for design-handoff and design-tool-import work.

How many pixels in 0.875 em (small-text)?

Zero point eight seven five em equals 14 CSS pixels under the standard 16-px-default browser convention. That is a typical small-text or caption font-size translated to design-mockup pixel reference. The fractional em-value preserves accessibility-zoom adaptation while specifying a precise design-pixel target for design-handoff work.

Quick way to convert em to pixels in my head?

Multiply the em figure by 16 — straightforward integer arithmetic for common values. For 1 em that gives 16 px, for 1.5 em that gives 24 px, for 2 em that gives 32 px, for 0.5 em that gives 8 px, for 0.875 em that gives 14 px. The relationship is exact under the standard 16-px-default browser convention, with no rounding error introduced at the conversion step.

What is the difference between em and rem?

Em is cascading-relative-to-current-font-size — 1 em equals the computed font-size of the current element, with nested font-size overrides multiplying scale at each level. Rem is absolute-relative-to-root-font-size — 1 rem always equals the root html font-size regardless of DOM nesting depth. For most design-system work use rem for application-wide consistent scaling and em for component-internal proportional scaling.

When does em-to-px conversion appear in real work?

It appears in CSS em-unit design specifications translated to pixel design-mockup values for design-handoff and in component-design em-based padding-and-margin specifications translated to pixel verification values. It also appears in design-system typography-scale em values translated to pixel design-tokens for tool-import and in email-template em specifications translated to pixel-based email-client-rendering values. The conversion is one of the most-run CSS-relative-to-absolute typography conversions in modern design-system work.

How precise should em-to-px be for design work?

For design work the em-to-px conversion is exact under the standard 16-px-default browser convention (1 em = 16 px), with the precision allowance coming from rounding to integer pixel values for crisp screen rendering. Most design-system documentation rounds to integer pixels (1 em → 16 px, 0.875 em → 14 px) rather than fractional values, with intermediate em-values like 1.0625 em (17 px) and 0.9375 em (15 px) used when integer-pixel granularity is needed.