Who Owns Your Website When You Pay For It? The Answer Nobody Gives You Straight

01

The 10-second answer: who owns your website right now (and why it's probably not you)

You paid the invoice. You approved the design. You've been running the site for two years. So you own it, right? Under U.S. law, probably not — not the parts that matter.

Here's the rule most contracts never spell out: whoever writes the code, draws the design, and types the copy owns the copyright the moment it's created. Paying for the work buys you the right to use it. It does not, by itself, transfer ownership. Per Southtown Web Design, your designer 'owns the source code, website files, visual design, CMS customizations, and HTML/CSS unless you sign a written agreement transferring those rights.' Final payment and ownership are two separate things.

There's one clean exception, and it's the whole point of this guide: a written copyright-assignment clause. Without it, you hold what lawyers call an implied license — permission to use the site, not the deed to it. That distinction stays invisible until the day you want to switch developers, move hosts, or sell the business. Then it decides who has leverage.

The good news: you can find out where you stand in about a minute, and you can fix it with one clause before you pay a cent. Both are below.

02

The legal default: whoever built it owns the code — paying in full doesn't change that

Copyright attaches to original creative work automatically, the instant it's fixed in a file. The author is the owner. For a website, the 'author' is the person or shop who wrote the code, built the layout, and produced the content — not the client who commissioned it.

This trips up smart business owners because it's backwards from how we buy everything else. Buy a truck, you own the truck. Buy a website, you own a license to use the website. The atoms transfer; the copyright doesn't, unless a document says so.

Southtown Web Design states it plainly: by default the designer owns the source code, files, visual design, CMS work, and HTML/CSS even after full payment; the client gets only an implied license. Their fix is a single line: a written assignment of copyright, or a valid work-for-hire clause. Notice the word written. A handshake, an email that says 'it's all yours,' a paid-in-full stamp — none of those move the copyright. A signed clause does.

So when a developer tells you 'you own it because you paid,' they're either being loose with the truth or they don't know the law. Ask one question: is the copyright assigned to me in writing? If the answer is no, you're licensing your own website.

03

'Work made for hire' is a trap: why a website almost never qualifies

People who've heard of 'work made for hire' assume it saves them. It usually doesn't. There are two ways work counts as made-for-hire: it's made by your actual W-2 employee inside their job, or it's a commissioned piece that falls into a short, specific list.

You hired an outside developer, not an employee, so you're in the second bucket. And that bucket is narrow. Per McNeelyLaw LLP, a commissioned work qualifies as work-made-for-hire only if it fits one of nine enumerated categories in the Copyright Act: a contribution to a collective work, part of a motion picture or audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas.

Read that list again. Software isn't on it. A website isn't on it. Source code, page templates, and design files don't fit any of the nine. That's not a loophole — it's the statute. A commissioned website can't be work-made-for-hire, which is exactly why Southtown calls a work-for-hire clause 'rare for websites.'

The takeaway: if your contract leans on 'work made for hire' language to give you ownership of a site built by a contractor, it's probably doing nothing. You need the other mechanism.

04

The one clause that actually transfers ownership: copyright assignment in plain English

A copyright assignment is a written statement, signed by the creator, that transfers ownership of specific work to you. It's the deed. Work-for-hire is a status that a website can't hold; assignment is a transfer that works on anything. For your site, assignment is the tool.

Here's the shape of the clause to demand, in plain terms you can hand your developer:

'Upon receipt of final payment, [Developer] hereby irrevocably assigns to [Client] all right, title, and interest in the copyright to the source code, design files, and content created under this agreement, including the right to modify, host, and transfer the work to any third party.'

Three things make or break it. One: the word assigns, not 'licenses' — a license can be revoked or limited, an assignment is a transfer. Two: it names the specific assets — source code, design files, content — so nothing gets quietly carved out. Three: it includes the right to transfer to a third party, which is what lets your next developer legally touch the code. Add a line requiring delivery of all files on request, and you've closed the loop.

One honest caveat: fonts, stock photos, and licensed plugins usually stay licensed, not owned — that's normal and fine. The assignment covers what your builder actually created for you.

05

Your site is five assets, not one: domain, code, design, content, and analytics

The word 'website' hides the problem. A site isn't a single thing you either own or don't — it's five separate assets, each with its own owner and its own paper trail. Orbit Media Studios breaks it down bluntly: you don't actually own a domain name (you lease it), your host owns the server and leases it to you, the CMS is 'owned by the respective creators and licensed to you,' and the source code is owned by whoever authored it unless an agreement says otherwise.

So a builder can technically be telling the truth that 'you own your website' while three of the five assets sit under their control. The table below shows how ownership shifts by who built the site and how — Yours or Theirs, item by item. Cells marked 'Theirs*' mean it defaults to them unless a signed assignment moves it.

06

Who owns your domain? A 60-second WHOIS/RDAP self-check

Your domain is the one asset you can verify yourself, right now, for free. It's also the one people most often discover is registered to their developer. Do this before you finish reading.

First, the rule that decides it. Under ICANN's Registration Data Policy, effective 21 August 2025, the domain's legal owner is set by the Organization field on the registration. Per Ecenica: if the company name is filled in, 'that organisation is now legally recognised as the Registered Name Holder' — the owner. If the field is blank, the individual registrant listed is the legal owner. Whoever's name is on that record holds the domain, full stop.

Now check yours. As of 28 January 2025, RDAP replaced WHOIS as the definitive standard for looking up gTLD registration data (per Network Solutions), though older WHOIS lookups still work for a quick read. Search 'RDAP lookup' or 'WHOIS lookup,' enter your domain, and read the Registrant Organization and Registrant Name fields.

If you see your business name or your name: good. If you see your developer's name, their agency, or their email on a field you can't access — that's a flag, not a crisis. Domains can be transferred. But it means the person who can move or park your web address today is them, not you. Ask for the registrar login and the auth/EPP code so the registration sits under an account you control.

07

The subscription trap: $249/mo where you rent forever and own nothing

Subscription websites are engineered around the ownership rules above — not to break them, but to keep you inside them permanently. The pitch is friendly: no big upfront bill, no contract, we handle everything. The structure is a rental.

Footbridge Media, a contractor-website company, advertises the textbook version: '$249/Month,' no build fee, month-to-month, custom site included. It is also the example of the model done honestly — asked 'Do I own the website?' their site answers 'Of course,' and states that on cancellation 'we simply provide all of your site files to you.' That is what a good exit clause reads like, and it is worth knowing what one looks like, because plenty of subscription shops do not offer it — in the other version, documented across the industry, the files are deleted and you are locked out. Same monthly model, opposite outcome — and the only way to tell which one you signed is to read the clause.

The number that stings is the multi-year total. At $249/mo, three years is $8,964 — and at the end you own the same nothing you started with. Stop paying, the site can disappear. There's no asset on your balance sheet, no file you can hand a new developer, no leverage.

The single question that separates a fair subscription from a trap: on cancellation, do I get the source code, design files, and content, in a form I can host elsewhere? If yes, it's a service you can leave. If no, you're renting a storefront that the landlord can lock at will.

08

8 red flags you don't own your website (and the 'hostage' scenarios)

None of these means your developer is dishonest. Plenty of good builders default to these setups out of habit. But each one is a point where control sits with them, not you.

Watch especially for the hostage pattern: everything works fine right up until you try to leave. That's when a missing assignment clause or a developer-owned domain turns a routine switch into a negotiation.

• Your contract never mentions 'copyright assignment' — so by default the code and design stay with the builder.
• The domain WHOIS/RDAP record shows their name or agency, not yours.
• You've never been given a registrar login, hosting login, or Google Analytics access in your own account.
• There's a monthly fee with no end date and no clause about what you keep if you cancel.
• The site is locked to a platform you can't export from (proprietary builder, no code handoff).
• Analytics live in the agency's Google account, so your traffic history walks out the door when they do.
• Getting a copy of your own files requires 'asking' — and there's a fee, a delay, or a shrug.
• The builder went quiet or vanished, and you have no files, no logins, and no way to update the site.

09

The pre-purchase ownership checklist — and how to reclaim a site you already have

Before you pay anyone, get these in writing. It costs nothing to ask, and a builder who balks is telling you something. If you already have a site, use the same list as an audit — walk each item and confirm whose name is on it.

Get in writing before you pay: a copyright-assignment clause covering source code, design files, and content; confirmation the domain will be registered in your name/organization; the right to transfer everything to a third-party developer; delivery of all files on request; and analytics set up in an account you own.

To reclaim an existing site: pull your WHOIS/RDAP record and confirm the registrant is you. Ask your current developer for the registrar auth code, the full source and design files, and admin access to hosting and analytics — in writing, with a date. If your contract has no assignment clause, request a signed assignment now; most developers will sign one, because refusing looks worse than agreeing. If the site's trapped on a proprietary platform, plan a clean rebuild you own rather than a fight over files that may not be exportable.

One realistic note: if your original agreement was silent and the developer is unreachable, you may not be able to force a transfer of the copyright. In that case, the cheapest path forward is often a fresh build with the ownership terms fixed from day one.

10

Owning vs. renting: the real 3-year total cost, side by side

Ownership sounds expensive and renting sounds cheap. Over three years, it's usually the reverse. Market pricing sets the frame: freelancers run roughly $500–$3,000 per project, agencies $5,000–$30,000+ upfront plus a $97–$2,000/mo retainer, and DIY builders $16–$49/mo — one industry roundup (JIM) reports the top ends running higher still. The low monthly numbers hide the catch — you're renting.

Compare the two paths that actually compete for a local service business. A common contractor subscription at $249/mo costs $8,964 over 36 months, and the meter never stops — and what you keep on cancellation is that vendor's clause, not a rule of the model. Stop paying and the site can go dark.

Our path: a $2,490 Growth build you own outright, plus the optional $149/mo care plan, is $2,490 + ($149 × 36) = $7,854 over the same three years — and you keep the domain, code, and analytics. That's $1,110 less than the rental, and the difference compounds after year three, when the owned site keeps running whether you renew care or not.

The care plan is optional on purpose. Drop it and your three-year cost is just the $2,490 build; the site still loads, because you own it. With a subscription, month 37 costs the same as month one, forever, and you still can't take the files with you.

11

When renting is genuinely fine — and where our model is the wrong call

Owning isn't automatically right. For some businesses, a rented site is the smarter, cheaper choice, and we'd rather say so than oversell.

A DIY builder at $16–$49/mo is genuinely fine if you're testing an idea, you'll have fewer than five pages, and you're comfortable spending a weekend on it. You'll own little, but you'll spend little, and you can walk away cleanly. A managed subscription is fine if you truly never want to think about the site, you value one throat to choke over ownership, and you've confirmed you can export your content if you leave. Not owning the code doesn't hurt if you never plan to move it.

Where a flat-fee owned build is the wrong call: you need constant hands-on changes every week (a retainer or subscription fits that rhythm better), you have no budget for an upfront build right now, or your business is so early that a landing page and a phone number is all you actually need. Buying an asset you'll outgrow in six months is just a slower way to overspend.

Our model earns its keep when you're an established local business — a roofer, plumber, salon, restaurant — that intends to be around in three years and wants an asset it controls, not a subscription that controls it. If that's not you yet, rent, and revisit when it is.

12

How we hand you the keys: domain, code, and analytics in your name, guaranteed in writing

Our whole model is built to end the ownership question before it starts. One-time price, you own it: Starter $1,490 (one page, live in 3 days), Growth $2,490 (5–8 pages, 7 days), Pro $3,490 (multi-city, 7–10 days). There is no deposit: you see the finished site, approve it, and pay once — and if it misses Lighthouse 95+ or two seconds on a real phone, we fix it or you don't pay.

The ownership terms are in the contract, not the sales pitch. In writing, you get the domain, the code, and the analytics in your name — a real copyright assignment, not an implied license, plus every file and login on handoff. Switch developers next year and the next one can legally open the code. Move hosts and nothing breaks. The WHOIS/RDAP record reads your business, because we register it there.

The care plan is month-to-month and optional: $99/mo for Starter, $149/mo for Growth and Pro. Keep it for updates and monitoring, or drop it — the site is yours either way, because you own the files. We also guarantee the build quality in writing: Lighthouse 95+ on every page and loads under 2 seconds on a real phone.

That's the difference between buying and renting a website. Do the 60-second domain check above. Then ask any builder you're considering the one question that settles it: will you assign me the copyright, in writing? Our answer is yes, and it's already in the contract.