back_office_ops · saas · workflow

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.

How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Designer initiates AI search
A designer initiates a search using a screenshot, selected frame, quick sketch, or text-based query.
Tools used
RAGplugin API
Outcome

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.

What failed first

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.

Results
Volume75%
Running sinceConfig 2024
Source

https://www.figma.com/blog/how-we-built-ai-search-in-figma/

How we source this →

Grounding & classification
Source type: technical build writeup
22 fields verified against source quotes.
computer visionenterprise searchknowledge searchragknowledge basefailure mode describedhuman review describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwareemployee productivitytechnical build writeupback office opsrag answering