Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

AEM Asset Uploads should be case-insensitive


Community Advisor


Request for Feature Enhancement (RFE) Summary: Case Insensitive Asset Upload in AEM
Use-case: Currently, if we upload assets - abc.pdf and ABC.PDF - They are treated as different assets in AEM (Your local machine's storage parses it in case insensitive manner)
The JCR stores the nodes abc.pdf and ABC.PDF as 2 distinct nodes. 
Most storage systems even in different OS (Mac | Windows) store files by default in case insensitive manner.
Current/Experienced Behavior: The assets are treated as different due to their case difference.
Improved/Expected Behavior: The assets should be treated as similar and versioning popup should be displayed.
Environment Details (AEM version/service pack, any other specifics if applicable): 2023.11.14227.20231108T162349Z
Customer-name/Organization name: TA Digital
Screenshot (if applicable): N.A
Code package (if applicable): N.A


1 Comment





Thanks for proposing this idea
This has been reported to the engineering under the internal reference ASSETS-32211. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Status changed to: Investigating