DPI metadata property not generated for image assets in AEM Assets
In Adobe Experience Manager (AEM) Assets, the tiff:pixelDpi metadata property isn’t generated or populated for image assets, which affects implementations that rely on this property for DPI-based validation and processing. AEM populates supported DPI metadata properties instead. To fix this issue, use dam:Physicalwidthindpi and dam:Physicalheightindpi to retrieve DPI values and verify that the source asset contains valid embedded DPI metadata.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all environments)
Symptoms
When uploading image assets to AEM, the metadata property ./jcr:content/metadata/tiff:pixelDpi isn’t generated or populated for any asset type. This issue occurs consistently across all environments and affects all image formats, including JPEG, TIFF, PNG, and PSD. Implementations that rely on tiff:pixelDpi for DPI-based validation and processing are affected.
Cause
AEM as a Cloud Service doesn’t extract or populate the tiff:pixelDpi property during asset ingestion. Instead, the standard metadata
Resolution resolution
Follow these steps to resolve the issue:
-
Use the following properties to extract DPI values from image assets:
./jcr:content/metadata/dam:Physicalwidthindpi(horizontal DPI)./jcr:content/metadata/dam:Physicalheightindpi(vertical DPI)
-
Ensure that your implementation uses
dam:Physicalwidthindpianddam:Physicalheightindpiinstead oftiff:pixelDpi. -
For assets where these properties are missing but should be present, re-save or reprocess the source asset in an image editor to ensure that DPI metadata is embedded before uploading it to AEM.
-
If DPI values are still missing for assets that contain valid embedded DPI metadata, verify the source file’s metadata using a tool such as exiftool before uploading it to AEM.
-
After uploading or reprocessing the asset, check the asset metadata in AEM to confirm that
dam:Physicalwidthindpianddam:Physicalheightindpiare populated.