Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 36 ยท Interface and Frames

Pages and File Organization: A Structure That Scales

Organize a Figma file with pages, sections and covers, set up a clean structure for exploration, final screens and components, and check it with runnable stand-ins.

A design file that starts as a tidy handful of frames can grow into hundreds of layers in a few weeks. Without a structure, people lose work, developers open the wrong screen, and designers duplicate things that already exist. This lesson shows how to use pages, sections and a cover to keep a file readable as it grows.

What a page is

A page is like a separate canvas inside the same file. In the left sidebar, the Pages list sits above the layers. Click the plus button to add a page; double-click a page name to rename it; drag to reorder; right-click for duplicate and delete. The Layers panel always shows only the current page's layers.

Each page has its own infinite canvas, its own zoom position and its own background color (set it by clicking the empty canvas and using the Design panel). Components and styles are shared by the whole file, so you can keep your components on one page and use them on others.

A page structure that works

There is no single standard, but many teams use something close to this:

Page Purpose
Cover A thumbnail that identifies the file in the file browser
Read me What the file is, status, owner, links, changelog
Exploration Rough ideas, abandoned directions
Design / Final Screens ready for review
Components Reusable building blocks
Archive Old versions you might still need

Some teams add a separator page named --- so the list looks grouped. Because pages are just a list, separators are a naming trick, not a feature.

A tidy file

Cover What the file is
Read me Status and notes
Exploration Messy ideas allowed
Final Reviewed screens

Messy work goes on its own page

1 / 2

The cover

The file thumbnail is chosen from a frame on the first page. Right-click a frame and choose Set as thumbnail. A cover could be a simple frame with the product name, version and a few key screens. It makes the file easy to recognize in the file browser, and a design team's projects look more professional with consistent covers.

Sections inside pages

On a page like Final, group the screens by user flow using sections, as described in Frames, Groups and Sections. A page might contain sections named Onboarding, Checkout and Settings, each holding the relevant screens laid out left to right in order. The reading direction should match the flow of the experience.

Lay out flows left to right, with a consistent gap (such as 120 px) between frames. People scan flows like text, and a regular gap makes screens easy to count and compare.

Naming frames for flows

Name top-level frames so they sort and explain themselves, for example 01 Welcome, 02 Sign up, 03 Verify email. Numbers set the order of reading. When developers or stakeholders comment, they can say "screen 03" without confusion.

Version history

Figma keeps version history. Open it from the file name menu (the file name at the top, then Show version history) to see autosaves and named versions. You can:

  • Add to version history with a title and description for milestones such as "Sent to review".
  • Browse and restore an older version (restoring creates a new version, nothing is lost).
  • Duplicate an older version to compare without changing the current file.

Name a version before big changes, and treat it as a save point, not as a substitute for branching.

Branching (concept)

On plans that offer it, branching lets you copy a file, work on changes in isolation and merge them back after review, much like source control. We introduce it in the collaboration chapter. For now the rule is: explore on a dedicated page or branch rather than editing your final screens directly.

Checking structure with a stand-in

The following stand-in checks a planned page list against a recommended minimum. It is only plain Python and does not talk to Figma.

Python Stand-in: file structure checklist

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Sorting frames into a flow

Numbered names help you see the flow. This stand-in orders names the way a human expects, putting 02 before 10.

Python Stand-in: natural ordering of frame names

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A plain text sort puts "10" before "9". Zero-padded numbers (09) sidestep the issue entirely, which is why design teams write 01, 02.

Working with large files

  • Split by product area if a file gets slow: separate files for different features, joined through a shared library (covered in the design systems chapter).
  • Avoid thousands of nested layers; flatten decorative vector art, and remove hidden duplicates.
  • Use the Read me page to state what is final, what is draft and who to ask.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does the Layers panel show?

    Each page has its own layer tree, and the panel shows the current page.
  2. 2. How do you set the file thumbnail?

    Pick a frame and set it as the file thumbnail.
  3. 3. Why prefix frame names with 01, 02, 03?

    Numbered names make the reading order obvious and let people refer to screens by number.
  4. 4. Where should rough, abandoned ideas live?

    Keep unfinished work away from the pages that stakeholders and developers rely on.

Summary

  • Pages are separate canvases in one file; layers belong to the current page.
  • A common structure is Cover, Read me, Exploration, Final, Components and Archive.
  • Sections and numbered frame names make flows easy to read.
  • Name important versions in version history and explore on separate pages or branches.

Next: Shapes and Boolean Operations