About GPLDL

Why GPLDL?

At GPLDL we believe in free software. We also believe that the WordPress ecosystem works best when more people can build, learn, experiment and ship real websites without being blocked at the starting line by stacked license costs.

Many excellent WordPress plugins and themes are sold together with support licenses. Those licenses can be valuable. If you need implementation help, bug fixing, maintenance advice, managed updates or direct access to the team that built the product, paying the original developer for support can be the right and responsible choice.

But experienced builders often need something different: access to the GPL-licensed code itself. They can install it, test it, debug it, update it manually and decide later whether direct developer support is worth buying for a specific project.

That is where GPLDL comes in. GPLDL lowers barriers to entry by separating access to GPL-covered WordPress code from bundled support services. This matters for freelancers, small agencies, students, hobbyists, nonprofits and budget-conscious entrepreneurs everywhere, including in places where a full WooCommerce stack can quickly add up to thousands of dollars per year.

GPLDL is not about breaking copyright or taking software outside the license. It is about using the permissions the GPL was designed to give.

GPLDL does this by relying on the license that covers WordPress itself and most WordPress plugins and themes: theGNU General Public License version 2. This page explains the idea in plain English. It is general information, not legal advice.

What the GPL changes

The GPL is not a normal proprietary software license. It is a copyleft license. Instead of using copyright only to restrict copying, it uses copyright to protect the freedom to use, study, share and improve the program.

That is the important difference between GPL-covered software and typical proprietary software. With proprietary software, the license usually tells you what you may not do. With GPL-covered free software, the license gives every recipient broad rights, provided the GPL terms continue to travel with the software.

Those rights are not reserved only for the person who first paid for a download. They belong to every lawful recipient of the GPL-covered software.

Free software does not always mean zero-cost software. Developers can sell GPL software, sell support, sell updates, sell hosting and sell professional services. The point is that once someone receives the GPL-covered code, the GPL grants real rights over that code.

What you can do with GPL WordPress code

You can use a GPL-licensed plugin from GPLDL on a test site to see whether it solves a real client problem before committing a budget to support or SaaS services.

You can study how a theme structures templates, how a plugin registers custom post types, how a form plugin stores submissions or how a WooCommerce extension integrates with checkout hooks.

You can share a GPL-covered plugin or theme with a teammate, developer, agency partner or client so they can review the same source code, reproduce an issue or maintain the site.

You can modify a theme template, remove unused features, patch a plugin conflict, add a small integration for your site or create a private project-specific fork for a client build.

You can redistribute your modified version, but you need to do it responsibly: keep attribution, include the GPL license text, make clear what changed and avoid confusing users about whether your version is the original developer's product.

Attribution and modified versions

Good attribution starts by keeping the original copyright notices, author names, license headers, readme files and license files that came with the plugin or theme.

If you modify and redistribute a product, add your own notice without erasing the original one. A clear example is: Based on Example Plugin by Example Developer, licensed under GPLv2 or later. Modified by Acme Studio on 2026-05-21. Changes: checkout template adjustments and compatibility fixes.

Your ZIP should include the full GPL license text, commonly in a file named LICENSE, COPYING or GPL.txt, and your readme should tell users that the software is distributed under the GPL.

If your version is public, rename it clearly. For example, do not ship a changed plugin as Super Checkout Pro if that is the original developer's name. Use a name such as Acme Checkout Toolkit, update the plugin header, adjust the text domain or slug where appropriate and explain that it is a fork based on GPL-covered code.

This protects users from confusion, respects the original developer's reputation and keeps the GPL chain understandable for everyone who receives the software after you.

What GPLDL does and does not do

GPLDL redistributes original GPL-licensed WordPress files as they came from the developers. GPLDL does not modify them, does not add malware, does not crack them and does not distribute renamed forks under the original product identity.

Some products include hosted features, cloud APIs, automatic update services, premium template libraries, account dashboards or support portals. Those services may require a developer subscription, a license key or a separate SaaS account. GPL rights over code do not automatically create a right to third-party hosted services.

Many WordPress plugins and themes work without license keys or serial numbers for their core local functionality. When a product relies on remote services, the practical result can be different: the GPL-covered code may still run, while the developer's separate service remains unavailable without a direct account.

GPLDL does not provide license keys, developer support, SaaS access or help bypassing access controls. If a project depends on those things, the right path is to buy the appropriate service or support plan from the original developer.

A practical free software project

In a nutshell, GPLDL aims to make free software free again, both in the sense of libre software freedom and in the practical sense of accessible code. A large part of the catalog is available for free download so more people can benefit from GPL-covered WordPress software.

Paid memberships help finance the expenses of maintaining, curating and extending the catalog. We think of those memberships as contributions to keep the project useful, not as recurring subscriptions that lock people in.

GPLDL is not a get-rich-quick business model. It remains a hobbyist, not-for-profit project that has become more professional over time because the repository, the users and the WordPress ecosystem deserve that care. Proceeds beyond expenses are reinvested into the catalog and the cause.

Some other things we deeply care about are security, malware-free code, privacy, freedom and a clean user experience without ads.

We will never ask you for more data than we need to run the site, protect accounts, process downloads and keep the service working. We do not sell personal data, build advertising profiles or use intrusive tracking to follow or control you.

We dislike ads and the many subtle forms of commercialization that make the web worse, so GPLDL does not display ads. We care about our users and ask everyone not to exploit or misuse the service, so all of us can enjoy it for many more years to come. GPLDL has been around since 2013, and we would like to keep it that way.

Thanks for taking the time to read this. We hope GPLDL helps you learn faster, build better WordPress projects and enjoy the freedoms that the GPL was created to protect.

Your GPLDL-Team