Importing

Paste a prototype link (or just the file key) and urTRACE rebuilds your design as a live, scalable reconstruction: real elements, real text in the real fonts, real image fills - not a stack of screenshots. Scrolling pages come across with their sticky sections and pinned navigation behaving like the real thing.

• Connect once. Link your Figma account in Settings and importing is one paste - no tokens. A personal access token also works under "Advanced".
• Re-import any time. Importing the same file again refreshes it in place. Tests keep working as long as their goal screen still exists, and storage from removed screens is reclaimed automatically.
• Fallbacks are built in. Every screen also imports a flat screenshot; anything the reconstruction can't rebuild falls back to it gracefully.

What carries over - and what doesn't

Navigation (On tap → Navigate to, overlays, Back/Close, scroll-to), component variants (Change to - on click and on hover), sticky sections and pinned navigation, layouts, text in its real fonts, and image fills (including crops) all come across and work for testers. A few things can't, because Figma's API doesn't hand them over:

• Logic built on Figma Variables - conditionals, counters, typed text - is never exposed by the API. urTRACE Variables and Paths exist to replace it.
• Drag interactions and smart-animate transitions aren't exposed either; clicks and taps are what testers use.
• Component sets from an external published library can't swap states - the variants live in a file the import can't reach. Moving or duplicating the component set into the prototype's own file (then re-importing) makes them work.
• A few interaction triggers don't fire during a test: hover-triggered whole-screen navigation, key/gamepad presses, after-delay auto-advance, and Open-URL link-outs (deliberately blocked so testers stay inside the prototype).
• Some visuals are approximated: proprietary fonts (anything outside the free Google catalog) render in a fallback font, radial/angular gradients flatten to their first color, and mixed styling inside one text block uses its base style.

You never have to guess which of these your file hit: after every import, the report on the prototype's card lists exactly what won't work and why, and scores each screen's reconstruction fidelity against Figma's own render. And where telemetry can't reach - a live-embed test's missing movement heatmaps especially - a per-test screen recording (optional, desktop browsers, with the tester's explicit permission) can supply the movement evidence as video.