Adobe Exchange offers a web service called the Developer portal, that developers can use to upload and distribute their created extensions to share or offer for sale.  Users can browse, purchase, and download, to augment the capabilities of their Creative Cloud apps.

This article provides an overview of the process for adding new content or updating existing content on the Adobe Exchange Developer portal. Links to articles that describe each section of the process in greater detail is provided.

To get started, check the Quick-start summary.

Features of the Developer portal

Joining the Adobe Developer portal allows you to:

  • Define products to be offered in Adobe Exchange.
  • Submit and publish products: submit your product for approval, then publish it when it is approved.
  • Share your products with everyone, or with specific users for purposes of testing and private distribution.
  • Offer products for sale using our PCI-compliant third-party vendor for no-hassle payment, including handling VAT tax issues for international purchases.
  • Create free trial versions of products that you offer for sale (feature due in a future release).
  • Maintain your products by uploading patches and updates to posted products, or withdrawing a previously posted product.
  • Manage what a consumer sees on the Adobe Exchange website.
  • View metrics for each posted product, reviews, and ratings of purchased items.

Development cycle

  1. Define your product
    To create a product for Adobe Exchange, you must develop content that augments the capabilities of Adobe Creative Cloud.
  2. Package your product
    For content (such as C++ plug-ins built with an application SDK), you can use the online Adobe Exchange Packager and the Packaging and Signing Toolkit.
  3. Upload the product to the Adobe Producer portal
    Use the Producer’s portal to upload your packaged content, preview both the in-app appearance and functionality and check the download and purchase workflows. See Getting Started with the Producer portal for more information.
  4. Submit your product for review
    When you have finished testing your product, use the Producer's portal to submit the final content to Adobe for approval. All content must be approved before you post it to the public server. See the Approval guidelines below.
  5. Publish your product to the Adobe Exchange website
    When your product is tested and authorized, use the Producer’s portal to publish your product to the public server. Users can discover and download on the Adobe Exchange website as per the rules you have set up for it. Published products are either Free, or Paid.
  6. Manage your product
    Once you have offered products publicly, use the Producer portal to maintain, and build your product line. You can post patches and updates to new versions, define product groups, and view metrics about your product. Users who install your product can post reviews and ratings that you can use to improve your product.

Approval guidelines

Adobe Exchange only features content that conforms to our guidelines and the Terms of Use, and that pass our Approval Process. Here is a summary of our guidelines and some of the types of content that are not allowed:

  • Content must install without error.
  • Content must be accessible from within all targeted Adobe Creative Cloud applications.
  • Content must not cause crashes, system errors, or any major failures.
  • Credentials for content that requires authorization to use.
    If content requires a special username/password or code or serial number, pre-create an account and provide the credentials to the Adobe Exchange Team. Be sure to include this information in the Note to Approvers field when you submit your product for approval.
  • Content redirects to non-Adobe Exchange sales channel.
    A free item on Adobe Exchange, cannot contain a redirect to any outside sales site for purchase of the functionality or other products from the producer.
    A for-fee item on Adobe Exchange can contain a link to a non-Adobe Exchange website that promotes the Producer’s business in general. It cannot link to any third-party web store or to any location other than the Producer’s home page or site.
  • Extensions must be free from all inappropriate content (see below).

Inappropriate content

  • No adult content.
    Extensions must not contain intense violence, blood, gore, sexual content, nudity, or strong language.
  • No malicious content of any kind.
    Extensions must not contain or promote (for example) phishing, spamming, hacking, password trafficking, spyware, or contain malware, trojans, or viruses.
  • No illegal or questionable content.
    • Extensions must not contain or promote illegal or highly regulated activities. For example, pharmaceutical sales, promotions or sweepstakes, alcohol or tobacco sales.
    • Extensions must not violate intellectual property rights. For example, extensions must not promote DRM circumvention, or contain copyrighted or trademarked content belonging to someone else.
    • Extensions must not promote hatred, violence, or bullying. For example, extensions must not contain hate speech or promote or enable cruel behavior toward others.

Submission of an extension with content violating our guidelines is not approved. To conform to our guidelines, modify the content and resubmit.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy