Organize your Figma projects like a pro: nested folders have arrived

What Figma just changed about file organization

Until now, structuring a Figma account often meant stacking dozens of "Projects" flat, with no hierarchy possible. A growing team, a client juggling multiple brands, an agency managing fifteen accounts at once: past a certain volume, finding the right file turned into a scavenger hunt.

Figma is fixing this with nested folders. In practice, Projects become regular folders, which you can now stack inside one another, up to 10 levels deep, and color-code for instant visual cues.

What actually changes

• Every file in a Team now lives inside folders, and every mention of "Projects" in the interface has been renamed to "Folders"
• Folders nest up to 10 levels deep and can be color-coded to create a clear visual hierarchy
• Sharing gets simpler: a nested folder automatically inherits access from its parent folder, unless you restrict access to specific people

The rollout is happening gradually over the coming weeks, across all plans, from Starter to Enterprise.

Why this update matters more than it seems

On paper, this looks like a simple organizational feature. In practice, it is a direct answer to a problem every agency or product team knows well: a tool's structure needs to keep up with the growth of the work, not hold it back.

Previously, the only way to fake a hierarchy was to prefix Project names with homemade conventions ("01_Client_Brand_Phase2"), or multiply Teams to make up for the lack of nesting. It worked, but it demanded iron discipline and quickly fell apart the moment new team members joined.

Mazette.co's take: a great idea, almost overdue

At Mazette.co, we juggle multiple brands, multiple clients, and sometimes several project phases within a single account on a daily basis. Needless to say, we had been waiting for this feature for quite a while.

What we particularly appreciate is the permission inheritance. On a client project with sub-brands or regional variations, being able to set access once at the parent folder level, then fine-tune it for a specific sensitive subfolder (a phase that is still confidential, for example), is exactly the level of granularity that was missing. Before, we had to piece things together with file-by-file sharing, which always ended up leaving gaps.

Folder color-coding might seem purely cosmetic at first glance. But on accounts juggling fifteen active projects at once, that kind of visual cue saves precious seconds every time you open Figma, and seconds multiplied by the number of designers on an account eventually add up.

One caveat though: the 10-level nesting limit, generous as it sounds, can also become a trap. Nothing stops a poorly disciplined team from building an endless tree structure, just as unreadable as a 2000s-era Windows file system. The feature gives you the tools to organize well, but it does not guarantee you will use them wisely. As always with Figma, governance remains a human matter before it is a tooling one.

Our recommendation for teams managing multiple accounts or brands: use this change as an opportunity to rethink your folder structure now, rather than simply recreating your old, poorly stacked Projects. This is the perfect moment to finally clean house.

If you work with Figma daily on web projects, this update fits into a broader trend: a tool maturing toward large-scale team workflows. Worth following alongside the developments around Figma Motion and the AI agents announced at Config 2026, which are also set to reshape how we collaborate within the tool.