On this page
The version number is the first thing to check
A template built on an old major version of React, Next.js or WordPress can cost more to upgrade than it saved you. That is not a hypothetical warning — it is the single most common reason buyers regret a purchase in this category.
The fix is simple. Every listing on Website Templates & Themes states the framework and version. Read it before you look at the screenshots. If the description does not name a version, ask the seller for the dependency list. A seller who cannot produce one is telling you something.
Why old versions hurt more than they look
A template is not a finished website. It is a starting point that has to survive your hosting, your plugins and your updates. When the underlying framework moves on, the template does not move with it. You inherit the gap.
For a React or Next.js template, that gap shows up as build errors, deprecated APIs and packages that no longer resolve. For a WordPress theme, it shows up as functions removed in later core releases, or a page builder that stopped receiving updates two years ago. For a Shopify theme, it shows up as Liquid syntax that no longer matches current theme requirements.
The upgrade maths
Ask what the upgrade actually involves. Sometimes it is a version bump in a config file. Sometimes it is rewriting every component because the template relied on patterns the framework has since replaced. The second kind is where the money goes.
What a template licence usually covers
The default licence on this marketplace is commercial. That is broader than many buyers assume, and narrower than others assume.
A commercial licence lets you build client websites and company websites. You can charge for that work. What you cannot do is resell the template itself or redistribute its source. If you want to ship the template inside a product you sell to end users, you need an extended licence.
The licence is printed on the listing and in your receipt. Read both. If the listing's licence terms and your intended use do not line up, the time to notice is before payment, not after you have built something on top of it.
Where buyers misjudge it
The common mistake is treating a template purchase as a purchase of the code itself. It is a licence to use the code in defined ways. That distinction matters most when a project grows — a client asks for a white-label version, or you want to bundle the theme into a SaaS product. Those are different licences, and the original one will not stretch to cover them.
Fonts, images and plugins are often not included
This is the gap between the demo and the download, and it catches people every time.
Preview images, premium fonts and paid plugins in a demo are frequently placeholders. You replace them with your own licensed copies. The demo looks the way it looks partly because of assets you are not buying.
Sellers must disclose third-party assets, so look for the 'included / not included' section before purchase. If it is missing, treat every asset in the demo as excluded until the seller says otherwise in writing.
What typically falls outside the download
- Photography and illustration used in the preview
- Premium typefaces loaded by the demo
- Paid plugins or extensions the demo relies on
- Icons from commercial icon sets
Each of those carries its own licence, and none of them transfer to you with the template. Budget for them separately, or plan to substitute free alternatives.
Open-source licences travel with the code
If a template incorporates open-source components, those licences come with it. They may impose attribution requirements or other conditions that sit alongside your commercial licence. This is another reason to read the dependency list rather than skim it.
Read it before you run it
The pattern across all three problems is the same: the information exists, and buyers skip it because the demo is convincing.
A practical order of operations when you buy a website template:
- Confirm the framework and its major version against your own stack.
- Request the dependency list if it is not in the description.
- Read the licence on the listing and match it to your intended use.
- Check the 'included / not included' section for third-party assets.
- Confirm the delivery method — download, repository access, or manual handover.
That takes ten minutes. It is cheaper than discovering the problem after you have built on the foundation.
What you cannot check before buying
Some things are only knowable after delivery, and it is worth being straight about that.
You cannot verify code quality from screenshots. You cannot confirm that the template runs cleanly in your specific hosting environment until you run it. You cannot know whether the seller responds to support requests at the speed you need until you send one.
What you can do is check the template runs before you confirm delivery. If your order uses download delivery, the files unlock the moment your payment is protected, so you have a window to test before the transaction closes. Use it.
Signals worth weighing in a listing
A listing that names exact versions, lists dependencies, states the licence plainly and separates included from excluded assets is doing the work. A listing that shows a polished demo and says little else is asking you to trust the parts that matter most.
Neither is proof of quality. But the first gives you something to check against, and the second gives you nothing.
Questions buyers ask
Are the templates on Attesar original?
Yes. Sellers must be the author of the template or hold a written licence that permits resale, and every listing is reviewed by our team before it is published. Templates that reuse other people's work are removed.
Can I use a template for client projects?
With a commercial licence, yes — you can build client and company websites. You cannot resell or redistribute the template itself. Each listing states its licence, so check that it matches what you intend to do with the finished site.
How do I receive the files?
Files unlock for download the moment your payment is protected, or the seller invites you to a repository. Check the template runs before you confirm delivery, particularly if you are working with a next.js template or a WordPress theme that depends on specific server configuration.
What if the template does not work as described?
Open a dispute from the order page before confirming delivery. Our team reviews the evidence and either resolves it with the seller or refunds you. Raising it before you confirm is what keeps the option open.