EPS asset dc:format changes from postscript to pdf in Adobe Experience Manager

Last update: June 29, 2026

In Adobe Experience Manager as a Cloud Service, EPS assets show an incorrect dc:format value that changes from application/postscript to application/pdf after asset processing or XMP writeback workflows. The system initially identifies the correct format but later updates it from embedded XMP metadata. To fix this issue, correct the embedded XMP metadata before uploading or processing the asset.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

EPS asset uploads initially show dc:format=application/postscript
After processing, the value changes to dc:format=application/pdf

Logs show metadata updates during asset processing workflows as following:

code language-none

code language-none
`com.adobe.cq.assetcompute.impl.connection.CreateRenditionJob Update asset metadata for asset '/content/dam/.../your-file.eps' with: {dam:size=567843, dam:sha1=..., dc:format=application/pdf, dam:processingId=...}`

com.adobe.cq.assetcompute.impl.connection.CreateRenditionJob

Update asset metadata for asset '/content/dam/.../your-file.eps'

with:

{dam:size=567843, dam:sha1=..., dc:format=application/pdf, dam:processingId=...}

EPS file contains embedded XMP metadata:<XMP-dc:Format>application/pdf</XMP-dc:Format>
AEM extracts embedded XMP metadata and synchronizes it during XMP writeback, which may overwrite the repository metadata stored at /content/dam/<asset>/jcr:content/metadata/dc:format.

Cause

AEM stores metadata in the repository and synchronizes it with embedded XMP metadata when supported.

During asset ingestion, AEM inspects the binary content and identifies EPS files as application/postscript. During XMP extraction and writeback, AEM reads embedded metadata. If the file contains:

<XMP-dc:Format>application/pdf</XMP-dc:Format>

AEM updates the repository metadata to match the embedded XMP value.

This behavior is expected and aligns with XMP metadata synchronization in AEM.

Resolution resolution

To fix this issue, follow these steps:

Identify EPS assets where the dc:format value changes from application/postscript to application/pdf.
Verify the embedded XMP metadata using a metadata inspection tool like ExifTool: exiftool -XMP-dc:Format your-file.eps

Note: If the output shows application/pdf, the embedded metadata drives the value update in AEM.
Update the embedded XMP dc:Format value to application/postscript before uploading the asset:

exiftool -XMP-dc:Format="application/postscript" your-file.eps
Upload the updated file or replace the existing asset in AEM.
Review the application or workflow used to generate the EPS files.
Confirm that the embedded XMP metadata is correctly populated during export.
Check export workflows in the following tools:
- Adobe Illustrator
- Adobe InDesign
- Third-party publishing tools
- Automated file conversion pipelines

recommendation-more-help

experience-cloud-kcs-help-kbarticles