If Outlook for Mac crashes specifically when you reply to or forward an email, the most common cause is a corrupted reply template or a problematic add-in, and the fix is usually to reset the reply template or disable add-ins. This article walks through the most effective fixes, from quick resets to deeper cache rebuilds, so you can get back to emailing without losing your data.
Why Does Outlook for Mac Crash on Reply?
Outlook for Mac (the standalone app, not the web version) uses a hidden reply template file that stores the formatting, fonts, and signature behavior for replies and forwards. When this file becomes corrupted—often after a macOS update, a crash during a previous send, or a sync conflict—every reply attempt can trigger a crash. Add-ins (like Zoom, DocuSign, or Teams) can also interfere because they load into the compose window. Less commonly, a large or malformed email signature or a corrupted cache database causes the crash only when the reply window tries to render.
Fix 1: Reset the Reply Template (Quickest Fix)
Outlook for Mac stores reply/forward formatting in a file called ReplyTemplate. Resetting it forces Outlook to rebuild it from defaults. This does not delete your emails, contacts, or signatures.
- Quit Outlook completely (Cmd+Q).
- Open Finder and press Cmd+Shift+G (Go to Folder).
- Paste this path and press Enter:
~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main Profile/Data/
Note: “UBF8T346G9” is the standard container ID for Microsoft Office on Mac; it appears the same on all current versions. - Look for a file named
ReplyTemplate(no extension). If you see it, drag it to the Desktop (as a backup) or trash it. - Restart Outlook. It will create a fresh template. Try replying to a test email.
If the crash persists, the template wasn’t the culprit—move to the next fix.
Fix 2: Disable Problematic Add-ins
Add-ins are a common crash trigger because they inject code into the compose window. To test if an add-in is the problem:
- Open Outlook and go to Settings (gear icon) > General > Manage Add-ins.
- You’ll see a list of installed add-ins. Disable them all by unchecking each box.
- Restart Outlook and try replying.
If replies work after disabling all add-ins, re-enable them one at a time (restarting Outlook each time) until you find the one that causes the crash. Leave that add-in disabled or check for an update from its developer.
Fix 3: Rebuild the Outlook Database (More Thorough)
If the template reset and add-in disable don’t work, the Outlook database itself may be corrupted. Rebuilding it is safe and preserves your data—it just reindexes and repairs the database file.
- Quit Outlook.
- Hold the Option key and reopen Outlook. Keep holding Option until you see the “Outlook Database Utility” window.
- Select your main profile (usually named “Main Profile”).
- Click Rebuild. Outlook will create a new database and move your old one to the trash (it’s saved as a backup).
- After the rebuild, Outlook opens normally. Test a reply.
Rebuilding can take several minutes for large mailboxes. It does not delete any emails, but it will reset some view settings (like column widths).
Fix 4: Check for Corrupted Signatures and Email Drafts
Sometimes the crash is caused by a specific signature with embedded images or unusual fonts, or by a stuck draft in the Outbox that uses a broken template.
- Signatures: Go to Settings > Signatures. Temporarily remove all signatures (set “No Signature” for new messages and replies/forwards). Try replying. If it works, re-add signatures one by one to find the culprit.
- Outbox drafts: In the folder list, check your Outbox and Drafts folders. Delete any stuck drafts—especially ones that were being composed when a previous crash occurred.
Fix 5: Update Outlook and macOS
Microsoft regularly releases Outlook for Mac updates that fix crash bugs. Apple’s macOS updates can also resolve underlying compatibility issues.
- Update Outlook: Open Outlook, go to Help > Check for Updates (or use the Microsoft AutoUpdate tool). Install any available updates.
- Update macOS: Go to System Settings > General > Software Update. Install pending updates and restart your Mac.
After updating, try replying again. If the crash only started after a recent update, this is the most likely fix.
Frequently Asked Questions
Will resetting the reply template delete my emails?
No. The reply template only stores formatting defaults for replies and forwards. Your emails, contacts, calendars, and tasks remain untouched.
What if I don’t see the ReplyTemplate file?
That’s normal in some versions. If the file doesn’t exist, skip that fix and try disabling add-ins or rebuilding the database. The file is only created once you’ve used reply/forward at least once.
Can I backup my Outlook data before trying these fixes?
Yes. You can export a backup by going to File > Export in Outlook. Choose “Outlook for Mac Data File (.olm)” and save it to your Desktop or an external drive. This is a good safety step before rebuilding the database.
Why does Outlook crash only when I reply to certain emails?
If the crash happens only with specific messages, the email itself may contain malformed HTML or embedded content that triggers a bug. Try viewing the message in plain text (Settings > Reading > “Show messages as plain text”) or ask the sender to resend as plain text.
Is there a way to prevent this from happening again?
Keep Outlook and macOS updated, avoid force-quitting Outlook while a reply is composing, and periodically clear your Outbox of stuck drafts. Also, limit the number of add-ins you keep enabled.
Do these steps work for Microsoft 365 and standalone Outlook?
Yes, the steps apply to both the Microsoft 365 subscription version and the standalone Outlook 2019/2021 for Mac. The file paths and menu names are the same in current versions.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Windows 10 Wi-Fi Not Connecting: Step-by-Step
- Scaling Headless Chrome: A Practical Guide
- Fix Windows Upgrade Error 0x80090011
- Fix Microsoft Store Apps Not Updating
- v0 Alternatives: Which Fits Your Web App Build?9.26 yd³
- Fix Hard Disk Error 0x80071ac3