WordPress theme licenses and the GPL explained

WordPress itself is released under the GNU General Public License version 2 (or later). That placement of WordPress under the GPL has direct effects on themes: the PHP code and server‑side HTML of a theme are treated as covered by the GPL, while other files packaged with a theme can be subject to different licensing terms. This guide summarizes official documents from WordPress.org, Envato/ThemeForest and Automattic, consulted on September 27, 2026, to explain what the GPL covers for themes and what commonly sits outside it.

Why the license question matters for buyers and sellers

The licensing status of a theme determines what you may legally copy, modify, redistribute or resell. Because WordPress is published under the GNU GPLv2 (or later), the PHP portions of themes are treated as derivative works of WordPress and therefore fall under the GPL. That established position appears in WordPress.org documentation and in the historical analysis “Themes are GPL, too.” These sources were consulted on September 27, 2026.

Practically, this means that rights to copy and adapt the server‑side code are granted by the GPL. However, many theme packages contain assets—CSS, images, fonts, third‑party JS libraries—that can be licensed differently. Marketplaces and authors commonly rely on a “split license” approach: GPL for the PHP and a distinct license for other files. Understanding that split avoids surprises when you reuse or redistribute a theme package.

Method: the facts below synthesize WordPress.org license pages, Envato/ThemeForest help documentation and Automattic communications, all consulted on September 27, 2026.

What the GPL covers for a WordPress theme

Official WordPress material and related commentary make a consistent point: the PHP code and embedded server‑side HTML of a theme are viewed as being covered by the GPL. The position is stated on the WordPress license page and in the historical article explaining that themes fall under the same copyleft regime as WordPress itself. That classification flows from how WordPress executes PHP code on the server and how derivative works are interpreted under the GPL.

Because those parts are GPL, a recipient of that PHP code receives the rights to copy, modify and redistribute it under the same GPL terms. The copyleft nature of the GPL imposes that redistributed copies of the covered code remain under GPL, preserving recipients’ freedoms for that code portion.

Readers should keep in mind the scope: the statement applies to the server‑side code as described by WordPress.org and related commentary consulted on September 27, 2026. It does not automatically extend to every file bundled in a theme package unless the author explicitly licenses those files under the GPL.

Which theme files commonly fall outside the GPL (split licensing)

Theme packages frequently include files that are not strictly server‑side PHP and therefore may be licensed differently. Examples commonly cited by marketplace documentation include CSS files, images and photographs, font files, and third‑party JavaScript libraries or premium assets. Envato/ThemeForest documents the split licensing approach and explains that while PHP and embedded HTML are GPL, other assets may fall under the marketplace’s “other part” of the license or be subject to separate proprietary terms.

That practical split means a buyer can often treat the PHP as GPL but must verify licensing for every non‑PHP asset before redistributing a complete theme package. Marketplaces like ThemeForest provide license descriptions and author guidance that clarify which files are covered by which license component; checking those pages is the usual first step.

An important practical note from marketplace documentation: consult the theme’s README or license.txt and the item page on the marketplace. Those places typically state which files are GPL and which are not. When the seller supplies a clear breakdown, you can confirm whether images, fonts or bundled plugins are covered by GPL or by a separate license.

Consequences for buyers: what you can and cannot assume

From the GPL coverage of PHP code follow concrete implications. You may modify and redistribute the PHP portions under GPL terms. You may incorporate that PHP into another GPL project, subject to copyleft obligations. However, redistributing a full theme package without checking non‑PHP assets can expose you to contractual or copyright issues if images, fonts or premium libraries are restricted.

Before offering a complete theme for redistribution, verify whether the package contains assets under a proprietary license. If it does, those assets remain subject to their original terms and may require permission or separate licensing to redistribute. Marketplace license pages and the theme’s documentation are the primary places to confirm those distinctions.

Marketplaces also maintain commercial rules—different license tiers for buyers, limits on usage and support policies. These contractual layers sit alongside the GPL’s code rights and can restrict how marketplaces permit distribution of certain assets even when the underlying code is GPL.

Sale and resale of GPL‑covered themes: legal framework and practical limits

The GPL permits selling copies of GPL‑licensed code. Selling a theme that contains GPL‑covered PHP code is therefore legally possible. In practice, the commercial value often resides in packaging, support, updates and integration services rather than in exclusive ownership of the code, because the GPL preserves recipients’ rights to reuse and redistribute the code.

Practical limits to resale include trademark rules and marketplace conditions. Trademarks are outside the GPL: use of protected names or branding can be restricted by trademark law even where the code is GPL. Automattic’s public materials underline that trademarks are managed separately from GPL licensing. Marketplace terms can also shape how a resale is handled on that platform, for example by requiring adherence to specific listing rules or prohibiting certain repackaging.

For these reasons, sellers commonly differentiate what they sell: access to packaged convenience, support contracts, update delivery and brand‑specific services, rather than exclusivity in the code itself.

Checklist of items to verify before reusing or reselling a theme

Before redistributing or repackaging a theme, work through a short factual checklist:

If uncertainty persists about a specific combination of files or the legal effect on a planned commercial use, consult an intellectual property attorney for tailored advice.

Practical examples drawn from official venues

The documentation landscape yields clear category examples. A theme downloaded from the WordPress.org repository must adhere to repository rules and is effectively expected to be GPL for the code portions; repository guidance and review policies support that position. A theme sold on ThemeForest frequently follows a split licensing pattern: PHP under GPL and images/fonts or third‑party premium components under a separate part of the marketplace license. Finally, some authors choose to release a theme entirely under GPL, including assets, which makes all packaged files subject to the same copyleft terms—when that choice is explicitly declared by the author.

These three patterns—repository themes, marketplace split‑licensed themes, and fully GPLed author releases—cover the common configurations buyers will encounter. Always confirm the specific file‑by‑file licensing statements for the theme you handle.

Sources and further reading

All documents below were consulted on September 27, 2026 and form the basis of the explanations above:

Related guides

• Easily Publish and Manage Podcasts on Your WordPress Site
• Unlocking Design Freedom: How Kirki’s Visual Builder Transforms Your WordPress Experience
• Unlocking WordPress 6.4: Essential Upgrades for Your Website
• WordPress Themes