Review & Guidelines

If you are looking to distribute your plugin to the Adobe Creative Cloud Marketplace, you will need to submit it for review and follow our guidelines.

Overview

Plugins submitted to the Creative Cloud Marketplace always go through a review process, designed to ensure that every product—whether free or paid—meets Adobe's quality standards.

A dedicated team carefully audits and approves extensibility listings. To help avoid delays and keep the review queue moving smoothly, please ensure your plugin fully complies with our requirements.

data-slots=text

data-variant=info

Review Criteria

The review team will assess your submission based on a variety of factors, including:

• Branding and Trademark Compliance: proper use of Adobe trademarks, brand assets, and naming conventions
• Listing Quality: clear descriptions, valid links, appropriate subtitle, and support channel availability
• Functional Testing: UI behavior, button functionality, input handling, error feedback, and keyboard shortcuts
• Platform Compatibility: multi-architecture support, code signing, and installation behavior
• External Services Integration: login/logout flows, test credentials, and service connectivity
• User Experience: responsive layouts, loading indicators, scrolling behavior, and accessibility
• Performance: resource usage (CPU/RAM) and compatibility with host applications
• Localization: multi-locale support and keyboard compatibility
• Content Safety: harmful or unacceptable content policies
• Transparency: privacy policies, terms of service, and third-party dependencies
• Code Quality: presence of bugs, harmful code, or exposed developer tools

Submission Checklist

Check off the tasks in this list before submitting. If you have any questions, feel free to contact us at ccintrev@adobe.com.

1. Assets

Ensure that all required assets are included and named correctly in your plugin submission, as per the Create Listing guide, including:

• Files: all required plugin files and dependencies
• Icons: custom-designed icons for all themes, resolutions, and display scales (no placeholder or default icons)
• Screenshots: high-quality screenshots that accurately represent your plugin's functionality
• Release notes: clear documentation of changes and new features
• Testing information: comprehensive testing instructions and scenarios
• Test credentials: share login credentials, license keys, or test accounts with the review team so they can validate all functionality, including any paid or premium features

All visual assets must:

• Be free of unauthorized Adobe logos or trademarks
• Display correctly in both light and dark themes
• Meet the required dimensions specified in Adobe's documentation
• Use unique icons for each panel (if your plugin has multiple panels)

2. Metadata

Provide accurate and up-to-date information, including:

• Plugin name: must be unique and use ASCII-only characters in the manifest
• Subtitle: must be relevant and clearly describe what the plugin does
• Description: must be clear, accurate, and localized where applicable; avoid vague or misleading language
• Version: current version number
• Author: developer or company name
• Contact information: valid email or support channel (email, GitHub, or website with contact form)
• Website and support links: must open successfully and contain valid contact information
• Privacy policy and terms of service: must provide valid, accessible URLs
• Third-party dependencies: clearly mention if your plugin requires another application or service
• Pricing information: if your plugin is paid, offers a trial, or has a free tier, this must be clearly stated
• Trader information: required in the publisher profile if you wish to distribute your plugins in the EU region. See the EU Digital Services Act Trader Requirements for more information.

data-slots=text

data-variant=warning

3. Legal

Ensure that all legal and licensing requirements are met, including:

• Attribution
• Copyright
• Intellectual property rights

4. Branding Guidelines

Review the Adobe Branding Guidelines thoroughly to ensure your plugin and all related materials—including advertising, websites, and other media—comply with Adobe's branding standards.

These guidelines regulate, among other things, the correct usage of:

• The Adobe logo and other trademarks
• Adobe product names (do not use Adobe trademarks like "Photoshop Enhancer" without written permission)
• Approved badges and icons
• Social media presence
• Public profile and website content

data-slots=heading, text

data-variant=info

5. Platform Compatibility

Ensure your plugin works correctly across all supported platforms and architectures:

• Multi-architecture support: UXP Hybrid plugins submitted to the Marketplace must include binaries for all three architectures (macOS arm64, macOS x64, Windows x64)—submissions with missing architectures will be rejected
• Code signing: macOS .uxpaddon executables in Hybrid plugins must be code signed and notarized with a valid Apple Developer ID certificate (minimum 1 year validity). See the Hybrid Plugins packaging guide for details.
• Installation: avoid OS-level warning prompts during installation; ensure no crashes during install or use
• Host application compatibility: test that your plugin does not crash or negatively impact host applications

6. Functional Requirements

Your plugin must meet the following functional standards:

• Launch behavior: plugin must launch successfully via the Plugins menu, Plugins panel, or other entry points
• User interface: no empty screens, blank panels, or clipped modal dialogs; every screen must display meaningful content
• Loading indicators: display progress feedback for any content or operations that take time to load
• Buttons and controls: all interactive elements must be visible, not overlap, and perform their expected actions
• Input handling: text fields must support English characters, special characters, numbers, and localized keyboards
• Error handling and feedback: provide clear user guidance when actions fail, selections are unsupported, or internet is disconnected; plugin must recover gracefully after reconnecting
• Keyboard shortcuts: must work as expected (except in applications where unsupported, such as InDesign v18.5 or Premiere Pro v25.6)
• Scrolling behavior: scrollbars must appear when needed; content must be accessible without resizing the panel
• Responsive layout: plugin must work without requiring users to resize the panel
• No developer tools: do not expose debug consoles or developer tools in production builds

7. External Services Integration

If your plugin connects to external services, ensure the following:

• Test credentials: provide valid test login credentials or license keys in the "Notes to Reviewer" section
• Login and signup flow: users must be able to sign up or log in; if login is browser-based, the plugin must handle abandoned login gracefully and provide a link back to your website
• Logout functionality: users must be able to log out from within the plugin
• Service connectivity: handle network failures gracefully with appropriate user feedback

8. Companion Apps

If your plugin uses a companion application:

• The companion app must install successfully on all supported operating systems
• The plugin must communicate with the companion app successfully
• Monitor for abnormal CPU or RAM usage
• The plugin must not launch external applications (only browser links are allowed)

9. Localization

If your plugin supports multiple languages:

• Test plugin functionality in all supported locales (Mac only for review purposes)
• Ensure no string truncation occurs in any supported language
• Support localized keyboard layouts and input methods

10. Performance and Resource Usage

Your plugin must demonstrate responsible resource management:

• Monitor and optimize CPU and RAM consumption
• Ensure the plugin does not cause performance degradation in host applications
• Avoid memory leaks or excessive background processing

Common Rejections Causes

The following table lists frequent reasons for plugin submission rejections, along with recommended actions to resolve them.

Content Requirements

Plugins must adhere to Adobe's General Terms of Use and Content Policies found in the Adobe Transparency Center. For example, in the interests of user safety and acceptable standards, plugins must not:

• Contain or generate illegal content (such as CSAM, content that encourages illegal drug use, etc.).
• Contain or generate adult content (such as sexual content, nudity—consensual and non-consensual, gore, graphic gore or violence, or strong language).
• Contain or generate hate speech or speech that promotes violence or bullying or cruel behavior to anyone.
• Generate content that promotes, automates, or facilitates highly regulated activities (such as financial advice, medical advice or diagnosis, legal advice or documents, contracts).
• Contain or generate code that is malicious (such as viruses, malware, spyware, etc.).
• Participate in misinformation/disinformation campaigns.
• Violate intellectual property rights, including copyright, of other persons and companies.
• Automatically perform actions determined by AI that would be destructive or that can't be undone without explicit user consent.

Generative AI Guidelines

If your plugin leverages generative AI to create content, it must adhere to Adobe's General Terms of Use, Developer Terms of Use and Content Policies found in the Adobe Transparency Center. Specifically:

• Your plugin must not generate illegal, adult, or hateful content.
• Your plugin must leverage filtering technologies to prevent the generation of prohibited content.
• You must thoroughly test your plugin to ensure that illegal content is not generated.
• Your plugin must not automate regulated activities (such as financial, medical, or legal advice) without proper disclaimers and user consent.
• Your plugin must not generate malicious code or participate in misinformation campaigns.
• Your plugin must not violate intellectual property rights of other persons and companies.
• Your plugin must not perform destructive actions without explicit user consent.

data-slots=text

data-variant=warning