How Figma built AI-powered visual and semantic search
Designers at Figma and elsewhere were spending significant time searching for existing designs—tracking down source files from screenshots, navigating organizational structure, and asking teammates in Slack for help finding files. Finding designs between low-level component libraries and entire files was time-consuming and disruptive to creative flow.
Figma first built a design autocomplete feature as its primary AI initiative, adding it to the product roadmap after a hackathon, before internal research revealed that improved search was a more immediate and impactful need and autocomplete was deprioritized.
Figma launched AI-powered visual and semantic search at Config 2024, enabling designers to search using a screenshot, sketch, or natural-language text query, after months of scoping, testing, and iterative quality evaluation.
Frequently asked questions
What did this team achieve with this AI workflow?
Figma launched AI-powered visual and semantic search at Config 2024, enabling designers to search using a screenshot, sketch, or natural-language text query, after months of scoping, testing, and iterative quality eva…
What tools did this team use?
RAG, plugin API.
What results were reported?
Share of canvas objects sourced from other files: 75%; Slack messages seeking design files: hundreds of messages in Slack; development duration for AI search: months of scoping and testing (source-reported, not independently verified).
What failed first in this deployment?
Figma first built a design autocomplete feature as its primary AI initiative, adding it to the product roadmap after a hackathon, before internal research revealed that improved search was a more immediate and impactf…
How is this back office ops AI workflow structured?
Designer initiates AI search → RAG retrieves similar designs → Heuristics identify indexable UI frames → Edit-inactivity gate filters incomplete work → Eval plugin grades search quality → Search results delivered with previews.