/

Deliverables

Releasing files on payment is one of the few moves that gets a late invoice through without adding anything to it. What to hold, what to release, and what never to touch.

Should You Hold the Files Until the Client Pays?

By Tatiana Stepanova

6 min read

Featured image

The short answer

Yes, in most cases you can hold back final and source files until the invoice for them is paid, provided your contract says that is how handover works. Release them the day payment arrives. Share view-only previews in the meantime so the client can check the work. Never hold back anything the client already owns or has already paid for, and do not take down work that is already live.

What

Hold until paid?

Why

Source files: Figma, InDesign, layered artwork, the code repository

Yes, if the contract ties handover to payment

This is what the final invoice pays for

Final exports at full resolution, print-ready files

Usually

Send previews or proofs instead until payment clears

Drafts and previews for approval

No, send them

Share them view-only, watermarked or at low resolution

Work from milestones the client has already paid

No

It has been paid for

The client’s own logins, domain, data and supplied content

No

It belongs to the client

A website or campaign that is already live

Do not take it down

That is a different act, with legal risk

Why this works when reminders do not

Holding files puts the payment between the client and something they need, usually for a launch, a print run or a handover to another team. Paying the invoice is the quickest way to get it.

It also avoids the problem that makes late fees weak with larger clients. A late fee is a new amount that needs approval. Releasing files asks for nothing new: the invoice has already been approved, and someone on the client’s side now has a reason to push it through the payment run.

It is the most widely agreed advice in a 2026 r/graphic_design discussion about a client asking for source files before paying the final invoice. The most upvoted replies gave the same answer: files go out once payment is complete, stated calmly as policy.

Who owns the work before it is paid for

The contract decides this, and the law fills in where the contract says nothing. The defaults may be closer to your side than you expect.

  • United Kingdom. When work is commissioned, the first owner of copyright is the person or business that created it, not the client, unless both sides agree otherwise in writing. The same guidance notes that a court may still find the client has an implied licence to use the work for the purpose it was commissioned for.

  • United States. Work by an outside contractor is generally owned by its creator. It counts as a “work made for hire” owned by the client only in specific categories and only with a written agreement signed by both sides, or if the rights are assigned in writing.

  • Elsewhere. Rules vary by country, so check before you rely on a default.

That leads to 2 practical points. First, ownership is set by the contract, so write it there. Second, an implied licence may let a client use work they already have, which is one more reason to send previews rather than finished files before payment.

The clause that makes it routine

With a clause in the contract, holding files means applying terms the client already signed, and the conversation stays about process. Example wording to adapt with your lawyer:

Ownership of the final deliverables, and delivery of all source and production files, pass to the Client on receipt of payment in full. Until then, the Client may use previews supplied by the Agency for review and approval only.

Pair it with milestone billing so that the last invoice is tied to handover. If the final payment is small compared with the work before it, there is little reason for anyone to push it through. The payment clauses to put in every contract cover the rest.

What to send while you wait

The client needs to check the work and plan around it. Give them enough to do that without handing over the finished files:

  • View-only links to design files, with downloading and copying turned off where the tool allows it.

  • A password-protected staging site in place of the live launch.

  • Watermarked or low-resolution exports.

  • PDF proofs for print work, with the print-ready files released on payment.

How to say it

Keep it short, refer to the agreement, and make the next step obvious:

Subject: Final files for [project]

Hi [Name],

The final files for [project] are ready. As set out in our agreement, I’ll send the source files and full-resolution exports as soon as invoice #214 for [amount] is paid.

In the meantime, here’s a view-only link so your team can check everything: [link]

If the invoice is already scheduled for your next payment run, let me know the date and I’ll have everything ready to send the same day.

Thanks,

[Name]

If the client says they need the files urgently for a launch, that is the moment to ask who can approve the payment today. Your contact now has a reason to find them. The same approach works when finance says it is handling it.

What not to hold back

  • Anything already paid for. Files from milestones the client has paid belong in their hands.

  • The client’s own property. Their logins, domain names, hosting accounts, data, and the copy and images they supplied.

  • Live work. Taking down a website, pausing a running campaign or locking a client out of an account they own is a different step from holding back new files, and it carries legal risk. Take advice before doing anything like it.

  • Files you are not licensed to hand over. Many font and stock image licences do not let you pass the files on. Leave them out of any handover, and tell the client where to license them.

The cost worth naming

Holding files only works before handover. Once the finished files have gone out, you have nothing left to hold, which is why the structure of your billing matters more than the policy itself. A deposit covers the work before the first milestone.

It can also strain the relationship, especially with a client under deadline pressure. Keep the tone calm, offer previews, and release the files the moment payment arrives. If a client disputes the work itself, holding files will not resolve it, and the dispute process is the better route.

FAQ

Can I withhold work until a client pays?

In most cases you can hold back final and source files that have not been paid for, especially if your contract ties handover to payment. Do not hold back work the client has already paid for, their own property, or anything already live, and check the law where you operate.

Do I have to give a client the source files?

It depends on your contract. In the UK and the US, an outside creator generally owns the copyright unless it is transferred in writing, so whether source files are included, and when, should be stated in the agreement.

Can I take down a website if the client doesn’t pay?

Taking down live work is very different from holding back new files, and it can expose you to legal claims. Take advice first, and rely on contract terms agreed in advance rather than acting on your own.

Should I send final files before or after the last payment?

After, if your contract says so. Send view-only previews or proofs so the client can approve the work, then release the finished files as soon as the payment clears.

What if the client says they need the files urgently?

Offer to send them the same day the payment is made, and ask who can approve the invoice now. An urgent need for the files is often what gets a stalled payment moving.

Not legal or tax advice. Payment law and enforceable interest rates vary by state and country — have your contract terms and any decision to withhold work reviewed by your own lawyer before use.

Collected42

Don’t want to send these yourself?

Collected42 steps into your existing payment thread and owns the follow-through — reminders, calls, payment dates, AP contacts and escalation — while you stay focused on the client work.

Schedule a call