Skip to main content

Wild take: Figma needs page types, not separate file types for everything

  • July 27, 2026
  • 1 reply
  • 14 views

Metin Saray

I think It’d be much better if Figma to stop treating its products (FigJam, Slides, Buzz, Site, Make) as separate file types and start treating them as page types within a single file.

Every time Figma releases a new tool, it forces us into another siloed file type. If I’m working on a product feature, I shouldn't need one file for research and flows (FigJam), one for Exploration (Design), one for presenting to stakeholders (Slides), and another for campaign assets (Buzz).

It breaks context and creates insane file sprawl for what is ultimately a single project.

If these were all just specialized page types inside a single master file, everything would live under one roof:

  • Page 1 (FigJam): Research & User Flows

  • Page 2 (Design): High-Fi Mockups & UI Systems

  • Page 3 (Slides): Stakeholder Deck

  • Page 4 (Site / Buzz): Landing Pages & Marketing

I know this clashes directly with Figma's tier/seat pricing model for different products, but purely from a UX and workflow perspective, moving from file-level to page-level separation would be a massive upgrade.

Not sure if this echoes with anyone, but I just really dislike the process of creating an empty FigJam file to make a user flow diagram, copy-pasting it over to my design file, and then having to keep that original FigJam file around forever just in case I need to edit it later. It creates insane file sprawl and feels like a very fragmented experience.

 

Let me know your thoughts

1 reply

Apolline
  • Active Member
  • July 27, 2026

FigJam and Figma especially would benefit from working in the same file, at least with my workflow