15% off individual templatesCUTER15
Apply it at checkout
Legal

FAQ

Every question that reaches the inbox, answered in one place — buying, licensing, product versions and support.

Last updated: October 6, 2026


Buying

What exactly do I get when I buy?

A ZIP with the full repository — source code, content collections, README and setup documentation. No build output, no obfuscated code: what you get is what the demo is built from.

Do I need an account?

No. Checkout takes an email address and a card, and the download link arrives by email seconds later. There is nothing to log into.

What payment methods work?

Credit and debit cards, PayPal, Apple Pay and Google Pay, through Lemon Squeezy. Prices are in US dollars and local tax is calculated at checkout.

Is my payment data safe?

We never see it. The checkout runs entirely on Lemon Squeezy, who act as merchant of record and hold PCI compliance. See the Privacy Policy for the full picture.

Can I get an invoice for my company?

Yes. Enter your company name and tax ID at checkout and Lemon Squeezy issues a proper invoice. If you already paid without them, write to us and they can be added.

Email cuterdev97@gmail.com from the address you paid with and include the order number. We will help recover the files purchased when possible, but you should keep your own backup after downloading.

Are there discounts?

The promo bar at the top of the site shows whatever is running. Packs are priced separately from individual templates. Discounts and previous orders are not applied retroactively.

Licensing

Can I use a template for client work?

Yes, on as many client sites as you want. Every template license covers unlimited projects, yours or your clients’, and a pack grants that same license for each included template.

Is there a limit on projects?

No. Buy a template once and use it on every site you build with it. The one line you cannot cross: each project has to be a website for someone, not a website builder, theme or other product that lets people make their own sites from the template.

Can I sell a site I built with a template?

Yes, to as many clients as you like. What you cannot do is sell the reusable template source itself, or let a client reuse it for another site. The full rules are in the License.

Can I put my project on GitHub?

Not publicly, because that redistributes the source. Private repositories are fine, including private repos shared with a client or a team. Genuine open source cases get looked at individually — just ask.

Do I have to credit CuterDev?

Never required. Remove every trace of us from the footer if you want. A link back is appreciated and nothing more.

Can my whole team work on it?

The license belongs to the buyer — one person or one company. People working under that buyer may use it on any of the buyer’s projects, but the license and reusable template source cannot be transferred to another person or company.

I bought before the license changed. Does this apply to me?

Yes. Since October 6, 2026 every template is licensed for unlimited projects, and that covers every earlier order as well. Your download may still include the old single-use LICENSE file; the current License replaces it, and you do not need to do anything.

Can my client get the source code?

Yes, the source of their own site, so they or their developers can host and maintain it. They can use it for that site only — not as a starting point for another one, and not to pass on.

Product Version

Are future updates included?

No. Your purchase includes the exact files and version available at checkout. Future versions, patches, framework migrations, new sections and newly released templates are not included.

Will the purchased version change later?

Your order remains for the version you purchased. CuterDev may change products sold in the future, but that does not add files or features to an existing order.

Is future framework compatibility guaranteed?

No. The template is sold for the stack and versions documented on its product page. Future changes to Astro, Tailwind, hosting providers or other third-party tools may require work on your side.

Should I keep a backup?

Yes. Download the files after purchase and keep your own local or private-repository backup of the purchased version.

Technical

What is the stack?

Astro 7, Tailwind v4 and strict TypeScript, with content in Markdown through typed content collections. No UI framework unless a template explicitly needs one, and no runtime dependency you did not ask for.

Do I need to know React or Vue?

No. Templates are Astro components with plain HTML and CSS. If you can read HTML, you can edit them. Adding a React island later is supported by Astro but never required.

Where does the content live?

In Markdown files with typed frontmatter. Adding a page means adding a file; changing a price, a feature list or a post means editing text, not components.

Where can I deploy?

Anywhere that serves static files: Vercel, Netlify, Cloudflare Pages, or your own server. Templates output static HTML by default and ship with configs for the first three. GitHub Pages works too, but only from a private repository — the License does not allow publishing the source publicly.

Is there dark mode?

On the templates that list it, yes, following the system preference and stored per visitor. It is built on the same design tokens, so it stays consistent if you swap the palette.

How is the design customized?

Every template has one tokens file with colors, type and spacing. Change it and the whole site follows. Below that, components are small and commented, so deeper changes are local and safe.

Are the templates accessible?

They ship with semantic markup, visible focus states, keyboard-navigable menus and contrast that passes WCAG AA. Accessibility of what you build on top of them is yours to keep.

What about performance?

Demos score 95+ on Lighthouse across the board: no client JS by default, self-hosted fonts, images optimized through Astro’s pipeline.

Do they support a CMS?

Not out of the box — content is Markdown. Wiring one up is straightforward, and the README of every template sketches the path, but the integration itself is not covered by support.

Support and Final Sales

What does support cover?

Bugs in the purchased version, questions about how it is meant to work, and recovering access to your files. It does not include installation, deploy or hosting work, custom features, your modifications, guaranteed patches, future compatibility or teaching the stack. Details in Support.

How fast do you answer?

Support is offered on a best-effort basis, with no guaranteed response or resolution time. A response does not guarantee a patch, replacement version or custom implementation.

Can I get a refund?

No. Digital purchases are final once the files are delivered. CuterDev does not offer a 14-day refund period. Processor-controlled or legally mandatory exceptions are explained in the Refund Policy.

Can I upgrade from a template to a pack?

You can buy a pack later, but previous purchases are not credited automatically. Each order is separate and final.

Do you take custom work?

Sometimes. Send the scope and the deadline to cuterdev97@gmail.com and you will get a quote or a straight no.

My question is not here.

Write to cuterdev97@gmail.com. That is the whole support system, and it works.

Something here unclear?

These pages try to answer everything up front. If yours is not covered, ask and you get a straight answer.

Write to us