What You Actually Own When You Buy a Template

Ask somebody what they own after buying a website template and the answer is nearly always "the template". It is a reasonable answer and it is wrong about two of the three ways templates are sold. What you own depends entirely on which mechanism you paid into, and the checkout buttons look identical in all three cases, which is presumably not an accident.

Here are the three, described by what is in your hands afterwards.

Model one: you hold files, and a permission attached to them

Buy a theme outright from a marketplace or a theme shop and two separate things arrive. There is a zip, which is a physical fact — it is on your disk, it stays on your disk, no one can reach in and take it. And there is a licence, which is a permission, and permissions have shapes.

The permission is the part people forget they are holding, because it weighs nothing. On Envato's marketplace that permission covers exactly one end product, whichever grade you bought. So the file is unlimited and the permission is not, and since the file is the visible object, the mismatch is invisible until the second site.

This model is the only one of the three where non-payment leaves you with anything durable. Stop renewing an independent theme shop's annual fee and the theme keeps running on your site — what stops is updates and support. That is worth saying plainly because it is often described, by people who should know better, as the theme "expiring". Themes do not expire. Maintenance relationships do.

The ownership test worth applying

One question separates this model from the other two: if the seller went dark tomorrow, would my site still be up? Under model one the answer is yes, indefinitely, with a slowly growing maintenance problem. That is a materially different position from the two below.

Model two: you hold files, and a permission that can lapse

Subscription marketplaces look like model one because you still download a zip. The zip is real. The permission is not the same shape.

Envato Elements grants a licence per project, created automatically at the moment of download. Their own pricing page says that once a subscription ends you can still see what you previously licensed and continue using those items for the completed projects they were licensed for. The word carrying the weight there is "completed".

So: the site you finished last March is fine forever. The identical file, reused next January for a new client, is not covered, even though it never left your machine and nothing on it changed. Using it in a new project requires a live subscription at the time of use.

This is the arrangement that trips up honest people most often, and the reason is purely psychological. Ownership feels like possession, possession feels like the file, and the file is right there. Nothing about the experience of opening that folder communicates that half of what you paid for has quietly ended.

There is one asymmetry in your favour, and it is worth banking. If you downloaded and licensed an item and the author later pulled it from the catalogue, your existing licence survives the removal. Items do get withdrawn — by authors and by the platform, without notice — which is why the sellers' own advice is to download what you intend to use immediately and keep your own copy. Take that advice; it costs nothing and it is the only backup that exists.

Model three: you hold nothing, and that is the correct trade

Pick a template inside a hosted builder and there is no file at any point. There is no download, no zip, no licence document with your name on it. There is a design applied to an account, maintained by the platform, and it exists for exactly as long as that account is paid for.

This reads as the weakest position on the page, and in one narrow sense it is: you cannot take it anywhere, you cannot archive it, and when the subscription ends it does not degrade — it is simply gone, along with the site it was applied to.

But look at what the other two models are buying with their files, because it is not freedom. It is a maintenance obligation they have transferred to you. A downloaded theme is a component you are now responsible for keeping compatible with a platform that updates on its own schedule. A built-in template is a component the platform is responsible for keeping compatible with itself. For most people running most sites, that trade is correct, and pretending otherwise is a hobbyist's mistake dressed up as prudence.

What you can take out is content, never design

Whichever model you are in, the portable part is the same and it is not the part you chose. Text, images you supplied, product data, customer records — these have export paths of varying quality. Layout, typography, spacing, component behaviour: these do not travel. Not between platforms, not in any direction, not at any price.

A template is therefore a commitment to a platform, made at the moment in the process when you are thinking hardest about colour. That mismatch between what the decision feels like and what it is doing is the single most expensive thing in this whole category, and it is why the ranking of template sources leads with the licence rather than the catalogue.

The question clients ask, and the answer that avoids an argument

Every freelancer meets this eventually: the client, a year later, asks for "the template files", meaning they would like to take the design somewhere else.

Under model one you can hand over files, but not necessarily the permission — a marketplace licence covers one end product, and transferring a site to a client is a different act from licensing that client to build a second one. Under model two you can hand over files while the permission stays attached to the completed project it was created for. Under model three there is nothing to hand over at all.

The way to avoid the argument is to answer the question at quoting time rather than at handover. One sentence in the proposal stating which model the project uses, and what the client will and will not hold at the end, costs nothing to write and settles a conversation that otherwise happens at the worst possible moment.

Three sentences to put in a project file

For every template you buy, write these down where the next person will find them:

1. Where the files are, if there are files, and where the licence certificate is. The certificate names the project; in two years it will be the only record of which build the permission attached to.
2. What the permission covers — one end product, unlimited sites, or nothing beyond this account.
3. What happens if payment stops, split honestly into what keeps running and what may still be started.

Three lines. They take a minute, they answer every question anybody will ask you about that template for the rest of its life, and they are almost never written down, which is why this entry exists.

The uncomfortable summary

If you bought a theme outright: you own a file and a narrow permission, and the file outlives the seller.

If you subscribe: you own a file and a permission that is alive only while you pay, and the file will outlive the permission without telling you.

If you are on a hosted builder: you own neither, you have offloaded a real maintenance burden, and you should plan on the assumption that the design is not coming with you.

None of these is the wrong answer. All three are sold as if they were the same answer, and that is the part worth being annoyed about.