Documentation

Dynamic Media doesn’t publish or generate delivery URLs for unsupported file types

Last update: Wed Jun 17 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Dynamic Media only processes and publishes asset types it explicitly supports, so unsupported formats — fonts, Office documents, Lottie/JSON, .ics/.oft/.emltpl, AEP/AEX, and others — don’t synchronize to Dynamic Media and produce no delivery URLs. The root cause is that Dynamic Media enforces its own server-side list of supported input formats, and that list isn’t extended by local AEM MIME type configuration. Adding custom MIME mappings in AEM doesn’t change what Dynamic Media will ingest. The resolution is to confirm the format against the official supported list and, for unsupported types, deliver the file through an approved alternative such as AEM direct delivery, ZIP packaging, or OpenAPI static delivery.

Description description

Issue: Dynamic Media doesn’t publish unsupported file types or generate delivery URLs for them

Description

Users upload assets to AEM expecting Dynamic Media to publish them or generate public delivery URLs, but Dynamic Media rejects or ignores unsupported file types. Affected assets show as UploadFailed, appear without delivery URLs, return empty /original/ responses, or don’t appear in the Scene7 company at all. The failures occur regardless of whether the MIME type is manually added to the Scene7AssetMimeTypeServiceImpl configuration, because Dynamic Media’s asset ingestion is restricted by its own server-side supported format list.

Environment:

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • AEM Dynamic Media
  • AEM Managed Services
  • Dynamic Media Classic / Scene7

Issue/Symptoms:

  • Dynamic Media shows the error was not processed because it is not a supported file format!.
  • Delivery URLs are missing or empty for formats such as .ttf/.woff, .emltpl, Lottie/JSON, MS Office files, and AEP/AEX.
  • Assets upload to AEM, but don’t appear in Scene7.
  • Publishing Office, Lottie, or JSON assets generates no Dynamic Media embed code or public URL.

Root cause:

Dynamic Media maintains a strict list of supported input formats. Unsupported formats can’t be processed, transformed, or published, regardless of local AEM MIME type configuration. Adding custom MIME mappings in AEM doesn’t extend Dynamic Media ingestion capabilities. Dynamic Media Classic / Scene7 also blocks certain file types for security, such as JS and TXT depending on the delivery domain. In AEMaaCS, additional restrictions apply because assets must fall within both the AEM and the Dynamic Media supported MIME lists.

How to confirm

  1. Check whether the asset type is supported. Review the official supported file format list for Dynamic Media and cross-check the extension in the tables. If the file type isn’t listed, Dynamic Media won’t publish it.
  2. Check the Dynamic Media failure message stored in the asset metadata. Open the asset in AEM under Properties > Advanced (or Metadata) and look for the dam:scene7FailureMsg field. Unsupported types show errors such as was not processed because it is not a supported file format!. Confirm dam:scene7FileStatus = UploadFailed or that no Scene7 job IDs appear.
  3. Validate the MIME type AEM detected. In the asset’s jcr:content/renditions/original/jcr:content node, review jcr:mimeType. For example: application/octet-stream for .emltpl, or text/calendar for .ics. If AEM detected the wrong MIME type, correct it using the Day CQ DAM Mime Type Service — though this doesn’t make the file supported if Dynamic Media doesn’t list the type.

Resolution resolution

  1. Confirm whether the file type is unsupported by product design. The following formats can’t generate Dynamic Media delivery URLs:

    • Fonts (.ttf/.woff)
    • Office formats such as XLSX, PPTX, and DOCX
    • Lottie (.lottie, JSON)
    • ICS/OFT, even with MIME configuration applied
    • AEP/AEX

  2. Serve the file directly from AEM Publisher when Dynamic Media processing isn’t possible.

  3. Repackage unsupported files into a supported container. For example: package an .emltpl file as a ZIP.

  4. For AEMaaCS only: use Dynamic Media OpenAPI URLs for static delivery if the capability is enabled.

  5. Test the resulting URL and confirm the correct content downloads through the chosen delivery mechanism.

Validation

  1. Confirm the asset now has a valid delivery mechanism (AEM direct, ZIP, or OpenAPI) and loads successfully.
  2. Re-test a Dynamic Media upload with a confirmed supported format. For example: a JPG, to confirm Dynamic Media itself is functioning correctly and no global misconfiguration exists.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f