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.
Release Date release-date
The release date of Adobe Experience Manager as a Cloud Service current feature release (2025.9.0) is September 25, 2025. The next feature release (2025.10.0) is planned for October 30, 2025.
Maintenance Release Notes maintenance
You can find the latest maintenance release notes here.
Experience Manager Sites as a Cloud Service sites
New features in Experience Manager Sites Prerelease prerelease-sites
The Content Model Editor for AEM Content Fragments has been modernized to align with other React Spectrum–based interfaces in AEM. Its user interface implementation and extensibility model are now consistent with the Content Fragment Editor and Universal Editor. The new Model Editor is now default when opened from the new Content Model Admin UI. Opening a content model in Touch UI opens the Touch UI editor and offers to try out the new editor.
Experience Manager Assets as a Cloud Service assets
New Features in Assets view new-features-assets-view
Enhanced Text Formatting with Substrings in Dynamic Media Templates
You can now apply formatting to substrings within Dynamic Media template text layers. A selected word or phrase is treated as a separate layer, allowing you to adjust its font, font size, color, and more. The substring layer is parameterized so you can update it in real-time using the template’s delivery URL.
New Features in Content Hub new-features-content-hub
Mark Collections as Favourites
You can now mark collections as Favorites in Content Hub, making it easier to organize and retrieve them. Once added, your favourite collections are conveniently available from the Favourites tab on the Content Hub home page.
Pin collections for quick access
Content Hub Administrators can now pin collections in Content Hub for quick access. Pinned collections are displayed in a dedicated Pined section on the Collections home page, making it easier to keep important collections within reach.
New Features in Dynamic Media with OpenAPI capabilities new-features-dynamic-media-with-openapi
Branded and Readable Asset Delivery URLs
Make Dynamic Media with OpenAPI URLs more human-readable by leveraging Vanity URLs in Dynamic Media with OpenAPI. Vanity URLs allow replacing long, system-generated, hard to memorize UUIDs in asset delivery URLs with short, brand-controlled identifiers. This makes Vanity URLs shorter, easier to read and share, and allow for better alignment with your brand or campaigns. Vanity URLs resolve automatically to the original asset UUID at runtime without disrupting existing workflows.
Experience Manager Forms as a Cloud Service forms
New features in Experience Manager Forms new-features-forms
Invoke Form Data Model Workflow Step for SharePoint List Attachments
The Invoke Form Data Model workflow step now supports handling workflow-side metadata for Base64-encoded attachment arrays in SharePoint List–based Form Data Models. With this enhancement, the workflow step can pass, store, and retrieve metadata such as file name, MIME type, and custom properties for each attachment. This capability enables more comprehensive data management and facilitates seamless downstream integration. For details, see Enhanced support in Invoke Form Data Model workflow step for SharePoint List attachments.
Pre-Release features in AEM Forms
Rule Editor Enhancements
The Rule Editor now supports enhanced navigation and allows use of function and mathematical expressions in input parameters.
Enhanced Navigation with Event Payload Support
The Navigate To action in the Invoke Service handlers now supports EVENT_PAYLOAD, enabling form authors to configure follow-up actions based on event responses. This enhancement offers greater flexibility in designing post-submission workflows, ensuring smoother transitions and more personalized user experiences. For more information, see Enhanced Navigation with Event Payload Support.
Function and Mathematical Expression Support in Input Parameters
Input parameters now support both function calls and mathematical expressions, enabling form authors to pass dynamically computed values directly. This enhancement streamlines rule configurations, eliminates the need for extra fields, and makes forms more adaptable to complex logic and calculation-driven scenarios. For more information, see Function and Mathematical Expression Support in Input Parameters.
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.
PDF Preview in Interactive Communication Editor
Users can preview Interactive Communications PDFs without data, with local JSON data files, or with data from a data model, enabling flexible data-driven testing. For more information, see PDF Preview in Interactive Communication Editor.
Support of Custom Fonts in Interactive Communication
The Custom Fonts feature allows users to embed custom or organization-approved fonts in the Interactive Communications, ensuring consistent and branded PDF rendering across devices and platforms. For more information, see Support of Custom Fonts in Interactive Communication.
Import and Export Interactive Communications
This feature enables migration and reuse of Interactive Communications across different environments. You can now export an Interactive Communication along with its associated fragments and data models from one environment and import it into another. For more information, see Import and Export Interactive Communications.
Experience Manager as a Cloud Service Foundation foundation
New Features in Release Management new-features-release-management
Pause Automatic Maintenance Updates
Go‑live days, live events, peak sales—these moments can’t break. Our new self‑service features stop automatic mainteanance updates when it matters, so your teams stay focused.
- Quiet Hours: Block automatic maintenance during set times each day. Ideal for working hours, nightly runs or morning cutovers.
- Update‑Free Period: Block automatic maintenance for a full week. Use it for launches, promos, or yearly freezes.
Email aemcs-update-free@adobe.com to get it activated on your programs.
New Release of AEM Developer Tools for Eclipse aem-develeper-tools-for-eclipse
Version 1.4.0 of the AEM Developer Tools for Eclipse has been released. This version adds support for Eclipse IDE 2022-12 or newer and has been validated with the current version (2025-09). The tooling now works with modern versions of the AEM Project Archetype and incorporates improvements from the Sling IDE Tooling 1.3.0.
Install from the Eclipse Marketplace and see the AEM Developer Tools page for more details.
Upcoming Java API Deprecations java-api-deprecation
Several deprecated APIs were marked for removal on August 31st and thus should no longer be referenced. You will receive Actions Center notifications if deprecated API usage is detected in your code, and after Nov 13th, 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:
org.apache.sling.commons.authorg.apache.felix.webconsoleorg.eclipse.jettycom.mongodborg.apache.abderaorg.apache.felix.http.whiteboardorg.apache.cocoon.xmlch.qos.logbackorg.slf4j.spiorg.slf4j.eventorg.apache.log4jcom.google.commoncom.dreworg.bsonorg.apache.jackrabbit.oak.plugins.bloborg.apache.jackrabbit.oak.plugins.memory
Java 11 Runtime Deprecation java11-runtime-deprecation
The Java 11 runtime is deprecated, and most environments have already been upgraded to the higher-performance Java 21 runtime.
If your environment could not be upgraded due to unsupported dependencies (see the Java 21 runtime requirements), you should have received an email from Adobe with next steps. As described there, Adobe upgraded your Dev and RDE environments on September 18, 2025 so you can validate your site and processes and address any issues. Upgrades for Stage and Production will proceed on October 14, 2025.
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 October 30th, 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:
- 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.
Edge Authentication for Edge Delivery Services (Beta Program) edge-authentication
Edge Authentication lets you restrict access to Edge Delivery Services pages to only those who have authenticated with your identity provider (IdP). This is achieved by deploying an OpenID Connect (OIDC) configuration YAML file.
If interested, please email aemcs-edgecompute-feedback@adobe.com with a brief description of your use case and any questions you may have.
Canary Production Deployments to Test Code Before Accepting Live Traffic (Beta Program) canary-beta
Validate a production build with internal-only test traffic before exposing it to end users. Ship to production, route only canary traffic (using a special header), monitor behavior, then either promote to live traffic or roll back—without impacting customers.
Deploy your code releases to production, but restrict it to only internal test traffic before deciding whether to accept live traffic versus rolling back.
Email aemcs-canary-deployments-beta@adobe.com to request access and share feedback.
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.
Expanded Application Performance Monitoring (APM) (Alpha program) apm-alpha
For observability, AEM Cloud Service currently supports Adobe-provided New Relic One and customer-managed Dynatrace. As we explore support for additional APM options, please email us at aemcs-apm-beta@adobe.com with your preferred vendor or technology, along with use cases.
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.