Find and export
your Figma data.

1. 1Use an account with access to all required team folders, projects and business drafts.
2. 2Count the relevant files in those locations, checking for duplicates or shared-library copies.
3. 3Open representative files and choose Main menu → File → Save local copy.
4. 4Measure the copies in GB. If estimating, report the sample sizes and file count used in the calculation.

Report in files, listing the product types and folder scope. Add measured local-copy storage in GB, or a documented size estimate, if available.

Give the earliest retained designs and users represented. Identify required comments or older versions separately.

1. 1Open each accessible file and use Save local copy for its native file representation.
2. 2Collect rendered frames where required using the supported image or PDF export.
3. 3For earlier design states, review version history and save the agreed versions through the supported controls.
4. 4Use a file list or API inventory to track completion across a large account.

Figma says a local copy excludes comments and version history. Those need a separate plan when relevant.

A REST API file representation and a native local-copy file are different exports. Check which representation the dataset requires.

Design files can show how screens, components and flows fit together.

Selected revisions and related discussion can provide context about how a team develops and evaluates an interface.

Choose business files and versions in scope, reviewing client rights, private drafts and licensed design assets.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.