Figma Pages: The Folders Inside Your Files

WHY IT EXISTS Figma files can become massive and chaotic, containing everything from early sketches to final developer handoffs. Pages were created to provide an organizational layer within a single file, preventing the need to create countless separate files for different parts of the same project.

THE MENTAL MODEL A Figma file is like a binder, and pages are the tabbed dividers inside it. Each page is a separate, massive canvas where you can place frames, components, and other layers. This allows you to group related work together, making it easier for you and your team to navigate a large project without getting lost.

HOW IT WORKS In the left sidebar's Layers panel, you can view, create, and manage pages. Click the current page name to see the list. You can add a new blank page or duplicate an existing one to create a snapshot of your work. Pages can be renamed by double-clicking or right-clicking. Anyone with edit access can manage pages, while those with view access can only navigate between them.

WHEN TO USE IT Pages are essential for organizing any non-trivial design file. Common strategies include: first, creating separate pages for different design stages like "Exploration," "In Progress," and "Ready for Dev"; second, dedicating a page to your main component library and styles; third, isolating each major user flow onto its own page to simplify prototyping. You can also use emojis in page names (e.g., ✅ Final) or blank "spacer" pages for visual separation.

WHEN NOT TO USE IT Don't use pages for entirely separate projects that don't share components or context; those should be in different files. Also, be mindful of plan limitations. If you're on a free Starter plan, you are limited to three pages per file. Over-organizing a very simple, single-screen project with many pages is also unnecessary overhead.

ONE CANONICAL EXAMPLE A team is designing a mobile banking app. Their Figma file has several pages: one page named "🎨 Styles & Components" holds all the color styles, typography, and main UI components. Another page, "➡️ Onboarding Flow," contains all the screens for user sign-up. A third page, "💸 Send Money Flow," details that specific user journey. Finally, a page called "Critique - May 28" is a duplicated, static version of a flow used for a feedback session.