Manual Removal Prerequisites

Uninstalling Office on macOS requires more than moving the application to the Trash. You must manually locate and delete specific folders within the Library directory—specifically under Containers and Group Containers—to ensure all license credentials, cached data, and preferences are fully removed from your system environment.

  • Drag the Office application to the Trash, then empty it.
  • Delete files in /Library/Containers/ related to Microsoft.
  • Remove items in /Library/Group Containers/ for Office.
  • Restart your Mac to finalize the removal process.

System Preparation

Before initiating the deletion, quit all active Microsoft applications. Verify no background services are running by opening Activity Monitor and filtering for "Microsoft" or "Office" processes. Force quit any instances found to prevent locked file errors during the deletion process.

Use the keyboard shortcut Command + Shift + G in Finder to open the Go to Folder dialog; this allows you to paste directory paths directly rather than navigating through hidden subfolders manually.

Verifying System State Post-Termination

Before you commit to deleting directories, confirm that no invisible processes are holding file handles open. Even after you force quit applications, a lingering helper process might remain attached to the system kernel. Use the Terminal application to execute the command line query for active Microsoft tasks if the Activity Monitor interface feels too sluggish for your current needs. Observing the process list directly ensures you avoid the frustration of encountering errors that claim a file is in use during your manual cleanup. You gain peace of mind knowing the environment is completely static.

Take a moment to inspect your Dock and login items before finalizing the manual purge of the application. Sometimes, Office utilities are set to launch at login, which complicates the removal process by restarting the very services you intend to kill. Check your System Settings under General and then Login Items to verify that no remnant Microsoft auto-launchers are present. Disabling these at the source prevents accidental service reactivation while you are in the middle of navigating your file system. Clearing these entries first creates a clean slate for the subsequent file deletions.

Targeting Application Containers

After the main application is moved to the Trash, the next step involves cleaning the sandbox environments where Office stores user-specific data. macOS uses container folders to isolate application data, which persist even after the main binary is deleted.

Locating Container Folders

Navigate to ~/Library/Containers. Search for any folder starting with "com.microsoft". These directories contain cached data, temporary files, and local settings. Select these folders and move them to the Library path designated for the Trash. Be precise; deleting unrelated folders can impact system stability or other installed software.

Distinguishing Sandboxed Data Directories

Navigating the ~/Library/Containers directory requires a keen eye because the folder naming convention often involves complex, randomized character strings following the base identifier. You might notice folders such as com.microsoft.Word or com.microsoft.Excel, but others will appear as opaque identifiers like com.microsoft.Office.standalone. Ensuring you target the correct containers prevents the collateral deletion of data from other applications that might share a naming prefix. A simple way to verify a folder is to inspect the folder creation date, which usually corresponds to your initial software installation time. Take caution to select only those containers specifically associated with the version you are uninstalling.

When moving these items to the Trash, watch for potential permission prompts that might interrupt your workflow. Because these containers are sandboxed, your user account holds full ownership, but macOS occasionally enforces strict access controls on the underlying plist files. If you find yourself unable to move a specific container, do not attempt to force the deletion via administrative override immediately. Instead, verify if any child process is still actively writing to the logs within that container path. A quick refresh of your Finder window usually clears the temporary block, allowing the removal to proceed as expected.

Clearing Group Containers

Shared configuration data often resides in a separate location from standard container files. This directory holds data shared across multiple Office applications, such as license tokens and shared integration scripts.

Identifying Shared Data

Access ~/Library/Group Containers. You will find specific folders prefixed with identifiers like UBF8T346G9. These contain critical shared assets. Once identified, remove these folders to ensure no residual configuration persists.

A clean uninstall is defined not by what you move to the trash, but by the dormant configuration files left behind in the hidden root directories.
Ensure you have administrative access to perform these Group Containers deletions, as macOS may prompt for your password.

Managing UBF8T346G9 Shared Data

The directory path containing UBF8T346G9 is the primary repository for shared cross-application metadata, which often acts as a bridge between separate Office programs. Deleting this specific group container is necessary because it holds the authentication tokens that allow your Outlook profile to communicate with your Word templates. If you skip this folder, the system might retain a ghost of your previous installation that complicates a later clean install. Always verify the contents of this folder by enabling column view in Finder, which allows you to inspect sub-directories without needing to open every individual item. This visual verification saves significant time when handling large numbers of similar configuration files.

Consider that these shared containers often grow in size significantly over time due to persistent log files and crash reports. If you have been using Office for an extended duration, checking the storage usage of this specific group folder before moving it to the Trash provides a clear indicator of how much space you are reclaiming. You may find that cache files account for the majority of the footprint, which are irrelevant once the suite is gone. Deleting these shared assets ensures that no residual integration scripts remain to trigger errors in other productivity software. It effectively resets the shared subsystem environment to a pristine state.

Removing Licensing Credentials

Removing the application binaries does not automatically purge your Office license. If you intend to install a different version or a fresh copy, existing license artifacts can cause activation conflicts.

License Reset

Search your system for the Microsoft License Removal Tool if you prefer an automated approach to this specific task. If performing this manually, look for files containing "Office" and "License" within the /Library/PrivilegedHelperTools directory. Deleting the wrong license file can disrupt other installed services, so verify the file path before confirmation.

Auditing License Artifacts

Locating license files requires precision because they are often buried within deep system hierarchies, not just the user-specific folders. The PrivilegedHelperTools directory is a common place for these artifacts to reside, but keep in mind that installer packages might place related activation keys in protected system libraries. You need to be confident in your search parameters, as file names often appear generic or obfuscated to prevent tampering. If you are uncertain about a specific file, check the 'Get Info' pane in Finder to review the creator and ownership details. This step confirms the file's association with Microsoft before you initiate a permanent deletion.

Another vital location to monitor for license remnants is the Application Support folder inside the root Library directory. While most user data stays within your home folder, activation-related configuration often lives at the system level to ensure consistency across all user profiles. If your machine is shared, failing to clear these root-level files can cause persistent activation prompts for other users even after you have cleared your own account. Carefully inspect the contents of these folders, focusing on filenames that include 'Office' or 'Licensing'. Deleting only what is necessary preserves the integrity of other system software that may rely on different licensing protocols.

Cleaning Keychain Entries

The macOS Keychain stores your stored Office credentials, which include network paths, email login tokens, and cloud synchronization data. These entries remain even after the software is gone.

Managing Keychain Access

Open the Keychain Access utility from your Utilities folder. Perform a search for "Office" or "Microsoft". Right-click and delete each item found. This step is critical for a Keychain Access sweep, preventing the system from auto-filling old or potentially corrupted credentials when you next install or use similar services.

Purging Residual Keychain Certificates

The Keychain Access utility functions as a persistent memory for your system, holding onto credentials even after the source application is eradicated. Searching for the specific keyword 'Microsoft' is useful, but do not stop there, as some entries might be tagged under names like 'MSFT' or specific service descriptors such as 'Exchange' or 'OneDrive'. Reviewing the 'Kind' column in the utility helps you isolate the items that are actually related to the Office suite versus other authentication tokens for your email or browser. Selecting these entries requires careful attention to avoid deleting unrelated network passwords that you might need for other system functions.

Once you have identified the appropriate entries, right-clicking and selecting the delete option will trigger a confirmation dialog. Proceeding with this action permanently destroys the stored credentials, so ensure you have any necessary account recovery information saved elsewhere if you anticipate needing it later. You will notice that once these entries are cleared, your system no longer attempts to authenticate those previous sessions. This cleanup prevents the frustrating occurrence where a fresh install of the suite immediately inherits old, potentially broken login tokens. It effectively forces a complete, fresh handshake between your user account and the server services.

Deleting Preference Lists

Application preferences are stored as .plist files. These files dictate settings like window position, toolbar customization, and recent file history, which can become corrupted over time.

Managing Preferences

Go to ~/Library/Preferences. Look for files starting with "com.microsoft". These are the preference list files that dictate how the application behaves on your user account. Removing these forces the application to create factory-default configuration files upon any future reinstallation.

Isolating Preference Configuration Conflicts

Preference list files, identified by the .plist extension, are the primary cause of erratic software behavior when you perform a reinstall after an incomplete removal. These files record your unique interface choices, such as ribbon customizations or dictionary settings, and they often persist in the Library folder indefinitely. To target these correctly, look within ~/Library/Preferences for files that begin with com.microsoft and follow with the application name. If you find a file that does not correlate to your current installation, it is usually safe to treat it as legacy debris. Deleting these files returns the application to its factory-default state, eliminating strange layout bugs.

Be aware that some applications create auxiliary preference files located in specialized sub-folders rather than the main Preferences directory. If you still experience issues with a newly installed version, check the ~/Library/Preferences/ByHost folder, where system-specific preferences sometimes migrate. This requires searching for the same com.microsoft prefix to catch hidden overrides that might cause persistent crashes or initialization errors. Diligently clearing these secondary locations ensures that the application has absolutely no prior state to load upon the first launch. A truly clean environment allows the software to generate new, healthy configuration files from scratch.

System Integrity Verification

Once all folders and files are moved to the Trash, empty it securely. A system restart is required to clear the file system cache and ensure the OS registers that the application components are no longer present.

Post-Removal Check

After the reboot, open Activity Monitor again to confirm no Microsoft processes are active. If you notice persistent processes, check the LaunchAgents and LaunchDaemons folders in your Library to ensure no startup items remain that were designed to launch Office components automatically at login.

Verifying System-Wide Component Removal

After the Trash is emptied, the file system might still cache references to the deleted applications, which is why a restart is non-negotiable. This action forces the macOS kernel to rebuild the service cache and acknowledge that those previously active paths are now empty. Monitor the system behavior immediately following the reboot to see if any residual error messages pop up, which would indicate a missing dependency. If the machine boots cleanly without any notification dialogs related to Microsoft, you have successfully detached the software from the primary system environment. It is the most reliable way to confirm that no background processes are still reaching for missing files.

Inspect the LaunchAgents and LaunchDaemons folders in the root Library after your restart to be absolutely certain no hidden tasks survived. While the user-level Library gets a lot of attention, these root folders can hold system-wide tasks that trigger Microsoft-related updates or background synchronization. If you find files ending in .plist that reference the suite, move them out of the folder to test their necessity, or delete them if you are confident they are redundant. This layer of verification captures those last few items that an uninstaller might miss. You are left with a system that is genuinely free of the application's influence.

Final Considerations

The complexity of removing Office often stems from the interconnected nature of its components. If you are preparing the machine for a new user or addressing a severe software conflict, ensure you have accounted for all user profiles on the machine.

Multi-User Impact

If your Mac has multiple user accounts, the Library folders mentioned above are unique to each user. You must perform these steps while logged into each account to ensure background processes are completely eradicated from the system. If you only perform this on the administrator account, residual data will remain for other users.

Addressing Cross-Account Data Residue

In environments where multiple users share a single machine, residual configuration files in one account can potentially interfere with the system-wide operation of the software. Each user account maintains its own unique Library folder, meaning that the removal process must be replicated in every active profile. Simply clearing the administrator account leaves behind cached containers and preference files in every other standard account on the device. Failing to address these individual libraries means that if another user logs in, they may encounter corrupted configuration files that could trigger system instability or permission conflicts. It is essential to treat every user directory as a distinct entity that requires the same rigorous cleanup protocol.

Verify your work by logging into each secondary account and performing the check for the same directories mentioned in previous sections. You might find that one user has significantly more residual data than another, depending on their specific interaction with the software. Consistent application of these steps across all accounts eliminates the possibility of hidden background services persisting for other users. This approach is the only way to guarantee a complete and uniform eradication of the software from the machine. Once you have cleared every user profile, you can be certain that no hidden data remains to influence the system environment or future software installations.