What is a commercial template licence?

A licence that grants the right to use a design template in a project that earns money — a client site, a paid product, an ad-supported blog. It sits alongside copyright: the designer keeps ownership, you get defined usage rights. Scope, seat count and whether you can charge clients vary, so read the licence text.

Is a free template licence enough for commercial use?

Not always. Free templates commonly ship under licences that limit use to personal or non-commercial projects, or require attribution and forbid resale. Others, such as GPL-licensed WordPress themes, do permit commercial use. The licence file — LICENSE, LICENSE.txt or the vendor's terms page — is the authority, not the price tag.

How do I verify which licence a template ships under?

Check the download for a LICENSE or LICENSE.txt file, read the vendor's terms page, and look at the item's metadata where you bought it. Fonts, icons and stock photos bundled inside usually carry their own separate licences. Record the licence name, version, purchase date and order reference with the project files.

Can one commercial licence cover multiple client websites?

Usually no. Most marketplace licences, including the common Regular and Extended tiers, permit one end product per purchase. An Extended licence typically adds the right to charge end users, but still limits you to a single installation or project. Agencies building several sites normally buy a licence per project, or negotiate a broader agreement directly with the author.

What is the difference between a Regular and an Extended licence?

On marketplaces like ThemeForest, the Regular licence covers one end product that is not charged for, while the Extended licence covers an end product where users pay — a paid app, a subscription, or work billed to a client. Both limit you to one end product. Terms change, so confirm against the vendor's current documentation.

What happens if I use a template without a commercial licence?

You are in breach of copyright. Typical outcomes are a takedown notice, a demand for retroactive licence fees, a DMCA complaint to your host or registrar, and in serious cases litigation. The site may be pulled offline while the dispute runs. The fix is to buy the correct licence or replace the design, then document it.

Do I own the copyright after buying a commercial licence?

No. You buy usage rights, not ownership. The author retains copyright unless the agreement says otherwise with an explicit assignment. That means you cannot resell the template itself, sublicense it, or register it as your own work. Check the terms for assignment wording if ownership matters to you.

Can I modify a licensed template and use it commercially?

Generally yes — most licences permit modification for your own end product, and this is normal practice. What stays restricted is redistribution: you cannot repackage the modified template and sell or share it as a template. Some licences also restrict removing attribution. Document your changes and keep the original licence on file.

Are GPL WordPress themes safe for commercial projects?

WordPress itself is GPLv2, and themes distributed publicly generally inherit that. GPL permits commercial use and modification, and requires that derivative code you distribute also carries GPL. The catch is bundled assets: images, fonts and icon sets inside a theme often sit under separate, more restrictive licences. Check each one.

What are the alternatives when a template licence does not fit?

Buy exclusive rights or a broader agreement directly from the author, commission a custom design, or build on permissively licensed foundations where the terms allow commercial use. Custom design costs more upfront but removes per-project licence accounting and attribution constraints. If you want the licence and the build reviewed before launch, our team can help — start at /contact.

Commercial Template Licence: What You Can Legally Ship

Using someone else's design template commercially

A commercial template licence is the permission that lets you use someone else's design — a theme, a UI kit, a Figma file — in paid work. It sets how many sites or apps you may use it on, whether you can charge clients, whether you may modify it, and what you must keep in the files.

Key Takeaways

"Commercial" on a marketplace listing rarely means unlimited. It usually means one end product, one client, one deployment.
Licences travel with the assets inside the template. Fonts, stock photos, icons and illustrations are licensed separately and are often not covered by the template's own terms.
Review the terms before design sign-off, not before launch. Swapping a hero image at mockup stage is cheap; rebuilding a shipped product is not.
Keep the receipt and a copy of the licence text inside the project repository. In a dispute, you carry the burden of showing what you bought and when.
GPL-licensed themes and plugins are genuinely free to use commercially, but distribute modified code and you inherit the obligation to share those changes.
If the client is meant to own the deliverable, they should hold the licence or a written assignment. Otherwise they are running software they cannot prove they are allowed to run.

The five stages where a template licence gets decided, from sourcing the file and reading its terms to the handover that transfers obligations to your client.

What does a commercial template licence actually grant?

A licence is a grant of rights, not a sale of the file. The vendor keeps copyright and gives you permission to use the design inside stated limits: number of end products, whether the end user pays, whether you may modify, and whether you may redistribute the source. Anything not granted stays reserved to the vendor.

Why does the licence matter after launch, not at download?

Licence problems surface late. A takedown notice, a stalled app-store review or a client procurement questionnaire arrives months after go-live, when the site carries real traffic and revenue. By then the cheap fix — replacing one asset — competes with the expensive one: rebuilding templates, re-licensing fonts, and explaining the delay.

When do you need a commercial or extended licence, and when don't you?

You need commercial terms the moment money changes hands or a client's brand ships. You don't need an extended tier for one internal tool, a prototype or a personal site. Extended licences exist for work you charge for at scale, or where the end user can't be named — an app sold to many buyers.

How the common template licence tiers map to the work you are doing, from a one-off mockup to a product you sell repeatedly.

How does a template licence work in practice?

Mechanically, a licence is a scope plus a set of restrictions. Scope covers seats, domains, end products and duration. Restrictions typically ban redistributing the source files, reselling the template itself, and using it inside a competing template product. Some vendors require a credit line or forbid removing it.

How do you check a template licence before you ship?

Work through this before the first line of customisation, while replacing an asset is still a design decision rather than an incident. Store the output with the project so the next developer inherits the answer instead of the question.

Find the licence document itself, not the sales page. Copy the terms or download the PDF and commit it to the repository.
Record the licensor, the item identifier, the version you downloaded and the purchase date. A receipt with no item ID proves very little.
List every asset bundled inside the template: fonts, photography, icons, illustrations, video and any third-party plugin.
Map each asset to your actual use — how many domains, how many apps, does the end user pay, is the client named on the licence.
Check fonts separately. A desktop font licence usually does not cover webfont embedding; you need a webfont or app licence for that.
Read the attribution and credit-removal clauses. If removing the footer credit is prohibited, decide whether you can live with it or must swap the asset.
Write a one-page licence summary into the project README: what is covered, what was replaced, and what the client now holds.

What breaks in production when a licence is wrong?

Three failures recur. A takedown notice forces an asset offline while you argue about scope. A desktop-licensed font gets embedded as a webfont, and the foundry invoices the client or demands removal. An app-store review stalls because the submitter cannot show a licence for bundled artwork. None of these arrive on launch day.

The nastier version is quiet. Nothing breaks, the site runs for two years, and then the client asks for the source files so they can move to another developer. If the licence sits in your account and permits one end product only, the handover is now a commercial negotiation you did not budget for.

Do fonts, photos and icons need their own licence?

Almost always, yes. A template's terms cover the layout and code the vendor wrote, not the third-party assets inside it. Stock photography may be royalty-free for web use but restricted for print or merchandise. Icon sets are often MIT or CC-BY, where attribution is the price of use. Map each one separately.

How do you verify compliance before handover?

Verification is a checklist, not a feeling. Confirm every asset's licence file is in the repository, that domain and product counts sit inside scope, that required credits are present, and that the client holds the licence or a written assignment. Re-run the check after any template upgrade — new versions sometimes ship new assets.

A project timeline showing that template licence questions typically arrive long after launch, at the point where changing the design is most expensive.

What does licence compliance cost in time and risk?

Done early, licence review costs a few hours on a typical build: reading the terms, replacing one or two fonts, and buying an extended tier where the scope genuinely demands it. Done late, it costs a rebuild, a legal conversation and a damaged client relationship. The asymmetry is the whole argument for doing it first.

Which mistakes do teams repeat?

The same four mistakes show up on project after project, and they are all cheap to avoid. Most come from treating the licence as paperwork rather than as part of the build specification, which is why they tend to be caught by someone outside the team.

Buying one commercial licence and reusing the template across three client sites.
Assuming "commercial" covers fonts and photos that ship inside the download.
Leaving the licence in the developer's account at handover, so the client cannot prove anything.
Removing a required credit line because it looked untidy in the footer.

What does this look like on a real project?

Picture a trekking operator in Kathmandu who wants a booking site before the season. You buy a travel theme, customise it, launch, and everyone is happy. A year later they expand into two more brands and ask you to reuse the same design. That is the moment the single-end-product clause stops being theoretical.

The same project usually hides a second issue: the theme ships with a display font that was licensed for desktop use only, and it has been embedded as a webfont since launch. Both problems are solvable — buy the extended tier, swap the font for a properly licensed webfont — but only one of them is cheap, and only if you find it early. We have seen this exact pattern on more than one build, and it is the reason our website design work starts with an asset and licence inventory before any Figma file is opened.

What are the alternatives to a marketplace template?

You have four realistic paths, and the right one depends on how much you value owning the design outright. A template is the fastest route to something decent; a bespoke design system is the slowest but leaves nothing licensed to anyone else. The middle options trade time for control.

Option	Licence position	Fits when	Main risk
Marketplace template	One end product, per purchase	You need to launch quickly on a modest budget	Reuse across clients breaches the terms
Extended-licence template	Broader product and resale rights	You sell the same product to many buyers	Higher cost, still no ownership of the design
Open-source UI kit	MIT or GPL, free to use	Your team can assemble and maintain components	GPL obligations if you distribute modified code
Bespoke design and build	You or the client own it	The brand matters, or the product is the business	Slower and more expensive up front

If you are weighing a licensed template against building from scratch, our breakdown of custom software versus off-the-shelf options covers the same trade-offs from the software side, and the design contract clauses worth agreeing up front are the natural companion to a licence review.

In short: a commercial template licence is a scope document, not a receipt. Read it before design sign-off, inventory every bundled asset, record the terms in the repository, and make sure the client holds the licence or a written assignment at handover. If the deliverable is something they will own, hand over the paperwork with it. Our team can help you review licensing before you commit.

People also search for

These are the questions teams ask once they realise a template licence affects the build, not just the invoice. Each one leads into the commercial decisions that sit around a design project, from quoting to handover.

Get the licence review done at the start and it costs you an afternoon. Leave it until a client asks for the source files and it costs a rebuild. If you want a second pair of eyes on the terms before you sign or ship, talk to our team, or look at work we have delivered to see how we handle handover.

Frequently asked questions

A licence that grants the right to use a design template in a project that earns money — a client site, a paid product, an ad-supported blog. It sits alongside copyright: the designer keeps ownership, you get defined usage rights. Scope, seat count and whether you can charge clients vary, so read the licence text.
Not always. Free templates commonly ship under licences that limit use to personal or non-commercial projects, or require attribution and forbid resale. Others, such as GPL-licensed WordPress themes, do permit commercial use. The licence file — LICENSE, LICENSE.txt or the vendor's terms page — is the authority, not the price tag.
Check the download for a LICENSE or LICENSE.txt file, read the vendor's terms page, and look at the item's metadata where you bought it. Fonts, icons and stock photos bundled inside usually carry their own separate licences. Record the licence name, version, purchase date and order reference with the project files.
Usually no. Most marketplace licences, including the common Regular and Extended tiers, permit one end product per purchase. An Extended licence typically adds the right to charge end users, but still limits you to a single installation or project. Agencies building several sites normally buy a licence per project, or negotiate a broader agreement directly with the author.
On marketplaces like ThemeForest, the Regular licence covers one end product that is not charged for, while the Extended licence covers an end product where users pay — a paid app, a subscription, or work billed to a client. Both limit you to one end product. Terms change, so confirm against the vendor's current documentation.
You are in breach of copyright. Typical outcomes are a takedown notice, a demand for retroactive licence fees, a DMCA complaint to your host or registrar, and in serious cases litigation. The site may be pulled offline while the dispute runs. The fix is to buy the correct licence or replace the design, then document it.
No. You buy usage rights, not ownership. The author retains copyright unless the agreement says otherwise with an explicit assignment. That means you cannot resell the template itself, sublicense it, or register it as your own work. Check the terms for assignment wording if ownership matters to you.
Generally yes — most licences permit modification for your own end product, and this is normal practice. What stays restricted is redistribution: you cannot repackage the modified template and sell or share it as a template. Some licences also restrict removing attribution. Document your changes and keep the original licence on file.
WordPress itself is GPLv2, and themes distributed publicly generally inherit that. GPL permits commercial use and modification, and requires that derivative code you distribute also carries GPL. The catch is bundled assets: images, fonts and icon sets inside a theme often sit under separate, more restrictive licences. Check each one.
Buy exclusive rights or a broader agreement directly from the author, commission a custom design, or build on permissively licensed foundations where the terms allow commercial use. Custom design costs more upfront but removes per-project licence accounting and attribution constraints. If you want the licence and the build reviewed before launch, our team can help — start at /contact.