(1) License
(2) Branding
- (2.1) The name "Blender" should not be included in the name of the extension.
- (2.2) Blender logo or icon should not be used in extensions thumbnails, icons, or preview images. Blender logo guidelines should be respected.
- (2.3) Extensions should not make statements that give a false impression to users that they're supported or endorsed by Blender, or affiliated with it in some way.
- (2.4) Logo or other trademarked images of third-party software/companies should only be used if guidelines of that software/company allow it and extension authors can provide evidence of that.
(3) Content of the Extension
- (3.1) No surprises: An extension must have an easy-to-read description mentioning everything it does. It must be abundantly clear from the extensions listing what functionality it offers, and users should not be presented with unexpected experiences when they download and install the extension.
- (3.2) Extension listings must not do anything illegal or otherwise violate applicable law.
- (3.3) Extensions offered on extensions.blender.org should be fully functional, documented and actively maintained products.
- (3.4) 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.
- (3.5) Extension code must be reviewable: no obfuscated code or byte code is allowed.
- (3.6) Extension should avoid including redundant code or files.
- (3.7) Extension must not negatively impact performance or stability of Blender.
- (3.8) If extension bundles copyrighted code (or other materials) all copyright holders should be properly credited in
blender_manifest (copyright section).
- (3.9) 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. It must credit creators, contributors, and other copyright holders of the original extension.
- (3.10) Extension should not require purchasing additional content to function.
(4) Connecting to Internet
- (4.1) Extension that connects to the internet should request permission for it in
blender_manifest and state the clear reason for the request.
- (4.2) Extension should respect the "Allow Internet Access" user preference (
bpy.app.online_access) and only connect to the internet if it is enabled.
- (4.3) 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). Extensions can connect to other websites requiring a login (account), provided the offering on that website is complete and aligned with Blenders mission. If the offering is a mixed product (for example with optional commercial extras), it will not be accepted.
- (4.4) Online access and network permission aren't required for buttons that open the browser from inside the Blender (i.e. Online Manual, Report a Bug...) if the button makes it clear that it will open the browser.
- (4.5) Extension must not send data to any remote locations without authorization from the user.
(5) Third-Party Applications
- (5.1) Extension must be self-contained and not load remote code for execution.
- (5.2) Extensions should not require any external functional components (other than Blender itself) that need to be downloaded from elsewhere.
(6) Advertisment
- (6.1) Advertisements (links to commercial and funding websites, donation buttons, images or text labels prompting users to purchase anything) are not allowed inside the Blender UI.
- (6.2) 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.
- (6.3) Showcasing features of the commercial version of the extension not listed on extensions.blender.org in description, thumbnail, or preview images will be considered as an advertisement and is not allowed.
Last updated: 18 Dec 2024