Copyright applies regardless of the conversion method
A website's visual design, layout, original text, photography and custom graphics are typically protected by copyright the moment they are created, whether or not the site displays a copyright notice. Converting that design into a WordPress theme, whether by hand-coding it or using an automated capture tool, does not remove the underlying copyright from the original creator.
This means the legality question is really about ownership and permission, not about the technical method of conversion. Capturing a page you built yourself, for your own client, or that you have an explicit license to reuse is a fundamentally different situation from capturing a competitor's or stranger's site.
Template versus content: where the line usually sits
A useful distinction is between the structural template, layout, spacing system and generic component patterns, and the specific content, actual copywriting, brand photography, logos and unique illustrations. Layout ideas in the abstract, such as a three-column pricing table or a hero section with a centered headline, are generally not protectable in the same way specific creative expression is.
In practice this means if you plan to sell a theme, you should strip out and replace all original text, images, logos and brand-specific elements with your own or licensed placeholder content, keeping only the generic structural pattern, not the original site's actual creative output.
GPL and how it applies to WordPress themes
WordPress core is licensed under the GPL, and the Free Software Foundation's guidance, which the WordPress project follows, holds that PHP theme code that calls WordPress functions is a derivative work and therefore must also be GPL or a GPL-compatible license if distributed. This is why themes sold on the official WordPress.org repository and most reputable marketplaces are GPL-licensed for the PHP and functionality code.
Important nuance: GPL applies specifically to the functional code, the PHP, not automatically to design assets bundled with a theme such as images, fonts or artwork, which can carry separate, more restrictive licenses even inside a GPL theme package. Selling a theme means being clear about which parts are GPL and which bundled assets carry their own terms.
Third-party assets and font licensing
Fonts loaded from services like Google Fonts are generally open licensed and safe to redistribute, but custom or purchased fonts almost always carry licenses that restrict redistribution or require a separate license for each end user, which matters a great deal if you intend to sell the theme to multiple buyers.
Stock photography, icon sets and illustration libraries used on the original site typically carry standard or extended licenses tied to the original licensee, not to anyone who later captures the page. Reselling a theme containing such assets without the appropriate redistribution license is a separate infringement risk from the design copyright question.
- Google Fonts and most open-source web fonts: generally safe to redistribute
- Purchased or custom fonts: usually restricted, check the license before redistributing
- Stock photos and icon packs: standard licenses rarely permit resale bundled in a template
- Original brand logos and copy: virtually never safe to redistribute without permission
A safer path to a sellable theme
The lowest-risk approach to building a theme you intend to sell is to design your own layout from scratch, or convert a page you fully own the rights to (your own site, or a client project where the contract grants you reuse rights), then replace any third-party fonts, images and copy with properly licensed or original alternatives.
If capturing an existing page for personal or client use, keeping the theme private and used only on the site it was built for, or with the explicit permission of the site owner, avoids the resale question entirely since you are not distributing it to third parties.
Practical checklist before listing any theme for sale
Before listing a converted theme for sale anywhere, verify ownership or explicit licensing for every visual and content element in it, confirm the PHP code complies with GPL if using WordPress hooks, and check every bundled font and image against its original license terms.
When in doubt, replace the element rather than risk it, since swapping a font or stock photo for a properly licensed alternative is far cheaper than a copyright dispute after the theme has already sold.
- Confirm you own or have explicit rights to reuse the original design and content
- License PHP/theme functionality code under GPL or a GPL-compatible license
- Audit every font for redistribution rights, replacing any that are not clearly licensed
- Audit every image, icon and illustration the same way
- Remove or replace all original brand-specific copy, logos and photography
Frequently asked questions
- Is this legal information reliable enough to act on without a lawyer?
- This is general information intended to explain the common considerations, not legal advice for a specific situation; consult a qualified intellectual property attorney before selling any theme derived from another site.
- Can I sell a theme converted from my own previous website?
- Generally yes, since you own the copyright to your own original design and content, though you should still check any third-party fonts, stock images or plugins used on the original site.
- Does GPL mean I can freely resell any WordPress theme?
- GPL covers the redistributable functional code, but it does not override separate licenses on bundled non-code assets like custom fonts or stock photography, so those still need individual clearance.
- Is it safer to convert my own site with Themify than someone else's?
- Yes, converting a site you own or have explicit reuse rights to removes the core copyright risk entirely, which is why personal or authorized-client use is the most straightforward application of a conversion tool.
- What is the biggest risk in reselling a converted theme?
- The biggest risk is typically bundled third-party assets, fonts, stock photos and brand-specific content, carried over unnoticed from the original site rather than the general page layout itself.