When selecting typography, a solid understanding of the fundamentals of various types and styles is crucial for making informed decisions.
How typography is referenced
Typography in code is built from tokens. Tokens are generated from a platform-agnostic JSON file, and each token defines one property of a text style rather than a whole style. A heading in the Display/500/Bold style is therefore put together from these tokens:
font-family: var(--i80-typography-display-500-font-family);font-size:var(--i80-typography-display-500-font-size);line-height:var(--i80-typography-display-500-line-height);font-weight:var(--i80-typography-font-weight-bold);
Rather than calling upon each of these tokens in code every time text is styled, the Text Component groups them in one place. Additional CSS helper classes have been created to ease the style creation process, if necessary.
Font families
i80 ships its own fonts. They are served from design.i80.dk next to the stylesheet, never from a font CDN, so a page makes no third-party request and a visitor's address is not handed to anyone.
| i80 | zPlan theme | |
|---|---|---|
| Headings | Inter | Sora, and only at 18px and above |
| Body and UI | Inter | IBM Plex Sans |
| Code and data | JetBrains Mono | IBM Plex Mono |
All five are licensed under the SIL Open Font License 1.1.
Why Inter for i80. Its proportions sit close to the system fonts the component styles were drawn against, so the layouts keep fitting. One variable file carries every weight, and its optical-size axis keeps 13px labels open while tightening a 30px title by itself.
Why Sora stops at 18px. It is wide and geometric. At label and body sizes it reads blurry and takes more width than the layout has, so the two small display steps use IBM Plex Sans instead. The theme sets that; you do not have to think about it.
Each family ships with a matching fallback face — a local Arial or Helvetica with the real font's metrics applied — so the page does not jump when the web font arrives.
If a weight is missing
base.css sets font-synthesis: none. A weight the loaded font does not have renders at the nearest one it does, instead of a browser-smeared imitation. That makes a missing face visible while you are building, rather than shipping a blurry approximation.
Font weights
In addition to font size, font weight helps create different levels of emphasis throughout the UI. Font weights include:
- 400 (regular)
- 500 (medium)
- 600 (semi bold)
- 700 (bold)
Within these ranges, bold is used only for display and some code text styles, while regular is associated with body text styles which may include code.
Text styles
Display
Display styles should be used for headings or visual emphasis (like remaining balances). Unless used for visual emphasis, if the display text looks like a page heading, it should use an HTML heading tag.
Display text styles are available in the following sizes and weights:
- Display 500 (30px) - Bold
- Display 400 (24px) - Bold
- Display 400 (24px) - Semibold
- Display 400 (24px) - Medium
- Display 300 (18px) - Bold
- Display 300 (18px) - Semibold
- Display 300 (18px) - Medium
- Display 200 (16px) - Semibold
- Display 100 (13px) - Medium
Body
Body styles should be used for all general page content. Commonly placed within components (like buttons) and blocks of text, this style supports different font weights and sizes to establish a clear visual hierarchy. Body 200 is used as the default body content size as the majority of i80 products are data dense. Body 100 is often used as secondary text for hierarchical purposes while Body 300 is used for bigger UI elements like the large variant of the Button component.
Body text styles are available in the following weights and sizes:
- Body 300 (16px) - Semibold
- Body 300 (16px) - Medium
- Body 300 (16px) - Regular
- Body 200 (14px) - Semibold
- Body 200 (14px) - Medium
- Body 200 (14px) - Regular
- Body 100 (13px) - Semibold
- Body 100 (13px) - Medium
- Body 100 (13px) - Regular
Code
Code styles are used exclusively for text representing code in the UI (like the Code Block component).
Code text styles come in the following weights and sizes:
- Code 300 (16px) - Bold
- Code 300 (16px) - Regular
- Code 200 (14px) - Bold
- Code 200 (14px) - Regular
- Code 100 (13px) - Bold
- Code 100 (13px) - Regular
How typography is used
Body content
Body 200 is the default font size for body content. Scaling up or down is used as a means to create visual hierarchy in page UI, or component usage. As an example, the Button, medium (default) variant is sized at Body 200 while the large variant is Body 300.

Similarly, form fields' labels and input texts are Body 200, while any other secondary information, like helper text or error messages are sized at Body 100. This ensures that primary information is more prominent with the larger size for visual hierarchy.

For more details about form patterns, read the form patterns documentation.
Semantic heading or not?
The Text component does not equate a specific style (Body, Display, or Code) with a specific HTML semantic structure (like <p/>, <h1/> or <span>), it is up to the consumer to define the logical semantic element for the each piece of text. To ensure accessible page content, the scaling of the Display styles often are associated with the scaling of the HTML headings such as:
- Display 500 → H1
- Display 400 → H2
- Display 300 → H3
- Display 200 → H4
- Display 100 → H5
In general we recommend mapping Display font sizes sequentially to markup, but this is not always possible. Additionally, Display text styles do not always need to be headings. They may be used to emphasize important information, such as remaining balances, so that users are able to visually understand the level of importance of information on the page.

An important note: The card is still following the semantically correct logical order of headings, where “Total period usage” is a heading (an H3 with semibold weight), while the balance below it is not (medium weight as a span or paragraph). Font weight is used to create the visual hierarchy here instead size.
Loading the fonts
The fonts come with the stylesheet. components.css declares the faces and serves them from the same version path, so there is nothing to install and no third-party request:
<link rel="stylesheet" href="https://design.i80.dk/v/0.6.0/components.css">
<link rel="stylesheet" href="https://design.i80.dk/v/0.6.0/base.css">
base.css is the second half and is opt-in: it sets the page's own font, the box model the component styles assume, and tabular figures in tables and times. Without it, text outside an i80 tag falls back to the browser default — the same page in two fonts. Load it unless your application already has a reset you would rather keep, in which case set font-family: var(--i80-typography-font-stack-text) on :root yourself.
To cut the moment of fallback text on a first visit, preload the text face:
<link rel="preload" as="font" type="font/woff2" crossorigin
href="https://design.i80.dk/v/0.6.0/fonts/inter/InterVariable.woff2">
Preload the one face the page starts with, not all of them: each preload competes with the markup for the same connection.
Numbers that line up
base.css gives tables and <time> tabular figures, so a column of hours or amounts aligns. Anywhere else a number is read as a number — an amount, a duration, an ID — add the class:
<span class="i80-numeric">1 240,50 kr.</span>
It also turns on a slashed zero, so 0 cannot be read as O in a reference or an employee number.
Line length
Running text stops at --i80-layout-measure (70 characters). Put class="i80-measure" on the text column — not on a table, a code block or a layout that needs the full width.
How to use these styles
We offer different ways to apply typography styles to UI elements:
- The Text element: the preferred way to apply i80 text styles, because it puts the classes on the tag you choose.
- CSS helper classes: for markup you write yourself, or that something else renders for you.
- Design tokens: This should be the last resort when none of the previous options are possible (or when only some of the I80 style properties are needed, like
font-family,font-size,line-height, etc.)
The Text element
<i80-text> renders the tag you ask for and puts the right typography classes on it, plus colour and alignment. See Text for everything it takes.
For details about this component, see the Text page.
CSS helper classes
In a single declaration, these predefined CSS classes contain everything to apply a standard typographic style to an element: font-family, font-size, line-height, and a reset for margin and padding to match the intended design language.
The quick brown fox jumps over the lazy dog.
<p class="i80-typography-display-300">
The quick brown fox jumps over the lazy dog.
</p>
Font styles
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
-
Aa
Font family
While we don’t recommend using custom styles often, font-family helpers are available to change the font family of an element.
The quick brown fox jumps over the lazy dog.
<p class="i80-font-family-sans-text">
The quick brown fox jumps over the lazy dog.
</p>
font-family helpers |
Use for |
|---|---|
font-family-sans-display |
Headings and titles |
font-family-sans-text |
Body copy |
font-family-mono-code |
Monospaced text |
-
Aa
-
Aa
-
Aa
Font weight
Use the font-weight helpers to change the weight of text in an element.
The quick brown fox jumps over the lazy dog.
The quick brown fox jumps over the lazy dog.
<!-- with font-family CSS helpers -->
<p class="i80-font-family-sans-text i80-font-weight-medium">
The quick brown fox jumps over the lazy dog.
</p>
<!-- with typographic style CSS helpers -->
<p class="i80-typography-display-300 i80-font-weight-semibold">
The quick brown fox jumps over the lazy dog.
</p>
-
Aa
-
Aa
-
Aa
-
Aa
Style and weight
The following are recommended style and weight combinations for use in our applications:
-
The quick brown fox jumps over the lazy dog.
display-500 (bold) -
The quick brown fox jumps over the lazy dog.
display-400 (medium) -
The quick brown fox jumps over the lazy dog.
display-400 (semibold) -
The quick brown fox jumps over the lazy dog.
display-400 (bold) -
The quick brown fox jumps over the lazy dog.
display-300 (medium) -
The quick brown fox jumps over the lazy dog.
display-300 (semibold) -
The quick brown fox jumps over the lazy dog.
display-300 (bold) -
The quick brown fox jumps over the lazy dog.
display-200 (semibold) -
The quick brown fox jumps over the lazy dog.
display-100 (medium) -
The quick brown fox jumps over the lazy dog.
body-300 (regular) -
The quick brown fox jumps over the lazy dog.
body-300 (medium) -
The quick brown fox jumps over the lazy dog.
body-300 (semibold) -
The quick brown fox jumps over the lazy dog.
body-200 (regular) -
The quick brown fox jumps over the lazy dog.
body-200 (medium) -
The quick brown fox jumps over the lazy dog.
body-200 (semibold) -
The quick brown fox jumps over the lazy dog.
body-100 (regular) -
The quick brown fox jumps over the lazy dog.
body-100 (medium) -
The quick brown fox jumps over the lazy dog.
body-100 (semibold) -
The quick brown fox jumps over the lazy dog.
code-300 (regular) -
The quick brown fox jumps over the lazy dog.
code-300 (bold) -
The quick brown fox jumps over the lazy dog.
code-200 (regular) -
The quick brown fox jumps over the lazy dog.
code-200 (bold) -
The quick brown fox jumps over the lazy dog.
code-100 (regular) -
The quick brown fox jumps over the lazy dog.
code-100 (bold)
Design tokens
i80 offers numerous typographic design tokens should your project require more flexibility.
Since these are “atomic” definitions that associate a particular typographic property (e.g., font-size, line-height, letter-spacing, etc.) to a single value, we don’t consider them “typographic” styles. Therefore, we advise against using them directly in your CSS and recommend using the CSS helper classes instead.