Supported file formats for assets

The Digital Assets are data that are stored digitally in the application. Digital Asset includes images, videos, audios, and documents. You can search, upload, download, and manage assets in the Digital Asset Library app. You can also link the multiple assets to an entity and vice-versa.

Supported file formats

Here is the list of formats which DAM module supports:

Unsupported file formats

The following file formats are not supported in DAM module:

application, aru, bat, chm, cla, class, cmd, com, cpl, cpl, dll, drv, ecc, exe, gadget, hta, inf, ins, jar, js, jse, lnk, met, micro, msc, msh, msh1, msh1xml, msh2, msh2xml, mshxml, msi, msp, ocx, pif, ps1, ps1xml, ps2, ps2xml, psc1, psc2, reg, scf, scr, shs, sys, vb, vbe, vbs, vxd, ws, ws, wsc, wsf, wsh, xtbl.

Supported special characters

The following are the special characters that are supported for digital asset attribute:

• Alphanumeric characters such as "a" through "z", "A" through "Z" and "0" through "9" remain the same.
• The ".", "-", "*", and "_" characters remain the same.
• Space character "" is converted into plus sign "+"
• Other supported characters are "Ã¥", "ä", and "ö".

Supported modes for DAM assets

The application supports the following modes for DAM assets:

1. Assets stored in DAM

   • In this setup, all the assets with their original files and thumbnail files are stored in DAM.
   • Users can view, download, and link the assets to products and SKUs.
   • Metadata is extracted by DAM.
   • DAM can create renditions for images.
   • Asset files or file URLs can be exported.

2. Thumbnails stored in DAM (old approach, may get deprecated)

   • In this setup, only the thumbnail files are stored in the DAM. Original files are neither stored nor referenced by DAM.
   • Users can view the thumbnails and link the assets to products and SKUs.
   • Users cannot view or download the original assets.
   • Metadata needs to be imported into DAM.
   • DAM cannot create renditions.
   • Only the asset identifiers can be exported.

3. No files stored in DAM

   • In this setup, the asset entities are created in DAM with asset entity having URLs pointing to the original asset file and thumbnail file stored outside DAM.
   • Users can view the thumbnails, original files, download them and link the assets to products and SKUs.
   • Metadata needs to be imported into DAM.
   • DAM cannot create renditions.
   • Only the asset URLs can be exported.

Supported conversions for WebP format

• From EPS to WebP
• From PNG to WebP
• From JPG to WebP
• From WebP to JPG
• From WebP to PNG
• From WebP to EPS

Additionally, the following conversions are supported:

• From EPS to JPG
• From JPG to EPS

Limitations for Image file formats

Some of the supported .eps and .psd image file formats have the following limitations as they are huge in file size and contain multiple image layers.

• Displays default thumbnail if you upload more than 20MB file.
• Image renditions are not supported if the file size is more than 20MB.
• Add double quotes for ‘image names that have fractions while performing a search. For example, “Blue Short ½”.
• Supported image sizes (width*height):
  • 1500px * 1000px
  • 700px * 800px
  • 800px * 1000px

Limitations of supported raw formats

Creating thumbnails and renditions are limited to images lesser than 20MB. If an image size is greater than that, thumbnails and image renditions are not created but the image entity and its metadata are created.

Limitations

The following are the limitations:

• You cannot preview any document file extensions.
• The maximum asset file size is 5GB via UI. You can upload up to 2000 assets with a maximum size limit of 50GB in a single upload.
• Creating thumbnails and renditions are limited to 20MB or even lesser for images. If an image size is greater than that, thumbnails and renditions are not created but the image entity and its metadata details are created.
• File extensions are case insensitive.
• If you wish to create custom renditions then the original asset has to be <20MB.
• The external Digital Asset Management (DAM) do not adhere to limits or functionality features.
• The external DAM takes precedence over the DAM, if the customers have their own DAM service, they adhere to the limits provided by the system, which is not monitored by us.
• Out-of-the box (OOTB), the DAM models are supported only with user interaction locales.