AEM Desktop App Release Notes

You are reading the AEM 6.2 version of AEM Desktop App Release Notes.
This documentation is also available for the following versions: 

Release Information

Products Adobe Experience Manager (AEM) Desktop App

1.3 ( on Mac OS X; 1.3.12 on Windows)

Type Minor Release

September 16, 2016 (Mac OS X)

November 14, 2016 (Windows)

Download URL

AEM 6.2 (with Hot Fix 11099 applied)

AEM 6.1 SP2 (with Feature Pack 6658 and Hot Fix 8723 applied)

Adobe Experience Manager (AEM) Desktop App 1.3 provides performance enhancements and stability of accessing files and saving changes to AEM, especially from Creative Cloud desktop applications, such as InDesign, Illustrator, or Photoshop. This release aims to provide users with a more local desktop-like experience when working with files, while simultaneously handling network data transfer operations in the background.


Want to start quickly?

  • Install the required server-side components on your AEM server (see Installation for details)
  • Download the AEM Desktop App binary from download page and install on your local machine


What's included in AEM Desktop App 1.3

This release of AEM Desktop App provides the following benefits:

  • Increased efficiency. Users spend less time waiting for network operations to complete.
  • Improved Finder integration, which provides more stability and access to features, such as thumbnails.
  • Caching and performance improvements.
  • Better support for saving directly from desktop apps (PS, ID, AI, and so on).
  • Improved integration with Mac OS (local network drive protocol changed from WebDAV to more stable SMB1)
  • Desktop app connects with the AEM server using AEM native HTTP RESTful protocol
  • Files are saved locally first and then uploaded back to AEM in background after a predefined time (30 sec). This reduces the time to save files.
  • Better handling of desktop applications that use intermediate file operations to save a file (partial saves and temporary files), which enables the AEM Asset timeline to display correct version and asset upload information.
  • Dialog provided to track the status of background upload tasks.

List of changes

Protocol change

  • Mac OS X
    • The local network drive protocol for OS X desktop integration changed to SMB1 from WebDAV.
    • The AEM repository mounted with Desktop App will be visible as an “smb” network drive in Finder, instead of a WebDAV drive.
  • Windows
    • The local network drive protocol for Windows dekstop integrations stays; AEM will be mounted as a WebDAV share
  • For both platforms (Windows and Mac)
    • The protocol to access/download assets and to upload changes to AEM has been changed to the native AEM protocol, which is a HTTP-based RESTful protocol. It provides greater control over network operations and is more compatible with the network infrastructure.


On Mac OS X: The change of local network drive protocol from WebDAV to SMB1 results in a different local path to the same asset in the repository. This might impact links to files placed in CC applications via "Place" command. See documentation for more information.

File handling

  • Folders are updated automatically after a predefined delay (currently 30s). 
  • Files checked out by other users are marked as read-only. 
  • Files are saved to a network drive location mounted via Desktop App in two phases.
  • In the first phase, a file is saved locally. This way, the user saving the file need not wait until the file is fully transferred to AEM, and can resume work as soon as the file is saved.
  • In the second phase, Desktop App uploads an updated file to AEM server after a predefined delay ( for example, 30s). This operations occurs in the background. Use the Show Background File Sync Status option to view the status of the upload operation. 

Important Notices

Please note that AEM Desktop App doesn't support a self-signed SSL certificates when connecting to AEM via a HTTPS secure connection. A CA-signed certificate is required on the server for such connections. (CQ-87941)

Known issues

  • Copying large number of assets at the same time from the local machine to AEM using AEM Desktop App might fail after 40-50 assets. CQ-92912

    : Desktop App should not be used to carry out bulk copy operations on larger number of files. Instead, consider using a smaller batch size or use a tool/script to upload assets directly through the AEM HTTP API.

  • Server URLs are required to point to the server without a path (e.g. http://server, https://server, http://server:port, or https://server:port). Context paths and sub-folders other than /content/dam are not supported. CQ-97388, CQ-89343, CQ-87272, CQ-87272
  • File and folder names with reserved characters are not properly handled. Make sure to use file and folder names that fit AEM requirements. CQ-93361, CQ-93308, CQ-89276
  • File and folder names with Unicode characters are not properly handled. CQ-85558
  • Folders may show an incorrect modified date in Finder. CQ-92289
  • Checkin/Checkout
    • Changing files simultaniously by multiple users may cause some modifications to get lost. The workaround is to use the checkin/checkout functionality to prevent multiple users from changing the same file. CQ-97035
    • Certain applications don't support the read-only flag properly which allows a user to save a file that's checked out by another user. The modified file is not transferred until the other user checks in the file. Both modifications are available in AEM as different versions of the asset. CQ-89551, CQ-87572, CQ-89615
    • The checked-out and readonly status are reported independently in Finder. This results in 2 lock icons when a user checks out an asset. CQ-89507
  • Finder integration
    • Manual folder reload does not always work. The workaround is to wait 30s for the folder to be automatically updated. CQ-97389
    • More Asset Info... is limited to single file selections. CQ-89542, CQ-87656
    • Open in AEM Assets... is limited to single file and folder selections. CQ-83382


  • Files with Alternate Data Streams (ADS) are only fully supported on NTFS. Copying such files to the WebDAV share provided by the Desktop App will result in a caution dialog warning the user that the file has properties that can't be copied to the new location. This is usually fine since the properties are only relevant to a particular application on the user's desktop and have nothing to do with the actual file contents. CQ-103770
  • Assets can't be uploaded to private folders owned by admin. CQ-101556
  • Folders show up empty intermittently during folder browsing. CQ-103276.
  • Folders created by the Desktop App are not removed after they are deleted in the same session. CQ-104605

Installation instructions


AEM Desktop App 1.3 is compatible with AEM 6.1 Service Pack 2. If you are running AEM 6.1, ensure that you have installed AEM 6.1 Service Pack 2 before installing AEM Desktop App 1.3.

Installing server-side components

Depending upon the AEM version, install the appropriate server-side components. 

AEM 6.1:

Install the following:

AEM 6.2:

Install the following:

Installing AEM Desktop App 1.3 on local machine

For instructions, see Adobe Experience Manager Desktop App.

Helpful resources

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.