How to Get Your Adobe Express Add-on Approved: Avoiding the Most Common Rejections

https://youtube.com/shorts/hRNmOtOWna0

Editor’s Note: Welcome Sonya P., a 2026 Adobe Developer Champion, software developer, and content creator, to the Adobe Developer Blog!

So you’ve spent hours coding, tweaking, and perfecting your brand-new Adobe Express add-on. You’re ready to share it with the world, hit "Submit for Review," and then... rejection.

If you’ve received that dreaded email from the Adobe Express Review Team, you aren't alone. Every single add-on submitted to the Adobe Express Marketplace is reviewed by a real person. While we officially communicate a turnaround time of 10 business days, reviews are typically completed much faster — in most cases within 2-3 days, provided all required details are submitted.

Delays usually happen when test credentials are missing, when additional discussion with internal stakeholders is needed to address specific concerns, or when developers submit multiple add-ons for review on the same day.

Here’s a breakdown of the most common pitfalls developers face when submitting their Adobe Express add-ons — and exactly how you can avoid them to ensure a smooth approval process.

1. Violating brand guidelines

One of the quickest ways to earn a rejection is by mishandling Adobe branding. It’s easy to get excited and want to splash the Adobe logo everywhere to show compatibility, but there are strict rules in place.

The mistake: Using Adobe logos or product names incorrectly.

The fix: Double-check your listing images, descriptions, and — crucially — your own external website. The review team checks your site, too. Make sure you are strictly following Adobe's official brand guidelines for third-party developers. You should also ensure you obtain approval from the branding team before using any Adobe logos. If you don’t want to seek permission, you can use the “Designed for” Adobe logo as a compliant alternative.

2. Functional issues and UI traps

According to the review team, a massive 70% of rejected add-ons fail due to basic functional issues. You might have built a brilliant AI integration or a stunning design tool, but if the core user interface is broken, it won't pass.

The mistake: Missing critical UI controls. A very common example is leaving out a "Cancel" button — or implying that a “Cancel” button always stops the process when it may not. The request may already have been sent to the server for processing, and cancellation may no longer be possible. And if users enter a workflow with no way to back out, they’re essentially trapped.

The fix: Map out every single user journey inside your add-on. Make sure there is always a clear, accessible way to cancel an action, go back, or close a menu. When cancellation is not technically possible after processing has begun, explicitly state that. If the operation consumes credits, be clear that credits will be deducted once the process starts — even if the user tries to cancel afterward. Providing this kind of upfront clarity helps set the correct expectations and improves the transparency of the experience.

3. Forgetting test credentials

This one seems obvious, but it happens all the time. If your add-on requires an account, a subscription, or specific permissions to use, the reviewer needs a way in.

The mistake: Submitting an add-on that sits behind a login screen without providing test credentials in the notes to the reviewer. This also applies to add-ons that use AI for data processing or other credit-based workflows: If the review process needs to run those flows end-to-end, there must be enough credits available for testing.

The fix: Always include a dedicated username and password for the review team when submitting your add-on. Reviewers need to be able to log in and actually test the functionality you built. Because the review team performs thorough testing across Chrome, Safari, Edge, and Firefox, make sure there are sufficient credits available for a complete and effective evaluation if your add-on uses AI or other credit-based processing.

4. Testing on only one browser and/or "localhost"

"It works on my machine" is a classic developer excuse, but it won't fly with the marketplace review team.

The mistake: Testing your add-on only in your localized, perfectly optimized development environment.

The fix: Test your add-on across multiple browsers (Chrome, Firefox, Safari, Edge) to catch compatibility errors early. You should also test under real network conditions, not just on your lightning-fast local setup. Throttle your network speed in your browser's developer tools to see how your add-on performs when the connection isn't perfect.

The final checklist

Getting your Adobe Express add-on approved doesn't have to be a painful cycle of submissions and rejections. By paying attention to a few key details can significantly improve your chances of a fast approval.

Before you hit that blue Submit for Review button, always make sure you:

  1. Verify all logos and product names against Adobe brand guidelines.
  2. Ensure no users can get trapped in a workflow (add those “Cancel” buttons!).
  3. Provide valid test credentials.
  4. Test on different browsers and network speeds.
  5. Review the official Adobe Express developer documentation and pre-submission checklists.

Happy developing!