If you build, edit or sell WordPress themes, you will sooner or later hear the words “license” and “copyright attribution”. Many beginners ignore them, and this is a common reason why themes get rejected, flagged or even removed. Even if you only use themes on your own website, it helps to know what these terms mean.
This guide explains WordPress theme license and copyright attribution in simple language, with examples and a checklist.
Why does license attribution matter?
WordPress is released under the GPL (GNU General Public License). The GPL is a “copyleft” license, which means that work built on GPL code must be shared under the same kind of terms. Because of this, themes and plugins made for WordPress are expected to be GPL-compatible, and they must clearly say who wrote the code and under which license it is shared.
Attribution matters for three reasons:
- It tells users that they are free to use, change and share the code under the license.
- It credits the people who created the work.
- It lets reviewers check that every part of a theme is allowed to be used together.
The WordPress Themes Team has explained this topic in an official post, and the discussion in its comments is also useful for beginners. You can read it here: proper copyright and license attribution for themes. Please note that this post was written in 2014, so always check the latest Theme Review requirements before you submit a theme.
The four types of attribution
| Type | What it means | Example |
|---|---|---|
| The theme itself | Your own work. It needs your copyright notice and license statement. | A theme you wrote from scratch |
| Derivative work | Your theme is built on top of another theme. | A child-style theme made from a starter theme |
| Incorporated code | You copied some functions or code from another theme or plugin. | A few helper functions taken from another project |
| Bundled resources | Third-party files that come inside your theme. | Icon fonts, JavaScript libraries, images, CSS frameworks |
The difference between a derivative work and incorporated code is mostly about how much you used. If another theme is your starting base, your theme is a derivative. If you only borrowed a few functions, it is incorporated code. In both cases you must give credit and keep the license.
What a simple attribution looks like
These are made-up examples that show the kind of information you should include.
Your own theme:
Sunrise Theme, Copyright 2026 Ali Khan Sunrise is distributed under the terms of the GNU GPL
A theme built on another theme:
Sunrise Theme is derived from Starter Theme, Copyright 2024 Jane Doe Starter Theme is distributed under the terms of the GNU GPL
A bundled resource:
Sunrise Theme bundles the following third-party resources: Example Icons, Copyright 2025 Example Studio Licensed under the GNU GPL, Version 2 (or later) Source: example.com/icons
The exact format can be different. What matters is that the copyright holder, the license and a source link are clear.
Where to put the information
- Theme readme or license file: list your own copyright, any derived or incorporated work, and every bundled resource with its license and source.
- File headers: keep the original copyright notices in files that you copy or bundle.
- Code comments: if you copy a function, add a short comment above it with the author, license and source link.
Images need extra care. They do not have a readable file header, so the readme is the only place where users can find who made the image and which license applies.
A quick checklist for theme authors
- Add your name and the year in a clear copyright line.
- State that the theme is distributed under the GPL (or a compatible license).
- List every library, font, icon set and image you did not create yourself.
- Check that each of these has a GPL-compatible license. If you are not sure, do not use it.
- Mention if your theme is built on another theme, and keep that theme’s copyright notice.
- Keep the readme up to date when you add or remove resources.
- Do not remove the original copyright notices of other authors.
What this means if you only use themes
If you are a website owner and not a developer, you do not need to write any of this yourself. But it still helps to know a few things:
- The code license and the purchase license are different things. A premium theme can be GPL code and still require you to buy a license key to get support and updates. If your site breaks after an update, check whether your premium license is active before you blame the code.
- Avoid “nulled” themes. These are paid themes shared illegally. They are often infected with malware and can harm your site and your search rankings.
- Do not remove credits you do not understand. Some themes ask you to keep a credit link or a copyright notice. Read the theme’s license page before you edit the footer.
- Use safe images. Pick pictures from sources that clearly state their license, and keep a note of where each image came from.
Common mistakes
- Copying code from another theme without credit
- Bundling a font or script with a license that does not allow redistribution
- Using images from a random search without checking the license
- Putting the attribution only in one file and forgetting the readme
- Assuming that “free” means “no rules”
Frequently asked questions
Do all WordPress themes have to be GPL?
Themes shared in the official WordPress theme directory must be GPL-compatible. Themes sold elsewhere often use the GPL too, because they are built on WordPress code.
Can I change a GPL theme for my own website?
Yes. The GPL gives you the freedom to use and modify the code. If you share your changed version with others, you must keep the original license and copyright notices.
What is the difference between a derivative theme and incorporated code?
A derivative theme uses another theme as its base. Incorporated code means you took only some parts, such as a few functions. Both need credit and the original license.
Do I need to list images in the readme?
Yes. Images do not carry a visible header, so the readme should state the creator, license and source of each one.
Is this legal advice?
No. This guide is for general information. If you have a serious legal question about licensing, speak to a qualified lawyer.
Final thoughts
Proper attribution is not hard if you do it from the start. Keep a simple list of every resource you use, copy its license and source link, and keep the readme up to date. If you are new to WordPress, you can also read our summary of the WordPress Training Team update to find free lessons.
Disclaimer: This article is for general information only and is not legal advice. Licensing rules and review requirements can change, so please check the official WordPress documentation and the license of each product you use.