Install and configure Experience Manager desktop app v1.10

Using the Experience Manager desktop app, the assets within Experience Manager are easily accessible on your local desktop and can be used in any desktop applications. Assets can be easily revealed in Mac Finder or Windows Explorer, opened in desktop applications, and changed locally – the changes are saved back to Experience Manager when you upload and a new version is created in the repository.

Such an integration allows various roles in the organization to manage the assets centrally in Assets and to access them in the Creative Cloud and other applications, while making it easy to adhere to the various standards including branding.

To use Experience Manager desktop app,

For detailed information, see the Experience Manager desktop app release notes.

Install and connect the app to Experience Manager server

For details, see Install and connect Experience Manager desktop app to Experience Manager server.


Only one instance of the Experience Manager desktop app can be installed and be active at a time.

File handling

When changing a file from a network share location mounted by the desktop app, files are saved to that location in two phases. In the first phase, a file is saved locally. A user can save the file and continue working on the file, without waiting for the transfer to complete.

In the second phase, desktop app uploads the updated file to Experience Manager server after a predefined delay (for example, 30s). This operation occurs in the background. Use the View Asset Status option to view the status of the upload operation.

  1. Upload an asset to Assets.

  2. Click the Experience Manager desktop app icon from the toolbar.

  3. From the menu, select the View Asset Status option.

  4. From the dialog, review the status of the upload operation.


Experience Manager desktop app can handle assets up to 40 GB in size.

Connect to an Experience Manager instance behind a dispatcher

The copy and move methods in the Assets API require the following additional headers to be passed to Experience Manager:

  • X-Destination
  • X-Depth
  • X-Overwrite

Experience Manager desktop connects to Experience Manager using a URL that includes the default port. Therefore, the virtualhosts setting in the dispatcher configuration should include the default port number. For more information around virtualhosts configuration, see identify virtual hosts.

For additional information on configuring the dispatcher to pass through these additional headers, see Specifying the HTTP Headers.

Proxy support

Experience Manager desktop app uses system’s pre-defined proxy to connect to the Internet over HTTPS. The app can only connect using a network proxy that does not require extra authentication.

If you configure or modify proxy server settings for Windows (Internet Options > LAN Settings), restart the Experience Manager desktop app for the changes to take effect.


Proxy configuration is only applied when you start the desktop app. Close and re-launch the app for any changes to take effect.

If your proxy requires authentication, the IT team can allow the Experience Manager Assets URL in the proxy server settings to allow the application traffic to pass through.

Customize the Asset Info dialog

You can customize the Asset Info dialog by overlaying one or both of these components:

  • The Granite user interface page at /libs/dam/gui/content/assets/moreinfo.

  • The HTL /css/javascript component at /libs/dam/gui/components/admin/moreinfo.

Which component is overlaid, depends on the nature of the customization. To change which components are displayed as part of the Asset Info dialog, overlay the Granite user interface page. To change the HTML, CSS, or JavaScript content of the dialog, overlay the HTL component.

Manage cache

On Windows, the cache is at %LOCALAPPDATA%\Adobe\AssetsCompanion\Cache\, where is an encoded version of the Experience Manager host configured in the desktop app. For example, http://localhost:4502 appears as http%3A%2F%2Flocalhost%3A4502%2F.

On Mac OS X, a similar directory is at ~/Library/Group Containers/

In-app option to manage cache

You can control the amount of disk space made available for local caching purposes. The artifacts from the Assets server are cached locally for a smoother experience. You can change the defaults to suit your requirements. Also, you can clear the cache to fetch all assets afresh. To set the desired options, click the application’s icon and click Advanced > Manage Cache. ****


When you clear the cache, it preserves your unsaved changes. Any assets not checked into Experience Manager server are retained and not deleted.

Change location of cache on Windows

The default location of the cache for the Experience Manager desktop app is as follows:

  • In Windows, %LocalAppData%\Adobe\AssetsCompanion\Cache\EncodedAEMEndpoint.

  • In Mac, ~/Library/Group/Containers/

EncodedAEMEndpoint is app’s configured Experience Manager endpoint URL. The value is an encoded version of the targeting URL of the Experience Manager server. For example, if the application is targeting http://localhost:4502, the directory name is http%3A%2F%2Flocalhost%3A4502. The Windows path to the cache directory in this example is %LocalAppData%\Adobe\AssetsCompanion\Cache\http%3A%2F%2Flocalhost%3A4502.

To point the application to a different folder or a different drive, edit the application’s configuration file.

  1. Navigate to the app’s installation directory. The default location on Windows is C:\Program Files (x86)\Adobe\Adobe Experience Manager Desktop.

  2. Edit Adobe Experience Manager Desktop.exe.config file with a text editor.

    Administrator privileges are required to save changes to this file.

  3. Search for the string “ProxyCacheRoot”. You see that its value is set to the cache location %LocalAppData%\Adobe\AssetsCompanion\Cache. Simply change this value to any valid path.


    The app automatically creates an <Encoded AEM Endpoint> subdirectory. This behavior is not configurable.

On this page