The CSS Files – Variables
An introduction to CSS Custom Properties (a.k.a. Variables).
This post is part of a series on CSS:
One of the biggest issues with writing large amounts of CSS is keeping things consistent. For example, in a large codebase a single color can be used hundreds of times in hundreds of places. This repetition makes maintenance difficult as a simple design tweak like changing a color can result in that change needing to be made in many, many places.
CSS pre-processors like Sass and Less attempt to solve this particular problem (and others) by including variables. Variables let you set common values like colors and sizes in a single place then reference the variable when you need to use those values. Now a simple color change only needs to be made in one place.
Modern CSS, though, is very powerful and CSS now has native support for variables. You don’t need any build tools or pipelines; they are just part of the language. The code you write is the code that the browser uses. Formally, variables are “custom properties” but are commonly referred to simply as variables. Let’s explore how they can be used and how they can make writing CSS a much better experience.
One of the telling things about the name “custom properties” is that they are CSS properties. Since they are properties, they have to be declared within a CSS rule like any other property:
/* Nope! */
To differentiate variables from standard properties, they must start with
--. Any name can be used though, so long as you only use letters, numbers, and dashes. Remember that they are case-sensitive, so
--Foo are not the same variable.
Variables are also part of the normal cascade of CSS properties. This effectively means that you will want to declare your global variables on the highest element in the document tree, which is almost always
html. But if you have styles that apply to the
html element and want to keep your variable declarations separate, a common practice is to use the
The values of your variables can be many different things as basically any valid CSS value can be the value of a variable. Sizes and colors are just the beginning as entire border and background values can also be stored. You can also use the value from one variable to set another. The possibilities are endless.
In the code sample above, you probably noticed how we access the value of variables: the
var() function. The first parameter to that function should be the variable you need the value from. The second (optional) parameter is used as a fallback value. This is useful if you are not sure if a variable has been set and can be used for all sorts of fun tricks.
In that example, since we did not declare a
var() will return 16px since that is the fallback value. Note that only the first value is considered the variable to evaluate and, like the values of variables, the fallback value can contain commas. For example,
var(--foo, red, blue) defines a fallback of
red, blue and not two separate fallback values.
I mentioned earlier that variables are part of the normal cascade. This means that variables declared at the root scope are global and apply to everything on the page, but the cascade also enables two amazing features.
First, you can alter variables in smaller scopes. Think of having a global color that is used for all the buttons on a page. If you want to make all buttons within a specific kind of widget a different color, you can re-declare the variable on the widget class and any buttons that are within that widget will use the redefined color.
The second feature this unlocks is being able to scope variables to specific components. If you set a variable like
--widget-color on a
.widget rule, then only elements that are descendants of a
.widget element will be able to use the
--widget-color variable. Trying to access the value outside of the scope in which it was declared will result in no value being used (not an error).
Variables are a great addition to CSS. They have great potential to simplify large codebases by unifying disparate values. They can also simplify rules by allowing you to change specific values based on an element’s state or class rather than needing to re-declare entire properties. Because variables can be changed in various places including within
@media queries, they make it easy to integrate system light/dark mode settings into your site. When combined with the powerful
calc() function, you can turn a few simple variables into a comprehensive design system.
Are they a replacement for CSS pre-processors? No. Sass and Less still have many unique features that CSS lacks. They allow rules to be nested to reduce selector duplication. They have color functions which are difficult to replicate in CSS. There are still things they can do which the browser is simply not capable of, but they do require some sort of build process to generate the CSS that can be used.
All in all, pre-processors still have their place, but native variables expand the power of CSS without the need for any additional tooling.
- A Complete Guide to Custom Properties - CSS Tricks
- Using CSS custom properties (variables) - MDN
- Patterns for Practical CSS Custom Properties Use - CSS Tricks