Forma 36: Icon component

Usage no npm install needed!

<script type="module">
  import contentfulF36Icon from 'https://cdn.skypack.dev/@contentful/f36-icon';


title: 'Icons' type: 'component' slug: /components/icon/ github: 'https://github.com/contentful/forma-36/tree/master/packages/components/icon' storybook: 'https://v4-f36-storybook.netlify.app/?path=/story/components-icon--default' typescript: ./src/Icon.tsx,../icons/src/ArrowDown.tsx

Icons are used to indicate actions, statuses and navigation. The icon components can be used in Button, TextLink, Note and other components.


import * as icons from '@contentful/f36-icons';
// or, for custom icons
import { Icon } from '@contentful/f36-components';


Forma 36 provides a list of built-in icons that can be used as regular React components.

Icon variants

The icon components can be configured in different ways using variations in color and size:

Icon sizes

All icons

Custom icons and third-party libraries

Custom icons can be rendered with Forma 36 to take advantage of the same props and styling as the built-in icons. This means you can use a prop like variant="primary" or size="large" on your own icons and they will match the built-in icons from Forma 36.

Custom icons can be used in two ways: with as prop and with an SVG path.

as prop

Passing a React component with an SVG icon to the as prop on Icon makes it render that SVG. This works both with your own icons and with icons from third-party icon libraries such as react-icons:

Using a loader like SVGR makes it easier to use your own SVG files with the as prop as it helps import them as React components.

SVG paths

Another way to render custom icons is to wrapping SVG paths in the Icon component directly:

Props (API reference)

Built-in icons

Custom icons

Content guidelines

  • Select an icon that accurately represents the subject
  • Pair icons with text
  • Position buttons consistently in the interface
  • Ensure the meaning of the icon is consistent in all use cases
  • Consider how the icon fits into the context of the screen and reduce complexity where possible