Missing search function for searching agreements in Adobe Acrobat DC Mac

​

Hi @MasterStudent42069 , 

Hope you're doing well and thanks for flagging this. What's most likely happened is that a recent update quietly pushed you onto the New Acrobat experience, which has reorganized (and in some cases temporarily displaced) certain features that lived in the classic interface.

Here are a few things to try, in order:

Check your Acrobat version and update
Go to Help > Check for Updates and make sure you're on the latest build  26.001.21691 Planned update, Jun 25, 2026 and reboot the computer once. 

Toggle back to the Classic view (temporarily, to confirm)
You've already found that Classic View restores the search bar, that's actually a really useful confirmation that this is a UI-layer issue, not a missing feature. It means your agreements and their searchability are intact; it's just a matter of which interface is surfacing the control.

Try toggling the New Acrobat experience off and back on
Sometimes the New Acrobat UI gets into a partially-loaded state where certain elements don't render correctly. To reset it on Mac, go to View > Disable New Acrobat, let Acrobat restart, then go back to View > Enable New Acrobat again. This forces a clean reload of the interface and has resolved missing UI elements for a number of community members.

Clear Acrobat's preferences cache
If the toggle above doesn't help, corrupted preferences can cause elements to silently not render. On Mac, quit Acrobat completely, and follow the steps as described here  https://adobe.ly/4wyeXMk and check if the search bar is back.

Log out and back into your Adobe account
Since Agreements is tied to your Adobe Sign / Acrobat Sign account, a session sync issue can occasionally cause the Agreements UI to render incompletely. In Acrobat, click your profile icon > Sign Out, then sign back in.

If none of the above brings the search bar back in the New Acrobat view, would you be able to share your Acrobat version number (Help > About Adobe Acrobat) and your macOS version? That'll help narrow down whether this is tied to a specific build.

~Amal