Show Menu
TOPICS×

Add digital assets to Adobe Experience Manager

Adobe Experience Manager enriches the binary content of the uploaded digital files with rich metadata, smart tags, renditions, and other Digital Asset Management (DAM) services. You can upload various types of files, such as images, documents, and raw image files, from your local folder or a network drive to Experience Manager Assets.
A number of upload methods are provided. In addition to the most commonly used browser upload, other methods of adding assets to the Experience Manager repository exist, including desktop clients, like Adobe Asset Link or Experience Manager desktop app, upload and ingestion scripts that customers would create, and automated ingestion integrations added as Experience Manager extensions.
We will focus on upload methods for end users here, and provide links to articles describing technical aspects of asset upload and ingestion using Experience Manager APIs and SDKs.
While you can upload and manage any binary file in Experience Manager, most commonly used file formats have support for additional services, like metadata extraction or preview/rendition generation. Refer to supported file formats for details.
You can also choose to have additional processing done on the uploaded assets. A number of asset processing profiles can be configured on the folder, into which assets are uploaded, to add specific metadata, renditions or image processing services. See Additional processing below for more information.
Experience Manager as a Cloud Service leverages a new way of uploading assets - direct binary upload. It is supported by default by the out of the box product capabilities and clients, like Experience Manager user interface, Adobe Asset Link, Experience Manager desktop app, and thus transparent to the end users.
Upload code that is customized or extended by customers technical teams needs to use the new upload APIs and protocols.

Upload assets

To upload a file (or multiple files), you can either select them on your desktop and drag on the user interface (web browser) to the destination folder. Alternatively, you can initiate upload from from the user interface.
  1. In the Assets user interface, navigate to the location where you want to add digital assets.
  2. To upload the assets, do one of the following:
    • On the toolbar, tap the Create icon. Then, on the menu, then tap Files . You can rename the file in the presented dialog if needed.
    • In a browser that supports HTML5, drag the assets directly on the Assets user interface. The dialog to rename file is not displayed.
    To select multiple files, press the Ctrl or Command key and select the assets in the file picker dialog. When using an iPad, you can select only one file at a time.
  3. To cancel an ongoing upload, click close ( X ) next to the progress bar. When you cancel the upload operation, Assets deletes the partially uploaded portion of the asset.
    If you cancel the upload operation before the files are uploaded, Assets stops uploading the current file and refreshes the content. However, files that are already uploaded are not deleted.
  4. The upload progress dialog in Assets displays the count of successfully uploaded files and the files that failed to upload.
    In addition, the Assets user interface displays the most recent asset that you upload or the folder that you created first.
To upload nested folder hierarchies, see bulk upload assets .

Handling uploads when asset already exists

If you upload an asset with the same name as that of an asset already available at the location where you are uploading the asset, a warning dialog is displayed.
You can choose to replace an existing asset, create another version, or keep both by renaming the new asset that is uploaded. If you replace an existing asset, the metadata for the asset and any prior modifications (for example annotations, cropping, and so on) you made to the existing asset are deleted. If you choose to keep both assets, the new asset is renamed with the number 1 appended to its name.
When you select Replace in the Name Conflict dialog, the asset ID is regenerated for the new asset. This ID is different from the ID of the previous asset.
If Asset Insights is enabled to track impressions/clicks with Adobe Analytics, the regenerated asset ID invalidates the data-captured for the asset on Analytics.
To retain the duplicate asset in Assets, click Keep . To delete the duplicate asset you uploaded, tap/click Delete .

File name handling and forbidden characters

Experience Manager Assets prevents you from uploading assets with the forbidden characters in their filenames. If you try to upload an asset with file name containing a disallowed character or more, Assets displays a warning message and stops the upload until you remove these characters or upload with an allowed name.
To suit specific file naming conventions for your organization, the Upload Assets dialog lets you specify long names for the files that you upload.
However, the following (space-separated list of) characters are not supported:
  • asset file name must not contain * / : [ \\ ] | # % { } ? &
  • asset folder name must not contain * / : [ \\ ] | # % { } ? \" . ^ ; + & \t

Bulk upload assets

To upload larger number of files, especially if they exist in a nested folder hierarchy on disk, the following approaches can be used:
  • Use a custom upload script or tool that leverages asset upload APIs . Such a custom tool can add additional handling of assets (for example, translate metadata or rename files), if required.
  • Use Experience Manager desktop app to upload nested folder hierarchies.
Bulk upload as a part of content migration from other systems when setting up and deploying to Experience Manager requires careful planning, consideration, and choice of tools. See the deployment guide for guidance on content migration approaches.

Upload assets using desktop clients

In addition to web browser user interface, Experience Manager supports other clients on desktop. They also provide upload experience without the need to go to the web browser.
  • Adobe Asset Link provides access to assets from Experience Manager in Adobe Photoshop, Adobe Illustrator, and Adobe InDesign desktop applications. You can upload the currently open document into Experience Manager directly from Adobe Asset Link user interface from within these desktop applications.
  • Experience Manager desktop app simplifies working with assets on desktop, independent on their file type or native application that handles them. It is particularly useful to upload files in nested folder hierarchies from your local file system, as browser upload only supports uploading flat file lists.

Additional processing

In order to have additional processing done on the uploaded assets, you can use asset processing profiles profiles on the folder, into which assets are uploaded. They are available in the folder Properties dialog.
The following profiles are available:
Additionally, if Dynamic Media is enabled in your environment:
Dynamic Media cropping and other operations on assets are non-destructive, that is, they do not change the uploaded original, but instead provide parameters for cropping or media transformation to be done when delivering the assets
For folders that have a processing profile assigned, the profile name appears on the thumbnail in the card view. In the list view, the profile name appears in the Processing Profile column.

Upload or ingest assets using APIs

Technical details of the upload APIs and protocol, and links to open-source SDK and sample clients is provided in asset upload section of the developer reference.