Can AEM Assets do renders on the fly instead of during asset processing?

[dmescia2]

We have use cases (mainly for print purposes) where we need to be able to have assets rendered out to different file types. For example, we may have a large ful size tiff that the end user needs as a jpg. The current process for creating renditions appears to require those renditions to be created and take up storage in the system at asset processing. And then there is not a way for end users to select the rendition they need when they download the asset(s) or link to them via Asset Link.

I'd like to be able to set up what the renders need to do (ex. convert file to jpg) but not have the file rendered out until the end user clicks to download it. I'd like for them to see the render options for the file when they click download and then select the render they want. Is there a way to handle this now in AEM or would this be a feature request?

[narendiran_ravi]

AEM assets do not support this functionality OOB. We can create custom services for this. 

AEM Dynamic Media is actually an excellent solution for this use case! It provides on-demand image transformations through URL parameters without requiring pre-generated renditions. This is a much simpler approach than implementing a custom solution . Refer - https://experienceleague.adobe.com/en/docs/dynamic-media-developer-resources/image-serving-api/image... 

[dmescia2]

Dynamic Media does not address the need to manage renditions for non digital work. And from what we’ve been told it also does not work with Asset Link. We still do a lot of print work so we need a solution for those workstreams. Dynamic Media would only solve the digital needs. 

[kautuk_sahni]

@dmescia2 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!

[dmescia2]

It did not address the full issue. Only the digital ones. I opened a feature request to address the full scope. One of the challenges I have with AEM is that it seems to be built to only address the needs of the digital world. And more specifically, the world of websites. There are a ton of other mediums out there that do not follow the same workflows as web. It would be nice to see AEM start to address those as well ... especially print. AEM seems especially poor at dealing with any of the print workflows out there.