Skip to main content
juniper
juniper
New Member
September 18, 2026
Question

Variables panel doesn't show some existing local variables (large collection, 1000+ variables)

  • September 18, 2026
  • 1 reply
  • 15 views

I have a local variable collection called "Shared Copy" with a single "Default" mode and around 1050+ STRING variables. Some variables in this collection are correctly present in the file's data model and correctly bound to text layers, but they don't appear in the Variables panel UI — even after fully closing and reopening the file.

Example: the variable copy/dashboard/upcoming_actions_banner/text (ID VariableID:32790:506500) is confirmed present via GET /v1/files/{file_key}/variables/local, which returns a valid entry with that ID and a non-empty string value. It's also resolvable via the Plugin API — a plugin using figma.variables.getLocalVariableCollectionsAsync() + getVariableByIdAsync() successfully finds and reads it, and confirms a text layer's boundVariables.characters.id correctly points to it. Despite this, the variable doesn't show up when searching for its exact name in the Variables panel, and isn't visible when browsing the relevant group in the panel tree.

I've already tried:

  • Fully closing and reopening the file
  • Searching for the exact variable name in the panel's search box
  • Collapsing and re-expanding the group it should be in

Since the same variable checks out correctly through two independent paths (REST API and Plugin API) — both agreeing on name, ID, value, and binding — this looks like a rendering/indexing bug in the Variables panel itself, not a data problem. It may be related to the collection's size, since it's grown past 1000 variables over the course of this project.

Has anyone else run into variables silently missing from the panel on a large collection like this? Any workarounds, or is this a known issue?

    1 reply

    adamsmasher
    Figmate
    adamsmasher
    Figmate
    September 19, 2026

    Thanks for documenting this so thoroughly, ​@juniper. I’m glad you can access the variable outside of the panel as that helps narrow this down to something more specific. It’s easy to see that this would be disruptive, though, since you can’t manage the variable through the panel at all. 

     

    We support up to 5000 variables in a collection (as noted in our Create a variable help article), so your collection is well within that limit and the overall number of them shouldn’t be an issue. The Variables panel should also be able to find a variable by its exact name, even if there was an issue with displaying more than a specific number.

     

    Since you can find the variable with both the REST and Plugin APIs, and an existing text layer remains correctly bound to the same variable ID, the underlying variable data appears intact. This does lead me to the same conclusion as you that it could be an indexing or display issue with the variables panel.

     

    Are you using the desktop app or a web browser? Do you see this happen in both, or just one? I’d like to make a ticket for you with our Technical Quality team, but I want to get a bit more info first so we have a clearer idea of the scope. Thanks!

    Terms & ConditionsAccessibility statement