Which Figma File Types Can You Back Up? (Sites, Slides & More)

Not all Figma file types can be backed up, and that surprises many teams. Figma’s platform now includes several products beyond classic design files, such as Sites, Slides, and Buzz. However, Figma’s public API only provides access to some of them. In this guide, we explain which Figma file types you can back up, which ones you can’t, and what our backup tool does when it finds an unsupported file.

Figma file types you can back up

Our Figma backup tool retrieves your files through Figma’s official REST API. Everything the API exposes can be backed up automatically on a schedule. Today, that includes:

• Figma design files: your regular UI and product design files, including all pages and frames.
• Branches: if your plan uses branching, we back those up too. Read more in our post on branch support.

For these files, every backup run stores a new version. As a result, you can restore or download any earlier state of your work at any time.

File types Figma’s API does not support

Some newer Figma products are not available through the Figma REST API. When a tool requests one of these files, Figma answers with the error “File type not supported by this endpoint”. The affected Figma file types currently include:

• Figma Sites: published websites built in Figma.
• Figma Slides: presentation decks.
• Figma Buzz: brand asset and template files.
• Figma Make: AI-built prototypes and apps.
• FigJam boards: Figma marks whiteboard files as not exportable through the API, so they cannot be backed up either.

Because Figma does not expose the content of these files, no backup tool on the market can export them. This is a limitation of Figma’s platform, not of any specific product. If Figma adds API support for these formats in the future, our tool will pick them up automatically.

What our backup tool does with unsupported files

Previously, an unsupported file simply failed on every backup run with a generic error. That was confusing, so we improved it. Now, the tool detects the file type behind a failure and reacts accordingly:

• The file is clearly marked in your dashboard with the reason, for example “This is a Figma Sites file”.
• We stop retrying it, so your backup history stays clean and you receive no repeated failure emails.
• If Figma ever adds support, backups resume automatically without any action on your side.

In other words, an unsupported file never blocks or pollutes the rest of your backups. All your regular design files continue to back up on schedule.

What about files deleted from Figma?

A related case is a file that no longer exists on Figma. Perhaps it was deleted, or your access was removed. In that situation, we also stop scheduling new backups for it. Importantly, your existing backup versions remain stored and downloadable. After all, a deleted source file is exactly the moment a backup matters most. You can remove the file from your backup list whenever you like, or hit Retry if your access has been restored.

What you can do with unsupported files

Although automated backups are not possible for Sites, Slides, Buzz, and Make files, you still have some manual options. For instance, Figma Slides lets you export a deck as PDF from inside the editor, and FigJam boards can be exported manually as PDF or images from the FigJam editor. Similarly, Figma Sites content can be duplicated within your Figma workspace as a safety copy. For everything else, we recommend keeping the source material of those files in your regular design files, which are fully covered by backups.

Questions?

If you see an unsupported file type in your dashboard and are unsure what it means, reach out to our support team via the chat on backup.magicul.io. We are happy to check your specific files.