Free and Open Source

Uploaded add-ons must be wholly compliant with the GNU General Public License, version 3 or later. Other extensions (themes) must be compatible with the GNU General Public License, version 3 or later. See all compatible licenses.

No surprises

An extension must have an easy-to-read description mentioning everything it does.

It must be abundantly clear from the extension’s listing what functionality it offers, and Blender users should not be presented with unexpected experiences when they download and install the extension.

Content

• Extension listings must not do anything illegal or otherwise violate applicable law.
• Extensions offered on extensions.blender.org should be fully functional, documented and actively maintained products.
• Extensions should not require any external functional components (other than Blender itself) that need to be downloaded from elsewhere.
• Extensions that (need to) connect to Internet services outside of blender.org ecosystem, should offer access to these sites without additional restrictions (such as login or registration).
• Add-ons can connect to other websites requiring a login (account), provided the offering on that website is complete and aligned with Blender's mission. If the offering is a mixed product (for example with optional commercial extras), it will not be accepted.
• If the extension is a fork of another extension, the name must clearly distinguish it from the original and provide a significant difference in functionality and/or code.
• Extensions that are intended for internal or private use or are only accessible to a closed user group may not be listed on extensions.blender.org.
• Linking to external funding platforms in the description is allowed. However, it is not allowed to have additional requirements (such as registration, payments or keys) blocking functionality of the extension.

Acceptable code practices

• Extension code must be reviewable: no obfuscated code or byte code is allowed.
• Extension must be self-contained and not load remote code for execution.
• Extension must not send data to any remote locations without authorization from the user.
• Extension should avoid including redundant code or files.
• Extension must not negatively impact performance or stability of Blender.
• Add-on's code must be compliant with the guidelines.

Branding

• Do not include the name "Blender" in your extension.
• Do not use the Blender logo or icon in the extension thumbnail, icon or gallery.
• When in doubt, consult the Blender logo guidelines.