Do I Own the Source Code After My Website Is Built?

This is the single most consequential question in any web or app development contract, and it's also the one most business owners never think to ask until something goes wrong, they want to switch developers, or the original agency stops responding. The default answer isn't automatically "yes." Here's how ownership actually works, and exactly what to check before you sign anything.

This article assumes you already know the basics of hiring and buying digital services, covered in our complete guide to business tech guides.

The Default Isn't What You'd Assume

Under standard copyright principles, the person or company who actually writes code generally owns it by default, unless a contract explicitly transfers that ownership to the client. This means simply paying for a website doesn't automatically mean you own the underlying code, unless the agreement specifically says so. Many small business owners assume payment equals ownership. It doesn't, not without the right contract language backing it up.

What "Ownership" Actually Includes

Genuine ownership of a website or app means all of the following, not just one or two of them:

• The actual source code, handed over in a usable format, not locked inside a platform only the agency can access
• The domain name, registered in your name and accessible through your own account, not the agency's
• Hosting account access, or at minimum, the ability to move hosting elsewhere without the agency's cooperation
• Any custom assets, design files, custom graphics, and similar materials created specifically for your project
• Third-party account credentials, payment gateway, analytics, and similar integrations set up under your ownership, not buried in the agency's accounts

Missing even one of these means you don't have full practical ownership, even if the contract says you "own the website."

Common Ways Businesses Lose Effective Ownership

The domain is registered under the agency's account, not yours. This is the most common and most damaging version of this problem. If the domain isn't in your name, the agency effectively controls whether your business keeps its own website address.

Hosting is bundled under the agency's master account. You can technically "use" the site, but you can't move it, back it up independently, or grant access to a new developer without the original agency's involvement.

The site is built on a proprietary, closed platform. Some agencies build on their own internal tooling or a locked-down page builder that only they can edit. Even with full "ownership," you're stuck needing them for every future change.

No source code was ever actually handed over. The site works, but no one ever gave you a copy of the underlying code, meaning you're trusting the agency to keep it safe and available indefinitely.

The Exact Contract Language to Look For

A contract that genuinely protects you should include something close to this:

"Upon full payment, [Business Name] shall own all rights, title, and interest in the source code, design files, and associated assets created for this project. [Agency Name] shall transfer all relevant files, credentials, and access necessary for [Business Name] to independently host, modify, and maintain the deliverables."

The key elements: explicit ownership transfer upon payment, and an explicit obligation to actually hand over usable access, not just a vague ownership claim with no practical transfer attached.

What to Do If You're Not Sure About an Existing Project

If you already have a website or app and aren't sure where things stand, a few direct checks:

1. Check your domain registrar account — log in directly (not through the agency) and confirm the domain is registered under your name and contact details, not theirs
2. Ask directly for a full source code export — a legitimate agency should be able to provide this without resistance or a surprise fee
3. Confirm hosting account ownership — you should be able to log into hosting independently of the agency
4. Review your original contract — check specifically for ownership and handover language, not just a general "we built your website" clause

If any of these checks come back unclear or the agency is resistant to providing straightforward answers, that's worth treating seriously, not dismissing as a formality.