I'm experiencing an issue with the Image Map editor in AEM as a Cloud Service DAM and would appreciate any insights.
Is there a way for adding WebP support to the image map editor?
Issue Description:
What I've Tried:
Environment:
Views
Replies
Total Likes
hi @SyntaxError_07,
The Image Map editor plugin uses a supportedMimeTypes property to determine which file formats can be edited. By default, this configuration only includes traditional formats like JPEG, PNG, TIFF and SVG.
To add WebP support to the image map editor, update the supportedMimeTypes property on the image map plugin's configuration node:
<map
jcr:primaryType="nt:unstructured"
supportedMimeTypes="[image/jpeg,image/png,image/tiff,image/svg+xml,image/webp]"
features="*"/>I'm not completely certain because I've tried before but after applying this configuration, the image map editor should recognise WebP images and display the editing interface similar to JPEG and PNG formats.
Views
Replies
Total Likes
Hi @giuseppebaglio, thanks for the reply.
I did tried setting the image/webp in the maps plugin, but no luck i got the same issue again
Views
Replies
Total Likes
Hi @SyntaxError_07,
The behavior you’re seeing is expected in AEM as a Cloud Service, because the Image Map Editor currently does not support WebP format. Even if you add image/webp within the supportedMimeTypes configuration, AEM will still display the message: “Editing is not supported for this type of asset”
The Image Map editor is implemented using Adobe’s Asset Editor framework, and the supported image formats are currently limited to:
JPEG (image/jpeg)
PNG (image/png)
TIFF (image/tiff)
SVG (image/svg+xml)
WebP is supported for rendering & preview inside DAM, but not supported for editing features such as image map creation, cropping, smart crop, rotation, etc.
So modifying this config will not work:
supportedMimeTypes="[image/jpeg,image/png,image/tiff,image/svg+xml,image/webp]"
because the editor backend does not include WebP handlers.
Until Adobe adds native WebP support, you can use one of these approaches:
1. Convert the WebP to JPEG/PNG temporarily
Create your image map on a PNG/JPEG version
Save the imageMap metadata
Reapply the map configuration to the WebP asset if needed
2. Use a custom image map component
If you need WebP editing frequently:
Develop a custom UI that uses a JavaScript-based image map library
Example libraries: ImageMapPro, ImageMapster, or native <area> map UI
Bind generated coordinates to asset metadata
3. Submit a feature request
You can request Adobe Support to enable WebP Image Map editing in future releases, since WebP support is currently on the product backlog.
Summary
1. WebP images display correctly in AEM DAM
2. WebP is not supported by the Image Map Editor in AEMaaCS
3. Use JPEG/PNG for editing or build a custom solution
Hope this helps!
Let me know if you need a sample custom implementation approach.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies