How to Fix Word for Mac Out of Memory or Disk Space Error

Encountering an error that claims your Mac is out of memory or disk space when trying to save or open a document is incredibly frustrating, especially if you know you have plenty of storage available. This false alert is rarely about actual hard drive space. Instead, it stems from macOS sandboxing restrictions, corrupted global templates, or font cache conflicts within the software itself. By following the targeted diagnostic steps below, you can clear the underlying bottlenecks and force the application to accurately read your system resources.

Verify Storage and Clear the Application Sandbox Cache

Modern macOS environments isolate applications into specific sandboxes. When the cache within this sandbox becomes bloated or corrupted, the application mistakenly believes the entire system is out of memory. Your first step is to verify actual storage, then manually clear the temporary cache files.

• Check Actual Space: Click the Apple logo in the top-left corner of your screen, select About This Mac, and click Storage. Confirm you have at least 10 GB of free space. If you do, the error is definitely software-related.
• Close the Application: Ensure the application is completely shut down. Right-click its icon in the Dock and select Quit.
• Access the Library Folder: Open Finder. Click Go in the top menu bar, hold down the Option key on your keyboard to reveal the hidden Library option, and click it.
• Navigate to the Cache: Go to Containers, find the folder named com.microsoft.Word, and navigate through Data > Library > Caches.
• Delete Cache Files: Drag all files inside the Caches folder to the Trash. Empty the Trash.

Once you complete these actions, relaunch the application and open your document. Try saving it immediately. This verification step confirms whether a simple sandbox limit was triggering the false memory warning.

Rebuild the Global Normal.dotm Template

The global template file dictates default formatting, margins, and macros for every new document you create. Over time, saving over this file repeatedly can corrupt its code, causing memory leaks that trigger the out of memory or disk space error. Forcing the application to generate a fresh template will clear these underlying structural errors.

• Quit the Software: Make sure the document editor is completely closed.
• Open the Group Containers Path: Open Finder, press Command + Shift + G to open the Go to Folder dialog box.
• Enter the Directory: Paste the path ~/Library/Group Containers/UBF8T346G9.Office/User Content/Templates and hit Return.
• Isolate the Template: Locate the file named Normal.dotm. Do not delete it yet. Click and drag it to your Desktop to serve as a backup in case you have custom macros you need to recover later.
• Generate a New Template: Open the application. Upon launching, it will detect that the template is missing and automatically build a clean, factory-default Normal.dotm file in the original folder.

Open the specific file that was causing issues and attempt to save it. If the save is successful, the previous template was the root cause of the memory spike.

Resolve Font Book Duplicates and Conflicts

When you open a document, the software loads the entire macOS font library into active memory. Duplicate fonts or corrupted font files cause the loading sequence to hang, artificially maxing out the allocated RAM and prompting the error. Cleaning up your Font Book is a necessary diagnostic check.

• Launch Font Book: Open Launchpad, type Font Book in the search bar, and open the application.
• Scan for Errors: Click Edit in the top menu and choose Look for Enabled Duplicates.
• Resolve Duplicates: If any duplicate fonts appear, a prompt will ask if you want to resolve them automatically. Choose Resolve Automatically to disable the conflicting redundant files.
• Validate Active Fonts: Select all remaining fonts by clicking one and pressing Command + A. Click File > Validate Fonts. A window will appear showing green checkmarks for healthy fonts and red warning signs for corrupted ones.
• Remove Corruptions: Right-click any font with a red warning sign and select Remove.

Restart your Mac to refresh the system-wide font cache. Open your document and test the save function to verify the memory error has cleared.

Compress High-Resolution Images in the Document

If the error only happens with one specific file, the document itself is likely overwhelming the system's memory allocation. Pasting raw, uncompressed images (like high-resolution photos from an iPhone) directly onto the page forces the software to render gigabytes of visual data in real-time.

• Select an Image: Click on any photograph or large graphic inside your document.
• Open the Picture Format Tab: Click the Picture Format tab that appears in the top ribbon menu.
• Compress Pictures: Click the Compress Pictures icon. In the dialog box that appears, select All pictures in this document.
• Lower the Resolution: Choose On-Screen (150 ppi) or Print (220 ppi) instead of High Fidelity. Check the box that says Delete cropped areas of pictures. Click OK.

Wait a moment for the application to process the compression. Click Save As and try saving the file under a new name. This will permanently reduce the document's footprint and prevent active memory limits from being breached.

Continue Editing Lightweight Documents Using WPS Office

If you have cleared caches, resolved fonts, and rebuilt templates, but complex Microsoft ecosystem issues, corrupted updates, or heavy background syncing continue to trigger memory limits on your Mac, you may need a more resource-efficient tool to finish your work. WPS Office provides a streamlined architecture that consumes significantly less active RAM while handling standard document formats seamlessly.

Because WPS Office uses an independent cache system and requires fewer background processes than traditional enterprise suites, it can easily open large, image-heavy files that previously crashed your system. To use this workflow:

• Install and Launch: Open WPS Office on your Mac.
• Open the Problematic File: Click Open and select the exact document that was triggering the out-of-memory error. WPS natively reads the existing formatting.
• Edit and Export: Make your necessary edits. Because WPS Office features built-in, lightweight PDF conversion tools, you can click Menu > Export to PDF. This bypasses traditional memory-heavy print spoolers, allowing you to quickly secure a finalized version of your work without triggering storage or RAM alerts.

Frequently Asked Questions

Why does the application report insufficient memory when my Activity Monitor shows plenty of free RAM?

macOS restricts how much physical memory a single background process or sandboxed application can claim at one time. Even if you have 16GB or 32GB of RAM installed, the application itself might hit a 32-bit ceiling limit on an older process, or it might be experiencing a sandbox memory leak. The error reflects the application's internal limit, not your Mac's overall hardware capacity.

Will deleting the global template file erase my saved documents?

No, removing or resetting the global template file will not delete, alter, or remove any of your saved text documents. The template only controls the default starting settings—like standard font size, default margins, and custom macros—when you click to create a brand-new blank page. Your existing files remain completely safe on your hard drive.

How do I recover my unsaved work if the memory error forces the software to close?

If a crash occurs, open Finder, hold the Option key, and click Go > Library. Navigate to Containers > com.microsoft.Word > Data > Library > Preferences > AutoRecovery. If the built-in auto-save feature was active before the memory failure, you will find a recovery file ending in .asd here. Drag it to your Desktop, right-click, and choose to open it with your document editor to retrieve your lost text.

Can third-party citation plugins cause a false disk space error?

Yes. Third-party add-ins, especially reference managers and grammar checkers, constantly scan your text and write temporary data to your Mac's cache. If an add-in is poorly optimized or incompatible with your current macOS version, it will flood the application's memory allocation. Disabling these add-ins via the Insert > Get Add-ins menu will instantly stop the background scanning and resolve the error.