Current Release Notes for Adobe Experience Manager as a Cloud Service release-notes

The following section outlines the feature release notes for the current (latest) version of Experience Manager as a Cloud Service.

NOTE
From here, you can navigate to release notes of previous versions such as 2023 or 2024.
Have a look at the Experience Manager Releases Roadmap to learn about the upcoming feature activations for Experience Manager as a Cloud Service.
NOTE
To receive a monthly email notification about updates to Experience Cloud release notes, subscribe to the Adobe Priority Product Update.

Release Date release-date

The release date of Adobe Experience Manager as a Cloud Service current feature release (2025.8.0) is August 28, 2025. The next feature release (2025.9.0) is planned for September 25, 2025.

Maintenance Release Notes maintenance

You can find the latest maintenance release notes here.

Experience Hub experience-hub

The Experience Hub is your centralized starting point for accessing all AEM capabilities. It is personalized based on your user persona and the licenses available to you, enabling each user to accomplish their outcomes efficiently.

AI Assistant in AEM AI-assistant

The AI Assistant for AEM offers a conversational interface designed to get you instant answers to your AEM product-related questions (available to all users) and automate support ticket creation (available to Support Admins). It is directly embedded in AEM and accessible from AEM Experience Hub, Cloud Manager, and Author UI.

Experience Manager Sites as a Cloud Service sites

New features in Experience Manager Sites enhancements-sites

  • In Content Fragments Admin UI you can now view the workflow status for content fragments, with detailed information about past and currently running workflows for a selected fragment.
  • The performance for opening content fragments in the new content fragment editor has been increased by 25% in common scenarios by opening fragments via UUID instead of by path.
  • When copying content fragments with referenced fragments, copies of the referenced fragments are now stored in the same location as the parent fragment copy.
  • You can now configure a custom workspace in the folder settings, to export the content fragments to the configured workspace in Adobe Target.

Experience Manager Assets as a Cloud Service assets

New Features in Content Hub new-features-content-hub

Bulk Search via Filter properties

Content Hub now makes it faster to discover the assets you need. With the new Bulk Search capability, you can enter multiple values for any filter property—separated by a delimiter (for example, multiple SKU IDs)—and instantly retrieve all matching assets using a single search.

New Features in Dynamic Media with OpenAPI capabilities new-features-dynamic-media-with-openapi

SEO friendly DM with OpenAPI URLs

Create Vanity URLs for asset delivery in DM with OpenAPI, replacing long system-generated UUIDs with short, readable identifiers. This makes links SEO friendly and better aligned with your brand or campaigns. Vanity URLs resolve automatically to the original asset UUID at runtime without disrupting existing workflows.

NOTE
This feature will be available as a Limited Availability feature on September 10. You can create and submit an Adobe Customer Support case to enable it for your deployment.

Experience Manager Forms as a Cloud Service forms

New features in Experience Manager Forms new-features-forms

Date & Time Input Component

A Date & Time component is now available, enabling users to select both date and time using a calendar and clock interface, or by manually entering values in a supported format.

Enhanced Error Handling for File Uploads

The File Attachment component now automatically validates the uploaded file type against the allowed list. If a user uploads a file in an unsupported format, the form displays an error during submission. The component also checks the file content to validate its type, enhancing the overall security of the form.

Specified Error Response for Custom Submit Action

When a custom submit action encounters an unhandled error, the system returns error code 502. This helps identify that the issue is related to the custom submit action, making debugging easier.

Excluding Hidden Fields from Document of Record

A new property allows exclusion of hidden fields from the Document of Record. By default, this option is not selected and applies to all form fields.

Pre-Release features in AEM Forms

Generate and Sync AFP Renditions

You can now use the AEM Forms Communication API to convert an XDP file to AFP format. AFP is a high-performance format widely used in large-scale enterprise printing.

Enhancements in Rule Editor

  • Validate Method in Function List: The validate and reset methods now support execution at the panel, field, and form levels. Previously, they were only supported at the form level.

  • Modern JavaScript Support: Support for ECMAScript 2019 and later features has been added for custom functions, allowing you to write more efficient, modular, and reusable code.

  • Download DoR Option in Rule Editor: A function to download the Document of Record (DoR) has been added as an out-of-the-box (OOTB) option in the Rule Editor.

    Document-of-Record

  • Dynamic Variables in Rule Editor: You can now use dynamic (temporary) variables in the Rule Editor for greater flexibility in defining conditions and actions. Hidden fields are no longer required to store temporary values.

  • Custom Event Based Rules Support: You can now define custom events and trigger rules based on those events.

  • Context-Aware Repeatable Panel Rules: In repeatable panels, rules are now executed based on context, instead of being applied only to the last panel instance.

  • Rules Triggered by Parameters: The Rule Editor now supports rule execution based on query parameters, UTM parameters, or browser parameters.

  • Form-Specific Custom Functions: Edge Delivery Services Forms now support form-specific custom function scripts, providing greater flexibility in managing reusable logic.

  • Static Imports for Custom Functions: The Rule Editor in Universal Editor now supports static imports, allowing developers to organize, share, and reuse functions across multiple forms.

New Early Access Features in AEM Forms forms-new-early-access-features

The AEM Forms Early Access Program offers a unique opportunity for you to get exclusive access to cutting-edge innovations and help shape their development.

These release notes list the innovations delivered in the current release. For the complete list of innovations available under the Early Access Program, see AEM Forms Early Access Program documentation.

Scribble Signature Component

You can now use the Scribble Signature component to help users add their signatures to a form, such as in an agreement form. The component allows users to draw their signature directly within the form using a mouse, stylus, or touchscreen.

Direct API Integration in Rule Editor

Adaptive Forms now support direct API integration in the Visual Rule Editor without requiring a Form Data Model. Authors can configure APIs using a URL or cURL import, map input/output parameters, and secure calls with authentication.

Experience Manager as a Cloud Service Foundation foundation

JavaScript Compilation Update javascript-compilation

The default client-side library (clientlibs) JavaScript compilation now targets ECMASCRIPT_2018 instead of ECMASCRIPT5. While overridable in the past, this update enables performance improvements, modern JavaScript syntax, and features by default.

Upcoming Java API Deprecations java-api-deprecation

Several deprecated APIs are targeting removal on August 31st and thus should no longer be referenced. In early September, Actions Center notifications will be sent if API usage is detected, and after September 25th, notices will appear during Cloud Manager builds to reinforce the importance of removing usage. See the deprecation article for full details, but for convenience, these APIs are listed below:

Expand to see the Java API deprecations
  • org.apache.sling.commons.auth
  • org.apache.felix.webconsole
  • org.eclipse.jetty
  • com.mongodb
  • org.apache.abdera
  • org.apache.felix.http.whiteboard
  • org.apache.cocoon.xml
  • ch.qos.logback
  • org.slf4j.spi
  • org.slf4j.event
  • org.apache.log4j
  • com.google.common
  • com.drew
  • org.bson
  • org.apache.jackrabbit.oak.plugins.blob
  • org.apache.jackrabbit.oak.plugins.memory

Java 11 Runtime Deprecation java11-runtime-deprecation

The Java 11 runtime is now deprecated, and most environments have already been upgraded to the more performant Java 21 runtime.

If your environment could not be upgraded due to unsupported dependencies (see Java 21 runtime requirements), you should have received an email from Adobe with specific next steps. Please ensure all required updates are completed by October 1st, 2025, so your environment can be upgraded without disruption.

Note: The runtime version is separate from your code’s build version. While we recommend building with Java 21, Java 11 builds are still supported for now. A separate deprecation notice for Java 11 builds will be shared in the future.

Enforcement of AEM Java Logs Configuration Policy logconfig-policy

As noted in the April release notes, AEM Java logs must follow a standard format to ensure reliable monitoring across all customer environments. Custom log configurations—such as changes to log formatting, output files, or default log levels—are no longer supported. Logs must remain directed to the default files, and default log levels for AEM product code must be preserved. See full details in the Logging article.

Starting on September 25th, any unsupported custom logging overrides will be ignored. Based on our analysis, most customers will not be impacted and Adobe has contacted customers whose current configuration may be affected.

Please review and update any downstream processes that rely on custom logging behavior. For example:

  • If your log forwarding system expects a custom log format, you may need to adjust your ingestion rules.
  • If you’ve previously reduced log verbosity by changing log levels, please note that reverting to default levels may increase log volume.

Edge Computing (Beta Program) edge-computing

Edge computing allows you to execute JavaScript at the CDN layer, bringing data processing closer to the end user. This reduces latency and enables responsive, dynamic experiences at the edge.

Common use cases include:

  • Authenticating users with an identity provider before granting access to content
  • Personalizing content based on geolocation, device type, or user attributes
  • Acting as middleware between the CDN and your origin
  • Reformatting responses from third-party APIs (and perhaps aggregating multiple API responses) before delivering them to the browser
  • Composing and serving server-rendered HTML at the edge using content stitched from various backends
  • Exposing an MCP server for LLMs like ChatGPT and Claude to access custom tools

We have a limited number of opportunities available for either AEM Publish Delivery or Edge Delivery Services projects for live production sites. If you’re interested in participating or want to learn more, please email aemcs-edgecompute-feedback@adobe.com with a brief description of your use case.

CDN Configuration for Edge Delivery Services (Beta Program) cdn-eds-beta

The Adobe-Managed CDN offers flexible configuration options, as described in the Config Pipeline article.

Now in beta, youcan deploy a config pipeline for features including CDN origin selectors, response and request transformations, CDN log forwarding and more. Please reach out to aemcs-cdn-config-adopter@adobe.com with the details of your use case.

Snapshots for RDEs (Alpha Program) rde-snapshot-program

In alpha, Rapid Development Environments (RDEs) now support a feature to take a snapshot of the current state of code and content, which can be restored at a later time. This can be useful when syncing code that may need to be reverted, or when switching between development of different features. It’s also possible to restore just the mutable content as a known starting point for testing.

Please email aemcs-rde-support@adobe.com if there’s interest in providing feedback on this feature.

AEM Log-Forwarding to More Destinations (Beta Program) log-forwarding-beta

While logs can be downloaded from Cloud Manager, many organizations find it beneficial to stream those logs to a preferred logging destination. AEM already supports AEM and CDN log forwarding to Azure Blob Storage, Datadog, HTTPS, Elasticsearch (and OpenSearch), and Splunk. This feature is configured in a self-serve manner, and deployed using the Config Pipeline.

Now in beta, you can forward AEM logs to Amazon S3, Sumo Logic, Dynatrace, and your own New Relic account (not the Adobe-provided account). Note that AEM logs (including Apache/Dispatcher) are supported for these logging destinations, but not CDN logs. Email aemcs-logforwarding-beta@adobe.com for access.

Learn more in the log forwarding documentation.

Experience Manager Guides guides

You can find a complete list of new and enhanced features of the latest release of Adobe Experience Manager Guides here.

Cloud Manager cloud-manager

You can find a complete list of Cloud Manager monthly releases here.

Migration Tools migration-tools

You can find a complete list of Migration Tools releases here.

Universal Editor universal-editor

You can find a complete list of Universal Editor releases here.

Generate Variations generate-variations

You can find a complete list of Generate Variations releases here.

Experience Cloud Release Notes experience-cloud

You can find information about releases of other Experience Cloud applications here.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab