How to Copy Figma Files to Another Account Easily

html

There is no send to another account button in Figma. People go looking for one, don’t find it, and assume they’re missing a menu somewhere. What actually exists is a handful of routes that get a file from one login into another, and the right one depends on your plan, your seat, and who currently holds ownership.

Client handoffs are the usual reason. Also: folding a personal login into a company account, or pulling work out of an old account you can no longer get into.

One number worth knowing before any of this. Starter plan accounts can only view 30 days of a file’s version history, while Professional and Education accounts retain the complete record (Figma Help Center, 2026). If the file you’re moving has history you care about, your plan may already have thrown most of it away.

What Is a Figma File Transfer?

Ownership and edit history move together, out of one account and into a completely separate one. The two accounts share nothing beforehand. Not a team, not a workspace, not a billing plan.

It applies to Figma Design files most of the time, though FigJam boards and Figma Slides decks follow the same rules.

Dragging a file into a different folder inside your own team is not a transfer. That’s a move, and Figma treats the two as unrelated operations with different requirements.

What Is the Difference Between Moving, Duplicating, and Transferring Ownership?

People use these words interchangeably. Figma doesn’t.

• A move relocates a file to a different folder or team, still inside the same account structure.
• A duplicate creates a second, independent copy with no link back to the original.
• Transferring ownership hands administrative control to someone else, while the file stays exactly where it lives.

Ownership can only go to someone who is already a collaborator on the file, so the recipient needs an invite before any handoff happens.

On its own, none of these gets a file into a separate account. Copying a file across usually means chaining two together, which is why the step-by-step methods below get specific about the order.

Why Can’t Figma Files Move Directly Between Accounts?

Files live inside teams. Teams live inside accounts. There’s no pointer that lets a file hop from one account’s structure into another’s.

Ownership, billing, and access permissions all attach to the account rather than to the file. Billing seats are assigned per account, team membership doesn’t cross account boundaries, and file permissions are inherited from the team rather than carried by the file itself.

Moving a file between folders in the same team never changes the account context, which is why that operation feels instant and this one doesn’t. Every method below works around the account structure instead of moving through it.

What Happens to Version History, Comments, and Library Links After a Transfer?

What survives depends on the method, not the file.

Starter plan accounts can only view 30 days of a file’s version history, while Professional and Education accounts can access the entire record (Figma Help Center). Exported .fig files carry over zero permissions, comments, or version history from the original file (Figma Help Center).

Version History

Transferring ownership outright keeps version history intact, because the file never leaves its original record. Duplicating breaks that record. Figma treats a duplicate as a brand-new file, and history does not come with it. Same for export and reimport.

If old iterations matter to anyone, capture what you need before you duplicate or export. There’s no way back afterward.

Comments and Activity

Comment threads and activity logs travel only on a direct ownership transfer.

Everything else resets. The copy that lands in the destination account starts with an empty comment thread, which stings most on client handoffs where the feedback history doubles as an approval trail.

Team Library Connections

Library links break. Every method, every time.

Local file structure comes through fine. Layers, frames, and however you’ve set up auto layout all arrive exactly as built.

The live connection to a shared library is what dies. Styles and components pulled from a team library stop receiving updates the moment the file sits in a different account, so it’s worth reviewing how components are structured before moving anything that leans on one.

• Colors and text styles freeze at whatever state they were in when the transfer happened
• Components stop syncing with the source library
• Nothing looks broken, which is the problem. The disconnect only shows up the next time someone updates the library and the file ignores it

Which Method Should You Use to Copy a Figma File to Another Account?

Three routes work. All of them start inside the Figma web or desktop app, though a folder or team transfer only finishes once an admin on the receiving side accepts it.

Figma’s documentation is clear that transferring a folder to a different account only requires the receiving account to be on a paid plan (Professional, Organization, or Enterprise). The sending account can be on anything, Starter included. A full team transfer tightens the receiving side to Organization or Enterprise.

Duplicate and share is the fastest, with no export step. Skip the duplicate and transfer ownership directly and you keep comments and version history. The catch is that the recipient has to already have access to the original file.

Saving a local copy and importing it works even when the recipient has no prior access at all, which is sometimes the only thing that matters. It strips permissions, comments, and version history, and it kills any team library sync.

A folder or team transfer moves many files at once and keeps the folder structure. The receiving account needs a paid plan, and only team or organization Admins can start one.

What Do You Need Before Transferring a Figma File?

A few requirements sit underneath all of this, and checking them first saves a round trip.

You need at least Editor or Owner access on the file whose ownership you’re transferring, though View access alone is enough to duplicate a copy. The recipient has to already be a collaborator, since Figma won’t hand ownership to a stranger. If you’re moving a folder or team, the receiving account needs a paid plan, while the sending account can be on Starter. And the receiving account needs the right seat type, because seat type decides what the person can actually do once the file lands.

Permission Level Required

View access is enough to duplicate a file into your own drafts. Figma only requires can-view permission for that, which surprises people who assume duplication is an editor thing.

Editors can duplicate, share, and invite collaborators. Only the file’s Owner can start an ownership transfer. Moving a folder or an entire team to a separate account goes further still and requires Admin on that team or organization, which is a different role from file Owner.

• Viewer can duplicate the file to their own drafts
• Editor can duplicate, share, and invite collaborators
• Owner can transfer ownership and delete the file entirely
• Admin can transfer a whole folder or team to a different account

Getting bumped to Editor, or handed an Admin role, usually needs a current admin to approve it on team plans.

Plan and Seat Requirements

On March 11, 2025, Figma restructured billing around four seat types: Full, Dev, Collab, and View.

• Full seat gives full editing rights across every Figma product, including Figma Design, Dev Mode, FigJam, Figma Slides, Figma Draw, Figma Sites, and Figma Buzz
• Dev seat gives full Dev Mode access plus full editing in FigJam, Slides, and Buzz. Only Figma Design itself is limited to view and comment
• Collab seat also gives full editing in FigJam, Slides, and Buzz, with view-and-comment access in Figma Design and basic inspection in Dev Mode
• View seat is read-only and free on every plan

That same update folded FigJam and Figma Slides access into every paid seat, so a receiving account only has one seat decision to make rather than several.

Free accounts can still duplicate and share individual files, and they can send a folder or team transfer request. Receiving one is the wall. That’s the line most people trip over when weighing Figma’s free plan against its paid tiers.

When Does Copying a Figma File to Another Account Not Work?

Failed transfers usually come down to access or to plan limits.

Permission and Ownership Limits

Ownership cannot go to someone who isn’t already a collaborator on the file. Figma requires that relationship first, with no exceptions.

• The recipient has never been invited to the file
• You only have view or comment access, including on a Collab seat, rather than Owner or Editor
• The actual Owner left the team and nobody reassigned the file

One risk is permanent and worth stating plainly. Figma’s help documentation notes that deleting the source account also deletes everything sitting in that account’s Drafts folder, no matter who technically owns each file.

Plan and Product Limits

Free accounts hit the ceiling as soon as a transfer involves more than one file.

According to Figma’s Help Center, a folder transfer can be received by any paid plan, meaning Professional, Organization, or Enterprise. A full team transfer can only be received by an Organization or Enterprise account. Nothing restricts the sending side.

• Starter accounts can duplicate and share files, and can send a folder or team transfer out
• The receiving account can’t be on Starter for either one
• Team-level transfers specifically need Organization or Enterprise on the receiving end

This is why the comparison table above splits single-file moves from whole-folder moves. The plan requirement changes depending on which you’re doing.

How to Duplicate a Figma File and Share It With Another Account

Use this when the person on the other account already has a link, or when inviting them directly is fine.

Worth repeating, because it’s the part people get wrong: comments and version history survive only when you transfer ownership of the original. Duplicate first and Figma treats the copy as a new file, so the record starts over from nothing.

1. Open the file and click Share in the toolbar, or right-click it in the file browser and select Share.
2. Enter the destination account’s email address to invite them.
3. Set their permission to Editor. Figma won’t let you jump straight to Owner.
4. Wait for them to accept the invite, then reopen the share modal.
5. Click their permission dropdown, select Owner, then confirm with Transfer ownership.

Skip the duplicate step altogether if the version history matters more to you than keeping a personal copy.

Sharing Directly vs Publishing to Community

Direct sharing sends the file, or a duplicate of it, to one account you pick.

Community publishing is a different thing. Anyone with a Figma account can grab a copy, and Figma’s documentation confirms that duplicated Community files arrive as a new copy without updates, version history, or comments from the original.

Duplicated Community files also get “(Community)” appended to the file name automatically. Handy for spotting one in a crowded Drafts folder.

Direct sharing when you know who needs it. Community when the file is a template meant for anyone.

Someone who just needs to look at a prototype and leave comments doesn’t need a Figma account at all, since Figma supports sharing a prototype without an account. That route carries no ownership, so it isn’t a transfer.

How to Save a Local Copy and Import It Into a Different Account

The file never leaves your computer, which makes this the only option when the recipient can’t be added as a collaborator.

Exporting the .fig File

1. Open the file in Figma.
2. Click the file name menu, then choose Save local copy or Export, depending on where the file lives.
3. Select the .fig format and save it to your computer.

Figma will also export a file to PDF, but that’s a static snapshot for sharing rather than an editable file for moving between accounts.

Importing Into the New Account

Log into the destination account first. Importing while signed into the wrong account is the mistake almost everyone makes at least once.

1. From the Drafts or folder view, click Import file.
2. Select the .fig file from your computer, or drag it onto the page.
3. Wait for Figma to upload and convert it.
4. Open the imported file and confirm everything looks right.

On the desktop app, dragging the file straight onto the Drafts page tends to work better than double-clicking it from your file system. That pattern shows up repeatedly on Figma’s community forum.

How to Transfer an Entire Folder or Team to a Different Account

This is the bulk method. Figma renamed “Projects” to “Folders” in an update that began rolling out on August 3, 2026, so older tutorials and your own muscle memory may both still say Projects.

Only Admins can start one. Any plan can send. The receiving account needs a paid plan, meaning Professional, Organization, or Enterprise for a folder, and specifically Organization or Enterprise for a full team.

Transferring a Folder

1. Move every file you want included into a single folder first.
2. Ask an admin on the destination team or organization for their destination URL. They’ll find it under All folders, All teams, or All workspaces, depending on their plan.
3. On the sending side, open the folder, click the dropdown next to its name, and select Settings, then Transfer.
4. Enter the destination URL along with your contact’s email address, then click Request transfer.

Figma emails the admins on the receiving side to accept, and they decide whether to keep the folder’s existing collaborators or strip everyone except themselves. Treat it as one-way. Undoing it means the new owner starting a fresh transfer back to you.

Transferring a Team

1. Ask an admin at the destination organization for their destination URL, found under All teams or All workspaces.
2. On the sending side, open the team page, click the dropdown next to the team name, and select View settings.
3. In the Transfer section, click Transfer team to an external organization.
4. Enter the destination URL and your contact’s email address, then click Request transfer.

The destination organization’s admins get an email to review and accept. Members either keep an existing paid seat on the receiving side or land with a free View seat, depending on the plan being transferred.

If the original owner is gone and nobody can log in as them, Figma support describes two paths: recover the account by regaining access to the original owner’s email address, or go through Figma’s identity-verification process to have the account’s email changed to one you control. Neither is fast.

How to Keep Team Library Connections Intact When Moving a File

Sequencing is the whole fix. There’s no setting for this. Move the library before you move anything that depends on it.

• Transfer the library file itself into the destination account first
• Then move the files that reference its styles and components
• Re-publish the library from its new home so the destination team can subscribe

According to Figma’s support team, a shared library and the files built on it need to move together in a single transfer. Split them and whatever gets left behind stops receiving library updates.

Before any of that, it helps to look at how components pull from a library, since that dependency is exactly what snaps when the order gets skipped.

Check the library’s “used by” count first. It tells you how many files need to travel with it, which beats discovering the answer three weeks later.

Common Figma Transfer Errors and How to Fix Them

Most problems trace back to who has access, or to what the file is trying to sync with.

Permission Errors

The Transfer ownership option simply isn’t there. That’s the one people report most.

• The recipient hasn’t accepted the invite yet
• You have Editor or Admin access, but you aren’t the actual Owner
• You’re trying to transfer a team rather than a file, and you’re on the wrong settings page

Figma’s community support team has confirmed that being an Admin or an Editor on a resource does not grant the ability to transfer it. Owner only.

Broken Library or Style Links

Styles or components showing up grey, detached, or flagged as missing almost always mean a library that didn’t travel with the file. Move the library into the destination account, re-link the file to it, and leave everything else alone until that’s done.

An “Unsupported file format” error during import is unrelated to libraries. That’s usually a corrupted export. Figma’s support team has confirmed it happens even to files that opened fine right before exporting, and the advice is to re-export from the original rather than troubleshoot the broken copy.

FAQ on How To Copy Figma Files To Another Account

Can FigJam Boards and Figma Slides Decks Be Copied the Same Way as Design Files?

FigJam files follow the same rules as Design files for sharing, duplicating, and transferring ownership. Publishing a Slides template to Community needs a paid plan, while Design and FigJam files publish to Community on any plan.

Does the New Owner Need to Accept a File Transfer?

They accept the initial collaborator invite, not the ownership change itself. Once they hold Editor access, the current Owner switches their role to Owner and confirms Transfer ownership, with no separate approval on the recipient’s side.

How Do You Move Files Out of a Figma Education Account After Graduation?

Figma’s support team confirms an Education account itself cannot transfer to another account. Move the files into a team folder and transfer that folder, or export each file as a .fig file and import it into your personal account.

What Do You Do If You’ve Lost Access to the Email on Your Old Figma Account?

Figma support can help through a documented recovery request, though it’s slower without the original inbox. On an Organization or Enterprise plan, an admin can often reach a departed member’s Drafts straight from the Admin panel and skip the old email entirely.

Can You Copy Just Specific Frames or Pages Instead of the Whole File?

Select the frames or layers, copy them, then paste into a file open under the destination account. This works between any two accounts with edit access, skipping ownership transfer, though only the content moves. Comments and version history stay behind.

What Should You Check First When a Figma File Transfer to Another Account Fails?

Start with the recipient. Are they already a collaborator on the file? If yes, look at the receiving account and confirm it’s on a paid plan. If that checks out too, the answer is almost always the team library, and whether it moved before the files that depend on it.

• Recipient already added as a collaborator
• Paid plan confirmed on the receiving account
• Team library moved before the dependent files

Running that order takes a few minutes. Skipping straight to the transfer button is what turns a five-minute move into a support ticket that sits open for a week.

Once the file is confirmed safe in its new account, the next job is usually getting it ready for engineering, which is where handing a design off to developers picks up.