Finding and exporting your Figma data

What it holds

Figma holds editable designs, prototypes, shared components and collaborative canvases. Comments and version snapshots add context but are not embedded in a current-state local file.

Where Figma shows the size

1. Join every relevant team and inspect each folder; Organization and Enterprise accounts can use All teams. Some interfaces still label folders Projects.
2. Count files and ask members to include work drafts, which are private by default.
3. For existing API integrations, GET /v1/teams/TEAM_ID/projects and GET /v1/projects/PROJECT_ID/files require projects:read; these legacy endpoints are deprecated in favor of folder endpoints.
4. Use Main menu > File > Save local copy on representative files. Multiply the average size by file count for an explicitly labeled GB estimate, or sum all downloaded files.

Plan and admin role. View access normally permits a local copy, unless copying/sharing is restricted. Cross-team administration is available on Organization and Enterprise, but private drafts still need member participation.

Exporting the full history

1. Confirm that copying is allowed, then open each file and use Main menu > File > Save local copy.
2. Collect the appropriate native extension: .fig, .jam, .deck, .buzz, .site or .make. There is no documented bulk native-file download.
3. For an earlier state, duplicate the chosen version from version history and download that duplicate separately.
4. Use GET /v1/images/FILE_KEY for frame renderings in JPG, PNG, SVG or PDF when visual output is also needed.

Local copies omit comments and version history. Reimporting creates an independent file whose components no longer receive updates from the original library.

REST file JSON and image rendering are not native .fig downloads. The legacy listing endpoints are Tier 2 and unavailable to public OAuth apps.

Keep file counts alongside size estimates: different design types can vary greatly in size. Native formats are proprietary and subject to change.

You don't need to run an export to talk to us, and there's no need to clean it first — removing personal data is part of our work.