Hello

For years, Figma has been the gold standard for interface design. It’s fast, collaborative, and somehow manages to make design feel fun again. But even with all its brilliance, there’s always been one small—but incredibly frustrating—gap in its system.

Figma doesn’t have subpages.

And honestly, that’s wild.

The chaos of one giant page

If you’ve ever worked on a complex design system or a product with multiple flows, you know exactly what I’m talking about. You open a Figma file, and suddenly you’re staring at 200 artboards, 50 prototypes, and a sea of arrows that look like someone spilled spaghetti on your screen.

Sure, you can organize things into pages. But those pages quickly become their own mess. Before you know it, you’ve got 25 of them—each representing some combination of “v2,” “final_final,” and “do_not_touch.” Not to mention the pages for design system tokens, experiments, and archived explorations.

It’s not that Figma’s organization tools are bad—they’re just flat. And that’s the problem.

Why subpages would change everything

Imagine being able to nest pages inside other pages. A small, simple addition that suddenly makes every file make sense.

• A “Main Product” page with subpages for “Onboarding,” “Dashboard,” and “Settings.”

• A “Design System” page with subpages for “Components,” “Icons,” and “Tokens.”

• A “Client Project” with subpages for “V1 Concepts,” “Approved Designs,” and “Archive.”

It’s not a radical idea. Most tools we use daily—Notion, Google Drive, even VS Code—let us organize content hierarchically. Because real projects aren’t flat. They grow, evolve, and require structure.

Right now, Figma forces us to hack that structure through naming conventions (“01_Onboarding,” “02_Dashboard,” etc.) or separate files altogether. Both options break the flow and make collaboration harder than it should be.

It’s not about clutter—it’s about focus

Designers love clarity. We spend hours aligning 8px grids, perfecting visual hierarchy, and making sure users know where to look next. So why doesn’t our design tool give us the same luxury?

Subpages would bring focus back to the design process. They’d let teams explore freely without losing context, organize work without splitting it apart, and create cleaner, more navigable design spaces. It’s structure without friction.

Figma’s next natural evolution

Figma’s superpower has always been how human it feels. It takes something complex—collaborative design—and makes it intuitive. Adding subpages feels like the next natural step in that journey.

A way to keep the playground fun, but finally give it some fences.

Because honestly, Figma doesn’t need more features. It just needs this one small piece of structure to make everything else it’s built feel complete.

So yeah—subpages. That’s the feature Figma’s been missing all along.