The project is delivered. The invoice cleared. You’re already three jobs deep into forgetting this client existed. Then the email lands, friendly as a knife: “Hey! Quick one — can you send me the source files?” Four words, one exclamation point, and the entire economic logic of your business quietly set on fire. It always arrives after the relationship is technically over, phrased like a favour you’d be weird to refuse. It is not a favour. It is the most expensive sentence anyone will say to you all year, and you’ll probably say yes.
The Request That Arrives After the Invoice Clears
Timing is the tell. Nobody asks for source files during the project, when the conversation is alive and the scope is on the table. They ask afterward, in the soft administrative afterglow, when saying no feels petty and saying yes feels like good service. The framing — “quick one” — is doing a staggering amount of work. It recasts your layered, named, lovingly organised working files as a USB stick you forgot to hand over. As if the deliverable and the machinery that produced it are the same object. They are not. You sold them a chair. They are now asking for the workshop, the lathe, and the tree.
And here’s the part nobody says out loud: in most jurisdictions, unless your contract explicitly transfers them, the working files and the underlying intellectual property are yours. The client bought a licence to use a final deliverable. They did not buy the editable, infinitely reusable engine behind it. This isn’t pedantry. It’s the difference between selling a meal and selling the recipe, the kitchen, and the right to open a restaurant.
What They Think They’re Asking For (and What They’re Actually Asking For)
The client genuinely believes they’re asking for a file. In their head it’s housekeeping — tidy up, hand over the folder, done. What they’re actually asking for is the ability to never hire you again. Source files mean their nephew can “just tweak it.” Source files mean the in-house junior can resize the logo at 11pm without paying you. Source files mean your craft becomes their template, edited forever by people who will make it worse and then blame the original.
This is the same instinct that powers half the indignities in this industry — the belief that the valuable part is the asset, not the thinking. It’s a cousin of paying in exposure and a sibling of spec work: in every case, the client is trying to extract the expensive thing (your judgement) while paying only for the cheap thing (the export). The source file request is just the politest version, because it arrives after you’ve already been paid, wearing the costume of a reasonable cleanup task.
The Polite Heist, Decoded
Let’s translate a few classics, because the genre has dialects:
“We just want them for our records.” Nobody archives layered Illustrator files for sentimental reasons. This means: we want optionality we didn’t pay for.
“It’ll save us going back and forth in future.” Correct. Specifically, it’ll save them going back and forth with you, because there will be no future with you.
“Our other agency needs them.” Ah. So the files aren’t for records. They’re a dowry for your replacement, and you’ve been asked to gift-wrap your own succession.
“It’s all paid for, right?” The deliverable is paid for. The means of production is a separate line item that, funnily enough, was never on the invoice — because they never asked, and you never quoted it, and now we’re all pretending that silence was a transfer of ownership.
How to Say Yes Without Setting Your Margins on Fire
You don’t have to refuse. Refusing makes you the villain in a story they’ll tell at networking events. Instead, do the thing that reframes the entire request: price it. Source files are a product, so sell them like one. A source file release fee — a clean, confident number — does three things at once. It signals the files have value (which trains the client to treat them as valuable). It converts a relationship-ending favour into a revenue event. And it filters: a client who genuinely needs the files will pay; a client who was chancing it will suddenly remember they don’t need them after all.
The healthier fix is upstream, in the contract, before anyone falls in love with the work. State plainly what the fee buys (a licence to use the final deliverable) and what it doesn’t (ownership of working files, which are available for an additional, named sum). Do this and the post-delivery email stops being an ambush and becomes a price check. You stop improvising boundaries at your most tired and least leveraged. This is the same energy as learning how to fire a client or surviving the Friday 5pm revision: boundaries set in advance are policy; boundaries set in the moment are a fight.
The Source File Is a Boundary, Not a Folder
Here’s the reframe that makes the whole thing simple. The source file request isn’t really about files. It’s a test of whether you understand what you sell. Designers who think they sell PNGs hand over the source files for free and wonder why they can’t raise their rates. Designers who understand they sell judgement, applied repeatedly, by a specific brain treat the working files as the keys to that brain — and they don’t leave the keys in the door because someone said “quick one.”
You are allowed to be generous. You are allowed to hand them over, even gladly, for the right client at the right price. What you are not required to do is treat your own intellectual property as a rounding error because refusing felt awkward over email. The awkwardness is the cost of the boundary. Pay it once, in a sentence, instead of paying forever in unpaid edits and a client who learned they could have the whole workshop for the price of a chair.
The Junior Who Inherits Your File (and Your Reputation)
Picture the afterlife of a source file you’ve handed over for free. It lands on the desktop of someone who was not in any of the meetings, has none of the context, and possesses exactly enough software access to be dangerous. They nudge the kerning. They swap the brand blue for a blue that is technically also blue. They stretch the logo because the new banner is wider and nobody told them logos have feelings. Six months later that mangled artwork is in the wild, and it still carries the faint genetic signature of your work — close enough that anyone who knows your portfolio will assume you made the ugly version. You didn’t. But you gave them the means, for free, with an exclamation point, because saying no felt rude.
That’s the hidden cost nobody puts on the invoice: handing over editable files doesn’t just forfeit future income, it outsources your quality control to strangers and keeps your name attached to the results. Craft isn’t only what you make; it’s what survives contact with the people who edit it later. A finished, locked deliverable protects the work and the reputation that made it worth buying. The source file surrenders both — which is precisely why it’s worth a number, not a shrug.
Stop handing over the workshop for free. If you need a daily reminder that your craft is not a free export, the NoBriefs shop stocks the gear for it — Fuck The Brief for the meetings, KPI Shark for the reports, and the Spreadsheet Sloth for the rate card you keep promising to update. Wear the boundary so you don’t have to argue it. Browse the rebellion →
