Autodesk App Store 3ds Max

Depending on the type of content, there may be different requirements. We'll list the details below.

Most of the information we need from you is collected through the web form you complete when submitting your content. This includes gathering information to create an HTML quick-start page that is included with the download of your product and viewable online.

Compatibility

Your product must be relevant to (and usable with) 3ds Max® 2025 and must run on any Windows operating system supported by 3ds Max 2025. You may also indicate compatibility with 3ds Max® 2024 |2023 | 2022 | 2021 | 2020.

Your product must work with any higher-tiered version of the 3ds Max product. For example, if your application works with the 3ds Max Suites, it must also work with the standard version of 3ds Max.

User privileges

If you don’t use the standard installer template we provide, or if your installer or product requires elevated user privileges (greater than a Windows 7/8.1/10/11 Standard User) to install, then this must be very clearly documented in the description of your product displayed on the Store.

Product stability

Your product should be stable and not behave or alter the behavior of 3ds Max in a way that we deem unsuitable, for example, blocking standard functionality, blocking the functionality of another plug-in, causing data loss, etc.

HTML help page

The documentation information you provide as part of the submission process is used to create a standard-HTML page. This information must allow the user to quickly understand how to use your product. You can reference additional information (for example, additional help files posted on your website) from this standard documentation. The auto-generated HTML page will be created using information you provide when submitting your product to the store—you will be prompted to supply it as part of the submission process.

Ready to run

Your product must be ready to run as soon as it's installed. It must not require the user to manually copy or register files, or manually edit 3ds Max settings (such as support paths).

Additional requirements

• Your plug-in must include a toolbar button and/or a menu to access your main command(s) when applicable. Plug-ins that install to other typical UI aspects are also fine. For example, a modifier plug-in, would display itself in the typical modifier UI.
• You must use a plug-in manifest as the loading mechanism. This is typically a PackageContents.xml file.

There are no additional requirements for products that are not integrated with 3ds Max. This might include eBooks, video tutorials, industry specific calculators, connectors to cloud-based services, and the like.

Use of the bundle and XML file for 3ds Max 2025 |2024 | 2023 | 2022 | 2021 | 2020 plug-in

Use of the bundle and XML file for 3ds Max 2025/2024/2023/2022/2021/2020 plug-in as a default location, we’ll be using the "All user" program data location to place the plug-in manifest: %ProgramData%\Autodesk\ApplicationPlugins.

The plug-in files will be contained in a specific folder with a name matching your tool and a PackageContents.xml file (created by the installer that we create for your app) will be stored within this bundle folder, together with the files that you need for your application:

PackageContents.xml contains a series of XML tags that describe the contents of the bundle, including the various components of the application. These tags will define where to load the application from, and also details about the application such as version(s) it supports.

Find more details on the plugin package.

Use the autoloader system

We strongly encourage you to make use of the autoloader mechanism to deploy your plug-in. Information on the required format for autoloader bundles is documented here.

You can also download some of the free plug-ins already available on Autodesk App Store and study their format, such as one of the Autodesk Plug-in of the Month samples (for example, Explode Geometry).

Special considerations

If your app or content has any special requirements that the standard installer template cannot handle as is, let us know.

For example, if you have specific requirements for your app to be written to a single-user, we can create the installer that install only to the current user.

For any other special needs that require a custom installation, you can provide them in the form of Windows Installer Merge Modules (.msm) files. We will merge your msm file with the Windows Installer (.msi) file that we create for your app. Examples of such a scenario would be: writing entries to the registry for a licensing system you are using, installing dependent components by other vendors, and running custom scripts.

For additional information, email us at appsubmissions@autodesk.com.

End User License Agreement

The installer that the ADN team creates for your app includes a button that allows the user to view the standard End User License Agreement (EULA) during the app installation.

Note: This EULA is not modifiable. If you wish to include your own EULA to your app, you can do either:

• Reference your EULA from the standard HTM help file text.

• Display your EULA when the app runs for the first time, and require the user to accept it before the app will work.

The ADN team is here to help you be a successful publisher on the Autodesk App Store. If you have any further questions after reviewing these guidelines and the other documentation on the Autodesk App Store Publisher Center, email us at appsubmissions@autodesk.com for support.