How to Sell a Blender Add-on in 2026: GPL Rules, License Keys and Paid Updates That Stay Legal
Sell a Blender add-on with GPL rights intact. Use purchase keys for official updates, support and private repository access, with clear expiry rules.
You can sell a Blender add-on. The useful commercial boundary is access to your official downloads, future releases and support, while the GPL governs the code customers receive. A purchase key can identify a service entitlement without becoming permission to open Blender or run an already-delivered tool.
This guide proposes an update-service architecture for independent sellers. It is general information, checked on November 18, 2026, not legal advice or a guarantee of compliance. Have your actual package, dependencies, sales terms and distribution channel reviewed before launch.
Can you sell a Blender add-on under the GPL?
Yes. Blender's FAQ says published scripts using its Python API must be supplied under the GNU GPL, and explicitly allows selling add-ons with their source. Recipients retain the GPL freedoms, including modifying and redistributing the code. Charging for a copy does not turn it into proprietary software.
The Blender license page describes paid script distribution as selling the download service. Build your offer around reliable releases, compatibility work, documentation and help. Describe those deliverables precisely so a buyer understands what a renewal purchases.
What a Blender add-on license key should control
Use the key as a credential for services you operate. Keep ordinary local operators independent of that credential. For example, a modeling tool should register and execute locally even if the customer has never entered an update key, their subscription has ended or your entitlement server is unavailable.
| Surface | Suggested design |
|---|---|
| Installed GPL add-on | Local tools keep working; include editable source and license notices. |
| Official release downloads | Your server checks the buyer's entitlement before delivering an eligible release. |
| Future paid updates | Renewal grants the official delivery service for the stated period. |
| Support | Verify the support contract and its scope when opening a ticket. |
| Private development repository | Control account membership separately; fulfill source obligations for every delivered version. |
A key does not override the GPL. GPLv3 sections 2 and 10 protect running the program and prohibit further restrictions on the granted rights. Do not add terms forbidding modification, redistribution or use of a lawfully received GPL copy without payment. A technical check is not, by itself, a complete legal analysis: the source, ability to modify it and surrounding terms all matter. This guide deliberately keeps purchase checks out of local execution. See the GPLv3 text.
Paid updates and private repositories: keep source delivery separate
The GNU GPL FAQ permits charging for downloads. You do not generally have to give every member of the public free access to your distribution site. A recipient can nevertheless redistribute the GPL code they receive, including a paid update. Your paid repository is an access service, not an exclusive right to control every copy.
Include the preferred form for modifying the add-on in each release ZIP, along with the GPL text, copyright notices and any required dependency notices. If you ship compiled components, satisfy the applicable corresponding-source requirements; do not make that source a separately priced upgrade. A link to the latest repository branch may not reproduce an older delivered build. Do not let subscription expiry defeat a source obligation that still applies to a delivered copy.
Repository membership can include work in progress, issue discussions and convenient release access. It does not replace the source package for a particular version. Keep a versioned release archive, and explain whether customers may re-download earlier purchases after service expiry. That re-download promise is a separate commercial commitment.
Choose a channel before adding a paid updater
Your own shop and the official Blender Extensions platform have different requirements. The Blender Extensions terms require GPLv3-or-later compliance for uploaded add-ons. They also prohibit additional requirements such as payments, registration or keys that block extension functionality, and prohibit using Blender UI elements to promote updates or commercial versions.
Do not assume a self-distributed paid-update design qualifies for that platform. Review its complete current submission rules before uploading. A freely usable extension on the official platform and a commercial service on your own site need a deliberate boundary; the official listing must meet its own rules.
A practical offer: the add-on plus twelve months of updates
Consider a fictional tool called Mesh Workshop. The initial purchase delivers version 1.0 with its GPL source, plus twelve months of official update downloads and support. If the customer does not renew, version 1.0 and the other versions they received remain usable under the GPL. Your official update service can refuse delivery of later releases outside the purchased period.
Write down how the dates work. One option is access to releases published during the paid window, with continued archive access to those eligible versions. Another is a download subscription that ends on a stated date. These are different offers. Neither should imply that expiration cancels GPL rights to code already received. Avoid promising lifetime support or compatibility with every future Blender version unless you can deliver it.
Keep any mandatory security-update obligations separate from optional feature upgrades and support. The Cyber Resilience Act guide explains why a maintenance price is not a substitute for checking applicable product-security duties.
Where PermitCore fits in the update workflow
PermitCore can issue product-scoped keys and return license status, features and maintenance information. Your application decides what those results authorize. For this model, create the product for the Mesh Workshop update service, rather than treating the key as a right to run the GPL add-on.
- Sell the service. Configure your Store or payment integration to issue the update-service key after verified payment. In the PermitCore Store, buyers access keys through their verified customer account; license keys are not sent in email.
- Check on your server. Your own authenticated download backend validates the supplied key against the expected product. If you use maintenance dates, compare the selected release's trusted publication date with
MaintenanceExpiresAt, as well as checking the relevant service status. - Authorize one artifact. Your backend selects a known release and returns a short-lived download grant. Keep the repository credential or object-storage secret on that backend.
- Offer the update. A self-distributed add-on can request an update when the user chooses to check. Refused or unavailable service leaves the installed local tools usable.
- Handle renewal and support. Re-check current server entitlement before a new download or support request. State clearly what a successful renewal restores.
This is an integration design you build. PermitCore does not supply a Blender updater, host your add-on releases, synchronize private Git membership or generate storage download grants automatically. Its validation API and Python SDK are building blocks. Do not put an Admin API key or private repository token inside the distributed add-on.
MaintenanceExpiresAt does not independently protect a file URL. An application-level release-date comparison must run on the download server. Choose how ExpiresAt, payment grace and archive rights interact before implementing that rule; an expired subscription's invalid validation result must not accidentally erase separately promised archive access. See maintenance and eligible-version delivery.
Protect the update service without interrupting an artist's work
Removing a local update check from editable Python must not grant access to your private server. Authenticate the download request there, enforce the expected product and authorize the specific artifact. Never trust a client-supplied release date or an unverified local flag saying the purchase is active.
Use HTTPS, keep credentials out of URL query strings and logs, and expire download grants. Pin the release catalog to reviewed artifacts, verify their integrity and avoid automatic execution of arbitrary downloaded Python. Explain any network access and honor the user's choice to check for updates. A service outage should produce an update-status message, without disabling modeling or corrupting a saved project.
Do not copy a node-locked desktop licensing tutorial wholesale into this design. Device activation limits and recurring local validation are different from checking an update-service entitlement. Start with the minimum data your service actually needs.
What happens when a customer shares the add-on?
Distinguish GPL redistribution from unauthorized service access. A person receiving a GPL copy can have rights to that copy without holding an account on your update service. They do not automatically acquire another customer's private support account, purchase credential or repository membership. Investigate leaked service credentials separately from legitimate redistribution; do not describe every shared GPL ZIP as piracy.
Independent assets, trademarks and genuinely separate hosted services may raise different licensing questions. Their treatment depends on the material and how it is combined or delivered. A label saying “premium” does not make GPL-covered Python proprietary, and moving code behind an API is not a universal legal workaround.
Before your first paid release
- Ship the correct source, GPL text, notices and dependency licenses with the release.
- Define update dates, support scope, renewal, refunds and archive access in the offer.
- Verify that a clean installation works locally without an update key.
- Test expired, revoked, wrong-product and unavailable update-service responses.
- Confirm a modified client cannot obtain private artifacts without server authorization.
- Check your distribution platform's rules separately from the GPL.
A sustainable paid Blender add-on gives artists useful code and gives paying customers a dependable official service. The commercial relationship can end while the GPL rights in delivered code continue. Start with the Store setup guide when you are ready to implement the purchase side.
Build your first licensed product without building a license server.
Create a free PermitCore account, issue a test license, and validate it from your application.