Web Design

Who Owns Your Website After Launch? What the Contract Should Say

September 17, 2026  ·  11 min read

Every website contract has a sentence about ownership. Most of them say something close to "all work product becomes the property of the client on final payment", and both sides sign believing the question is settled.

Under United States copyright law it frequently is not settled, and the gap only surfaces years later - when the agency closes, when you want to move to a new developer, or when someone else starts using a logo you thought was yours.

We build websites and logos for a living, so read this knowing we have a side. It is also why we can be specific: everything below is a term we are happy to sign ourselves, and every source is public and linked in plain language. None of this is legal advice. Copyright and contract law turn on details and on where you are, so have a lawyer read anything you are about to sign.

What happens if the contract says nothing

Copyright in the United States belongs to whoever created the work. There are two exceptions: the creator was an employee producing the work inside the scope of their job, or the work meets the narrow statutory definition of a work made for hire, covered in the next section.

A web design agency or a freelance designer is neither. They are an independent contractor. So if your contract is silent on copyright, the design, the code and the logo were made by them and the copyright began life with them. You would typically be left arguing you have an implied licence to use what you paid for. That is usually enough to keep your site online. It is usually not enough to let you hand the files to a different developer, redraw the logo, or register a trademark without a conversation first.

Which is the whole reason the clause matters. Not because anyone is planning to behave badly, but because ownership only ever gets tested at the worst possible moment.

Why a "work made for hire" clause usually does not do the job

This is the part that surprises people, including some of the people writing the contracts.

Section 101 of the Copyright Act defines a work made for hire in exactly two ways. The first is "a work prepared by an employee within the scope of his or her employment". The second is a work "specially ordered or commissioned" - but only if it was commissioned for use as one of nine specific things, and the parties sign a written agreement saying it is a work made for hire.

Here is the complete list of those nine categories, straight from the statute:

  • a contribution to a collective work
  • a 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
  • an atlas

Read it twice. A website is not on that list. Source code is not on that list. A logo is not on that list. Neither is photography commissioned for your site.

The US Copyright Office makes the point with an example of its own: a company commissioned a contractor to design wallpaper, and the two parties signed a written agreement stating the work would be a work made for hire. It still failed, because two-dimensional artwork is not one of the nine categories. Courts take the same approach - they look at what the work actually is, not at the label the contract puts on it. Designating something a work for hire after it has already been made has also been rejected.

So a clause resting on those four words alone can transfer nothing at all, in precisely the situation where you need it to work.

Ask for an assignment instead

An assignment is a different legal mechanism, and it is not limited to nine categories. Section 204(a) of the same Act sets the bar: a transfer of copyright ownership "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".

In plain terms, the clause you want does three things:

  • It assigns, rather than labels. Look for wording where the contractor assigns all right, title and interest, including copyright, in the deliverables - and check that "deliverables" is defined to include the design files, the source code and the logo artwork, not just "the website".
  • It is signed by them. Signed by the party giving the rights up, not only by you. A clause buried in terms you accepted by clicking a button is weaker than a signed agreement.
  • It has a trigger. "On receipt of final payment" is normal, fair and worth agreeing to. What you do not want is a clause with no stated trigger, or one tied to something as vague as project completion.

Good drafting usually adds a fallback: if the assignment fails for any reason, you receive a perpetual, worldwide, royalty-free licence instead. Ask your lawyer for that belt-and-braces version.

Two carve-outs that are entirely reasonable

  • Portfolio rights. Almost every agency reserves the right to show finished work in its portfolio and marketing. We do. It costs you nothing and it is how you were able to judge our work in the first place.
  • Pre-existing and generic components. Any established studio brings a framework, a component library and scripts written long before your project. You get a licence to use them inside your site, not ownership of the studio toolkit. That is normal. What is not normal is the same carve-out quietly applied to your design, your content or your logo.

Your domain name is a separate question, with a 60-day trap

The domain is not covered by the design contract at all. It is a registration held at a registrar in somebody name, and whoever is listed as the registrant controls it. Plenty of otherwise careful contracts assign every line of code and never mention the domain.

If your agency registered it under their own name and email as a convenience, moving it to you later is what the ICANN Transfer Policy calls a Change of Registrant - defined as a material change to the registrant name, organization or email address. The policy is blunt about what follows: "The Registrar must impose a 60-day inter-registrar transfer lock following a Change of Registrant."

So on the day you finally get the domain into your own name, you may be unable to move it to your own registrar for two months. There is an opt-out, but only the prior registrant - the agency - can use it, and only before the change is requested. ICANN even instructs registrars to warn people: if the final goal is to move registrar, "the Prior Registrant is advised to request the inter-registrar transfer before the Change of Registrant to avoid triggering the 60-day lock".

Two practical rules follow:

  • Register the domain yourself, before the project starts. In your business name, on an email address the business controls rather than one belonging to an individual employee or supplier. Then give your developer DNS access. They do not need the account.
  • If it is already in someone else name, agree the order of operations. Transfer to your registrar first and change the registrant second, or have them opt out of the lock at the moment of the change.

Then put the renewal date in a calendar you control and turn on auto-renew. A lapsed domain is the one website failure that is genuinely hard to undo.

Six accounts that should be in your name, not theirs

Ownership of the files means little if you cannot reach the places the site lives. Each of these should exist under an account your business owns, with your agency added as a user:

  • Hosting. At minimum an owner-level login. If the site sits inside an agency reseller account, ask in advance what a move looks like and what it costs.
  • The content management system. An administrator account for you personally, created at launch rather than requested later.
  • The code repository. Ownership of source code is worth much less if the only copy lives in a private repository on someone else account.
  • Google Analytics and Search Console. Create the properties under your own Google account and grant access to the agency. Historic traffic data cannot be recreated, and losing it means losing your only record of whether the last three years of marketing worked.
  • Your Google Business Profile. This one has bitten more local businesses than any other, because reviews are attached to the profile and cannot be moved. Our guide to optimizing your Google Business Profile covers claiming and ownership transfer.
  • DNS and business email. Whoever controls DNS can redirect both your website and your mail. Keep that at the registrar account you own.

"You own the website" still leaves four things out

Even a properly drafted assignment covers only what your agency created. Four categories sit outside it, and they are the ones that quietly stop working after a handover:

  • Editable source files. A PNG of your logo is not a logo. Ask specifically for vector artwork you can scale and recolour, plus the layered design files. Getting these a year later, from a designer who has moved on, ranges from awkward to impossible.
  • Stock photography licences. Usually bought by the agency under their account, and the terms vary on whether a licence can be transferred to you at all. Ask which images are licensed, from where, and under what terms.
  • Web fonts. Commercial font licences are often sold per domain or per monthly pageview and can sit in the agency account. This is the one that produces a site that suddenly renders in a fallback typeface.
  • Premium plugins, themes and API keys. Licence keys tied to an agency account stop receiving updates when the relationship ends, and a plugin that stops receiving security updates is a liability rather than a feature.

The fix is one line in the contract: a written inventory of every third-party licence used on the site, naming who holds it, what it costs and when it renews. It also makes your real running costs visible, which is the part most often missing from a quote - see our breakdown of what a website actually costs.

The clause that protects your search rankings

If the project replaces an existing site rather than creating a first one, one more clause belongs in the contract: a written commitment to produce a redirect map and implement permanent redirects from every old address to its closest new one.

Google states plainly that permanent redirects do not cost you link credit, but rankings attach to individual addresses rather than to your domain in general. A rebuild that changes URLs without redirecting them is the single most common way a business loses traffic it spent years earning. We set out the whole process in how to redesign a website without losing your Google rankings. Ask for it in writing before you sign, not in an email after launch.

The arrangement to think hardest about: rented websites

Some providers offer a low monthly fee with no build cost. The site is designed, hosted, maintained and updated for a flat rate, and it remains their property throughout. You are leasing it.

That is a legitimate model and it suits some businesses, particularly those who want no technical responsibility at all. But it is a fundamentally different purchase from the one this article describes, and it has one hard consequence: when payments stop, the site goes away, and there is usually nothing to take with you. If you are considering it, the questions are simple - is it disclosed clearly in the contract, what happens to the domain, and can you export your own content.

The warning sign is not the model itself. It is a contract that presents monthly pricing as if it were ownership.

A handover checklist

Before you release final payment, you should be able to tick every line:

  • A signed assignment of copyright in the deliverables, effective on final payment, with deliverables defined to include design files, source code and logo artwork.
  • Domain registered in your business name, at a registrar account you can log into.
  • Owner-level access to hosting, the CMS, and the code repository.
  • Analytics and Search Console properties owned by you, with the agency added as a user.
  • Editable source files: vector logo, layered design files.
  • A written list of third-party licences, with holder, cost and renewal date for each.
  • A redirect map, if this replaced an existing site.
  • A named warranty period for fixing bugs found after launch, and what support costs after it.

If a supplier hesitates on any of these, the answer tells you more than the rest of the pitch did. Our guide on how to choose a web design company covers the other questions worth asking before you commit.

Frequently asked questions

Who owns a website after it is built?

Unless the contract transfers it, the person who created the work does. Copyright in the United States starts with the creator, and the only automatic exception is an employee producing work inside the scope of their job. A web design agency or freelancer is an independent contractor, so without a written assignment signed by them you are usually left relying on an implied licence to use what you paid for rather than owning it outright.

Does a work made for hire clause give me ownership of my website?

Often not. Section 101 of the Copyright Act only allows commissioned work to be a work made for hire if it falls into one of nine listed categories, and a website, its source code and a logo are not among them. The US Copyright Office gives the example of a commissioned wallpaper design that failed the test because two-dimensional artwork is not on the list. Ask for an assignment of copyright instead, effective on final payment.

Should my web designer register my domain name?

No. Register it yourself before the project starts, in your business name and on a company email address, then give your developer DNS access rather than the account. If it is already registered in someone else name, moving it to you is a Change of Registrant under ICANN rules, which triggers a 60-day lock on transferring the domain to another registrar. Only the current registrant can opt out of that lock, and only before the change is made.

What files should I receive when a website project ends?

A written handover should include the site files or repository access, owner-level logins for hosting and the content management system, editable design source files, vector versions of your logo, and a list of every third-party licence used on the site - stock photography, web fonts, premium plugins or themes - naming who holds each one, what it costs and when it renews. Licences held in your agency account stop working when the relationship ends.

What happens to my website if I stop paying my web design agency?

It depends entirely on what you signed. If you own the copyright, hold the domain and have owner access to hosting, nothing happens beyond losing support. If you are on a rented or leased website plan, the site normally belongs to the provider and goes offline when payments stop, leaving you with no files to move. That model is legitimate when it is disclosed clearly, but it is very different from ownership and the contract should say so plainly.

In summary

Ownership is not one sentence, it is four separate things: the copyright, the domain, the accounts and the licences. A work made for hire clause on its own may cover none of them. An assignment signed by your supplier, a domain in your own name, owner-level logins and a written licence inventory cover all four, and none of it is unreasonable to ask for.

It is also the cheapest part of any website project. It costs a conversation before you sign, and it is expensive only when you skip it.

If you would like a second opinion on a proposal in front of you, or you are planning a new build, take a look at our web design services or get in touch - we are happy to tell you which clauses we would push back on, even if the quote is not ours.

Get a Free Quote