Convert em units to pixels instantly at your chosen base font size (16px by default). EM-to-PX helps when a component uses em for scalability but you need the resolved pixel value for a mockup, canvas, or fixed-width export. The table converts common em values at a 16px base.
| EM | Pixels |
|---|---|
| 0.25em | 4px |
| 0.5em | 8px |
| 0.75em | 12px |
| 0.875em | 14px |
| 1em | 16px |
| 1.25em | 20px |
| 1.5em | 24px |
| 2em | 32px |
| 2.5em | 40px |
| 3em | 48px |
| 4em | 64px |
Multiply the em value by the parent element's computed font-size. So 1.5em × 16 = 24px (if the parent is 16px), 1.5em × 20 = 30px (if the parent is 20px). The 'parent' for the em unit is whatever element is one level up in the DOM with its font-size in effect — usually a section, card, or button context. This calculator multiplies em × base for you.
Chrome DevTools shows the computed pixel value of any em property, which is great — but during code review or designer handoff you often see the source em value and need to know what it produces. This tool gives you the answer without spinning up a browser. Particularly useful for design-system audits where you're comparing em-based component styles to pixel-based Figma specs.
Yes. If a parent uses font-size: 1.5em (computed to 24px against root 16px) and its child uses font-size: 0.8em, the child's font-size computes to 0.8 × 24 = 19.2px — not 0.8 × 16. This calculator gives you the single-step conversion; for deep nesting, run it once per level and multiply the results.
Not necessarily. Em has clear use cases (component-local proportional scaling, padding that should grow with font-size, em-based breakpoints) where rem can't do the same job. The right pattern in modern CSS is: rem for global typography and layout, em for component-internal scaling. Use this calculator to spot-check em values when you're auditing a component that mixes both.
EM to PX conversion applies px = em × parentFontSize. Like the PX→EM tool, the base defaults to 16px but is user-configurable. The shared CssUnitConverter component renders both directions from identical state logic — only the input emphasis (which field is primary) differs between the two tool exports.