SVG should be able to replace with jpg/png

[#1]

Request for Feature Enhancement (RFE) Summary:	Add mimetype of svg files to DAMUtil.java as it is read only file.
Use-case:	Since it is an image mimetype, replace should happen between svg/png/jpeg etc.
Current/Experienced Behavior:	Currently we are unable to replace a jpeg/png with svg as it is not treating it as image mimetype in Dynamic Media
Improved/Expected Behavior:	We should be able to replace.
Environment Details (AEM version/service pack, any other specifics if applicable):	DEV/STAGE/PROD
Customer-name/Organization name:	Signify
Screenshot (if applicable):
Code package (if applicable):

[#2]

When you mention "DAMUtil.java", can you please provide the full package name?

And besides that, what is the requirement you want to solve? When you say "we are unable to replcae jpeg/png", in which are are you unable to do that? Can't you embed a SVG from DAM (a.k.a /content/dam) but only JPEGs and PNGs? Or is it rather related to Dynamic Media?

Please be a bit more specific, because I think that just adding SVG support to a DAMUtil.java library function is probably not solving your problem.

[#3]

Package com/day/cq/dam/commons/util/DamUtil.java

The requirement we're trying to solve is to support SVG assets in the same way we currently support JPEG and PNG files — specifically when embedding or referencing assets from the DAM. Right now, we're encountering issues where SVGs cannot be used interchangeably with JPEGs/PNGs, particularly when generating renditions or serving optimized assets.

To clarify, yes — we can upload and store SVGs in the DAM (e.g., /content/dam), but the issue arises when trying to use them dynamically or in places where JPEGs/PNGs work seamlessly, especially in contexts involving Dynamic Media. For instance, Dynamic Media does not process or optimize SVGs in the same way it does for raster formats.

So while adding SVG support to DAMUtil.java might be part of the solution, the broader issue seems to be related to how SVGs are handled across the delivery pipeline, including Dynamic Media limitations.

[#4]

thanks, it's much clearer now.

[#5]

@nidhi26 Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-57913. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.