Figma Layers Panel | Faster Performance for Complex Design Files

Figma has shared how it improved performance in the layers panel, one of the most important parts of the editor for navigating complex design files. The update focuses on new computation and caching strategies that make layer interactions faster, reduce unnecessary work, and help large files feel smoother during everyday design tasks.


Figma layers panel performance diagram showing frame conditions and dependencies

{getToc} $title={Table of Contents}

Figma improves layers panel performance for large design files


Figma has explained a major performance improvement to the layers panel, the part of the editor that shows design elements in a nested hierarchy. The company says the panel was originally built nearly seven years ago, when files were smaller and Figma had fewer features. Today, complex files can include tens of thousands of layers, making performance much harder to maintain.


The problem was not only inside the panel itself. According to Figma, sluggish layers panel interactions could also affect broader editor actions such as dragging, typing, and selecting colors. To address that, Figma rebuilt the layers panel architecture with new computation and caching strategies designed to reduce unnecessary work.



Why the layers panel became harder to optimize


The layers panel may look like a simple list, but it represents a large tree of nodes inside a Figma file. Each node can include properties such as name, visibility, lock state, selection state, icons, and children. In older architecture, Figma gathered a large amount of data for expanded nodes, even when only a small number of rows were visible on screen.


That created two main performance problems. First, the system computed too much information, including data for layers that users could not currently see. Second, it recomputed too often, because many changes required rebuilding large portions of the layers panel data from scratch.


Figma now uses a two-pass computation approach


To reduce unnecessary work, Figma split the layers panel data process into two passes. The first pass gets the ordered list of row IDs that make up the panel. The second pass computes detailed data only for the rows that matter, such as the rows visible in the current windowed view.


This matters because windowing only renders the list items visible on screen. The previous architecture used windowing for rendering, but it still gathered data for many layers outside the visible area. With the new approach, Figma can focus computation on a much smaller set of rows, which is especially useful in files with very large layer trees.


Caching derived data helps avoid repeated work


The second major change is a stronger caching strategy using derived properties. Figma explains that many node properties are computed from other fields, similar to how a spreadsheet formula depends on other cells. By modeling the layers panel structure through derived properties, Figma can update only the sections of the tree that actually changed.


For designers, the technical detail matters because it affects how responsive the editor feels. If expanding one frame no longer forces the entire tree to recompute, then large design systems, long pages, and complex product files can stay more stable during navigation and editing.


Memory usage was also part of the redesign


Figma also had to manage memory carefully. Caching can make interactions faster, but it can also increase memory usage if too much data is stored. The company says an early approach could have led to O(n²) memory usage in very deep trees, which would not be acceptable for large files.


To solve that, Figma used a recursive list approach similar to a rope data structure. This allowed the system to share structure instead of copying large sequences repeatedly. According to Figma, this reduced memory usage by up to 99% compared with the original prototype.


The result is faster interaction in complex files


Figma says the rebuilt layers panel makes critical interactions such as expanding and collapsing rows or toggling visibility and lock states nearly 30-50% faster in some of the largest and most complex files. The improvement also extends beyond the panel itself, helping the editor achieve higher FPS and fewer slow frames.


That is important for teams working with dense design systems, large product screens, many components, or detailed interface files. When the layers panel becomes faster, everyday actions like finding elements, organizing frames, hiding sections, locking objects, or selecting nested items can feel less frustrating.


IMPORTANT: Figma's reported 30-50% performance improvement applies to some of the largest and most complex files. Actual results may vary depending on file size, layer structure, device performance, browser conditions, and team workflow.{alertWarning}

Daisuki's Take: What This Means for Designers


This update is technical, but the design impact is very practical. Designers do not only need new features; they also need the workspace to stay responsive when projects become heavy. A faster layers panel can make large files feel easier to navigate, especially when teams are working with complex components or many nested frames.


The interesting part is that Figma is improving the hidden architecture behind everyday design actions. Expanding a layer, toggling visibility, dragging an object, or selecting a color may seem small, but those actions shape the feeling of the editor during real production work.


We see this as a quality-of-life improvement for serious Figma users. It may not look as flashy as a new AI feature or visual tool, but better performance can directly affect how fast designers think, organize, and iterate inside large design files.



Sources and Recommended Links