Scaleable interfaces with rem units

What are rem units?

According to W3 candidate reccomendation, one root elastic measurement (rem) unit is equal to the font-size of the <html> element.

Hello rem

Let's say you've defined the font-size of the <html> element as 16 pixels, and you want a 48 pixel tall <header>. Basic math tells us that's 3 rem.

html {
    font-size: 16px;
}
header {
    height: 3rem;
}

Try it

This blog is built using rem units; click the buttons below to adjust the font-size of the <html> element, and in turn, the entire site.

16px

Wait, how is that different from em?

Elastic measurement units cascade (em spec), whereas root elastic measurement units are always relative to the root element.

With ems, the following situation becomes confusing:

CSS:

.container {
    font-size: 16px;
}
.em1 {
    font-size: 1em;
    border-top: 1em solid red;
}
.em2 {
    font-size: 2em;
    border-top: 1em solid green;
}
.em3 {
    font-size: 1em;
    border-top: 1em solid blue;
}

HTML:

<div class="container">
    <div class="em1">
        Text 1
        <div class="em2">
            Text 2
            <div class="em3">
                Text 3
            </div>
        </div>
    </div>
</div>

Result:

Text 1
Text 2
Text 3

As ems cascade, the font-size of "Text 3" is effectively:

16px × 1 × 2 × 1 = 32px.

The same example, but with rems

If we use rem instead of em in the above example, since rems are always root-relative, the font-size of "Text 3" becomes:

16px × 1 = 16px.

CSS:

html {
    font-size: 16px;
}
.rem1 {
    font-size: 1rem;
    border-top: 1rem solid red;
}
.rem2 {
    font-size: 2rem;
    border-top: 1rem solid green;
}
.rem3 {
    font-size: 1rem;
    border-top: 1rem solid blue;
}

HTML:

<html>
    <div class="rem1">
        Text 1
        <div class="rem2">
            Text 2
            <div class="rem3">
                Text 3
            </div>
        </div>
    </div>
</html>

Result:

Text 1
Text 2
Text 3

Why should we do this again?

If you have a need to dynamically scale your interface, in part or in whole, with absolute precision, rems can be useful.

  1. A mobile interface that targets iPad Mini - You may want a slightly larger interface for the oddly sized iPad Mini display
  2. User preferences for the size of the site - You could provide a preference to increase the size of your site for a given user across all their devices
  3. You just want things a tad bigger - If your designers say "make everything 2 pixels bigger," you're gonna have a bad time, unlesss you're using rem units

Execution

Simply use rems in place of pixels in your CSS:

html {
    font-size: 16px;
}
.header {
    height: 2rem; /* 32px */
    padding: 0.5rem; /* 8px */
}

But fractions are hard, what if I want 9 pixels?

If you're using a CSS preprocessor, which you should be, it's easy to create a variable that represents a pixel:

Stylus:

// The size of 1rem in pixels
$baseSize = 16

// The size of a pixel in rems
$px = 1 / $baseSize + 0rem

Then, in your code, multiply the number of pixels you want by the variable:

Stylus:

html
    font-size: $baseSize

.header
    height: 48*$px
    border: $px solid black
    margin-bottom: -1*$px

Where you should still use px

You'll want to specify the font-size of the <html> element in pixels, but there are a few cases where you might want to use pixels elsewhere in your CSS.

Where you should still use em

If you want the flexibility of resizing a particular widget independently of the rest of the page, you should use a mix of em and rem:

button {
    font-size: 1rem;
    margin: 0.5em;
    border: 0.0625em;
    padding: 0.25em 0.75em;
}

Then, to make a large button:

button.large {
    font-size: 1.5rem;
}

The rest of the properties, specified in em units, will scale to be 50% larger.

Compatibility

Where rems don't work:

That said, all modern browsers support rem units. See the caniuse tables for details.

Fallbacks

You can specify units in pixels above if you'd like support for older browsers (minus the scalability):

width: 16px;
width: 1rem;

Show me the code

Take a look at the source of iOCSS and this blog for a few examples that combine rem units with media queries, ems, and CSS preprocessors.