Astro itself is MIT licensed, but every theme has its own license, and that license decides what you may do with the code on client sites. MIT is the safest: keep the copyright notice and you are fine. GPL and AGPL add source-sharing duties, a repo with no license is not free to use, and commercial themes limit projects and ban resale. Images, fonts and icons often carry their own licenses, and that is where most trouble starts. We sell themes too, and compare our terms with three other stores below.
Not legal advice
For a large client contract, a product you plan to sell, or GPL/AGPL code in commercial work, ask a lawyer who knows software licensing in your jurisdiction.
Which Astro theme licenses are safe for client work?
| License | Use on client sites | Modify | Hand repo to client | Resell the theme as a theme | Main obligation |
|---|---|---|---|---|---|
| MIT | Yes | Yes | Yes | Yes | Keep the copyright and license notice with the code |
| GPL v3 | Yes | Yes | Yes, but it stays GPL | Yes, under GPL only | Share source under GPL when you distribute it |
| AGPL v3 | Possible, with care | Yes | Yes, but it stays AGPL | Yes, under AGPL only | Offer source of modified versions to network users |
| Apache 2.0 | Yes | Yes | Yes | Yes | Keep the license and any NOTICE file, mark changes |
| No license | No | No | No | No | All rights reserved by the author |
| Commercial (typical) | Yes, within project limits | Yes | Usually yes, as a finished site | No | Stay within project limits, no redistribution |
Can you use an MIT theme commercially?
Yes. MIT is the most common license for free Astro themes and starter themes, and it allows commercial use, including paid client sites. It is short and permissive. You may use, copy, modify, merge, publish, distribute, sublicense and sell copies of the software. The one condition is that the copyright notice and the permission notice must be included in all copies or substantial portions of the software.
In practice, for a client site:
- Keep the
LICENSEfile (orLICENSE.md) from the theme in your project repository. Do not delete it or replace it with your own license. - If you add your own license or copyright for your changes, add it alongside the original notice rather than overwriting it.
- When you hand the repository to the client, the original
LICENSEfile goes with it. - A visible footer credit is not an MIT requirement. Some authors ask for one as a courtesy. That is worth honoring when you can, but it is not a condition of the license.
MIT also comes with no warranty. If the theme has a bug that costs your client money, the license says the author is not liable. That is one reason to check how actively a free theme is maintained before you build on it.
You may also meet MIT-0 (MIT No Attribution). It is the same license without the notice condition, so you do not even have to keep the copyright line.
Our free Lite themes, Folex Lite, Techlo Lite and Lumio Lite, are MIT licensed. The LICENSE.md file in each repository is the authoritative version. You can find more options in our roundup of free Astro themes and themes and Astro starter themes. Our Astro agency themes and Astro portfolio themes lists name the license of every free theme they cover.
GPL and AGPL on a website theme
GPL and AGPL are โcopyleftโ licenses. You can use and modify the code, but when their obligations are triggered, you have to make the source available under the same license. Few Astro themes use them, but you will meet them in some starters, components and libraries, so it pays to know where the lines are.
GPL v3: triggered by distribution
The GPLโs obligations apply when you convey (distribute) the code. According to the GNU GPL FAQ, you can run a modified GPL program on your own server without releasing your changes, because you are not distributing it. For a website theme, though, a few common situations count as distribution:
- Handing the repository to the client. If you give the client the source, you are distributing it. The client receives it under the GPL, with the same rights to copy, modify and share it. You cannot add terms that take those rights away.
- JavaScript sent to the browser. The GPL FAQ says that when GPL-covered programs, often JavaScript, are sent to visitorsโ browsers, the source for those programs must be released to users under the GPL. Astro ships little JavaScript by default, but any GPL scripts the theme does send to the browser fall into this category.
- Packaging the site as a theme for other clients or for sale. That is plain redistribution, and your version must stay GPL.
What GPL generally does not do is take over your clientโs content. The FAQ says a programโs output is generally not covered by the programโs license. Blog posts, page copy and photos your client supplies stay theirs. Where your own code ends and the GPL code begins can get legally murky, which is one reason to get advice before using GPL code in a commercial build.
AGPL v3: triggered by network use
The AGPL adds a clause aimed at software used over a network. If you modify AGPL code and users interact with it over a network, you must offer those users the source of your modified version. A website that runs modified AGPL code on the server, such as SSR routes, API endpoints or server functions, is the textbook case.
For client work, that means:
- Assume you will have to publish the modified source, and make sure the client agrees to that before you start.
- Check any AGPL dependency your SSR code relies on, not just the theme.
- If the client expects a closed codebase, choose something else.
The practical rule for agencies
GPL and AGPL themes can be used legally, but they shift obligations onto you and your client, and the client usually did not sign up for that. Unless you have a reason to use copyleft code and the client understands the terms, an MIT-licensed or commercial theme is the simpler choice. And again: this is the area where a short conversation with a lawyer is worth it.
Coming from WordPress: why its themes are GPL
If you have built WordPress sites, you may expect every theme to be GPL. That comes from WordPress itself: it is released under GPLv2 or later, and WordPress.org states that it considers themes and plugins derivative works that inherit the GPL, while admitting there is โsome legal grey areaโ (WordPress license page). Astro is MIT licensed and has no such rule, so an Astro theme can use any license its author picks. Check each one instead of assuming.
What if an Astro theme has no license?
A public GitHub repository is not the same as an open-source one. GitHubโs documentation puts it plainly: without a license, the default copyright laws apply and the author keeps all rights to the source code. Nobody else may legally reproduce, distribute or create derivative works from it.
So a theme with no license means:
- You can read the code and learn from it.
- You cannot legally copy it into a client project, modify it, or publish a site built on it.
- โItโs on GitHubโ or โthe README says feel free to use itโ is not a license. An informal sentence may show intent, but it does not clearly say what you can and cannot do.
If you really want to use an unlicensed theme, open an issue or email the author and ask them to add a license file. Until they do, treat it as off-limits for client work.
Images, fonts and icons are licensed separately
The theme license covers the code the author wrote. A theme can also bundle or point to assets made by other people, each with its own terms. This is where most real problems come from.
Images and illustrations. Demo photos may come from stock libraries, the authorโs own work, or AI tools, and some are included only so the demo looks finished. A theme license does not automatically give you rights to use every demo image on a production site. Unless the documentation clearly says the images are cleared for your use, replace demo images with assets you or your client have licensed. This is usually needed anyway, since a client site should not look like the demo.
Fonts. Many web fonts, including most Google Fonts, use the SIL Open Font License, which permits commercial use and self-hosting. Commercial fonts from foundries often have separate web, desktop and app licenses, sometimes priced by page views. Check src/config/fonts.json or wherever your theme declares fonts, and confirm each familyโs license. If a client asks to swap in their brand font, confirm they hold a web license for it.
Icons. Icon libraries have their own licenses. For example, Lucide, which several Astro themes use, is under the ISC License, and some of its icons derived from Feather are under MIT. Both are permissive, but both expect their notices to be kept with the code. Commercial icon packs may forbid use in themes you redistribute.
Logos and brand marks. Placeholder logos and client logos in a demo are not yours to reuse. Swap them out.
npm dependencies. Your node_modules folder can contain many packages, each with its own license. Most are permissive, but it is worth scanning for copyleft or unusual licenses on larger builds (see the checklist below).
What commercial theme licenses usually allow
Paid themes use custom licenses, so you have to read each one. Most share a similar shape:
- Personal and commercial use. You can build sites for yourself and for paying clients.
- Modification. You can change the code, design and content as needed.
- Project limits. One purchase covers a set number of projects, often one, with higher tiers or extended licenses covering more.
- No redistribution or resale. You cannot sell, share or give away the theme itself, including as a modified theme, a starter kit, or part of a theme bundle.
- No sublicensing. You cannot grant others rights to the theme as a product.
- Client handoff. Most allow you to hand the finished site over to the client who paid for it. Check whether the client then needs their own license for future projects with the same theme.
- Attribution. Some require a credit link, some make it optional.
What does โprojectโ usually mean?
This is the term that causes most confusion, and sellers define it differently. Common readings include one website on one domain, or one end product for one client. The edge cases are where it gets unclear:
- A staging site plus a production site for the same client
- The same site in several languages on separate domains
- Two related sites for one client, such as a main site and a careers microsite
- A client site you rebuild from scratch a few years later
- A white-label build for another agency
If the license does not answer your exact case, ask the seller before you start, and keep the reply in writing. A short email now beats an awkward conversation after launch.
How Astro theme stores word their licenses
The general shape above holds, but the details differ by store. This is what four stores that sell Astro themes said on their own license or pricing pages when we checked on October 21, 2026, and the pages still said the same on November 1, 2026. Terms change, so read the current page before you buy.
| Store | Who is covered | Projects | Client work | Resale or redistribution | Source |
|---|---|---|---|---|---|
| Getastrothemes (us) | Not stated per seat | Single theme 5; All Access Essential 1, Pro 10, Business unlimited per theme. Staging and preview copies count as the same project | Allowed, including handing the finished site to the client | Prohibited, including public repositories of the source | License |
| Lexington Themes | Personal and Studio: 1 seat; Team and Agency: 10 seats, where a seat is one named person | Unlimited, โfor yourself or for clientsโ | Allowed, white-label, no attribution | Not covered on the pricing page | Pricing |
| Cosmic Themes | Personal: one individual; Team: up to 20 employees and contractors | Unlimited end products | Allowed, including sites the client owns | Prohibited, including making a theme or theme from the items or using them in a site builder | License, last updated Nov 14, 2024 |
| Themefisher (premium) | Not stated per seat | One theme per website; more sites need more licenses or a bundle | Personal and commercial projects | Prohibited | License |
Two differences matter most for client work. First, โprojectsโ ranges from one website per purchase to unlimited, so count your sites before choosing a plan. Second, seat-based licenses (Lexington, Cosmic Themes) count people, so a freelancer who later hires a developer may need a different tier. Themefisherโs free themes and our free Lite themes use the MIT License, covered above.
The Getastrothemes license in short
Here is a summary of our terms. The license page is the authoritative version.
Premium themes:
- Use for personal and commercial projects.
- Modify the themes as needed for your project.
- Build a site for a client and hand it over. The client can use and edit that site.
- Reselling, redistributing or sublicensing the themes is prohibited, and so is publishing the source code in a public repository.
- Attribution is appreciated but not required. You can remove existing copyright links without asking.
- The number of projects you can build with each theme depends on whether you buy it on its own or get it with an All Access Pass plan:
| Plan | Projects per theme |
|---|---|
| Single theme | 5 |
| Essential | 1 |
| Pro | 10 |
| Business | Unlimited |
A project is one website or web app. Local, staging and preview copies of the same site count as that one project.
Free Lite themes are MIT licensed, as covered above, and the LICENSE.md in each repository is the authoritative text.
Figma files, where provided, follow the same rules as premium themes: personal and commercial use and modification are allowed, while reselling, redistributing or sublicensing the Figma files is prohibited.
We do not try to list every edge case here. If you are not sure whether a multilingual setup on several domains, a white-label build or anything else counts as a separate project, contact us before you build and we will give you an answer in writing.
Five checks before you clone a theme
Run these checks before you clone a theme into a client project. They take five minutes.
1. Look for a LICENSE file in the repo root
GitHub detects license files in the repository root, usually named LICENSE, LICENSE.md or LICENSE.txt. When it recognizes one, the license name shows in the repo sidebar. Open the file anyway and read it. A recognized license with an added clause, such as โno commercial useโ, is not the standard license anymore.
2. Check package.json
Astro themes are npm projects, so package.json often has a license field:
{
"name": "my-astro-theme",
"version": "1.0.0",
"license": "MIT"
}
If package.json and the LICENSE file disagree, ask the author which one applies. If there is no LICENSE file and only a license field, treat that as a signal to confirm with the author before relying on it.
3. Read the README and docs for asset notes
Look for sections on credits, images, fonts or third-party assets. Some themes say demo images are for preview only. Others list where each asset came from.
4. Check the assets themselves
Browse public/ and src/assets/ for images and font files, and check the font configuration. Note anything you will keep on the live site and confirm its source.
5. Scan dependency licenses
For a larger build, list the licenses of installed packages. One option is the license-checker package:
npx license-checker --summary
To flag copyleft licenses specifically:
npx license-checker --onlyAllow "MIT;ISC;BSD-2-Clause;BSD-3-Clause;Apache-2.0;0BSD;CC0-1.0"
The second command fails if it finds a license outside your allow list, so you can review those packages one by one. It reads license data from package metadata, so treat the output as a starting point, not a final answer.
Pre-launch license checklist
Run through this before you hand a site to a client:
- I know the themeโs license and have read the actual license text, not just the label.
- The themeโs
LICENSEfile is still in the repository (MIT, GPL, AGPL and similar). - If the theme is commercial, this site fits within my project limit.
- I have confirmed in writing any edge case, such as staging, extra domains or white-label work, that the license does not clearly cover.
- Every demo image, illustration and placeholder logo has been replaced, or I have confirmed it is cleared for production use.
- Every font on the site is licensed for web use, including any brand font the client supplied.
- Icon sets and their notices are kept as their licenses require.
- I have scanned dependencies for copyleft or unusual licenses.
- If any GPL or AGPL code is in the build, the client knows and agrees to the obligations.
- I am not reusing the theme as a theme I sell or give to other people.
- My client contract says what the client receives (finished site, source code, assets) and what licenses apply to it.
- I have kept copies of license files, receipts and any written answers from sellers in the project folder.
Pick a license you can explain to the client
MIT works when you are happy to maintain the code yourself. A commercial theme works when you want a finished, maintained base with clear project limits. Unlicensed code is out, and GPL or AGPL needs a deliberate decision.
If you want MIT, start with one of our free Lite themes. If you build several client sites a year, the All Access Pass gives you every premium theme, with project limits per theme set by plan. You can browse them all on the themes page. For setup once the license is sorted, see our guide to installing and customizing an Astro theme.