Skip to main content

Feature Request – Tags on Frames to Stay Sane in Large Projects

  • June 18, 2025
  • 1 reply
  • 19 views

Shakhlo Jumakulova

Hi Figma team,

I wanted to share a small pain point I keep running into — and maybe a solution.

As a UI/UX designer working on complex SaaS and mobile projects, I often end up with Figma files that have dozens of frames across multiple flows. Despite careful naming, it's easy to lose track of what’s ready for dev, what needs review, or which version belongs to which client.

Lately, I’ve found myself wishing I could just tag frames — like #ready, #needs-feedback, or #v1.2 — directly on the canvas or in the left sidebar.

Something lightweight, like sticky labels or even a built-in tagging system, would make navigating and collaborating inside Figma so much smoother.

Right now, I rely on naming hacks or color-coded backgrounds, but it gets messy — especially when the file grows.

I imagine a world where I could quickly filter or search for #mobile or #dashboard and instantly jump to relevant designs.

Thank you for building such a powerful tool already. I just thought this small improvement could make a big difference for those of us managing large design systems!

— Shakhlo Alisherova
UI/UX Designer

 

1 reply

StellaZ
  • New Member
  • January 12, 2026

Hi I am also having a problem with organising files within figma my main issue is introducing new features that affect multiple pages and platforms this is my suggestion:
 

Designers working on complex products often organize files by platform (web, mobile, portals), while features span across many pages and platforms. As features evolve, multiple features can impact the same page, making duplication risky and hard to maintain.

A native tagging system for pages and/or frames would solve this. Each page or frame could have multiple tags.

These tags could then:

  • Create an automatic feature-based table of contents, showing all pages affected by a feature

  • Allow searching and filtering designs by tag

  • Let teams track feature impact without duplicating pages or files

This would enable a single source of truth per page, while still offering a powerful feature-level view across platforms. It would greatly improve scalability, collaboration, and handoff clarity for large design systems.