You're viewing help content for version:

Release Information

Product Adobe Experience Manager
Version 6.3
Type Major Release
General availability date April 26, 2017
Recommended Updates See also Dynamic Media Feature Packs 14410 and 18912 Release Notes.
Feature Packs For a list of available Feature Packs visit AEM 6.3 Feature Packs


The release cycle for this version of Adobe Experience Manager started May 05, 2016, went through 21 iterations of quality assurance and bug fixing, and ended April 13th, 2017. The total number of customer related issues including enhancements and new features fixed in this release is 1023.

Adobe Experience Manager 6.3 is generally available since April 26, 2017.


What's new

Adobe Experience Manager 6.3 is an upgrade release to the Adobe Experience Manager 6.2 code base. It provides new and enhanced functionality, key customer fixes, high priority customer enhancements and general bug fixes oriented toward product stabilization. It also includes all Adobe Experience Manager 6.2 feature pack, hot fix, and service pack releases.

The list below provides an overview - while the subsequent pages list the full details.

Experience Manager Foundation

The platform of Adobe Experience Manager 6.3 build on top of updated versions of the OSGi-based framework (Apache Sling and Apache Felix) and the Java Content Repository: Apache Jackrabbit Oak 1.6.1.

The Quickstart uses Eclipse Jetty 9.2.19 as servlet engine.

Content Repository

Main repository enhancements are:

  • Oak Segment Tar File Format: A new TarMK format for optimized runtime and maintenance performance.
  • Full support for Online Revision Cleanup, to be scheduled for frequent automatic execution as a maintenance task without system down-time. For more guidelines please see the Revision Cleanup Tutorial.


The new Oak Segment Tar file format present in AEM 6.3 requires the existing Tar files to be rewritten. This step is mandatory during the release upgrade. For more information on what the benefits of the new Segment Tar are, see the Migrating to Oak Segment Tar FAQ.

User Interface

  • AEM 6.3 implements the 2017 Adobe Marketing Cloud UI design. Further - the user interface has been fully transitioned to the Web Component based Coral 3 UI framework.
  • The Classic UI is included in AEM 6.3. Mind that most entry points from within the Touch-optimized UI, that were enabled by default in version 5.6-6.2, to switch to the Classic UI equivalent have been disabled by default.


Adobe is planning to deprecate the Classic UI with the AEM release planned for April 2018. The 2018 release of AEM will still contain the Classic UI as it is part of AEM 6.2/6.3 releases. Following that, Adobe is planning to remove the Classic UI from the AEM release in April 2019. Read more.


  • Pre-Upgrade Maintenance Optimization has been enhanced for automation by allowing pre-upgrade tasks to be triggered using JMX.
  • Pre-Upgrade Compatibility Checks allow you to quickly perform compatibility checks on your APIs with the new version
  • Post Upgrade Check Automation makes it easier to check for errors after an upgrade.
  • Upgrade process has been made more resilient

Please see the upgrade documentation for more details on these features.


  • Use CDN (e.g. Amazon CloudFront, Akamai) to accelerate usage of AEM UI and content from author instance in a secure way. 


  • CUG
    • Closed User Group (CUG) implementation in AEM has been enhanced to address the performance, scalability and security issues present with the existing implementation.
  • OAuth
    • AEM's OAuth server can revoke previously granted access tokens and refresh tokens
    • Custom OAuth Scopes can be defined for use by AEM's OAuth server
  • CORS
    • Support for Cross-Origin Resource Sharing (CORS) requests with separate policies for different origins and resource paths

Please see the security documentation for more details on these changes.


  • Calendar view for active projects (see screenshot above)
  • Project Masters have been introduced as a new way of quickly creating Projects that reuse the same team structure

Please see the project documentation for more details on these features.


  • Workflow inbox with calendar view (see screenshot above)
  • Workflow inbox (replacing notification view from AEM 6.0-6.2) with ability to search and filter tasks.
  • Configure workflow stages in model editor, the stages help visualize the progress of the workflows while handling tasks.

Please see the workflow documentation for more details.

Supported Platforms

AEM 6.3 introduces support for:

  • Server OS
    • Microsoft Windows Server 2016
  • Application Server
    • IBM WebSphere Application Server 9.0
    • IBM WebSphere Application Server Continuous Delivery (LibertyProfile) with IBM JRE 1.8

Please find the complete matrix of supported platforms incl. Support-Level on AEM 6.3 Technical Requirements

More details are available on the AEM Foundation & Repository release notes page.

Oak MicroKernel for 
Oak MicroKernel for 

Experience Manager Sites

Full list of changes in AEM Sites and Add-ons. Here some of the highlights:

Page Editor


The Page Editor is arguably the UI most users of AEM spend most time in. AEM 6.3 features various refinements, improved loading speed and smarter reloading. The Component List gained the option to have longer descriptions for each component. The new Content Tree shows the hierarchy of components in the experience - and allow quickly find the part to edit, particular with long pages.

Comparing page versions, be it live copies, pages in launches or simply with older revisions has been improved. The new page comparison implementation focuses on the content elements and highlights changes independent of components used.

Components and Template Editor

With AEM 6.3, Adobe introduces a refined way to distribute and develop components. The Core Components are open source and distributed via GitHub. The components follow an extended set of best practices for extensibility, that allows continuous improvements, and ability for implementation partners and customers to contribute back. See the Core Components developing documentation for more details.


One for the key aspects is configuration over customization. For example the new Text component uses the design dialog to configure what Rich-Text-Editor options/plugins should be enabled, with that reducing the necessity for project based customization. Title component design dialog shown in screenshot above. See the Core Components authoring documentation for more details.

The Foundation Components, as part of the Quickstart distribution, will remain as is to allow customers to smooth update to AEM 6.3 and future versions.

Content Fragments


Introduced in AEM 6.2, Content Fragments allow working on text based content out-side the context of an experience. With AEM 6.3 the variations capability, that allows keeping flavors of the content in one place, was extended with the ability to propagate changes made in the original copy to the variations using the Sync feature. Further, to help shorten text, a Summarize feature was added, that leverages extractive summarization to recommend sentences that could possibility be removed. See short screencast.

Experience Fragments

Following on the concept of managing variations of content in-place, Experience Fragments allow to manage sections of experiences that can easily be reused and distributed. Experience Fragments and it's variations are template based and allow live copy relationship.

AEM 6.3 ships with variation templates for distributing the fragments to Pinterest and Facebook.

See the Experience Fragments screencast.

Integration with Adobe Experience Cloud

  • Leverage Adobe Cloud Platform Launch to instrument site with Experience Cloud and 3rd party tags
    (available starting July 2017).
  • The Adobe Target integration with AEM adds support for at.js. The at.js library is a new implementation library for Adobe Target designed for both typical web implementations and single-page applications.
  • The Page Editor provides a simple way to load the Activity Map. Activity Map is an Adobe Analytics application that is designed to rank link activity using visual overlays and provide a dashboard of real-time analytics to monitor audience engagement of your web pages. See the Activity Map screencast.

Multi-site Management Add-on

The new Livecopy Overview UI provide an instant view of the status, and is replacing the Blueprint Control Center.

Commerce Add-on

Adobe has work directly with commerce solution vendors to integrate their solution in the AEM Commerce Integration Framework. The following add-ons were added since April 2016:

Screens Add-on

Adobe first shipped it's digital signage solution as part of Adobe Experience Manager with AEM 6.2 in 2016. AEM 6.3 includes an all around improved solution that allows easy sharing of content and components between web sites and digital signage and kiosk experiences. Want to learn more? Follow the tutorial to explore the capabilities of AEM Screens.

With AEM 6.3, following key capabilities were added:

  • Support for local content overrides over global content (Livecopy of Channels)
  • Remote administration of Players
  • Extended hardware and OS support to run AEM Screens Player application

Experience Manager Communities

Full list of changes in AEM Communities. Here some of the highlights:

  • New We.Retail Community reference implementation
  • New account management features with email-based verification (member registration, lost member id, reset member password, email address change from member profile)
  • New ideation Community function allowing Community members to submit and to like the best ideas, then for Community moderators to review and assign a status
  • Enhancements to Community Site management (management of roles for each site)

Experience Manager Assets

AEM 6.3 brings in several new features and enhancements to Assets. A full list of changes is available in Assets. The highlights of the release are:

  • New and enhanced Assets Insights capabilities and integrations 
  • Assets Templates introducing new capabilities to create and manage assets efficiently
  • Brand Portal enhancements
  • Enhanced Catalogs capabilities and improved user experience
  • Enhanced capabilities for collaboration
  • Support for 3D files, new Adobe Imaging library and Adobe PDF library
  • New and enhanced Metadata capabilities
  • Enhanced Multi lingual assets
  • New machine learning based Smart tags & Moderation capabilities for advanced image tags automation
  • Introducing Related Assets for grouping assets on usage purpose
  • Enhanced support for Scalabilty and Performance
  • User Experience enhancements
  • Enhanced search capabilities for improved search relevance, discover ability and multi value search
  • MIME type validation is performed when binaries of files are uploaded to AEM.
  • Dispatcher IP masked in SurferInfoMgr.

AEM Desktop App

AEM Desktop App has been updated to Version 1.4, which is compatible with AEM 6.3 release. A full list of changes since the previous AEM release is provided in a dedicated AEM Desktop App release notes document. Here is a list of AEM Desktop App highlights.

Improved Architecture

The architecture of the Desktop App was improved to allow for better handling of certain operations, especially around saving larger files directly from other desktop applications (like Creative Cloud apps). Desktop app still provides the ability to mount AEM Assets repository locally as a WebDAV (Windows) or SMB1 (Mac) network share, but under the hood intercepts and translates the calls to native AEM HTTP calls. 

This allows for additional caching and optimization of the remote network calls. The AEM HTTP protocol is based on pure HTTP/S as opposed to WebDAV used previously, and allows for a much easier integration into existing IT/network infrastructure.

The new architecture is depicted here:


Saving Files with Background Upload

To ensure that users are not blocked in their application, waiting for the files being saved to be fully transported to AEM server, the saving operation saves files locally first (caches internally, so that it is invisible to the end user), and only then starts background upload to the AEM server.

This provides a better user experience (local save might be much shorter, especially with large files and/or slow network connection with AEM), and ensures that file versions are handled cleanly by AEM - even for applications, which save files in smaller chunks.

Uploading Folder Hierarchies in Background

Hierarchical / large folders can be uploaded directly from the AEM UI now, leveraging the new Create > Upload Folder option, that calls the Desktop App to execute the upload in background. The upload process can be monitored using Desktop App upload monitoring dialog.


Dynamic Media Add-on

New features and enhancement highlights for the Dynamic Media add-on include:

  • Color Management
  • Configuration & Setup Simplification
  • Components Enhancements
  • Custom Video Thumbnails
  • Dynamic Image Thumbnails
  • HTTPS Video Streaming
  • HTTP/2 Delivery
  • Image memory configuration
  • Improved efficiency of editing interactive video
  • Improved Set Creation
  • Non-Flash Adaptive Video Streaming on Desktop
  • Real-time progress status for video encoding and Youtube publishing
  • Enhanced Designer Viewer

Experience Manager Forms

AEM 6.3 Forms brings in several new features and enhancements. The highlights include:

  • Enhanced authoring and end-user experience of Adaptive Forms
  • AEM Forms data integration
  • Forms-centric AEM Workflows for AEM Forms on OSGi
  • Enhanced integration with Adobe Sign
  • Enhanced AEM Forms app
  • Enhanced Correspondence Management
  • Enhanced Document Security

More details on AEM Forms release notes page. Also, see the Summary of new features and enhancements in AEM 6.3 Forms for information about new and improved features and documentation resources.

Experience Manager Livefyre

Informations on product updates in Livefyre can be found at and subsequent release notes pages.

Leverage Customer Focused Development

Adobe is using a customer focused development model that allows customers to contribute to all stages of the development process, during specification, development and testing. Our thanks goes to all contributing customers and partners in this process.

Adobe has the procedures and processes in place to enable collection, prioritization, and tracking of customer focused bug resolution and enhancement request development. The Adobe Marketing Cloud Support Portal is integrated with the Adobe Enhancement & Defect Tracking System. Customer questions are identified and resolved with Customer Care where possible. When escalated to R&D, all customer information is captured, and used for prioritization and reporting purposes. Priority is given in development to paid support and warrantee issues and paid customer enhancements.

This process of prioritization has yielded more than 500 customer focused changes fixed in AEM 6.3.

List of files that are part of the Release




  • Adobe Experience Manager Desktop App (read more and download)
  • Package to add enhanced PDF Rasterizer (read more and download)
  • Package to add extended RAW image support (read more and download)
  • Package to add support for 3D files formats (release is planned for end of May 2017)



The user interface is available in following languages:

  • English
  • German
  • French
  • Spanish
  • Italian
  • Brazilian Portuguese
  • Japanese
  • Simplified Chinese
  • Traditional Chinese (limited support)
  • Korean

Experience Manager 6.3 has been certified for GB18030-2005 CITS to use the Chinese Encoding Standard.

Install & Update

See installation instructions for setup requirements.

Please see upgrade documentation for detailed instructions.

Certified Platforms

In order to see what platforms are certified to run with this release, please refer to the Supported platforms list.

Deprecated & Removed Features

Adobe constantly evaluates capabilities in the product and over time plans to replace capabilities with more powerful versions, or decides to re-implemented selected parts to be better prepared for future expectations or extensions.

For Adobe Experience Manager 6.3, read the list of deprecated and removed capabilities. The page also contains pre-announcement of changes in 2018 and important notice for customers that update from prior releases.

The following API classes, along with their member APIs, have been removed from the dam-api bundle:


The dam-api bundle does not export them anymore.

Following deprecated APIs have been removed from the dam-core bundle:


Detailed Changes Lists

Known Issues

Product Download and Support (Restricted Sites)

These sites are only available to customers. If you are a customer and need access, please contact your Adobe account manager.