Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
The new pages will be published when the release is published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Adobe Acrobat Sign release v17.1.2
Sandbox deployment: June 16, 2026
Production deployment: July 21, 2026
GovCloud deployment: July 23, 2026
Improved Functionality
- Preserve Existing Digital Signatures in Uploaded PDFs – Admins can enable Acrobat Sign to preserve existing digital signatures in uploaded PDF files, allowing pre-signed documents to move through supported agreement workflows without flattening the original signature. This helps organizations use documents that were digitally signed before upload while protecting the document from changes that would invalidate the preserved signature.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the configuration for preserving digital signatures >
Review the process for sending a PDF with an existing digital signature >
- Inline Document Editing During Authoring – Edit document text directly in the authoring experience
Senders can edit document text directly in the authoring environment without downloading and re-uploading the file. The Edit Document option preserves existing fields and agreement configuration, reducing disruption during pre-send updates. Editing is available only while the agreement is in a draft state and is not available after the agreement is sent.
In-line document editing is to be released on a rolling schedule, as referenced in the technical notification.
This feature is enabled by default for all users in supported accounts, allowing senders to edit documents that are sent through Request Signature. Account and group admins can disable document editing through the Send Settings.
In-line document editing is not available in Acrobat Sign for Government or for accounts using the legacy user management system.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions VIP and VIPMP customer accounts | Configuration scope: Account and Group; Enabled by default
Enable or disable in-line document editing >
How to edit text during field authoring >
Release errata - Elements removed
Below are the line items that previously were announced as part of this release, but have since slipped to a later release date.
- Customer-managed encryption keys for agreement files – Eligible Acrobat Sign customers can configure an AWS KMS customer-managed key to protect supported agreement files at rest. After the feature is enabled for an account, supported agreement files are encrypted using the customer-managed key, giving organizations more control over key management while preserving supported Acrobat Sign agreement workflows.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account only
