DocumentationAEMUser Guide

[AEM Assets]{class="badge positive" title="Applies to AEM Assets)."}

Assets supported file formats supported-file-formats

Last update: September 4, 2026
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • User
  • Admin

Adobe Experience Manager as a Cloud Service supports basic content management capabilities — storage, managing metadata online, versioning, upload and download, and so on — for any binary file, independent of its format. Adobe Experience Manager Assets supports a wide range of file formats and each product feature has varied support for different formats.

In addition, Experience Manager Assets provides extended support to generate previews and renditions and to extract metadata and text for full-text indexing. This extended support is provided using asset microservices.

The highlights for asset conversion using asset microservices include:

  • Key Adobe file formats produced by Adobe applications and services, including Adobe Photoshop, Adobe InDesign, Adobe Illustrator, Adobe XD, Adobe Dimension, and Adobe Acrobat or PDF.
  • Key imaging file formats.
  • Camera Raw file formats for a wide range of cameras, including Canon, Nikon, Fujifilm, Olympus, and other manufacturers (powered by Adobe Camera Raw).
  • Common document formats, including Microsoft® Office and Open Document formats.
  • Wide range of video and audio formats.

The following legend describes the level of support for each format.

Support level
Description
✓
Supported
*
See remarks below the table
-
Not applicable
IMPORTANT
Adobe Experience Manager Assets supports only the file formats listed in this article.
Some features might seem to work with other formats, but these formats are not officially supported. Results may be inconsistent, and features may not work as expected.
To ensure consistent and reliable results, use only the supported formats.

Adobe formats adobe-formats

File format
Thumbnail generation
Full-text extraction
Metadata extraction
Width/Height
AI
✓
-
✓
✓
COLLAGE
-
-
✓
-
DN
✓
-
✓
✓
SBSAR
✓
-
✓
✓
IDEAS
-
-
✓
-
INDD
✓
-
✓
✓ *
INDT
-
-
✓
-
PDF
✓
✓
✓
✓
PROTO
-
-
✓
-
PSB
✓
-
✓
✓
PSD
✓
-
✓
✓
XD
✓
-
✓
✓

* For Adobe InDesign files (INDD), the size of renditions are determined by the preview embedded in the INDD file. Configure the preferences in InDesign (Preferences > File Handling > Always Save Preview Images with Documents, Preview Size) so you can embed larger renditions.

Image formats image-formats

File format
Thumbnail generation
Metadata extraction
Width/Height
Crop
BMP
✓
-
✓
✓
EPS
✓
✓
-
-
GIF
✓
✓
✓
✓
JPEG
✓
✓
✓
✓
PNG
✓
✓
✓
✓
RGB
✓
✓
✓
✓
RGBA
✓
✓
✓
✓
SGI™
✓
✓
✓
✓
SVG
✓
-
✓
✓
TIFF
✓
✓
✓
-
WebP
✓
✓
✓
✓

3D formats support-3d-formats

The following 3D formats are supported.

See also Work with 3D assets in Dynamic Media.

Format
Storage
Versioning
Workflow
Publishing
Access control
Thumbnail preview
3D preview
Dynamic Media delivery
DN
✓
✓
✓
-
✓
✓
-
-
gLB
✓
✓
✓
✓
✓
✓
✓
✓
gLTF
✓
✓
✓
-
✓
-
✓
-
OBJ
✓
✓
✓
✓
✓
✓
✓
✓
STL
✓
✓
✓
✓
✓
-
✓
✓
FBX
✓
✓
✓
✓
✓
✓
-
-
3DS
✓
✓
✓
✓
✓
✓
-
-
USDz
✓
✓
✓
✓
✓
✓
-
✓
SBSAR
✓
✓
✓
-
✓
✓
-
-

Camera Raw formats camera-raw-formats

File format
Thumbnail generation
Metadata extraction
Width/Height
3FR
✓
✓
✓
ARW
✓
✓
✓
CR2
✓
✓
✓
CR3
✓
✓
✓
CRW
✓
✓
✓
DCR
✓
✓
✓
DNG
✓
✓
✓
ERF
✓
✓
✓
FFF
✓
✓
✓
GPR
✓
✓
✓
IIQ
✓
✓
✓
KDC
✓
✓
✓
MEF
✓
✓
✓
MFW
✓
✓
✓
MOS
✓
✓
✓
MRW
✓
✓
✓
NEF
✓
✓
✓
NRW
✓
✓
✓
ORF
✓
✓
✓
PEF
✓
✓
✓
RAF
✓
✓
✓
RAW
✓
✓
✓
RW2
✓
✓
✓
RWL
✓
✓
✓
SRF
✓
✓
✓
SRW
✓
✓
✓
X3F
✓
✓
✓

Document formats document-formats

The document formats supported for asset management features are as follows.

File format
Thumbnail generation
Full-text extraction
Width/Height
Metadata management
Connected Assets
Full document preview
DOC
-
-
-
✓
✓
✓
DOCX
✓
✓
✓
✓
✓
✓
EPUB
-
✓
-
-
-
-
HTML
-
✓
-
✓
✓
-
ODF
✓
✓
✓
-
-
-
ODM
✓
✓
✓
-
-
-
ODP
✓
✓
✓
-
-
-
ODS
✓
✓
✓
-
-
-
ODT
✓
✓
✓
✓
✓
-
OFG
✓
✓
✓
-
-
-
PDF
✓
✓
✓
✓
✓
✓
PPT
-
-
-
✓
✓
✓
PPTX
✓
✓
✓
✓
✓
✓
PS
-
-
✓
-
-
-
RTF
-
✓
-
✓
✓
✓
TXT
✓
✓
-
✓
✓
✓
XLS
-
-
-
✓
✓
✓
XLSX
✓
✓
✓
✓
✓
✓
XML
-
✓
-
-
-
-

Video formats video-formats

File format
Thumbnail generation
Metadata extraction
Width/Height
Preview
Output
3G2
-
✓
-
-
-
3GP
-
✓
-
-
-
AVI
✓
✓
✓
✓
-
DIVX
✓
-
✓
✓
-
F4V
✓
✓
✓
✓
-
FLV
✓
✓
✓
✓
-
M2T
✓
-
✓
✓
-
M2TS
✓
-
✓
✓
-
M2V
✓
-
✓
✓
-
M4V
✓
✓
✓
✓
-
MKV
✓
-
✓
✓
-
MOV
✓
✓
✓
✓
-
MP4
✓
✓
✓
✓
✓
MPEG
✓
✓
✓
✓
-
MPG
✓
✓
✓
✓
-
MTS
✓
-
✓
✓
-
MXF
✓
-
✓
✓
-
OGV
✓
-
✓
✓
-
QT
✓
-
✓
✓
-
R3D
-
✓
✓
✓
-
SWF
✓
-
✓
✓
-
WebM
✓
-
✓
✓
✓
WMV
✓
✓
✓
✓
-

Audio formats audio-formats

Assets as a Cloud Service provides XMP metadata extraction support for AIF, ASF, M4A, MP3, WAV, and WMA audio formats.

Supported inputs formats for audio and video transcription audio-video-transcription-formats

  • FLV (with H.264 and AAC codecs) (.flv)
  • MXF (.mxf)
  • MPEG2-PS, MPEG2-TS, 3GP (.ts, .ps, .3gp, .3gpp, .mpg)
  • Windows Media Video (WMV)/ASF (.wmv, .asf)
  • AVI (Uncompressed 8 bit/10 bit) (.avi)
  • MP4 (.mp4, .m4a, .m4v)
  • Microsoft® Digital Video Recording(DVR-MS) (.dvr-ms)
  • Matroska/WebM (.mkv)
  • WAVE/WAV (.wav)
  • QuickTime (.mov)

Tips and limitations limitations-and-tips

  • Currently, the file size limit for metadata extraction is approximately 15 GB. When uploading large assets, sometimes the metadata extraction operation fails.

Dynamic Media - Supported input video formats for transcoding video-dynamic-media-transcoding

Video file extension
Container
Recommended video codecs
Unsupported video codecs
AVI
A/V Interleave
XVID, DIVX, HDV, MiniDV (DV25), Techsmith Camtasia, Huffyuv, Fraps, Panasonic DVCPro
Indeo3 (IV30), MJPEG, Microsoft® Video 1 (MS-CRAM)
FLV, F4V
Adobe Flash
H264/AVC, Flix VP6, H263, Sorenson
SWF (vector animation files)
M4V
Apple iTunes
H264/AVC
−
MKV
Matroska
H264/AVC
−
MOV, QT
Apple QuickTime
H264/AVC, Apple ProRes422 & HQ, Sony XDCAM, Sony DVCAM, HDV, Panasonic DVCPro, Apple DV (DV25), Apple PhotoJPEG, Sorenson, Avid DNxHD, Avid AVR
Apple Intermediate, Apple Animation
MP4
MPEG-4
H264/AVC (all profiles)
−
MPG, VOB, M2V, MP2
MPEG-2
MPEG-2
−
MXF ‡
MXF
Sony XDCAM, MPEG-2, MPEG-4, Panasonic DVCPro
−
OGV, OGG
OGG
Theora, VP3, Dirac
−
WebM
WebM
Google VP8
−
WMV
Windows Media 9
WMV3 (v9), WMV2 (v8), WMV1 (v7), GoToMeeting (G2M2, G2M3, G2M4)
Microsoft® Screen (MSS2), Microsoft® Photo Story (WVP2)

‡ This video format is not yet supported for use with Interactive Videos in Dynamic Media or for use with Annotation in Experience Manager Assets.

Dynamic Media - Supported document formats document-support-dynamic-media

Format
Upload (Input format)
Create image preset (Output format)
Preview dynamic rendition
Deliver dynamic rendition
Download dynamic rendition
AI
✓
-
-
-
-
INDD
✓
-
-
-
-
PDF (See Note below)
✓
✓
✓
✓
✓
NOTE
For secure PDFs, only Upload is supported.

Dynamic Media - Supported raster image formats image-support-dynamic-media

Format
Upload (Input format)
Create image preset (Output format)
Preview dynamic rendition
Deliver dynamic rendition
Download dynamic rendition
Set types that support this format
AVIF
−
−
−
✓
−
−
BMP
✓
−
−
−
−
Image, Mixed Media, and Spin
EPS
✓
✓
✓
✓
✓
−
GIF
✓
✓
✓
✓
✓
−
HEIC
−
−
−
✓
−
−
JPEG
✓
✓
✓
✓
✓
Image, Mixed Media, and Spin
PICT
✓
−
−
−
−
−
PNG
✓
✓
✓
✓
✓
Image, Mixed Media, and Spin
PSD ‡
✓
−
−
−
−
−
TIFF
✓
✓
✓
✓
✓
Image, Mixed Media, and Spin
WEBP
−
−
−
✓
−
−

‡ The merged image is extracted from the PSD file. It is an image that is generated by Adobe Photoshop and is included in the PSD file. Depending on the settings, the merged image may or may not be the actual image.

Dynamic Media - Unsupported raster image formats unsupported-raster-image-formats-dm

The following subtypes of raster image file formats that are not supported in Dynamic Media:

  • PNG files that have an IDAT chunk size greater than 100 MB.
  • PSB files.
  • PSD files with a color space other than CMYK, RGB, Grayscale, or Bitmap are not supported. DuoTone, Lab, and Indexed color spaces are not supported.
  • PSD files that have a bit depth greater than 16.
  • TIFF files that have floating point data.
  • TIFF files that have Lab color space.

Dynamic Media - Supported 3D file formats support-3d-formats-dynamic-media

See also 3D formats supported

3D file extension
File format
MIME type
Notes
GLB
Binary GL Transmission
model/gltf-binary
Includes the materials and textures as a single asset.
OBJ
WaveFront 3D Object File
application/x-tgif
STL
Stereolithography
application/vnd.ms-pki.stl
USDZ
Universal Scene Description Zip archive
model/vnd.usdz+zip
Support for ingestion and thumbnail generation; 3D previews not yet supported. USDZ is a 3D format that can be viewed natively by Safari or iOS.

Asset file format support and validation asset-file-format-support-and-validation

Adobe Experience Manager (AEM) Assets processing has two distinct mechanisms that behave differently when a file type is not fully supported: standard renditions that is always requested for every asset, non-configurable and Dynamic Media or custom processing profiles that are configurable, and can be scoped by the MIME type or the asset selection criteria. Knowing which one is failing makes it easier to determine whether the behavior is expected or there is something to fix.

Expected Rendition Failures expected-rendition-failures

AEM’s asset microservices always request a fixed set of standard renditions, for example, text extraction, MP4 preview for every uploaded asset, regardless of its MIME type. For a PNG image, renditions such as cqdam.text.txt or cq5dam.preview.mp4 are inherently inapplicable and appears as entries in dam:failedRenditions. This is expected, by-design behavior and not a misconfiguration as long as the renditions relevant to the asset’s actual type (for example, standard image renditions, Dynamic Media processing for images) complete successfully.

Unsupported or restricted input formats unsupported-or-restricted-input-formats

File type or scenario
Behavior
Guidance
ZIP files sent through Dynamic Media processing profiles
Processing step fails explicitly with an unsupported-format error. This causes the workflow instance to accumulate in an unhealthy or retrying state at scale.
Exclude ZIP (and other archive or 3D package files) from Dynamic Media processing profiles using asset selection criteria so the profile is never applied to non-media file types in the first place.
AVIF images
File is stored in the Digital Asset Management (DAM), but AEM does not process it and no thumbnail or preview is generated.
AVIF is not a supported input format for asset processing in AEM as a cloud service. Convert to JPG or PNG before uploading if a preview or rendition is required.
JFIF images
This is not recognized as an image or JPEG because of the file extension. The standard image processing pipeline does not run, so no renditions are generated.
Rename or re-export the JFIF files as .JPG before uploading.
PPTX files containing restricted (read-only or licensed) fonts, for example, Avenir
PDF rendition generation fails; the file is reported as corrupted by the PDF conversion microservice (the same underlying service used by Acrobat)
Restricted fonts not bundled with Windows and blocked from export by the font vendor causes conversion failures independent of AEM. Replace the restricted fonts in the source file before uploading. Local conversion in Acrobat can be used to confirm whether a given PPTX fails before uploading, since it uses the same conversion service.
SVG files missing the offset attribute on <stop> elements
Dynamic Media’s image server returns HTTP 403 through /is/image for that specific file, while /is/content still renders it. This is because SVG violates the SVG 1.1 compliance.
Validate SVGs against the SVG 1.1 compliance, for example, with the W3C Validator before uploading. Re-export from the source tool, for example, Illustrator with SVG 1.1 compliance.
Files with MIME types outside the configured allow-list, for example, .pem certificates
Upload is rejected in the user interface.
AEM Assets can technically store any binary file, but an organization’s asset upload restrictions may limit the accepted MIME types. Update the allowed MIME type list globally, or per folder to include the required type.
Metadata values in a bulk CSV import that start with or contain reserved characters such as #, /, ;, backslash symbol, pipe symbol, [, ], %, {, }, ?, &
The parser skips or ignores the affected metadata entry without a hard failure.
Remove or replace the reserved characters in metadata values before running a bulk CSV metadata import.
DAM assets carrying non-standard or unregistered XML metadata namespaces, for example, exifEX, mwg-rs, photomechanic
Content package import or copy between the environments fail with messages such as unknown namespace prefix or no namespace mapping found.
Identify and clean the offending metadata properties on the source assets (they are often introduced by the external tools) before re-attempting the package import or content copy.

Restricting upload types per folder restricting-upload-types-per-folder

Out-of-the-box MIME type restrictions apply globally across the DAM by default, but folder-specific restrictions are also possible. Configure the allowed MIME types for a specific folder, for example, /content/dam/projects through Tools > Assets > Assets Configuration, listing only the MIME types that should be accepted for that folder. All other types, including common ones like Excel spreadsheets, are then blocked for that folder specifically without affecting rest of the DAM.

XMP metadata writeback conflicts XMP-metadata-writeback-conflicts

Concurrent updates to an asset’s metadata node (cqdam.metadata.xml), for example, from multiple custom workflows or services writing to the same asset at once can produce repository conflicts (InvalidItemStateException, CommitFailedException) during Extensible Metadata Platform (XMP) writeback. Repeated failures of this kind can also contribute to a backlog of unhealthy or retrying workflow instances. To avoid this:

  • Review custom workflows or services for concurrent writes to the same asset’s metadata, and serialize them where possible.
  • Enable and configure workflow purge maintenance so that completed and stale workflow instances are cleaned up automatically rather than accumulating.

Troubleshooting checklist troubleshooting-checklist

  1. If a rendition failure only affects a rendition type that does not apply to the asset’s format, for example, video preview on an image, treat it as expected and check whether the format-appropriate renditions succeeded instead.
  2. If a processing profile is failing on files that were never meant to be processed by it, for example, ZIP, 3D packages, fix the profile’s asset selection criteria rather than trying to make the file type work.
  3. If a specific file fails while similar files succeed, suspect the file itself first. Check for restricted or licensed fonts (PPTX or PDF), SVG compliance, or an unsupported format or extension mismatch (AVIF or JFIF) before assuming an AEM configuration issue.
  4. If workflows are backing up in an unhealthy state, check for both the unsupported-format processing failures and metadata writeback conflicts. They can co-occur and compound the backlog.

See also

Related Articles
recommendation-more-help
experience-manager-cloud-service-help-main-toc