Who Owns Your Work? IP Rights for UK Freelancers: Copyright, Assignment & Portfolio Use

A freelance designer spent three months building a complete brand identity for a client: logos, colour palettes, typography, icon sets. When the project ended, the client claimed they owned everything, including the designer's pre-existing icon library she'd spent years building. The contract said "all intellectual property created in connection with this agreement is assigned to the client." That one clause wiped out her entire toolkit.

IP disputes are one of the most expensive and emotionally draining problems freelancers face. The good news: with the right contract language, they're almost entirely preventable.

How Copyright Works in the UK

Under the Copyright, Designs and Patents Act 1988, copyright in a creative work belongs to the person who created it: the author. For freelancers, this means that by default, you own the copyright in everything you create, even if a client pays you to create it.

This is the opposite of employment law, where work created during employment generally belongs to the employer. As a freelancer, you start from a position of ownership. The only way that changes is if you explicitly agree to transfer or licence it in writing.

This matters because verbal agreements like "of course you can use my designs" don't transfer copyright under UK law. Only a written, signed assignment works. So even if you hand over files and the client starts using them, you still technically own the copyright until you sign it away.

Licence vs. Assignment: the Critical Difference

Most freelancers don't realise there are two completely different ways to give a client rights to use your work. Confusing them is one of the most common (and costly) mistakes in freelance contracts.

Licence

A licence gives the client permission to use your work in specific ways, while you retain ownership. You can licence exclusively (only they can use it) or non-exclusively (you can also licence it to others). A well-drafted licence specifies:

• What the work can be used for (e.g., digital marketing only)
• Where it can be used (e.g., UK only, or worldwide)
• How long the licence lasts (e.g., 2 years, or perpetual)
• Whether it can be sub-licensed to third parties

A licence is often the right choice. The client gets what they need (the right to use the work) and you keep ownership and the ability to use it elsewhere.

Assignment

An assignment permanently transfers ownership of the copyright from you to the client. Once assigned, it's gone and you no longer own the work. Watch out for language like:

• "assigns all rights, title and interest worldwide in perpetuity"
• "work made for hire" (a US concept that sometimes appears in UK contracts)
• "all intellectual property created in connection with this agreement"

When assignment is reasonable vs. a red flag

Assignment can be fair, for example if you're creating a bespoke logo that the client intends to trademark. What's not fair is a blanket assignment of everything, including work you created before the project started. Look out for:

• Assignment of pre-existing work (your templates, frameworks, code libraries)
• Assignment before payment ("IP transfers upon delivery" rather than "upon receipt of full payment")
• Assignment for a fixed fee with no ongoing royalty

Pre-Existing IP: Protecting Your Tools and Templates

Pre-existing IP (also called "background IP") is any work you created before the project started: code libraries, design systems, photography presets, writing templates, or anything else you bring to the project. Without a specific clause protecting it, an overbroad assignment clause could sweep it all up.

A background IP clause carves this out explicitly. Something like:

"The Contractor retains all rights, title, and interest in any pre-existing intellectual property, tools, frameworks, or methodologies used in delivering the services ('Background IP'). The Client is granted a non-exclusive licence to use the Background IP solely to the extent necessary to make use of the deliverables."

If your contract doesn't have something like this, push to add it. It's rarely controversial. Clients generally just want the finished work, not your underlying toolkit.

Portfolio Rights

Your portfolio is how you win your next client. But many contracts, especially those with large companies, include confidentiality clauses or IP assignment terms that effectively prevent you from showing the work publicly.

This is often unintentional. The legal team added a broad confidentiality clause without thinking about portfolio implications. But the effect is the same: you've done great work that you can't show anyone.

Always ask for an explicit portfolio rights clause. A simple addition works:

"The Contractor retains the right to display the deliverables in their portfolio and use them for self-promotional purposes, unless the Client notifies the Contractor in writing within 14 days of delivery that the work is confidential."

This gives the client a reasonable opt-out if the project is genuinely sensitive (a pre-launch product, a confidential campaign) while protecting your portfolio rights by default.

IP Transfer Timing: the Payment Trap

This is one of the most important and most overlooked IP red flags. When does the IP actually transfer?

If your contract says IP transfers "upon delivery" or "upon signing", the client gets ownership of your work before they've paid you. That means if they disappear without paying, you've lost both the money and the rights. You can't even use your own work elsewhere.

The fix is simple: tie IP transfer to payment.

"All intellectual property rights in the deliverables shall transfer to the Client upon receipt of full payment of all outstanding invoices. Until such payment is received, the Contractor retains all rights in the deliverables."

This gives you leverage if payment is delayed or disputed, and it's entirely standard. Most professional freelance contracts work this way.

What to Look For and Ask For

When reviewing the IP section of any freelance contract, check for these six things:

• Scope of assignment: Does it cover everything, or only the specific deliverables? Push back on "all IP created in connection with this agreement."
• Background IP carve-out: Is your pre-existing work explicitly excluded from any assignment?
• Transfer timing: Does IP transfer on delivery, or on receipt of full payment? Always push for the latter.
• Portfolio rights: Can you show the work? Add a clause if it's missing.
• Sub-licensing: Can the client licence your work to third parties? This matters if you're being paid for exclusive use.
• Moral rights: The CDPA gives creators the right to be identified as the author. Check whether you're being asked to waive this.

You can also check our 12 freelance contract red flags for more on IP warning signs, or use our 15-point contract checklist which covers IP transfer, portfolio rights, and pre-existing assets.

Frequently Asked Questions

Does freelance work automatically belong to my client?

No. Under the Copyright, Designs and Patents Act 1988, copyright in work created by a freelancer belongs to the freelancer by default. It only transfers if you sign a written assignment. If your contract doesn't mention IP, you technically retain ownership, though this creates ambiguity that's better resolved with a clear clause.

What if the contract says "work made for hire"?

"Work made for hire" is a US legal concept that doesn't apply in the UK. Under UK law, even if a contract uses this phrase, copyright belongs to the creator. However, if the contract also includes a valid IP assignment clause, that assignment does apply, so always read the whole IP section, not just the headline phrase.

Can I add a portfolio clause to any contract?

Yes. Portfolio rights clauses are standard and almost always accepted. You can simply ask to add: "The Contractor retains the right to display completed deliverables in their portfolio for self-promotional purposes." If the client insists the work is confidential, negotiate a delay (e.g., 12 months after launch) rather than a permanent prohibition.

What happens if I use pre-existing assets without a background IP clause?

If you use your own templates, code, or design elements in a project and there's no background IP carve-out, a broad assignment clause could technically transfer ownership of those assets to the client. In practice, this is rarely enforced, but it creates risk, especially if you use the same assets for other clients. Always protect your background IP in writing.