Sandbox/Protected mode becoming mandatory (macOS Oct 2026, Windows Dec 2026)
⚠️ Action needed:
Sandbox mode becomes mandatory for Acrobat, Reader, and all third-party plugins. Plugin developers should review and update any plugins that aren't Sandbox-compatible before then, or they may stop working once the disable option is removed—macOS October 2026; Windows December 2026.
As part of our ongoing commitment to protecting our customers, we are completing the rollout of temporary option — a security technology that isolates Acrobat and Reader from the rest of the system, known as App Sandbox on macOS and Protected Mode on Windows — as the required, standard experience for Adobe Acrobat and Acrobat Reader, for all users and all third-party plugins.
Background
In September 2024, we introduced Sandbox support for Acrobat and Reader on macOS, working closely with customers and plugin developers to ensure compatibility. Sandbox mode has since rolled out successfully and is enabled by default on macOS today.
On Windows, Protected Mode (Sandbox) is already enabled by default for all users.
In both cases, a temporary option to disable Sandbox mode has remained available, giving customers and plugin developers time to validate and update their integrations.
What's changing
As adoption has matured and the ecosystem has had sufficient time to transition, we are retiring the option to disable Sandbox mode. Once this option is removed, Sandbox mode cannot be turned off, and all third-party plugins must operate within the Sandbox environment.
| Platform | What changes | Effective |
| macOS | The option to disable Sandbox mode is removed. Sandbox mode is required for Acrobat, Reader, and all third-party plugins. | October 2026 |
| Windows | The option to disable Protected Mode (Sandbox) is removed. Sandbox mode is required for Acrobat, Reader, and all third-party plugins. | December 2026 |
Why Sandbox mode matters
Sandbox technology isolates Acrobat and Reader from the rest of the system, significantly reducing the risk of exploitation from malicious files and shrinking the attack surface introduced by third-party plugins.
Disabling Sandbox/Protected mode has always meant giving up these protections. Retiring that option ensures every customer benefits from the strongest available security by default, without needing to take any action.
What plugin developers need to do
- If your plugin is already Sandbox-compatible: no action is needed.
- If your plugin is not yet Sandbox-compatible: prioritise the necessary updates and complete validation before your platform's deadline — October 2026 for macOS & December 2026 for Windows.
Completing these updates ahead of the deadlines will help ensure a seamless experience for users and uninterrupted plugin functionality.
Sandbox Compatibility Guide
Windows
- For plugin sandbox compatibility, refer to the sample plugin and follow these steps to add custom policies.
macOS
- Sandboxing is implemented using the OS-provided technology, App Sandbox.
- For privileged operations, use Apple's standard XPC service, and refer to this guide to diagnose sandbox violations.
FAQ
- Can I still disable Sandbox mode after these dates? No. Once the option is removed on your platform (macOS October 2026, Windows December 2026), Sandbox mode cannot be turned off.
- What happens to plugins that aren’t updated? All third-party plugins must operate within the Sandbox environment. Plugins that haven’t been made Sandbox-compatible may not function once the option is removed.
Need assistance?
If you have questions or need support making your plugin Sandbox-compatible, please reach out to us. Our team is available to help ensure a smooth transition.
AdChoices