One of our design goals is to convey GitLab’s distinct personality through illustration that is aesthetically refined, visually consistent, and reflective of our particular sense of style.

Collection of GitLab illustrations


  1. Be simple. For clarity, we use simple and specific elements to create our illustrations. We take a "less is more" approach where illustrations are supportive. They should be obvious but not comprehensive, focusing on impression over complexity.
  2. Be optimistic. We take an open-minded, positive, and friendly approach. Those values are reflected in our illustrations with a light and airy feel.
  3. Be helpful. Our illustrations help users to understand concepts and guide them in the right direction.

Efficiency and reuse

Practically, applying the principles gives us more leverage to think of the relationship of illustration to use case as a one-to-many instead of one-to-one. In other words, a single illustration could be used in multiple instances.

For example, a single empty state illustration could be abstracted enough to be used in multiple empty state pages where the visual impression is supported more fully by the content and context. The illustration doesn't have to do all the heavy lifting.

To better support reuse, the illustration library in Figma also contains dozens of small illustration components that represent concepts found throughout the product. These small illustrations can be used on their own, or as part of a larger illustration.

Illustration elements and components assembled into larger illustration
Elements come together as part of a larger illustration.

By combining a multipurpose mindset with reusable components, the time it takes to create a new illustration, and the resulting number of illustrations, should both be reduced. This is a win both for designers and users where time and consistency matters.


Product illustration style derives from the GitLab Brand Design marketing illustrations guidelines. It's designed to work in both light and dark UI by placing most objects in or above containers with solid fills.

Use brand colors to create continuity with the larger GitLab brand. White, charcoal, and purple are used most frequently; the remaining colors are used to highlight and accent objects within an illustration. Specific uses are listed below.


All shapes have a solid fill, or overlap an element with a fill, so that they remain visible against any background color.

  • White is used for a majority of fills.
  • Purple 01p may be used to highlight the main ‘action’ or emphasis of the illustration.
  • Primary oranges and Purple 02p are used sparingly in favor of the secondary palette.
  • Secondary purples are used for background fills and muted elements. Note that muted elements will appear much stronger on a dark surface unless place on or over a container with a lighter fill.
  • Teals are useful to communicate positive actions or success.
  • The remaining colors in the secondary palette are used as highlights, shadows, and accents to differentiate objects within the illustration.


A stroke encapsulates most elements and is used for line work and depicting motion or action.

  • All strokes use a 2px weight and are aligned to the center or inside of the shape.
  • A dashed stroke makes connections and conveys empty or unpopulated elements.
  • A line uses square caps. Miter line joins are the default, but a bevel can be used if the resulting point is too extreme.
  • Charcoal is used for object strokes and small fill areas. Note that these strokes may not be visible on a dark surface and in most cases should overlap a background container.
  • Purple 04s can be used on strokes that make connections, depict motion, or represent unpopulated elements.


An illustration is primarily comprised of geometric shapes. Use circles, rectangles, squares, and triangles for base elements, with lines and organic shapes for details as needed.

There are two container shapes: leaf and round.

Example of the leaf and round container shapes, colored with Purple 02s, one of the recommended colors for background fills. The leaf shape is a square with rounded top-right and bottom-left corners. The round shape is a circle.
Container shapes: leaf and round
Define shapes usage, see for current exploration. Create an issue

Border radius

  • Corners and angles have no border radius by default, but a border radius between 4px to 16px can be used for softer, rounded objects.
  • When possible, apply a border radius to the bottom right corner of a shape to create an upward sweep and add a bit of personality.


  • An object should represent its most modern and recognizable form. For example, use a mobile phone instead of a rotary phone.
  • Typography should be avoided in illustration because it isn't accessible for all users and can't be translated. It is acceptable to include 1–2 characters to represent text or language in general. For example, a character on a keyboard.
  • The tanuki should only be used for marketing illustration and assets that directly represent GitLab in the product, like a GitLab bot avatar.

Grid and size

Using predefined grids and sizes not only helps illustrations feel more consistent and intentional throughout the product, they also add helpful and meaningful constraints to reduce the time it takes to create an illustration.

An illustration can use either a large isometric grid, or one of the four focal point grid sizes to align with the use case.

Focal point grid

A focal point grid leverages the rule of thirds to place elements with dedicated focal points. The vertical and horizontal guides divide the frame into nine equal parts. When multiple objects are present, placing them at or near the point of intersection can provide balance and movement.

Not all illustrations will have multiple objects or objects that need to align to an intersection point. Circular grid lines are also provided for centering within the frame.

  • Large: 288px × 288px frame size. Used for feature promotion.
  • Medium: 144px × 144px frame size. Used for empty states and error states.
  • Small ("spot" illustration): 72px × 72px frame size. Used for banners and when space is limited.
  • Extra small: 36px × 36px frame size. Used for individual illustration elements that are combined with other elements to form a larger composition, or to connect other elements in the UI.
Large, medium, and small focal point grid sizes
Focal point grid sizes: large, medium, and small
Example medium illustration that uses the focal point grid
Focal point grid example

Isometric grid

An isometric grid provides depth to concepts which can convey process, relationship, and parts. An isometric illustration isn't necessarily more complex, it's just leveraging dimension as an added attribute.

  • Large (only): 288px × 288px frame size. Used for feature promotion.
  • An isometric grid uses guides that are rotated 30º from the horizontal plane.
  • Three subgrids are available to handle different angles: ramp left, ramp right, and ramp forward.
Isometric grid lines and subgrid lines
Isometric grid and subgrids
Add isometric example Create an issue


While an illustration will always be created using one of the grid sizes above, the final output dimensions follow these rules:

  • Small illustrations are always output at 72px × 72px, even if that means there's extra white space in the frame. This helps ensure that when multiple small illustrations are present in the same context they will optically align. Icons follow a similar approach.
  • Large, medium, and extra small illustrations must fill either the width or the height of the frame (or both), and any remaining whitespace must be removed before exporting (frame cropped to artwork) to prevent alignment issues. Use GitLab UI utility classes if additional space is needed in a page layout.


Everyone can contribute to GitLab, including our product illustration in Figma Get started with our contribution guidelines.


Last updated at: