Client Wants Your Source Files: Should You Hand Them Over?

Short answer: no, not unless you signed something that says so — and you may still want to. In the US, copyright in commissioned work stays with the freelancer absent a signed transfer. But ownership isn't the real question. The real question is what the client can do without you afterwards.

A small business owner put the ugly version of this on r/smallbusiness: I got screwed by a client which now wants the source files. A designer on Stack Exchange described a repeat client suddenly demanding intellectual property rights after years of work, and noted the detail that decides most of these fights: "We have never had a contract."

Key Takeaways

• No US law makes you hand over source files; absent a signed writing, you own them.
• "Work made for hire" covers only nine listed categories — logos, sites and code aren't among them.
• The Guanzi records a state that sold its output at a great price and lost everything.
• Sell the deliverable, licence the use, price source files separately.

Do you legally have to hand over the source files?

No. In the US, a transfer of copyright has to be written down and signed. Section 204(a) of the Copyright Act is blunt about it: a transfer "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed."

Most freelancers assume that being paid settles it. It doesn't. In Community for Creative Non-Violence v. Reid, decided 5 June 1989, a unanimous Supreme Court held that the sculptor Reid "was an independent contractor rather than a § 101(1) 'employee'" — so the organisation that commissioned and paid for the sculpture did not automatically own the copyright in it.

The same logic reaches the source files themselves. Writing for AIGA Los Angeles in October 2013, Jonathan Tobin put it in one line: "As the creator of the source files, you are the owner of those files."

Citation capsule: Under 17 U.S.C. § 204(a) a transfer of US copyright ownership is invalid unless it's in writing and signed by the owner. Payment alone transfers nothing. CCNV v. Reid (1989) confirmed that an independent contractor, not the commissioning party, is the author of a commissioned work absent such a writing.

One caveat, and it matters: this is US law, and it's a description, not advice. Contracts you've already signed, work you did as an employee, and laws outside the US all change the answer. Ask a lawyer about your actual paperwork.

What did the client actually buy?

They bought an output. A source file — the layered original you actually edit, the repo, the working project — is what produces outputs. Those aren't the same purchase, and almost every argument about this starts because nobody said which one was on the invoice.

Consider what each side pictures. The client paid for a logo and assumes that includes "the logo." You delivered an exported file and think of the layered original as your workshop. Both readings are reasonable, and neither was written down.

So stop arguing about who owns the file. Ask the question with consequences: after this handover, can the client make the next version without you? Sometimes the honest answer is yes, and that's fine. Sometimes it's yes, and that was the point of asking.

What did the Guanzi say about selling what makes the work?

It told the story as a weapon. In the Guanzi's Qingzhong Wu chapter, Duke Huan asks how to bring the state of Hengshan under control. Guan Zhong's answer is to buy its tools at a high price and let other states bid the price up tenfold.

It works. 「衡山之民釋其本，脩械器之巧」— the people of Hengshan abandoned their base and perfected the craft of making implements. Qi then bought up grain elsewhere at a premium, closed the border, and stopped buying. Hengshan's implements were gone, its fields untended: 「內自量無械器以應二敵，即奉國而歸齊矣」— reckoning it had nothing left to meet two enemies, it handed over the state.

Notice what was never the problem. Hengshan was paid, and paid well. The high price wasn't the reward. It was the weapon. The same chapter records Qi doing this to the state of Dai with white fox pelts, and the line is 「齊未亡一錢幣，脩使三年而代服」: Qi didn't lose a single coin, and in three years Dai submitted.

Citation capsule: The Guanzi's Qingzhong Wu chapter records Qi destroying Hengshan by overpaying for its implements until "the people of Hengshan abandoned their base." The lesson is not that selling output is dangerous. It's that a very good price is exactly what it feels like when someone is buying your capacity rather than your goods.

Read it as a seller and you notice something uncomfortable: this is a manual written from the buyer's side. Guan Zhong isn't warning Hengshan. He's advising the state doing it. Our comparison of the Guanzi and Keynes covers the same 輕重 chapters as economic policy; here they read more like a guide to your own weak spot.

Why doesn't "put it in the contract" settle this?

Because the clause most people write doesn't do what they think. Section 101 of the Copyright Act lets a commissioned work be a "work made for hire" only if it's used as one of nine things: a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas.

Read that list again. Logos aren't on it. Websites aren't on it. Software isn't on it. Brand identities, photographs, illustrations — none of them. The US Copyright Office's Circular 30 states the requirement directly: a commissioned work qualifies only if "the work must fall within one of the nine categories of works listed above."

So a contract that says "all work is a work made for hire" and stops there may be doing nothing at all for a logo. What a client usually needs instead is an assignment — a signed transfer under § 204(a). What a court does with a mislabeled clause is contested, and it varies by state. That's the kind of gap you don't want to find mid-argument.

That's also why the Stack Exchange poster's "we have never had a contract" is less unusual than it sounds. Plenty of people who do have contracts have one that's silent on source files.

The four things a client might mean by "the files"

Separating them is most of the fix. Once they're four separate lines, the conversation stops being about trust and starts being about scope — the same move that makes telling a client something is out of scope survivable.

What's on the table	What it is	What the client can do next	Default owner, absent a signed writing (US)
Final deliverable	The exported PDF, PNG, built site, compiled app	Use it as delivered	Client owns the copy; you hold the copyright
Licence	Written permission to use, with a defined scope	Use it in the agreed places	You — you're granting, not selling
Source files	Layered originals, .fig, .psd, repo, working project	Edit it, hand it to anyone, reproduce your method	You, as their creator
Copyright assignment	A signed transfer of the rights themselves	Everything, including reselling	Client only once signed under § 204(a)

Most clients asking for "the files" want row one or row two and have used the wrong word. A few want row three. Knowing which you're being asked for takes one question.

When should you hand the files over anyway?

Often. If a client will maintain the thing themselves — a site they host, a deck their team updates weekly — withholding the source files makes you an obstacle rather than a supplier, and word travels.

There's a harder version of this, and it cuts toward you. If the only reason a client stays is that you hold the files, you've replaced your base with a lock. That's Hengshan's mistake running in reverse: 釋其本 means abandoning what you actually stand on. Skill, judgment, and knowing the client's business are a base. A file nobody else can open is not a base, it's a hostage, and hostages get worked around.

So the test isn't "will they be able to continue without me?" It's narrower: is this file my only advantage? If your edge is a reusable component library you built over five years, that's your 本 and it shouldn't leave in a project handover. If your edge is that you're good at this, a .fig file transfers almost nothing. Hand it over and charge for it.

Citation capsule: The Guanzi's Hengshan case turns on 釋其本 — abandoning one's base — not on the act of selling. Applied to freelance work, the danger of releasing source files depends entirely on whether the file is the advantage. Where the edge is judgment and knowing the client's business, a source file hands over a tool they still can't use well.

The reverse risk is real too. A freelancer whose retention rests on one locked file usually has a second problem: one client making up most of the income.

How do you word the handover without a fight?

Name it before you're asked. Four moves, in order:

1. List deliverables in the proposal by file type. "Deliverables: final logo as SVG, PNG, PDF. Working Illustrator files available separately." One line, before any work starts.
2. Price the source files as their own item. Not a punishment and not a favour — a different thing being sold. If that's a rate change for an existing client, raising prices without losing the customer is its own conversation.
3. If you're transferring rights, do it properly. A signed assignment, not a vague "work for hire" line. Say which files and which rights.
4. Keep your reusable toolkit out of it. Your own components, scripts, presets and snippets are the base you use on every job. Licence them if you must. Don't assign them.

The fourth is the operative rule, and it's the one the Guanzi would actually insist on: never sell the thing you use on every job, no matter how good the price is. Whether you're billing hourly or a flat fee changes nothing about that.

This sits next to two problems it's constantly confused with. All three feel like a difficult client. All three are actually a missing definition, and each needs a different one.

The request	What's really missing	What fixes it
"Just one more small change"	A finish line — see when the work is done	A completion standard agreed before the work
"Could you also add…"	A boundary — see out-of-scope requests	A price for the new work
"Send me the source files"	A list of what was sold	Named deliverables, plus source priced separately

Being firmer in the moment fixes none of them.

Where the Hengshan analogy stops

The Guanzi is describing economic warfare between states, and Guan Zhong is advising the aggressor. Your client is almost never running a campaign against you. They asked because their new agency asked them, or because depending on one person makes them nervous.

Import the analysis, not the posture. Treating every source-file request as an attack is how a good client becomes an ex-client. If the relationship has already broken down, that's a different problem — and an unpaid invoice comes first.

Want to argue it out with Guan Zhong directly? Ask Guanzi about your own handover, or read more about what the Guanzi actually covers.

FAQ

Do I have to give my client the source files?

Not unless your contract says so. In the US, copyright transfers require a signed writing under 17 U.S.C. § 204(a), and source files you created are yours as their author. You can choose to hand them over — usually as a separately priced item.

Does paying for design work transfer the copyright?

No. Payment buys the deliverable, not the rights. CCNV v. Reid (1989) held unanimously that an independent contractor, not the commissioning party, is the author of a commissioned work. A signed assignment is what moves copyright, not an invoice marked paid.

Can a contract make my logo a "work made for hire"?

Probably not by itself. Section 101 limits commissioned works made for hire to nine categories, and logos, websites and software aren't among them. Copyright Office Circular 30 confirms a commissioned work "must fall within one of the nine categories." An assignment is the usual route instead.

How much should I charge for source files?

There's no standard rate, and anyone quoting one is guessing. Price it against what the client gains: the ability to reproduce the work without you. That's closer to a licensing decision than an hourly one, and it belongs in the proposal, not in the argument.

Should I ever refuse outright?

Rarely, and only to protect reusable tooling you use across clients — your own component library, scripts or presets. Refusing to release a one-off project file mostly signals that the file is your only hold on the account. That's a weaker position than it feels like.

Sources and a note on the text

The Chinese text of 《管子·輕重戊》 was taken from Chinese Wikisource and checked character by character against the passage quoted; the English renderings are mine. The chapter survives as a set of dialogues of uncertain date, compiled well after Guan Zhong's death around 645 BC — the Guanzi is a collection assembled under his name, not a book he wrote, and the economic chapters are generally treated as the latest layer. Nothing in the argument here depends on the attribution being personal.

Legal material is US federal law, described rather than advised:

• 17 U.S.C. § 101, definition of "work made for hire" — Cornell LII
• 17 U.S.C. § 204(a), execution of transfers — Cornell LII
• Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), decided 5 June 1989 — Cornell LII
• US Copyright Office, Works Made for Hire, Circular 30 — copyright.gov
• Jonathan Tobin, "Does A Designer Have to Turn Over Source Files When A Client Asks For Them?", AIGA Los Angeles, 17 October 2013 — aiga.org
• r/smallbusiness, "I got screwed by a client which now wants the source files" — reddit.com
• Graphic Design Stack Exchange, "Repeat client is suddenly demanding intellectual property rights" — stackexchange.com