WordPress theme GPL licensing, explained plainly

01What the GPL is, in plain terms

The GPL — the GNU General Public License — is a free-software license that grants anyone who receives the code four freedoms: to use it, study it, modify it, and redistribute it. "Free" here means freedom, not necessarily price. You are free to do those things, whether or not you paid to get the code.

It matters to WordPress themes because WordPress itself is licensed under the GPL. That single fact ripples outward: software that builds closely on GPL code is generally expected to carry the same license. For most themes, that means they are GPL too.

The freedom that surprises people is redistribution. Once you have a GPL theme, the license lets you share the code onward. You can't stop others from doing the same with what you give them. That is by design — it is what keeps the code free as it travels.

The freedom people forget is modification. A GPL theme is yours to change without asking permission. You can fork it, strip it, rebuild it — and that right is part of why GPL software tends to outlive any single author. If they walk away, the code can be carried on by someone else.

02Why almost every WordPress theme is GPL

If you have shopped for themes, you have seen "100% GPL" plastered on listings and wondered whether it is a feature or a formality. It is mostly a consequence — of how the GPL treats software built on top of GPL software.

The inheritance, in one idea

The GPL is what's often called a "copyleft" license: derivative works built on GPL code are generally expected to be released under the GPL as well. WordPress is GPL, and a theme is software that runs as part of WordPress, so the widely-held position in the community is that the theme's PHP inherits the GPL.

The nuance about assets

• PHP code is the part most directly tied to WordPress, and is the clearest case for inheriting the GPL.
• CSS, images, and JavaScript are sometimes argued to be separable, and some authors license those parts differently — this is a genuinely debated, fact-specific area.
• "Split licensing" is the name for a theme that GPLs its PHP but puts a different license on its assets. You'll see it, and it is not automatically wrong.

For everyday purposes, the practical reality holds: the functional code of a WordPress theme is almost always GPL, and authors who want to be on the official theme directory must license it that way. The "100% GPL" badge is reassuring buyers that there's no hidden restrictive license lurking.

03What you're actually paying for

Here is the apparent paradox: if a premium theme is GPL and the GPL lets people redistribute it, how do authors charge for it? The answer is that you are not buying the license — you are buying a relationship.

• Updates. Themes need ongoing work — security patches, compatibility with new WordPress versions, bug fixes. Paying gets you a pipeline of those updates delivered to your site.
• Support. When something breaks, access to the people who wrote the code is worth real money. The GPL gives you the code; it does not give you the author's time.
• Convenience and trust. Buying from the author means a clean, complete, malware-free package and a clear update channel — not a copy of unknown provenance.
• Funding the work. Your payment is what keeps the author developing the theme at all. The commercial layer is what makes free-licensed software sustainable.

So the GPL and the price tag are not in conflict — they sit on different axes. The license governs what you may do with the code. The purchase governs what service you receive around it. A premium GPL theme is free as in freedom and paid as in support.

This is also why "the GPL means themes should be free" is a misreading. The license guarantees freedoms, not zero cost. Charging for GPL software is entirely consistent with the license — the freedoms ride along with whoever receives the code.

04The "GPL theme" reseller trap

The same redistribution freedom that keeps the code open also enables a murkier market: sites that resell copies of premium themes for a few dollars, branding themselves as "GPL" to imply it is all above board. It is worth understanding exactly what is and isn't going on.

What can be legitimate

Because GPL code can be redistributed, reselling the code itself is not inherently a copyright violation in the way pirating closed software is. That is the kernel of truth these sites lean on, and it is why they reach for the GPL label.

What you actually lose

• Updates dry up. A resold copy is frozen at the moment it was grabbed. You miss security patches and compatibility fixes — the very things that make a theme safe to keep running.
• No support exists. The reseller didn't write the theme and can't fix it. You are on your own with someone else's code.
• Provenance is unknown. Redistributed copies are a known vector for injected malware and backdoors. You are trusting a stranger's build of code that runs on every page of your site.
• Trademarks still apply. The GPL covers code, not brand names and logos. Reusing an author's name or marks to sell their theme can cross into trademark territory the license never touched.

The clean way to think about it: the GPL may make sharing the code lawful, but it says nothing about whether buying from a reseller is wise or safe. You gain a cheap file and lose the updates, support, and trust that were the actual value. For a site you depend on, that is a bad trade.

05How the GPL protects you as a buyer

It is easy to read the GPL as a loophole for resellers and miss the point: the license exists to protect you, the person running the theme. Those same freedoms are a genuine safeguard against lock-in.

• You can leave the author. If a theme company vanishes or goes a direction you hate, the GPL lets you, or a developer you hire, keep maintaining the code. You are never fully hostage to one vendor.
• You can modify freely. No clause forbids you from changing the theme however you need. You don't have to beg permission or void a license to customize your own site.
• You can audit it. The code is open to read, so you, or a security reviewer, can inspect exactly what runs on your site — impossible with truly closed software.
• You can't be locked out retroactively. A copy you legitimately received stays usable under the freedoms it came with; the author can't claw the license back on what you already have.

That is the ownership lens that makes the GPL worth caring about. A GPL theme is something you can keep and, if you must, leave — carry your code to a new developer, fork it, or simply read it. The standard, open license is precisely what stops a theme from becoming a trap.

The buyer's sweet spot, then, is straightforward: get GPL freedoms and a real support relationship by buying from the original author or an authorized seller. You keep every freedom the license grants and still get the updates and help that keep the site healthy.

06Frequently asked questions

If a theme is GPL, why am I being charged for it?

Because you are paying for updates, support, and the author's ongoing work — not for the license. The GPL guarantees freedoms, not a zero price. Charging for GPL software is fully consistent with the license, which is how nearly the entire premium WordPress economy operates.

Is it legal to use a theme bought from a GPL reseller?

Reselling GPL-licensed code can be lawful because the license permits redistribution, but it is fact-specific and trademarks may still apply. The bigger practical problem is what you lose: updates, support, and assurance the file isn't tampered with. This is general guidance, not legal advice.

Can I modify a GPL theme and use it on client sites?

Yes. The freedoms to modify and use are core to the GPL. You can adapt a GPL theme and deploy it for clients. If you then redistribute your modified version, the GPL generally expects you to pass along the same freedoms — but using it is unrestricted.

Does the GPL mean I can resell a theme I bought?

The license itself permits redistributing the code, so it can be technically possible. But it may run into the author's trademarks, and it strips the support and update value for whoever buys from you. Whether it's advisable, or fully clear in your situation, is a question for a lawyer, not a blog post.

This article is general editorial guidance to help you understand GPL licensing, and is explicitly not legal advice. Licensing and trademark questions are fact-specific — verify the specifics against the actual license text and consult a qualified attorney before relying on any of it.