Every designer who uses Figma has the file. It is called "Inspiration" or "Refs" or "Moodboards", it has been growing for two years, it takes fifteen seconds to open and it has crashed at least once during a client call. Somewhere in it is the exact reference you need, on one of forty pages, next to a sticky note that says "this". A Figma moodboard or Figma inspiration board that has grown too large is the most common reason a workspace feels slow, and knowing how to organize Figma files for inspiration fixes most of it.
Figma is a superb design tool and a poor database. If you are searching for how to organize Figma files because your inspiration file has become unusable, the honest answer is in two parts: organise what should stay in Figma, and move out what never belonged there.
Why the Figma inspiration board gets too slow and too large
Figma renders everything on the current page in the browser. A page with three hundred full-resolution screenshots is asking the browser to hold three hundred large images in memory and repaint them as you pan. It will slow down, then it will crash, and the point at which it does depends on your machine, not your discipline.
The second problem is quieter. Figma has no search for the content of images. You can find a frame by name, if you named it. You cannot find "the dark dashboard with the big number" because nothing in Figma knows the image contains a dashboard. The file gets bigger and less findable at the same time.
How to organize Figma files that stay in Figma
Some references belong in Figma: the ones a current project is actively using. For those, a few rules keep the file fast and legible.
- One file per project, not one for everything. The archive of every reference you have ever liked does not belong next to this quarter's work.
- One page per theme within the file. "Onboarding refs", "Pricing refs", "Type". Figma only renders the page you are on, so splitting by page is the single biggest speed fix.
- A note next to every image. One line in a text layer: what to look at and why. Without it, the reference means something different to everyone who opens the file.
- Compress before you paste. A screenshot straight from a Retina display is often four times larger than it needs to be. Resizing to the display width you actually need cuts file weight dramatically.
- Name the frames. "Stripe pricing table 2026" is findable with Figma's search. "Frame 2841" is not.
- Archive finished projects. Move the file to an archive team or project. It is still there. It is not slowing down today's work.
What should leave Figma entirely
The long-term collection, the one that spans every project and grows forever, should not live in a design tool. It needs three things Figma does not offer: search that understands the content of images, automatic organisation so you are not filing hundreds of items by hand, and a capture path from the browser that does not involve opening a heavy file to paste into.
That is what a reference manager is for. Everything you see, from any site or any Figma file, goes to one place with one click. It is read and tagged automatically. You search it by describing what you remember. When a new project starts, you search the library, pull twenty relevant references into a fresh Figma page, and the project file stays light.
GetRef is built for this and imports directly from Figma, which matters here: your existing inspiration file, all forty pages of it, can become a searchable library without re-saving each image by hand. We compared the alternatives, including Eagle and mymind, in Eagle vs mymind vs GetRef.
Moving the archive out without losing anything
- Duplicate the inspiration file first. Nothing below is destructive, but a copy costs nothing.
- Import the file into your reference library. With GetRef this is a direct import; with other tools, export the pages as images and bulk import.
- Let automatic tagging run over the whole set. Do not sort by hand first; sorting a backlog is the task that never gets done.
- Delete junk from inside the library, where you can see each image with its tags in context.
- Once the library holds everything and is searchable, archive the original Figma file. Keep it, just not open.
- Start the next project with an empty page and pull in only what it needs.
Keeping it that way
- New references go to the library first, from the browser, in one click. They only enter Figma when a project needs them.
- Project files hold references for that project. When the project ends, the file is archived.
- Once a quarter, delete anything in the library you would not show a client.
For the wider system, from capture to tags to pruning, see how to save design references. And if your Figma file is only half the problem because the other half is a screenshots folder, that has its own fix.
Common questions
- How to organize Figma files and inspiration boards?
- Keep inspiration in its own file, one page per project or theme, with a short note next to each image. Do not paste hundreds of full-resolution screenshots into one page; it slows the file and makes it unsearchable. For long-term reference collections, use a dedicated library outside Figma and pull into Figma only what a project needs.
- Why is my Figma inspiration file so slow?
- Almost always because of image weight. Hundreds of full-size screenshots on one page are heavy for the browser to render. Split by page, compress images, or move the archive out of Figma into a reference manager and keep only the current project in the file.
- Can I import my Figma inspiration into GetRef?
- Yes. GetRef imports images directly from Figma files, tags them automatically and keeps the source reference, so a crashing inspiration file can become a searchable library without re-saving each image by hand.
- Should I keep design references in Figma at all?
- Keep the references a current project actually uses in that project’s file. Keep the long-term collection outside Figma, in something searchable. Figma is a design tool, not a database, and it behaves like one when asked to store thousands of images.
