Skip to main content
Pick inputs that match what you want Figr to understand. The closer the match, the less generic the output.
GoalUse these inputsBest for
Understand an existing productScreen recordings, Chrome extension, screenshots, Figma framesRedesigns, UX audits, existing product improvements
Follow your design systemFigma input, design files, component examples, tokensMatching visual language, creating Figma-ready outputs
Understand requirementsPRDs, docs, PDFs, pasted text, product briefsPRD-to-design workflows, feature planning, requirements review
Reason from user behaviorAnalytics, CSVs, support tickets, research notes, user feedbackFunnel improvement, activation flows, product discovery
Study a live page or competitorChrome extension, URL input, website capture, screenshotsLanding page analysis, competitor research, web app audits

Pick an input

Screen recordings

Teach Figr a flow that one screenshot cannot explain.

Chrome extension

Capture live product pages with structure, not just a flat image.

Figma input

Bring in components, layout, and variants from existing design work.

Files and Research

Use PRDs, CSVs, research, and web context that live outside the screen.