Questions about Photoshop API integration with AEM Assets and advanced PSD manipulation

[Wilnaweb1]

Hello community,

I am currently exploring the use of the Photoshop API and I have a few questions regarding its capabilities and possible integrations:

1. Integration with AEM Assets

   • Can the Photoshop API directly access a file stored in AEM Assets for processing, or is it required to make the file available through a public URL or store it in a storage service such as S3, Azure, or Dropbox before processing?

2. Editing PSD files

   • Is it possible to perform multiple edits on the same PSD file (for example: text replacement, updating Smart Object images, applying adjustments) and only save/export the final result at the end?

   • Or does each change require a full cycle: download PSD → modification → upload again → new request for the next change?

3. Exporting with multiple artboards

   • Does the API allow exporting multiple images (e.g., JPGs) in a single request, based on the different artboards within the same PSD file?

I’d like to clarify these points to better evaluate the architecture for integrating AEM with the Photoshop API in an automation workflow.

Thanks in advance for any guidance or references!

What product are you using?What area of the product are you using?

PHOTOSHOP API

ADOBE AEM

[Abie]

Hi @Wilnaweb1 ,

A few points based on my experience-

• Reading your description, I believe you want to edit your PSD files but still persist those in AEM Assets. This can also be achieved using AEM Assets <> Photoshop integration without AIO. You should be able to connect these two applications, checkout assets from DAM into Photoshop and checkin again after changes. This works pretty well.
• Coming back to AIO integration, lets say you create an AIO app and consume photoshop API. If this app is an Asset Compute worker, which means the trigger is AEM, which means AEM asset is being processed by AIO using photoshop API, in this case the photoshop API will be able to access the asset stored in DAM.
• Continuing from above point, if the AIO app is not an Asset Compute worker, meaning the runtime action is not triggered by AEM, but something else, then indeed it won't be able to access asset from DAM. However, you could still use S7 URL of the asset in that case. We have tried this and it works well. 

I hope it helps, Thanks! 

[tmj]

Clarification: @Abie, when you say AIO, I assume you mean Adobe Developer App Builder. https://developer.adobe.com/app-builder/ 

[Abie]

Yes, I mean Adobe Developer App

[seong_kooio1189]

@Wilnaweb1 

ngrok http 80

•