Skip to main content
Question

Why remove multi‑file support in code layers in Figma Sites? Can we bring it back ?

  • January 9, 2026
  • 0 replies
  • 12 views

Ilakkiaselvan_Subbiah

I understand Figma Sites is still in beta and primarily aimed at design‑first, variables/CMS‑driven site generation. That said, it’s also clear that under the hood it uses a React‑based stack.

Removing multi‑file support in code layers makes the experience objectively worse. Large, single‑file components:

  • Reduce maintainability and code clarity
  • Degrade AI assistance performance as file size and line count grow
  • Go against basic, well‑understood best practices of keeping code modular and scoped

Keeping code split into reasonably sized files is a fundamental requirement when AI is expected to help users read, reason about, and modify code. Without this, even simple workflows break down, and Figma Sites becomes unusable in any meaningful way with Figma Make. This isn’t a power‑user edge case—it’s table stakes for AI‑assisted workflows.

Is the single‑file limitation a temporary beta constraint, or is there a planned, supported way to structure modular code in Figma Sites going forward?