Skip to content
Shortcut

Menu

Show guidance for
esc

Figma Guide

What each Figma tool is for, when to open it, and how they fit together. Figma Help explains how features work; this explains which one you need.

Verified 7 Oct 2026

Figma changes quickly. Descriptions restate Figma’s own pages as of that date.

What should I use in Figma?

I want to…

Open

Figma Design

Why. It has the layout, component and variable tools that screens need.

About Figma DesignLayout cheat sheet

Products and capabilities

This or that?

Make vs Design

What is the difference?
Figma Design is for designing and visual, click-through prototyping. Figma Make is code-backed, AI-assisted creation of something that actually works.
When do I use each?

Design: to decide what the interface is.

Make: to find out how it behaves, once you know what it is.

Can I use both?
Yes, in that order. Attach frames from Design to a Make prompt, test, then return to Design to refine.
Common mistake
Starting in Make with no requirements or system, and getting a generic product.

Official sources

Figma agent vs Figma Make

What is the difference?
The agent works on design layers in the canvas. Make produces code.
When do I use each?

Agent: modify existing designs, explore directions, bulk edits, find files, apply library guidance.

Make: functional prototypes, code-backed experiences, interaction exploration.

Can I use both?
Yes. Use the agent to prepare and vary the screens, then Make to bring one flow to life.
Common mistake
Asking the agent for behaviour, or asking Make for a tidy design file.

Official sources

Make vs Sites

What is the difference?
Both end in code. Make is for prototypes and apps. Sites is for designing and publishing a responsive website, with a CMS.
When do I use each?

Make: testing an idea, or an app with behaviour.

Sites: a public site whose content other people will update.

Can I use both?
Rarely on the same deliverable.
Common mistake
Publishing a Make prototype as if it were a maintained site.

Official sources

FigJam vs Design

What is the difference?
FigJam is a whiteboard for thinking together. Design is a precise tool for making screens.
When do I use each?

FigJam: workshops, mapping, synthesis, early flows.

Design: anything that will be built.

Can I use both?
Yes. Decisions made in FigJam are carried into Design.
Common mistake
Drawing detailed screens in FigJam, or running a workshop in a Design file where people are afraid to touch things.

Official sources

FigJam vs Slides

What is the difference?
FigJam is for working something out together. Slides is for presenting what you worked out.
When do I use each?

FigJam: the group is contributing, and the outcome is not known yet.

Slides: you are telling a story to an audience, with a prototype they can try.

Can I use both?
Yes. Run the workshop in FigJam, then present the decisions in Slides.
Common mistake
Presenting a workshop board as the readout. A board records the conversation; it does not tell the story.

Official sources

Variables vs styles

What is the difference?
A variable stores a single raw value: a solid colour, a number, a string or a boolean. A style can store compound properties such as gradients, images and blend modes.
When do I use each?

Variables: tokens, anything that changes by mode such as light and dark, and anything you want to scope or alias.

Styles: gradients, effects, and type styles that combine several properties.

Can I use both?
Yes. Figma says variables are additive, not a replacement. Variables can be applied to styles; styles cannot be applied to variables.
Common mistake
Converting everything to variables and losing gradients and effects, or keeping colours as styles and being unable to add a dark mode.

Official source

Variables vs component properties

What is the difference?
Variables hold values used across a file. Component properties are the changeable aspects of one component: variant, boolean, instance swap, text and slot.
When do I use each?

Variables: colour, spacing and other decisions shared by many components.

Properties: what a person using this component is allowed to change.

Can I use both?
Yes. A component's properties control its options; its colours and spacing come from variables.
Common mistake
Making a variant for every combination when a boolean or instance-swap property would do.

Official sources

Slides vs other presentation tools

What is the difference?
Slides can hold playable prototypes and live Figma objects, and has a Design Mode with Figma's design tools.
When do I use each?

Slides: presenting work that lives in Figma.

Another tool: when the audience must edit the deck there, or the organisation requires it.

Can I use both?
You can export, but the live prototypes are the reason to use Slides.
Common mistake
Pasting screenshots of a prototype into slides when the audience could have tried it.

Official source

Workflow recipes

Craft guidance

User research

  1. FigJam. Capture notes from each session
  2. FigJam. Affinity-map as a team
  3. Figma Design. Turn findings into flows
  4. Figma Design. Prototype
  5. Slides. Research and design readout

For ongoing research with many contributors, a dedicated research tool keeps evidence linked better than a board.

Workshop

  1. Shortcut. Decide whether it needs a workshop at all
  2. FigJam. Prepare the board and agenda
  3. FigJam. Run the session
  4. FigJam. Sort, summarise and record decisions
  5. Figma Design. Design from the decisions

Design to development

  1. Figma Design. Build with components and variables
  2. Figma Design. Clean the file
  3. Dev Mode. Mark ready, annotate, hand over
  4. Code Connect. Map to real components, if you have them
  5. Developer. Implement, and compare changes on updates

AI prototype

  1. Figma Design. Prepare the key screen and system
  2. Figma Make. Create the interactive prototype
  3. You. Test with users
  4. Figma Design. Refine from what you learned

Figma with other AI tools

  1. An AI assistant. Help structure the requirements
  2. Figma Design. Visual design
  3. Figma agent. Explore and edit
  4. Figma Make. Working prototype
  5. Shortcut. QA with Before You Send It
  6. Dev Mode. Developer implementation

One possible sequence. No single workflow fits every team.

AI in Figma

AI + Design

Figma notes that AI outputs may be misleading or wrong, and should be verified before you rely on them. Figma Help, Use AI tools in Figma Design(opens in a new tab)

  • Replace and rewrite content

    Use it for
    Realistic placeholder text, and resizing copy to fit.
    Don’t rely on it for
    Final copy or facts about your product.
    Workflow example
    Replace lorem ipsum on a screen, then check the layout with the longest strings.
    What to verify
    That every label is true for your product.
  • Translate text

    Use it for
    Seeing how a layout copes with another language's length.
    Don’t rely on it for
    Translation you will ship.
    Workflow example
    Translate a screen into your longest supported language and fix what overflows.
    What to verify
    Have a fluent speaker review anything that ships.
  • Generate and edit images

    Use it for
    Placeholder imagery, background removal, upscaling.
    Don’t rely on it for
    Brand imagery, or anything needing rights clearance.
    Workflow example
    Generate stand-in images so reviewers react to layout, not grey boxes.
    What to verify
    Rights, brand fit, and that generated people and products are not misleading.
  • First Draft

    Use it for
    Getting past a blank canvas, or seeing a typical layout to react against.
    Don’t rely on it for
    A design. It is a typical screen, not yours.
    Workflow example
    Generate a draft, list what is wrong with it for your users, and design from that list.
    What to verify
    Against the AI-look signals, and against your design system.
  • The agent

    Use it for
    Bulk edits, variations and applying library guidance.
    Don’t rely on it for
    Judgement about hierarchy or what to build.
    Workflow example
    Write two or three library guidelines, ask for a screen, and check each guideline was followed.
    What to verify
    Detached instances, off-system values and anything it invented.

Building a design system in Figma

Craft guidance
  1. Foundations first

    Decide colour, spacing, type, radius and elevation before any component.

    Spacing cheat sheet
  2. Raw values as primitive variables

    One collection for the palette and the scales. Nothing in a design should point at these directly.

    Design Tokens cheat sheet
  3. Semantic variables that alias them

    Name by role: background, text, border, action. These are what designs use.

    How SGDS layers its tokens
  4. Modes for contexts

    Light and dark, density, or brand: each a mode of the semantic collection.

    Variables vs styles
  5. Styles for what variables cannot hold

    Gradients, effects and type styles that combine properties.

    Variables vs styles
  6. Components, smallest first

    Build with auto layout and variables so they resize and re-theme.

    Components cheat sheet
  7. Properties before variants

    Use boolean, text and instance-swap properties for options; variants for real differences in state or size.

    Variables vs component properties
  8. Publish as a library

    One file as the source. Libraries need a paid plan.

    Libraries
  9. Name for the people using it

    Names a newcomer could search for. Match the names in code.

    Design Handoff cheat sheet
  10. Document when to use each

    A component nobody knows when to use gets rebuilt.

    How other systems document theirs

Before you hand your Figma file over

Craft guidance

Structure

  • Pages are named and ordered: final screens, explorations, archive
  • Explorations are separated from what should be built
  • Frames have names a developer could search for
  • Sections group flows that belong together

Components

  • No detached instances that should be components
  • No one-off components that duplicate a library one
  • Variants and properties are named consistently
  • Unused local components and styles are removed

Values

  • Colours, spacing and radii come from variables or styles
  • No near-duplicate values
  • Text uses type styles

Behaviour

  • Prototypes start from an obvious frame and can be followed
  • Every state is drawn, including empty, loading and error
  • Responsive behaviour is shown or annotated
  • Frames to build are marked ready for dev

Then check the design itself with Before You Send It

Testing responsive designs in Figma

Craft guidance

Do not design only for one static frame. A frame is one width; people will use all of them.

Build frames that resize

  • Use auto layout so content pushes and reflows instead of overlapping.
  • Hug for things sized by their content, Fill for things that share the space left.
  • Set minimum and maximum widths so a card or column cannot collapse or stretch too far.
  • Nest it: a page that resizes needs sections, and items inside them, that resize too.
  • Variable modes hold a different value per context. Light and dark is the common use; the same mechanism can hold values that differ by width or by density.

Hug, Fill or FixedCollections and modes

Widths to drag a frame through

  • 320
  • 375
  • 390
  • 430
  • 768
  • 820
  • 1024
  • 1280
  • 1440
  • 1920
  • Foldable, closed
  • Foldable, open

Small, standard and large mobile; tablet and large tablet; laptop, desktop and large desktop. Figma’s frame presets, like these widths, are references, not required breakpoints. Resize the frame between them and watch where the layout breaks.

Responsive test matrix

After Figma Make or any AI generates a screen

Generated UI should not be assumed responsive just because it renders. Check:

  • Overflow at mobile widths
  • The transition through tablet widths
  • How cards stack
  • How navigation collapses
  • What the table does
  • Modal sizing
  • Touch targets
  • Long text and translated text
  • Content that changes length or count

5 recent releases that affect design work. Tools updates need no action unless you want the feature.

FigmaAINow generally availableTool update

The Figma agent is generally available

What changed
The Figma agent has left beta. The release notes list improved latency, file search and configurable guidelines for design libraries.
Why it matters
An agent that reads library guidelines is only as consistent as those guidelines. Component documentation now shapes generated output, not just human use.
What to do
Review what usage guidance your libraries expose, and agree with your team where agent-made frames need a design review before handoff.
How to use it, and what to watch for

Use it for

  • Applying your library's guidelines to generated frames
  • Finding existing files and designs from a chat
  • Repetitive file work, such as renaming and tidying

Be careful with

  • Guidelines that are vague or missing: the agent can only follow what you wrote
  • Accepting generated frames without a design review

Try this workflowWrite two or three guidelines for one library, such as which button variant is primary. Ask the agent for a screen that uses it, then check each guideline was followed.

Source

FigmaToolsTool update

Connect multiple GitHub organizations to Figma

What changed
A single Figma plan can now be linked to more than one GitHub organization.
Why it matters
Teams whose code lives across several organizations no longer have to pick one to connect to their design files.
What to do
If your design system and product code sit in different organizations, ask your admin whether both can now be connected.

Source

FigmaToolsNew capabilityTool update

Motion adds custom styles, audio, text animations and Lottie export

What changed
Figma Motion gained reusable animation styles, audio on the timeline, character-level text animation and Lottie export.
Why it matters
Reusable animation styles let motion be specified once and shared, the way colour and type styles already are.
What to do
If your team documents motion by hand, try defining your standard durations and easings as animation styles.
How to use it, and what to watch for

Use it for

  • Defining standard durations and easings once, as animation styles
  • Having the agent apply those styles consistently

Be careful with

  • Motion added because it is easy, not because it explains a change
  • Reduced-motion behaviour, which you still have to specify

Try this workflowCreate three animation styles for your product: quick, standard and emphasised. Apply them to one flow and remove any animation that does not show what changed.

Source

FigmaToolsTool update

Vertical wrap available in auto layout

What changed
Vertical auto layout can now wrap content into new columns, mirroring CSS flexbox behaviour.
Why it matters
Layouts that flow down and then across can be built with auto layout instead of faked with fixed frames.
What to do
Nothing has to change. Try it on any list you currently split into columns by hand.

Source

FigmaAINew capabilityTool update

Figma designs can feed Weave workflows

What changed
A Figma node connects designs made in Figma Design to Figma Weave workflows. You choose which text and image layers become workflow inputs.
Why it matters
On-brand variations can be produced from a layout you designed, without the layout itself being regenerated.
What to do
Pick one template with clear text and image slots and try it as a workflow input before relying on it for a campaign.
How to use it, and what to watch for

Use it for

  • Producing content variations from a fixed layout
  • Keeping generated assets inside brand templates

Be careful with

  • Text that is longer than the layout allows
  • Generated images that need rights or brand review

Try this workflowMark the layers that may change, run five variations, and check each for overflow and off-brand imagery.

Source