Submission and Review

Congratulations! You've built a great plugin and you're ready to release it to your customers.

To publish on our Marketplaces, your plugin must first go through a review process. By reviewing every plugin, Adobe aims to help developers get ready for prime time and ensure that users have great experiences with the plugins they consume. Our goal is to balance providing you with the best developer experience during the review process as possible, while also ensuring the approved plugins offer a great user experience for our mutual customers.

data-slots=text
data-variant=info
This set of guides is meant to provide you with an idea of what types of information you will need for the submission process and how to best prepare for review. Working through the guides provided in this section will help you make sure you’ve accounted for all of the requirements so you can avoid having to fix things and resubmit before being published.

Submission Data Requirements

Below is the list of data you will be asked to provide during the submission process.

Publisher profile

Your publisher profile is about you as a company or developer as whole. Once you've submitted this information and it has been approved by Adobe, it is shown for all plugins and integrations you publish with Adobe.

Your publisher profile includes required details like:

  1. Your publisher public name (often company name or, for individuals, your own name)

  2. Your publisher marketing website (again, because this is part of the publisher profile, this website shows for all things you publish with Adobe and should be scoped to you as the publisher, not scoped to any single plugin or integration you submit)

  3. A description of you, the publisher

  4. Your logo

data-slots=text
data-variant=info
You must complete and submit your publisher profile in order to submit your first plugin, however this is only a one time thing, unless you decide you need to update for your own reasons.

Note: Any changes to your publisher profile will need to be submitted for approval again. Frequently changing your publisher profile will confuse users and erode trust. Please be sure you're ready before entering this information.

Commerce

For paid plugin listings, you’ll need to register with Adobe’s third-party payment provider, FastSpring, and enter your FastSpring key into your publisher profile. Please note that it may take up to 24 hours for FastSpring to create your key.

Listing Details

Your listing metadata provides Adobe and users with details about the plugin you are currently submitting. See the plugin version details below for the metadata that is submitted for each plugin version.

The information you add in the following tabs will be made public to users via Adobe's Marketplace surfaces once your listing is published.

General Tab

Localizations Tab

Localized versions of:

Media Tab

Tags Tab

Services Tab

Plugin Version Details

Here you will provide plugin level details for each plugin version submitted.

The information you add in the following tabs will be made public to users via Adobe's Marketplace surfaces once your version is published.

General Tab

Note: this tab will vary depending on plugin type being distributed, but may include:

Plugin file tab

This tab will appear specifically for ZXP plugin distribution, and is where you upload your plugin package file. Note: for UXP plugins, the file is uploaded in the 'General' tab.

Localizations Tab

Localized versions of:

Media Tab

Plugin file

As part of your submission, you will upload your plugin package. Take the following steps to create your plugin package, categorized by plugin type.

UXP plugin package

  1. Compress your plugin files as a .zip file

    • Select all files within your plugin's parent folder. On both macOS and Windows you can right-click to compress:

      macOS: Right-click > Compress items

      Windows: Right-click > Send to > Compressed (zipped) folder

      Note: You should not compress the plugin's parent folder. Instead, compress the contents of the parent folder. Failure to do so will likely cause a rejection when submitting.

  2. Rename the .zip extension to .xdx or .ccx depending on the target host app.

    • Adobe XD recognizes the .xdx file extension as an XD plugin and Photoshop recognizes the .ccx as a Photoshop plugin.

    • By using this file extension, your plugin automatically gets the "double-click to install" feature, meaning that if you share your plugin directly to users, all they have to do is double-click to install the plugin.

  3. Verify the packaging worked:

    • Double-click your final plugin package file. When your OS prompts you to install the plugin, click "Install".

    • Verify you see a success message upon installation and your plugin available in the host app.

For more information on how to package your UXP plugins, please refer to these additional resources (Photoshop, XD).

ZXP plugin package

  1. .zxp (CEP/MXI):

  1. Others (not CEP/MXI):

All non-zxp files (e.g. image, pdf etc.) need to be submitted in a .zip folder

On successful package upload, you’ll be asked on Developer Distribution for versions of Adobe products that your app supports, platform/s, and version number for your app. On successfully saving this information, a manifest file will be generated with unique bundle id for your app.