Use the Adobe Experience Manager desktop app, to easily access the digital assets stored in Adobe Experience Manager DAM repository on your local desktop and use these assets in any desktop applications. You can open the assets in desktop applications and edit the assets locally – upload the changes back to Experience Manager with version control, to share the updates with other users. You can also upload new files and folder hierarchies to Experience Manager, create folders, and delete assets or folders from Experience Manager DAM.
The integration allows various roles in the organization to manage the assets centrally in Experience Manager Assets and to access the assets on local desktop in the native applications on Windows or Mac OS.
When you open the application after logging out or for the first time, provide the URL of your Experience Manager server in the format
https://[aem-server-url]:[port]/. Then select the Connect option. Provide credentials to connect the app with the server.
The key tasks you perform using the Adobe Experience Manager desktop app are:Download [this](/docs/experience-manager-desktop-app/assets/aem_desktop_app_usecases_print.pdf?lang=en) print-ready PDF file.
Before you start using the application, understand How the app works. Also, familiarize yourself with the following terms:
Desktop Actions: From the Assets web interface, from within in a browser, you can explore the asset locations or check-out and open the asset for editing in your native desktop application. These actions are available from the web interface and use desktop app functionality. See how to enable Desktop Actions.
File status is Cloud Only: Such assets are not downloaded on the local machine and are available on Experience Manager server only.
File status is Available locally: The assets are downloaded and available on the local machine as is. The assets are not changed.
File status is Edited locally: Such assets are modified locally and the changes remain to the uploaded to Experience Manager server. After you upload, the status changes to Available locally. See edit assets.
File status is Editing conflict: If you and other users modify an asset simultaneously, the app indicates that an editing conflict has occurred. The app also provides options to retain or discard your changes. See how to avoid editing conflicts.
File status is Modified remotely: The app indicates if an asset that you have downloaded is changed on the Experience Manager server. The app also provides the option to download the latest version and update your local copy. See how to avoid editing conflicts.
Check-out: If you are editing a file or intend to edit a file, you toggle the status to check out. It adds a lock icon on the asset in the app and Experience Manager web interface. The lock icon indicates to other users to avoid simultaneously editing the same asset as it leads to an editing conflict.
Check-in: Mark the asset as safe for other users to edit without causing an editing conflict. When you upload your changes, the lock icon is automatically removed. Toggling the check-in status also removes the lock icon though it is recommended to not manually check in without uploading the changes. If you discard your changes, then manually toggle the check-in.
Open action: Just open the asset to preview it in the native application. It is not recommended to edit the asset by using this action, as it does not check out the asset and other users can make edits leading to editing conflicts.
Edit action: Use the action to modify the image. Clicking Edit action automatically checks out the asset and adds a lock icon on the asset. After clicking Edit, if you do not want to edit the asset, then click Toggle check-in. To delete, rename, or move assets in Experience Manager DAM folder hierarchy, use the Experience Manager web interface actions and not the edit action.
Download action: Download the asset to your local machine. You can download the assets now and edit later; work offline and upload the changes later. Assets are downloaded in a cache folder on your file system.
Reveal File or Reveal Folder action: While the assets are downloaded to a local cache folder, the app mimics a local network drive and provides a local path for each asset. To know this path, use the appropriate reveal option in the app. Reveal action is required to place assets in the Creative Cloud application. See place assets.
Open In Web action: To view the asset in Experience Manager web interface, open it in web. You can initiate more workflows from Experience Manager interface like updating metadata or asset discovery.
Delete action: Delete the asset from the Experience Manager DAM repository. The action deletes the original copy of the asset on the Experience Manager server. If you want to only discard modifications to the local asset, see discard changes.
Upload Changes: Desktop app uploads the updated asset only when you explicitly upload to Experience Manager server. When you save your edits, the changes are saved on your local machine only. When you upload, the asset is automatically checked in and lock icon is removed. See edit assets.
From within the Assets user interface in a browser, you can explore the asset locations or check-out and open the asset for editing in your desktop application. These options are called Desktop Actions and are not enabled by default. To enable it, follow these steps.
In the Assets console, click the User icon from the toolbar.
Click My Preferences to display the Preferences dialog.
In the User Preferences dialog, select Show Desktop Actions For Assets, then click Accept.
Figure: Select Show Desktop Actions For Assets to enable desktop actions.
You can browse to, search for, and preview the assets available in the Experience Manager repository, all from within the desktop application. Try the following in the app:
Browse to a folder and see some basic info of the assets available in the folder, along with small thumbnails of all assets.
To view more information and a larger thumbnail of an individual asset, click the filename.
Click Open or Edit to download the file locally and just view it or edit it in the native application, respectively.
Search using keywords to find a related asset in the Experience Manager repository. Use
* as wildcards. These wildcards substitute for a single character or for multiple characters, respectively. Filter and sort the results as necessary.
The app displays the assets by matching the search criteria across multiple metadata fields and not just the asset’s title or the filename.
You can download the assets on your local file system. The app fetches the assets from Experience Manager server and saves the same copy on your local file system.
Click for options and click to download.
When downloading or uploading a large file or many files, the application turns off the actions on assets and folders. The actions are available when the download or upload is complete.
Downloading multiple assets may lead to poor performance if queue size is large or if you face some network issue. Also, you may unknowingly queue many assets for download when you download a folder. To avoid long wait times, the app restricts the number of assets downloaded in one go. To know how to configure it, see Set preferences. Even below this limit, the app may at times seek a confirmation before downloading an apparently large folder.
If folder(s) are selected and downloaded, the application only downloads assets stored directly in the folder(s) in Experience Manager. It does not download assets from sub-folders automatically.
You can open the remote assets for viewing in the native application. The assets are downloaded to a local folder and launched in the native application associated with the file format. You can change the native application to open specific file types (extensions) in your Mac or Windows.
Click Open from the asset menu. The asset is downloaded locally and opened in the native application. Check the download progress and transfer speed of large assets in the status bar.
If the expected changes are not reflected in the app, click refresh icon or right click in the app interface and click Refresh. The actions are not available while larger downloads or uploads are in progress.
To open the local download folder of an asset, click and click Reveal File action.
In some cases, say when placing an asset into a native document, you access a file in Windows Explorer or Mac Finder. To get to the file system location of the locally downloaded file, use the Reveal File option.
Click Reveal File, or Reveal Folder on a folder, to open Windows Explorer or Mac Finder with the file or folder preselected on your local machine. The option is useful to, say place the Experience Manager files in the native applications that support placing or linking local files. To see how to place files in Adobe InDesign, see Placing graphics.
The Reveal File action opens a local network share, that displays only the assets that are available locally – that is, it displays assets that were revealed, downloaded, or opened/edited using the app. The local network share does not upload any changes to Experience Manager. To upload the changes, explicitly use Upload Changes or Upload actions in the app.
For backwards compatibility with Experience Manager desktop app v1.x, the files revealed are served from a local network share, exposing locally available files only. The desktop paths of the revealed files are the same as the paths created by app v1.x.
Do not use Reveal File option to edit assets in native applications. Instead, use the Edit actions. To know more, see Advanced workflow: collaborate on same files and avoid editing conflicts.
Open assets for editing when you want to make changes and upload the updated assets to AExperience ManagerEM server. To avoid conflicts with edits of other users, use the app to initiate an editing session. Before you start editing, ensure that the asset does not have a lock icon on it, that is, another user is not editing the asset.
To edit an asset, search for the asset or browse to the asset’s location. Click and click Edit.
Use Toggle Check-out to lock the asset to prevent conflicts with edits of other users in both the following situations:
Once you’re done making the edits, the app displays the Edited Locally status for the changed assets. All the changes saved to the assets are local-only until you upload the changes to Experience Manager. To upload an individual or a few assets one-by-one, click Upload Changes from the options for an asset. It creates a version of the asset in Experience Manager. Using the web interface of Assets, you can see asset history in the Timeline view.
For best practices around collaborative editing, see Advanced workflow: collaborate on same files and avoid editing conflicts.
In the following cases, you may want to discard your changes and edits to the local asset. Click Discard Changes.
If necessary, toggle check-out. The updated asset is removed from the local cache folder and is downloaded again when you edit or open it.
Users can add new assets to the DAM repository. For example, you may be an agency photographer or contractor who wants to add a large number of photos from a photoshoot to the Experience Manager repository. To add new content to Experience Manager, select in the top-bar of the app. Browse to the asset files in the local file system and click Select. Alternatively, to upload assets, drag the files or folders on the application interface. On Windows, if you drag assets on a folder inside the app, the assets are uploaded into the folder. If it takes longer to upload, the app displays a progress bar.
You can upload folders or individual files from your local file system. A folder’s hierarchy is preserved when it is uploaded. Before uploading assets in bulk, see Bulk uploads.
To view the list of assets transferred in a given session, click View > Assets transfers. The list allows you to view and quickly verify the file transfers of the current session.
You can control the upload concurrency (acceleration) in Preferences > Upload acceleration setting. More concurrency typically gives faster uploads, but can be resource-intensive, consuming more processing power of the local machine. If you experience a slow system, re-attempt uploads using a lower value of concurrency.
The transfer list is not persistent and is not available if you exit the app and reopen it.
In the legacy app, the node names created in the repository retained the spaces and casing of the folder names provided by the user. For the current application to emulate the node naming rules of v1.10 app, enable Use legacy conventions when creating nodes for assets and folders in the Preferences. See app preferences. This legacy preference is disabled by default.
The app changes only the node names in the repository using the following naming conventions. The app retains the
Title of the asset as is.
|Characters ‡||Legacy preference in app||When occurring in file names||When occurring in folder names||Example|
|`. / : [ ]||*`||Enabled or Disabled||Replaced with
||Disabled||Whitespaces are retained||Replaced with
|Uppercase characters||Disabled||Casing is retained as is.||Changed to lowercase characters.||
|Uppercase characters||Enabled||Casing is retained as is.||Casing is retained as is.||NA.|
‡ The list of characters is a whitespace-separated list.
Users can easily work with and manage multiple assets using actions like uploading all edits in one go or uploading nested folders in a few clicks.
When working with folders containing many assets, scroll to view more assets. To scroll using the keyboard, press tab a few times to select the asset at the top. Notice the highlighted asset to know when it is selected. Now use the Down Arrow key to move through the list of assets.
Click the thumbnail of a few assets to select the assets. To select all assets, click the check box in the top-bar of the app. The set of actions that are applicable to all the selected assets collectively are displayed in a toolbar at the bottom of the app.
Actions available in the toolbar at the bottom depend on the status of selected files. For example, if you only select Edited Locally files, you see Upload Changes icon. If you select a mix of Edited locally and Cloud only, the Upload Changes action is not available.
The application provides a view, called Edited locally, to give you quick access to all the files that you downloaded locally (via Open or Edit actions) and then modified. The app allows you to select all locally edited assets and upload the changes in a few clicks. This view also displays the locally edited assets that have an editing conflict.
Users or organization, such as photographers or creative agencies, can create numerous local assets in scenarios, such as photoshoots, retouching, or selection from a larger set done outside Experience Manager. They can upload these large local folders to Assets directly from the desktop app. The folder hierarchies are preserved and all the nested sub-folders and included assets are uploaded. The uploaded assets are immediately available to other users of the same server for consumption as well. Assets are uploaded in background, so the operation is not tied to a web browser session.
After uploading, if the expected changes are not reflected in the app, click the refresh icon .
Do not use upload functionality to migrate assets across two Experience Manager deployments. Instead, see the migration guide.
To view the list of assets transferred in a given session, see Upload assets to Experience Manager.
If necessary, initiate your workflow from the Assets web interface. The desktop app integrates with the Experience Manager to take over when requested using Desktop Actions.
A special case of starting workflow from the web interface is asset discovery. The Omnisearch bar in Assets user interface offers a rich and advanced search experience. You may want to first locate a desired asset on the web and then initiate the workflow in the app, using Desktop Actions. Some sample cases include filtering search results using facets, locating a specific asset licensed from Adobe Stock, or a customization implemented by your organization that allows you better discovery from the web interface.
Desktop app functionality is used when you attempt the following actions on the Assets web interface:
For example, the actions on the web interface that are available for an asset that is checked out in the app are Open, Reveal, and Check-in.
The browser may prompt you to permit the launch of Adobe Experience Manager Desktop. To enjoy uninterrupted transfer from the browser to the app, select the appropriate check box to always allow the app to take over.
You cannot find the following information or workflow using the web interface. Use the desktop app as the web interface does not track local changes and is not aware of the following:
On the contrary, you can open the asset in the web interface starting from the desktop app using the Open In Web action.
In collaborative environments, multiple users may work on same set of assets that can lead to versioning conflicts. To prevent conflicts, follow these best practices:
If a locally downloaded asset is updated on the Experience Manager server, the app displays a Modified remotely status. You can either remove your local copy or refresh your local copy, by clicking Remove or Update respectively. Links on the dialog allow you to view both versions of the asset.
If an asset you are editing locally is also updated on the server without your knowledge, the app displays an Editing Conflict status. You can retain one set of the changes – either retain your updates (click Keep Mine) and delete the other user’s edit or respect the other user’s updates and delete yours (Overwrite Mine).
When you use Experience Manager desktop app to open files with linked assets, the assets are pre-downloaded and appear placed in the native applications. For this workflow to work, your native application must support placing links to local assets and Experience Manager must support resolving these links in the binary files to server-side references.
Experience Manager desktop app supports this workflow with a few select Adobe Creative Cloud desktop applications and file formats – Adobe InDesign, Adobe Illustrator, and Adobe Photoshop. The workflow allows you to work efficiently with the supported Creative Cloud files. So if user A places a few assets in an InDesign file and checks it into Experience Manager, user B sees the assets in the InDesign file even though the assets are not part of the file. The assets are locally downloaded on the machine of user B.
The desktop app can map to any drive on Windows. However, for smooth operations, do not change the default drive letter. If users of the same organization use different drive letters, they cannot see the assets placed by others. The placed assets are not fetched as the path changes. The placed assets continue to remain placed in the binary file (say INDD) and are not removed.
To know the limitations of this workflow, see the system requirements and supported versions.
To try this workflow with an image asset and InDesign, follow these steps:
The app downloads the assets from Experience Manager server locally on your file system in many scenarios. The downloads consume bandwidth and disk space. Knowing the scenarios help you optimize your wait time for the downloads to complete.
You download the assets from within the app on-demand. See Download assets.
When you use the Open action to open an asset in a native desktop application, the asset is downloaded locally if not already available locally. See Open assets.
When you reveal the location of an asset or a folder from within the app, the asset or the folder is first downloaded locally and then opened on your machine in the local network share. See Open assets.
When you use the Edit action to edit an asset in a native desktop application, the asset is downloaded locally if not already available locally. See Edit assets and upload updated assets to Experience Manager.
If the app is installed and permitted to, it completes the actions when you use Desktop Actions from Experience Manager web interface. The app downloads the asset first and then completes the action.