Adobe’s marketplace is the first thing to price
Adobe distributes Creative Cloud plugins through the Developer Distribution portal into the Creative Cloud Marketplace, which appears in the Creative Cloud desktop app and on the Exchange website. The portal handles UXP plugins, and ZXP (CEP) packages too. Adobe’s FAQ describes the paid path:
- Paid listings use “our third-party payment provider FastSpring”. You create a FastSpring account, set a payment method, and add the key to your public profile.
- “For any paid product you offer for sale, you will take 90% of the sales revenue.”
- FastSpring can add an extra layer of security: customers receive “a unique license code in their receipt email”, so that only they can use your plugin. You generate and upload a large batch of codes for a new paid plugin, and have to contact Adobe to add more when the batch runs out.
That is a full path from listing to payout. If your buyers already open the Creative Cloud app to find plugins, it is worth taking seriously, and the 90% share is not a high fee. What you give up is the checkout, your pricing flexibility and, unless you collect it separately, the buyer relationship.
When to sell with Stripe and Clavem
| You want | Marketplace with FastSpring | Stripe and Clavem |
|---|---|---|
| Discovery inside Creative Cloud | Yes | No |
| Your own checkout, coupons, team invoices | Whatever the listing flow offers | Stripe Checkout, Payment Links, invoices |
| One key for a Photoshop plugin and an After Effects plugin | Per listing | One product or a bundle, as you choose |
| License codes you do not have to pre-load in batches | Uploaded in batches | Generated per purchase |
| Device limits and a page where buyers move devices | Not described in the FAQ | Device limit and a device page |
| Adobe’s reviews and store visibility | Yes | No |
You can also do both, because Adobe’s marketplace listing and your own site are separate channels; check the current listing terms in the portal before you rely on that.
Technical notes for UXP
Declare the domain. In manifest v5, “any permissions not explicitly declared in the manifest are not granted by default”. Under requiredPermissions, add network with the domains your plugin calls, for example https://clavem.io. Version 5 needs Photoshop 23.3.0 or later for the full permission model.
Secure storage is a cache. UXP offers require('uxp').storage.secureStorage for key-value storage. Adobe’s own reference says it should be regarded “as a cache rather than a persistent storage”, because data can be lost if the host application is uninstalled and its secure storage deleted, and that it is not for secrets you need to hide from the current user. Plan for it: if the stored key and token vanish, the plugin must be able to ask the user for the key again, and activation must not burn a second seat when it does.
Keep the fingerprint stable. If your fingerprint is a random id kept in secure storage, losing the storage loses the id, and the next activation takes a new seat. Keep the id in a file in the plugin’s data folder, which lasts longer, or derive it from something that survives. Activating again with the same fingerprint returns the same seat, so a stable one makes recovery free for the customer.
Photoshop runs on two systems. A person who owns a Mac and a Windows PC will activate twice. Device limits of 2 or 3 fit, with a name such as Photoshop on macOS as the instance_name.
Offline. Adobe’s FAQ notes that people working in restricted environments can install scripts, UXP plugins and CEP extensions without the Creative Cloud app, though a UXP package cannot be downloaded from Exchange first because it would tie to a specific user. A signed token lets the plugin keep running there: verify it with Web Crypto or a small library, and trust it until refresh_by. See offline verification.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Annual subscription, or one-time with paid major versions | Keeping up with new Photoshop versions is the ongoing cost to cover |
| Device limit | 2 or 3 | Two systems and a reinstall |
| Trial | 7 to 14 days from first run, or a free edition | Long enough to try the plugin on a real file |
| Updates | Marketplace listing if you list there; otherwise a download page and a check against the releases endpoint | Clavem releases can label files ccx or photoshop |
Doing this with Clavem
Create a product, connect Stripe, map the price. A buyer gets a key and an order page with the .ccx file. In the plugin panel, a field takes the key, activate runs once, and validate runs when the panel opens. UXP’s fetch does the calls. The License API answers with open CORS and accepts JSON or form bodies. The Node.js guide shows the call sequence in JavaScript, which maps directly onto a UXP plugin. For plugins on the Adobe side of After Effects, see After Effects plugins.
Guides to follow
- License key validation in Node.js
- Offline license verification in Node.js
- Device activation in Node.js
Questions
How does Adobe handle payment for paid plugins?
Adobe's Developer Distribution FAQ says paid listings use its payment provider FastSpring, and that for any paid product you take 90% of the sales revenue. You register with FastSpring and add its key to your profile. FastSpring can also issue license codes in receipt emails.
Does a Photoshop UXP plugin need to declare the network domain?
Yes. With manifest v5, permissions that are not declared in the manifest are not granted. List the domains the plugin calls under requiredPermissions, network, domains.