Model preparation
Tools for repetitive geometry cleanup, export preparation or splitting models. Explain what inputs and outputs the tool supports.
Turn a useful Blender workflow into a clear digital offer. Show your tool in action, explain compatibility and deliver the installation package after payment.
Installable release, setup guide and clearly stated support. Show the actual result instead of asking buyers to guess.
The exact installable add-on package, nested inside the delivery ZIP.
Installation, permissions, first use and a support contact.
Only the Blender versions and operating systems you have tested.
The applicable license, release identifier and changes.
Build your offer around the time-consuming job your tool improves, with a short demonstration and a clear list of dependencies.
Tools for repetitive geometry cleanup, export preparation or splitting models. Explain what inputs and outputs the tool supports.
Utilities for object organization, naming, materials or rendering. Include an example based on the retail release.
Specialist scripts for your audience's workflow. State the required software, permissions and external services.
Package your installation files, guide and usage terms in one ZIP. Check the current upload limit and test the exact archive.
Create a digital product, connect a supported payment provider and describe the files, dependencies, price and support you offer.
Review the product page, complete a buyer-view purchase and open the delivered files before promoting your link.
Use a ZIP to deliver several files together, including the guide and terms. Keep a separate release archive for your own support records.
Confirmed purchases receive a download link on the success page and in the order email. Download access follows the limits and expiry you configure.
Replacing a product's file makes the current file available through existing valid tokens. It does not renew their limits or expiry. Explain your correction and support policy.
PayRequest handles the product sale and file handoff. An in-app updater, activation server or software support service needs its own verified workflow. Download controls do not prevent a recipient from copying received files.
Blender's official FAQ says add-ons using its API can be sold under the GNU GPL, with the required sources and freedoms. Review the license of your code and any bundled assets before defining usage terms.
Read Blender's licensing FAQ →Digital products are available on Free with a 2% standard payment fee, capped at €25 per transaction. Premium (€5/month) and Business (€20/month) remove standard platform fees while paid access is active. Provider fees and commission-payment exceptions remain separate.
Compare plans and fees →Yes. Digital products are available on Free with a 2% standard payment fee, capped at €25 per transaction. Provider fees and commission exceptions are separate. A digital download does not by itself require a paid plan.
Upload a delivery ZIP containing your tested installable package, a start guide and the applicable license. Tell buyers which file inside the archive to install, rather than asking them to install the outer delivery ZIP.
Do not assume that it does. This offer covers a product page, payment and downloadable files. Verify any separate activation, in-app updating or notification workflow before promising it to customers.
Existing valid download tokens use the current file for the product. Replacing it does not reset their download allowance or expiry. Keep release notes and explain how a buyer should request support if access has expired.
Upload the reviewed package, explain the offer and share a product link with your own audience. A paid plan is optional for digital downloads.
Create your digital product