> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Add annotations

*Explain your design decisions right on the canvas.*

[Figr Canvas: show, point, annotate, then design](https://www.youtube.com/embed/ZZHGlkyyJgc)

Annotations are notes that stay visible next to your work. Use them to explain why a design looks the way it does, call out behaviour that isn't obvious from a static screen, or leave notes for developers before handoff. Unlike comments, annotations aren't conversations and don't get resolved.

**1. Add an annotation**

Choose the **Sticky Note** tool in the canvas toolbar and click where you want the note to appear.

![The Sticky Note tool in the canvas toolbar](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/docs/ann-01-tool.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=dee61dcdb1bef60a1a255c50c1325aeb)

**2. Write the note**

Keep it short and specific. For example: "Button stays disabled until all required fields are filled."

![A sticky note on the canvas with its formatting toolbar](https://mintcdn.com/figr-1af7ae64/6fNHqiw94uTEs_lh/images/docs/ann-02-note.png?fit=max\&auto=format\&n=6fNHqiw94uTEs_lh\&q=85\&s=82f1fac3789585b293910f612adc90f5)

> [!NOTE]
>
> Figr reads annotations on its next turn, so a note on the canvas also guides the next design.

**3. Point it at what it describes**

Place the annotation beside the screen or element it refers to, or connect it with a line so it's clear what it's about.

**4. Update it as the design changes**

Edit or delete annotations when the design moves on, so they never describe an old version.

> [!TIP]
>
> Annotate the things a developer would otherwise have to ask about: what happens on hover, loading, errors and empty states.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.