Who Owns Your Website When You Leave a Web Designer?

You paid for the site. You have the login. You still may not own it.

Do you actually own your website?

Probably not all of it. Website ownership is five separate layers — domain, DNS, hosting, codebase or CMS, and content copyright — and a web designer can hold any one of those layers while you hold the other four.

The trap is that everything looks fine while the relationship is fine. The site loads. The phone rings. You never discover which layers you do not control until the day you try to leave.

Then you find out the domain is registered to your designer's personal Gmail, the site runs on a builder with no export function, and the $250-a-month 'hosting' line on your invoice sits on top of a server that lists at $6. None of that is illegal. Most of it is in the contract you signed without reading.

This is the same failure pattern as an agency holding your ad account, which we cover in who should own your Google Ads account. The asset is yours. The access is theirs. That gap is the whole leverage play.

Which five layers of ownership are you checking?

Five, and each one transfers separately: the domain name, the DNS, the hosting account, the codebase or CMS, and the copyright on the copy, photos, and code. Owning one does not give you the next.

Notice that the last row is the one nobody checks. The US Copyright Office is blunt about it: 'Mere ownership of a copy or phonorecord that embodies a work does not give the owner of that copy or phonorecord the ownership of the copyright in the work' (Copyright Basics, Circular 1). Having the files is not owning the work.

Whose name is on the domain registration, and how do you find out?

Look up your domain's public WHOIS or RDAP record, because the Registered Name Holder listed there is the only party with authority to move it. ICANN's Transfer Policy states that the Administrative Contact and the Registered Name Holder listed in WHOIS 'are the only parties that have the authority to approve or deny a transfer request,' and that in a dispute, the Registered Name Holder's authority wins.

Read that again with your designer's name in the Registrant field. If they are the Registered Name Holder, they are not holding your domain. It is legally theirs, and the registrar will take instructions from them, not you.

Most registrars now mask the registrant behind privacy protection, so the public record may show a proxy service instead of a name. That is not an answer — it is a missing answer. Email the designer and ask, in writing, one question: which exact registrar account holds the domain, and what name and email are on the Registrant field?

• Run a WHOIS/RDAP lookup on your domain and read the Registrant Name, Registrant Organization, and Registrant Email fields.
• Check the domain status codes. clientTransferProhibited is normal on a healthy domain; it becomes a problem only when someone else can remove it and you cannot.
• Check the expiry date. A domain you do not control is a domain that can quietly lapse.
• Check the nameservers. They tell you who actually steers your traffic, which is a different question from who owns the name.
• Ask for registrar account access in writing, and keep the reply. It is your evidence later.

Can you export your site, or is the CMS a cage?

Open the admin panel today, find the export function, and run it. If there is no way to download your pages, templates, media, and database, you are renting the site, not owning it — and the rent has no ceiling.

This is the specific trap in proprietary CMS platforms sold to trades and clinics. Plumbers, HVAC companies, roofers, dental practices, and law firms get pitched an all-in-one platform with a site, a booking widget, and a review tool. The export button does not exist, and it does not exist on purpose. The switching cost is the product.

WordPress exports. Custom code in a Git repository you control transfers in an afternoon. A platform whose sales rep goes quiet when you ask 'show me a full export of a site like mine' has told you the answer. Our comparison of Next.js vs WordPress for a marketing site covers the honest tradeoffs of each, and what WordPress SEO services cannot fix covers where the platform itself is the ceiling.

A real export is not a PDF of your pages. Ask for all six of these before you sign anything:

• Every page and post as portable files or a database dump you can restore elsewhere.
• The full media library at original resolution, not the compressed versions the CMS serves.
• Templates and theme files, so the layout survives the move.
• Your redirect map. Losing it is how a rebuild tanks the rankings you already paid for.
• Form submissions and any lead data sitting in the platform's database.
• Analytics and tag configuration, under your own Google account, not the designer's.

What is the $250/month hosting bill actually for?

Usually a markup, and you should know how big it is. DigitalOcean's list price for a 1 GiB RAM, 1 vCPU, 25 GiB SSD droplet is $6 a month, and WP Engine's entry managed WordPress plan lists at $30 a month for one site and 25,000 monthly visits.

A markup is not automatically theft. Managed hosting, nightly backups, plugin updates, uptime monitoring, and a human who picks up at 9pm on a Friday all cost real money. A brochure site for a five-truck HVAC company does not need a $276-a-month plan built for 400,000 monthly visits.

The tell is an invoice that says 'hosting' and nothing else. Ask what is bundled into it. If the answer is a specific list — backups, updates, SSL, monitoring, a support SLA — you are buying a service and the price may be fair. If the answer is vague, you are paying a lock-in fee wearing a hosting costume.

Then ask the harder question: whose account is the server in? If it sits inside the designer's reseller account, you cannot move it, cannot see the bill, and cannot cancel without them. That is the point of a reseller account.

Who owns the copy and the photos on your site?

By default, the designer does. Under US copyright law, copyright in a work 'initially belongs to the author(s) who created that work,' and it reaches you only through a transfer that 'generally must be made in writing and signed by the owner of the rights conveyed' (Circular 1). Paying the invoice is not a signature on an assignment.

Now the part that surprises people who did put a clause in their contract. Most web design agreements include a 'work made for hire' clause and everyone assumes that settles it. For an independent contractor — which almost every web designer is — it often does not.

The Copyright Office says a specially ordered or commissioned work is a work made for hire only if it satisfies all four criteria: it falls within one of nine listed categories, there is a written agreement, the parties expressly agree it is a work made for hire, and all parties sign. The nine categories are a contribution to a collective work, 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, or an atlas. 'If a work fails to satisfy any of these requirements, it is not a work made for hire' (Works Made for Hire, Circular 30).

A website is not on that list. So a bare work-for-hire clause with a freelance designer can be an empty clause — and when it fails, the copyright does not fall to you. It stays with the designer. This is exactly why competent contracts pair the two: the work is a work made for hire, and to the extent it is not, the designer irrevocably assigns all right, title, and interest to the client. That second half is the half that actually works. Have a lawyer paper it; do not copy a clause off a forum.

Stock assets are their own layer. Photo licenses, premium fonts, and paid plugins are usually issued to whoever bought them. If the designer purchased them on their account, the license may leave when they do — and a site running unlicensed images is a demand letter waiting to happen. Ask for the license receipts, in your name, at handoff.

How do you get your website back from a designer who will not hand it over?

Start with the domain, and know the rules before you call. ICANN's Transfer Policy requires a registrar to give the Registered Name Holder the unique AuthInfo code and remove the clientTransferProhibited status within five calendar days of the request, where the registrar does not offer self-service tools to do it.

The catch you must understand: those protections run to the Registered Name Holder. If your designer's name is in that field, the registrar owes the code to them, not to you. Which is why the WHOIS check above is the first thing you do, not the last.

Where you are the registrant, the policy is firmly on your side. A registrar 'must not refuse to remove the clientTransferProhibited status or release an AuthInfo Code to the Registered Name Holder solely because there is a dispute between the Registered Name Holder and the Registrar over payment.' Non-payment for a pending or future registration period is explicitly listed as a reason a transfer may not be denied. And if the losing registrar simply ignores the request, failure to respond within five calendar days 'will result in a default approval of the transfer.' Silence works for you, not against you.

Then get the sequence right, because getting it wrong costs you two months:

• Transfer the domain to your own registrar FIRST, then change the registrant name. ICANN's policy advises the prior registrant to request the inter-registrar transfer before the Change of Registrant, precisely to avoid the lock in the next line.
• A Change of Registrant triggers a mandatory 60-day inter-registrar transfer lock, unless you opted out of that lock before the change was requested. Do it in the wrong order and your domain is frozen at the designer's registrar for 60 days.
• A domain also cannot be transferred within 60 days of its creation date, or within 60 days of a previous inter-registrar transfer. Fresh domains are stuck for their first two months.
• A completed transfer adds a one-year extension to your registration, so you are not throwing away the time you already paid for.
• Stand up your own hosting and rebuild the DNS zone BEFORE you flip nameservers. Repointing DNS to an empty server is a self-inflicted outage.

The honest verdict on the rest: if the site is trapped in a proprietary CMS with no export, stop negotiating and rebuild. A month of lawyer emails costs more than a new site, and you end the month with the same site you did not own. Take the domain, the content you can legally use, the redirect map, and the analytics, then rebuild on something you control. The same logic applies when you fire an SEO agency without losing rankings — protect the assets that carry equity, and let the rest go.

What should the next contract say?

Four clauses, agreed in writing before you pay a deposit. If a designer will not put all four in the contract, that refusal is your answer about what happens later.

• Registrant is you. The domain is registered in your business's name and email, in an account you control, from day one. Not 'we manage it for you.'
• Copyright assignment. Work made for hire, and to the extent any deliverable is not a work made for hire, all right, title, and interest is irrevocably assigned to you on final payment, including copy, images, design files, and source code.
• Credentials on delivery. Registrar, DNS, hosting, CMS admin, analytics, and tag manager, all in accounts you own, handed over at launch — not on request, not on exit.
• No platform lock-in. The site runs on a platform with a documented full export, and the contract names it. Ask them to demo the export before you sign.
• Stock licenses in your name. Photo, font, and plugin licenses purchased under your account or transferred to you with receipts.

This is the Foundgrove stance and we will put it in writing: the client owns everything. The domain, the codebase, the content, the ad accounts, the links. We work month-to-month with no minimum term, because a website you cannot leave with is not a website you own — and a contract that has to trap you is a contract that is not confident in the work.

If you are not sure which of the five layers you actually control right now, that is the thing to find out this week — before you need to. We build conversion-focused sites you own outright, and if you want a straight read on what you currently hold and what your designer is holding, get my free audit.