Office for Mac Issues

How to Fix Runtime Error 53 in Word for Mac

Phi Hung Vo Oct 15, 2026 868 views

Question details

Users experience persistent 'Runtime Error 53' pop-ups when trying to open documents in Microsoft Word for Mac, even after updating the operating system and the Office suite.

How to Fix Runtime Error 53 When Opening Word for Mac Documents

Product: Microsoft Word for Mac
Device & OS: macOS
Scenario: Opening a new or existing document in Microsoft 365 on a Mac.
Observed behavior: A 'Runtime Error 53' dialog box appears repeatedly every time a document or worksheet is opened, interrupting the user's workflow.

Before you start

Ensure you have completely quit Microsoft Word and saved all your work before modifying the application's system folders.

Solution 1Recommended

Remove Conflicting Startup Add-ins

Runtime Error 53 on Mac is most frequently triggered by an outdated Adobe Acrobat or third-party add-in attempting to load when Word starts. Removing it resolves the issue.

The most common culprit is an Adobe PDF add-in file named 'linkCreation.dotm' located in the Word Startup folder. Because it relies on libraries that may no longer be supported on your current macOS version, deleting this obsolete template usually resolves the error immediately.

Quit Microsoft Word

Ensure Microsoft Word is completely closed. Right-click the Word icon in your Mac's Dock and select 'Quit'.

Open the Group Containers folder

Open Finder. In the top menu bar, click on 'Go' and select 'Go to Folder' (or press Cmd+Shift+G). Paste the following path exactly: ~/Library/Group Containers/UBF8T346G9.Office/User Content/Startup/Word/ and press Return.

Delete the conflicting add-in

Look for a file named 'linkCreation.dotm' or any other recently added .dotm file in this folder. Drag this file to the Trash.

Restart Word

Reopen Microsoft Word and open a document to verify that the Runtime Error 53 no longer appears.

Add-in Removed Successfully: Word will now launch smoothly without attempting to load the incompatible dynamic library.

Solution 2

Disable Templates from Within Word Settings

If you cannot locate the startup folder or prefer not to modify system directories directly, you can disable active add-ins from Word's internal settings interface.

Free Microsoft Office alternative

Switch to WPS Office for a Stable, Error-Free Experience on Mac

Tired of troubleshooting runtime errors and add-in crashes in Microsoft Word? WPS Office provides a lightweight, highly compatible, and free alternative for Mac users. Enjoy seamless document editing without the hassle of complex system dependencies.

1. Download WPS Office: Visit the official WPS website and download the free macOS installer.
2. Install and Launch: Follow the standard Mac installation process and launch the application.
3. Open Your Documents: Drag and drop your existing .docx files directly into WPS Office to continue working seamlessly.

Fully compatible with Microsoft Word formats (.doc, .docx)Lightweight architecture that runs smoothly and efficiently on macOSNo complex add-in dependencies, minimizing annoying runtime errorsFamiliar, intuitive user interface for a zero-learning-curve transition

Frequently Asked Questions

What exactly does Runtime Error 53 mean in Word for Mac?

Runtime Error 53 generally indicates that a specific file or dynamic library could not be found by the system. On Word for Mac, this typically happens when an outdated add-in tries to load a supplementary file that doesn't exist on newer versions of macOS.

Will reinstalling Microsoft 365 fix Runtime Error 53?

Usually, no. Reinstalling Microsoft 365 does not clear out the user-specific 'Group Containers' folder where problematic third-party add-ins are permanently stored. You must manually locate and delete the conflicting add-in file to stop the error.

Can Adobe Acrobat cause Runtime Error 53 in Word?

Yes, the Adobe Acrobat 'Create PDF' add-in (often named linkCreation.dotm) is one of the most common causes of Runtime Error 53 on Mac following an Office or macOS system update. Removing this obsolete file from the Word Startup folder fixes the issue.

Office App Problems