Other PDF Issues

How to Fix Adobe Acrobat Crashing on macOS When Opening or Printing PDFs

Bushra ParveenBushra Parveen Nov 5, 2026 869 views

Question details

The user is experiencing frequent crashes with Adobe Acrobat on macOS after a software update, preventing them from performing basic document tasks.

How to Fix Adobe Acrobat Crashing on macOS When Opening or Printing PDFs
Product
Adobe Acrobat
Device & OS
macOS (Big Sur)
Scenario
Opening existing PDF files, saving PDFs exported from Illustrator, or attempting to print completed PDF forms.
Observed behavior
The application crashes and shuts down unexpectedly during standard operations like opening, saving, or printing.
Before you start

Before diving into complex troubleshooting, simply restart your Mac to clear temporary system glitches and test opening a few different PDF files to confirm if the crash is isolated to a single corrupted document or affects all files.

Solution 1Recommended

Reset Adobe Acrobat Preferences

Resetting the application preferences to default can resolve frequent crashing caused by corrupted configuration files after a software update.

Software updates can sometimes conflict with existing application preference files. Deleting these files forces Acrobat to generate fresh, uncorrupted settings upon its next launch.

1
Quit the application

Ensure Adobe Acrobat is completely closed. If it is unresponsive, use the 'Force Quit' option from the Apple menu.

2
Access the Library folder

Open Finder, hold down the 'Option' key, click on 'Go' in the top menu bar, and select 'Library'.

3
Remove preference files

Navigate to the 'Preferences' folder and locate files starting with 'com.adobe.Acrobat'. Move these specific plist files to the Trash.

4
Restart Acrobat

Relaunch Adobe Acrobat. The application will create new default preference files automatically.

Reset Adobe Acrobat Preferences
Preference Reset: If the crashing stops after this step, your issue was caused by a corrupted plist file. You can safely empty your Trash.

Use WPS Office to Open, Save, and Print PDFs Seamlessly

If your current PDF software continues to crash on macOS, WPS Office offers a built-in, highly stable PDF reader and editor. You can easily open, fill out, save, and print your PDF files without experiencing unexpected crashes.

  1. 1. Download and install: Download WPS Office for Mac from the official website and complete the installation process.
  2. 2. Open your PDF document: Launch WPS Office, select 'PDF' from the home screen sidebar, and click 'Open' to browse and load your PDF file.
  3. 3. Edit, save, or print: Use the intuitive top toolbar to make any necessary document modifications, click the 'Save' icon to keep changes, or press 'Cmd+P' to send the document directly to your printer.
Stable and lightweight PDF reader designed to perform efficiently on macOS.Fully compatible with Microsoft Office formats (Word, Excel, PowerPoint) and standard PDFs.Built-in printing and form-filling features for complete document management.Free and easy-to-use interface that requires no steep learning curve.
microsoft office alternative - wps office

Frequently Asked Questions

Why does Adobe Acrobat crash after updating macOS to Big Sur?

System updates can introduce new security protocols or framework changes that conflict with older versions of Adobe Acrobat. Updating the software to its latest patch or resetting preference files typically resolves these system conflicts.

How do I find PDF crash reports on my Mac?

You can find crash reports by opening the 'Console' app on your Mac (found in Applications > Utilities). Navigate to 'Crash Reports' or 'User Reports' on the sidebar to view logs related to Adobe Acrobat, which can be shared with support teams for deeper investigation.

Can a corrupted PDF file cause the entire application to crash?

Yes, if a PDF file contains broken code, corrupted images, or poorly embedded fonts, it can cause the software's rendering engine to fail and crash the application entirely. Always test with multiple, unrelated PDF files to determine if the issue is file-specific or application-wide.