Resell, Remix, or Rework? A Plain-English Guide to Template Licenses for US Creators
Photo: Renée Kools, CC BY 4.0, via Wikimedia Commons
Every template purchase is two transactions. You buy a file, and you buy a set of permissions. The file takes thirty seconds to download. The permissions take ten minutes to read and roughly a decade to understand — which is why almost nobody does it, right up until a client asks for the source files or a listing gets flagged.
This is an explainer, not legal advice. If real money or a real dispute is on the line, hire an attorney in your state. But you can learn a lot more than most people bother to.
The license is the product
A template, preset pack, or digital download arrives with terms attached. Those terms typically answer four questions: who can use it, what they can do with it, whether they can hand it to someone else, and what happens if they break the rules. Bundled assets — stock photos embedded in a deck template, for instance — often carry a second license stacked on top of the first.
When a marketplace listing says 'commercial use included,' that's not a magic phrase. It means the seller has granted a specific commercial permission, and you still need to find out how wide it is.
What 'personal use' actually covers
Personal use generally means you're the end user of the finished thing. A wedding photographer editing their own family photos with a preset is personal use. A designer running client galleries through that same preset is usually not.
The confusion comes from the word personal, which people read as 'belongs to me' rather than 'not for business.' A safer mental model: personal use means no revenue changes hands because of the output.
The three verbs, decoded
Resell. This is where most violations happen. Redistribution — handing over or selling the editable template itself, whether alone or inside a bigger bundle — is prohibited in nearly every consumer template license. Buying a pitch deck template and listing it on your own storefront, even heavily restyled, is still redistribution. The test isn't how different it looks; it's whether the buyer ends up with an editable file that does what the original did.
Remix. Remixing means creating a derivative work. Some licenses permit derivatives for your own use but forbid distributing them. Others allow derivatives outright. A minority forbid them entirely, which is where a 'no derivatives' clause shows up. Read that line carefully — it determines whether your heavily customized version can leave your hard drive.
Rework. Reworking is internal modification to produce a deliverable for a client. This is the sweet spot most people never realize they're standing in. If a license permits commercial use, building a client's brand deck on top of a licensed layout and delivering the flattened or exported output is usually fine. Delivering the editable source template is a different question entirely, and often a violation.
The client work question
When you hand a client work built from licensed assets, three things need to be true: your license permits commercial output, your client's use of that output fits the license's scope, and you're not quietly passing along redistribution rights you never had.
Keep a short written note in your project folder — vendor, license type, purchase date, receipt — for anything that ends up in a deliverable. It takes a minute and it's the difference between a confident answer and a panicked one when a client's legal team asks where an asset came from.
A practical habit: add one line to your client contract stating that third-party licensed assets are used under their original terms and those terms survive the project. It sets expectations before anyone starts asking for raw files.
The AI clauses buyers started asking about in 2026
This is the fastest-moving part of every template license right now. Buyers want to know three things, and sellers should answer all three in plain language:
- Can this file be used to train a model or fed into a generative tool? Many licenses now say no outright, or restrict it to the buyer's own internal tools.
- Does AI-assisted output count as a derivative? If you generate a variation from the template inside an AI design tool, does the no-derivatives clause trigger?
- Is AI involvement disclosed? Some buyers want to know whether any part of the deliverable was machine-generated.
If you sell templates, don't wait for the email. Write a short AI section and link it from every product page. "You may not upload these files to a training dataset or use them to generate competing products. You may use AI tools to edit your own copy of this file for your own projects." That's two sentences and it prevents a hundred awkward messages.
Writing terms that actually hold up
If you run your own storefront, the license page is a sales asset, not paperwork. Keep it short, use a permissions table (resell / remix / client work / AI use, each marked yes or no), state the refund position, name the state whose law governs, and give a real contact address for permission requests. Buyers who can understand your terms in ninety seconds are buyers who don't open disputes.
And if you're the one buying? Save the license text with your receipt. Vendors change terms. Your copy of what you agreed to is the only version that matters later.