By Mehdi HassanWho owns the website design when an agency builds it?
The contract decides who owns the website design when an agency builds it. Without a written transfer, the agency that created the design and code often keeps the copyright, even though you paid for the work. With a proper assignment clause, ownership moves to you, usually on final payment.
This surprises many founders, because it feels obvious that paying for something means owning it. Copyright doesn't work like buying a laptop. In the US, the creator of a work generally owns the copyright, and for an outside agency or freelancer, the client only becomes the owner if a signed agreement says so. Rules differ by country, so treat this as practical guidance rather than legal advice.
Ownership is one clause in a wider set. Our web design contract checklist covers the others, from scope to cancellation. This guide focuses on one question: when the project ends, what exactly is yours, and what words make it so.
Why doesn't paying for a website mean you own it?
Paying for a website doesn't mean you own it because copyright starts with the creator, and payment alone doesn't transfer it. You need a written assignment, or a valid work-for-hire arrangement, for ownership to move from the agency to you.
In US copyright law, work made for hire covers employees acting in their job and a narrow list of commissioned work categories that also need a written agreement. A website built by an outside agency doesn't fit neatly into those categories, which is why most well-drafted contracts don't rely on work for hire alone. They include an explicit assignment instead, often alongside a work-for-hire clause as a backup.
Without either, the most common outcome is an implied license: you can use the site for its intended purpose, but you may not be able to modify, reuse or move the code freely. That's the situation that causes trouble later, when you want a new agency to work on the site or you're doing due diligence for a funding round or acquisition.
What exactly should transfer to you after the project?
Everything made specifically for your project should transfer to you: page designs and design source files, custom code, written copy, illustrations and any brand assets created for the site. Pre-existing agency tools and third-party assets are handled differently, and the contract should say how.
Item | Who should own it | What to ask for |
|---|---|---|
Custom page designs and Figma files | You | Assignment on final payment |
Custom code written for your site | You | Assignment plus repository access |
Website copy and content | You | Assignment; agency keeps no reuse rights |
Agency's reusable components and tools | Agency | Permanent, royalty-free license for your site |
Open-source libraries | Their authors | List of licenses used |
Fonts, stock images, plugins | Their vendors | Licenses bought in your company's name |
The middle row is the one founders miss. Agencies often reuse their own internal starter code or component libraries across clients. It's reasonable for them to keep owning those, but the license to you should be permanent, irrevocable and not tied to an ongoing contract. If the license ends when you stop paying a retainer, you don't really control your site.
What transfer language should the contract include?
The contract should say that, on receipt of full payment, the agency assigns to you all rights, title and interest in the deliverables created for the project, and grants you a permanent license to any pre-existing materials included in them. It should also list what counts as a deliverable.
Four details make that sentence work. It names the trigger, usually final payment. It covers all deliverables, defined somewhere specific like the scope section. It separates agency background materials from new work. And it says the agency will sign any further documents needed to confirm the transfer, which matters if you later need to prove ownership.
Sample wording to adapt with your lawyer
This is illustrative wording, not legal advice; have a lawyer adapt it to your jurisdiction.
Assignment. Upon receipt of full payment, Agency assigns to Client all right, title and interest, including all copyrights, in the Deliverables listed in the Scope of Work.
Background materials. Agency retains ownership of tools, code and materials it created before or independently of this project. To the extent any are included in the Deliverables, Agency grants Client a perpetual, irrevocable, royalty-free, worldwide license to use, modify and maintain them as part of Client's website.
Further assurances. Agency will sign any documents reasonably needed to confirm Client's ownership.
Portfolio. Agency may show the completed, publicly launched website in its portfolio.
Payment timing ties ownership to cash, so it's worth reading alongside your web design payment terms. If you cancel halfway, the contract should also say what you own for the work paid to date, which we cover under kill fees and cancellation terms.
Do you own your code on Framer, Webflow or Next.js?
On Framer and Webflow you can own the design and content, but the site runs on the platform under its terms, and you can't take it elsewhere as a working codebase. On a custom Next.js build you can own the actual code repository, which you can host and change wherever you like.
This is a platform question rather than a contract question, and it's worth separating the two. A contract can assign you every right the agency has, but it can't give you rights the platform doesn't offer. On hosted builders, owning your site in practice means owning the project inside your own account, with the agency invited as a collaborator, plus exports of your content. Webflow's code export gives you static HTML and CSS without the CMS, which is helpful as a backup but not a portable site.
With Next.js, ownership is more literal: a Git repository with full history, in an organization your company controls. That's one reason teams choose a coded build. We cover what moving between those setups costs in Framer to Next.js migration cost.
Which accounts should be in your name, not the agency's?
Your domain, DNS, hosting, CMS, code repository, analytics and every paid license should be registered to your company, with the agency added as a user. Owning the copyright means little if the agency controls the accounts the site runs on.
- Domain registrar and DNS. The most important one. Losing it means losing your address.
- Hosting and deployment. Your account, the agency invited as a team member.
- Code repository. In your organization, not a personal account of a developer.
- CMS and site builder. The workspace or project owned by your company.
- Analytics, forms and email tools. So historical data stays with you.
- Font and image licenses. Bought in your company's name, with receipts.
Ask for this list in the handover section of the contract, then check it before your final payment. If you're unsure what a full handover includes, our guide to website ownership goes deeper, and the website warranty period guide covers what support should follow.
What if your current contract doesn't mention ownership?
If your contract is silent on ownership, ask the agency to sign a short assignment of rights now, while the relationship is good. Most studios will agree, especially once the project is fully paid, and it closes the gap before it matters.
Keep the request simple and specific: a one-page document that assigns the listed deliverables to your company and confirms a license for any background materials. Then move any accounts still in the agency's name into yours. If the agency refuses, find out why. Sometimes it's an unpaid invoice, sometimes a reused component they want to protect, and both can usually be solved. If you're choosing an agency now, ask to see the ownership clause before you get attached to a portfolio; it's one of the first things we'd check when choosing the best web design agency for startups.
