Book a free 30-min call (opens Calendly)

10 min read

Who Owns the Figma Files? A Founder's Agency Handover Guide

Who owns the Figma files when your design agency leaves? What your contract decides, what a Figma transfer keeps, and a 10-step handover checklist.

  • Contracts
  • Agency handover

The engagement is over. You’ve paid the last invoice. You open the Figma link to brief your next designer, and two small words sit in the corner of the screen: “Can view”.

You paid for the work. You can’t edit a single frame of it.

Who owns the files is decided by your contract, and by the Figma account the files live in. Both are settled on the first day of the project, not the last. If the contract says nothing, the law usually sides with whoever made the work. This post shows what to put in your next contract, and what to ask for if you’re already holding a view-only link.

This post gives you:

  • what the law assumes when your contract says nothing, in the US, the UK and Poland
  • a three-layer check: the account, the files and the rights
  • what a Figma transfer keeps, and what the shortcuts lose
  • a 10-step handover checklist to work through before you tell the agency you’re leaving

It’s a founder’s checklist, not legal advice. Have your counsel read any contract before you sign it. If the engagement has already gone wrong, our page on what to do after a bad design agency covers the recovery.

Paying the invoice doesn’t make you the owner

Most founders assume that what they paid for is theirs. Copyright law starts from the other end.

In the US, work by an outside contractor only belongs to the client automatically in nine narrow categories, with a written agreement signed by both sides. Product design rarely fits. Anything else needs a signed, written transfer.

In the UK, the person who created the work owns it, the Intellectual Property Office says, “unless you otherwise agree it in writing”. Without that, a court may decide you only have a licence to use it.

In Poland, where we’re based, a transfer must be in writing and covers only the uses the contract lists. The designer’s moral rights, such as the right to be named as the author, can’t be transferred at all. Much of the EU works in a similar way.

So the work stays with the studio until a written transfer moves it to you. Many agencies hold on even harder to working files. Some published policy says they stay with the agency “unless ownership is specifically ceded in the client contract”.

The agency isn’t acting in bad faith. That’s the default by the law, and your contract is where you adjust it.

Approved screens are not the same as working files

This is the gap most founders fall into.

The contract usually names the deliverables: approved screens, a prototype, maybe a style guide. The working files are everything behind them. The layered Figma file, the component library, the colour and spacing tokens, the version history, the research recordings.

If your contract transfers “final deliverables” and stops there, you can own every approved screen and still have nothing your next designer can work in. A PDF of 60 screens is a record of the product, not a file you can build on.

Check all three layers

Ownership can fail in three separate places.

Layer What to check Where to look What to ask for
The account Whose Figma team or organisation the files sit in, who pays for it, who can delete it The team name above the file, and the admin settings Files moved into your own Figma account at handover
The files Editable files, component libraries, tokens, version history, comments, prototypes Open the library file and check your screens still link to it Product files and their libraries moved together
The rights A written copyright transfer, what it covers and when it takes effect The IP clause in your contract A clause that names working files, says when rights pass and lists what’s excluded

The first two are technical. The third is legal. A studio can give you an editable file without the rights, or the rights without a file you can use. You need both.

What a Figma transfer keeps

Figma’s help pages are specific about this, and the details matter at handover.

When admins on both sides transfer a folder between accounts, it keeps the files, prototypes, comments and version history. It also keeps any component libraries that go in the same transfer. A library left behind freezes: your screens keep the components as they were, and they stop updating.

Some things never travel. Shared fonts, private plugins and Community resources stay behind, so font licences are a separate conversation.

The two shortcuts lose more. “Send a copy” duplicates the files but leaves the comments and version history with the originals. A downloaded .fig file loses them too. Figma says a local copy doesn’t include “any version history or comments”, and when you import it, its components are cut off from the original library. Treat a .fig file as an archive, not a handover.

We’ve met missing files from both sides. We inherit them when we start work on a client’s existing files, and we can’t control that. We’ve also caused them. Sending a second zip with the assets you forgot, because the client had to ask for them, is embarrassing. So we now run a short checklist before any files leave the studio.

Payment-gated handover is fair, if it’s written down

Founders who have been burned may not like this, but most studios, ours included, hand over editable source files when the final invoice is paid. That’s reasonable. The studio carries the risk of unpaid work, and the files are its only security.

What isn’t reasonable is a contract that leaves you guessing. Before you sign with anyone, the contract should answer three questions:

  1. What transfers? Approved screens only, or the working files and libraries too?
  2. When? On each payment, on the final invoice, or “on completion”, which nobody can put a date on?
  3. In what form? Live files moved into your account, or exports?

If you can’t answer all three from the document in front of you, ask before you sign.

Our answers to the same three questions

During a project with Spirixx, you have view and comment access to the Figma files, and all design feedback goes through Figma comments.

Copyright in each sprint’s deliverables passes to you when that sprint is paid, for the uses listed in the contract. The editable Figma files are handed over when the final invoice clears. Explorations that didn’t make it into a delivered sprint stay with us, and the contract says so.

If either side ends the project early, you get everything completed up to that date once open invoices are settled. A sprint that’s already under way is billed in full. And the designers keep their moral rights, because Polish law doesn’t allow them to be transferred. We don’t pretend otherwise in the contract.

None of this is unusual. What matters is that it’s written down before the work starts, so the end of a project holds no surprises.

If you’re leaving an agency now

Work through this before you tell them. Some of it is much easier to get while the relationship is still friendly.

  • Match your invoices to the work each one paid for. That’s most likely what your contract transfers.
  • Check whose Figma account the files sit in. If it’s the agency’s, you’re a guest there.
  • Set up your own Figma team, then ask for a folder transfer into it, with the product files and the libraries in the same transfer.
  • Ask for the component library, styles and variables as live files, not exports.
  • Ask for the prototype links, and check they still open after the transfer.
  • Ask for research material: recordings, interview notes, survey data and the consent terms participants agreed to.
  • Ask for the copy documents and any spreadsheets the screens were built from.
  • Ask for icons, illustrations, photos and fonts, with their licence terms.
  • Ask for the decision log, or whatever records why things look the way they do. Without it, your next team re-argues every decision.
  • Get written confirmation of the copyright transfer for everything you’ve paid for.

If the agency refuses or goes quiet, the contract is what you have. Read what it transfers and on what condition, then talk to a lawyer before you escalate.

Is the old work worth keeping?

Once you have the files, the question becomes what in them still serves the product. Designli’s framework is a simple way to sort it: keep, fix, replace or retire each part, based on where the product is going rather than on what it cost. That sorting is its own job, and it’s usually the first thing we do when a founder comes to us after a bad engagement.

There’s an irony in choosing the next studio. A studio that respects confidentiality can’t show you its clients’ Figma files, so you can’t judge its handovers by looking at old work. When the portfolio is under NDA, the contract is the evidence. Read the IP, handover and termination clauses before the first sprint. How we handle confidentiality is on our NDA-first product design studio page, and our mutual NDA checklist for design work covers the clauses to ask for.

FAQ

Can an agency refuse to hand over source files?

Yes, if the contract doesn’t oblige it to, or if invoices are unpaid and the contract makes handover depend on payment. Without a written transfer, the creator keeps the copyright in the US, the UK and Poland.

What should the contract say about working files?

Name them: editable design files, component libraries, tokens and prototypes. Say when they transfer, and that they move into your Figma account rather than arriving as exports. If explorations stay with the studio, the contract should say that too.

Does a .fig export keep version history and comments?

No. Figma’s own documentation says a local copy includes neither, and imported components lose their link to the original library. A folder transfer between accounts keeps both.

Who owns work in progress if we stop mid-project?

That depends on two clauses, the IP clause and the termination clause, so read them together. Many contracts transfer only work that has been delivered and paid for. Some bill an interrupted sprint in full.

Before you book anything, spend ten minutes on three checks. Look at the corner of your own design file: does it say “Can edit”? Read the team name above the file. Then find the IP clause in your contract and see whether it names working files. If any of the three goes against you, start at step 1 of the checklist above.

If you already have the files and don’t know what in them is worth keeping, that’s the first thing we read. Book a free 30-min call, or see how we help on our page about starting over after a bad design agency. If you’d like, we’ll sign a mutual NDA before the call.


Sources

Have a product that needs a clearer path?

Bring the brief, the number that won’t move, or just a hunch. In 30 minutes we’ll work out where design can make the biggest difference.

Book a free 30-min call (opens Calendly)