You might not own the theme your 'custom' website was built on
What a license actually hands your designer
"It's fully custom," the designer told you. The homepage looked nothing like a template gallery, so you believed it.
Underneath, a lot of small-business sites that get called custom actually started as a theme or framework the designer bought from a marketplace. A license like that grants the right to use the code inside a project. It does not transfer ownership of the code itself.
The company that built the theme keeps it. Your designer bought a ticket to work with the code, not the deed to it. That ticket comes with conditions attached: a cap on how many live sites it can run on, a rule against reselling it as a standalone product, or a requirement that credit stay somewhere in the footer or the source code.
None of that is a red flag on its own. Buying a license is a normal, sensible way to build a site faster than starting from a blank file. It saves real time on a real project. The problem shows up later, when "custom" quietly becomes shorthand for "fully owned by you," and nobody corrects that assumption before the invoice is paid.
Where the custom work stops and the license starts
Builds that get called custom are custom in a narrower sense than the word implies. The layout, the colors, the copy, the photography, and the way the sections are arranged were built specifically for your business. That part is genuinely yours.
The engine underneath is a separate piece. The grid system, the animation library, the code that makes a menu slide open smoothly, the contact form plugin wired into the page — all of that is often licensed, not built. It came from somewhere else and got dropped into your project as a foundation to build on top of.
This split rarely comes up during a sales call. A designer can walk you through everything they personally built without ever mentioning the borrowed engine holding it up. Both statements can be true at once. You paid for real, specific work, and a chunk of the underlying code was never anyone's to hand over in the first place.
Ask directly which parts started from a blank file and which parts started as a purchased template. Ask it plainly. A designer with nothing to hide will answer quickly, without getting defensive about the question.
A license does not become ownership just because you paid
A designer cannot give you something they never owned. If a theme was licensed to them personally, or to their business, the license terms decide what can happen at handover. Your contract with them does not override those terms.
Some theme licenses allow a one-time transfer to a client's own account, built specifically for this situation. Others forbid it outright, full stop, no exceptions written anywhere in the terms. In that second case, the visible site keeps running fine under your hosting, but the code underneath was never yours to move elsewhere on your own.
A large invoice does not change what a license permits. Money paid to a designer has no bearing on the terms a separate theme company set for its own product, sold to thousands of other buyers under the same conditions.
Reading the theme's own terms, not just the contract your designer sent, is the only way to know which situation applies to your site. Choosing the platform a theme like this actually has to run on is a decision worth making before any specific theme gets picked, since the platform is what decides which license terms even apply in the first place.
How to check what your site is actually built on
You do not need to write code to check this yourself. A handful of free browser tools will look at any live site and name the theme or framework it runs on, version number included. Most take a few seconds to run.
Your hosting account's file manager is another place to look. A folder named after a known theme company, sitting inside your site's files, is a plain signal. Searching the page source for the word "theme" sometimes turns it up directly, right in the code comments.
If you switch designers down the road, this check matters even more. A new designer inheriting a licensed theme needs to know that before quoting you on changes, not after they have already started work assuming everything in front of them was built from nothing.
None of this proves anything went wrong. It tells you, in plain terms, what you are actually dealing with before you take a claim about full ownership at face value.
It also gives you a starting point for the next conversation. Instead of asking a vague question about ownership, you can ask a specific one: this site is running on a known theme, so what exactly does our agreement say about that theme's license. That question is much harder to wave away with a general answer about "full custom work."
What transfers to you, and what stays with the license
When a theme sits underneath your site, ownership does not pass over as one block. It splits into layers. The layout, content, and design choices made specifically for your business should transfer to you outright, the same way they would on any build.
What a clean transfer looks like across a project as a whole covers far more than just the theme question, including the code, the domain, and the files behind everything you see.
The theme license itself stays exactly where it was bought, under whatever terms it was purchased with. A handover clause that names this split specifically is worth far more than one that talks about "full ownership" in vague terms. What that handover clause actually needs to say to cover a licensed element is its own topic worth reading before you sign anything.
Custom graphics laid over a licensed theme raise their own separate question again, with an answer that does not depend on the theme at all. Who actually owns the artwork sitting on top of a build like this has a different answer than the code underneath it.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go