CrashPlan: Default Exclusions
Purpose
This page explains CrashPlan’s default (global) file exclusions: how they are evaluated, what they exclude on each platform, and the behaviors administrators should know about when supporting users or changing exclusions.
Reference sources
Resource | Link |
|---|---|
Getting started with UTBackup (KB0020242) | |
Exclusion list (CrashPlan-Labs/Tools on GitHub) | |
Raw file (for copying into the console or API) | https://github.com/CrashPlan-Labs/Tools/raw/refs/heads/main/exclusions.txt |
Change history for the list | |
CrashPlan: Understanding default file exclusions | |
CrashPlan: Include and exclude files for backup (console and API) | |
CrashPlan: Exclude files using file type and regex |
|
CrashPlan: Reference for including and excluding files |
|
CrashPlan updates the list from time to time. Check the change history link before relying on this page’s interpretation.
How exclusions are evaluated
Behavior | Detail |
|---|---|
Matching | Each regular expression is matched against the file’s full absolute path, not just the file name. |
Path separator | CrashPlan uses forward slashes on every platform. Windows paths are evaluated as |
Processing order | Inclusions are processed first, then exclusions. A file that matches both is excluded. |
Case sensitivity | Expressions that start with |
Platform scope | Lines prefixed with |
Restricted characters |
|
API updates | The |
Applying changes | After changing exclusions, run Scan for file changes from Backup Set Settings in the CrashPlan app so the change is picked up. |
What the list excludes
Scope | Main categories excluded |
|---|---|
All platforms | Temp and partial files ( |
Windows |
|
macOS |
|
Linux |
|
AppData and ~/Library allowlists
On Windows, everything under C:/Users/<user>/AppData/ is excluded except:
Firefox bookmarks and history (
places.sqlite,favicons.sqlite)Edge and Chrome
BookmarksandFaviconsOutlook signatures (
Roaming/Microsoft/Signatures) andLocal/Microsoft/Outlook/RoamCacheSticky Notes data
OneNote 16.0 folder (including local backups)
Office unsaved files (
Local/Microsoft/Office/UnsavedFiles)
On macOS, everything under ~/Library/ is excluded except:
Safari, Chrome, and Firefox bookmarks and history
Stickies
Office AutoRecovery
~/Library/CloudStorage(OneDrive, Google Drive, and Dropbox file-provider locations)Apple Notes
iCloud Drive (
Mobile Documents/com~apple~CloudDocs)
Behaviors to be aware of
These items are our reading of the expressions as written. They are not CrashPlan statements. Test with a sample file before telling a user a file is or isn’t protected.
Pattern behavior | Practical effect |
|---|---|
Folders named | A user folder such as |
| Any file whose name ends in those letters is excluded. Examples: extensionless |
| Application settings and SQLite databases stored in user folders are skipped. |
Drive-root Windows rules use |
|
| PST files in |
Outlook custom dictionary entry is | This appears to allow only the folder itself, not the files inside it. Custom dictionaries may not actually be backed up. Verify by testing. |
macOS line with | On Macs, |
macOS | Apple Mail local mail stores, Messages history, and most app data are not backed up. |
macOS VS Code entry is | This produces |
| Uncommitted changes in a repo are backed up, but local commit history and unpushed branches are not. |
VM disk images and sparse images are excluded | Developer or lab VMs (Hyper-V, VMware, VirtualBox, Parallels, QEMU) are not protected by CrashPlan. |
Linux | If CrashPlan protects Linux servers, data stored under |
Last line excludes CrashPlan archive file structures | This prevents backing up CrashPlan’s own archives, for example on local or external backup destinations. |
Troubleshooting: “Why isn’t this file backing up?”
Convert the path. Rewrite the full path using forward slashes (for example,
C:/Users/jdoe/AppData/Local/...).Check it against the recommended list. Pay particular attention to the “anywhere in the path” folder rules and the AppData and Library allowlists.
Check our deviations. Review the organization and device exclusions in the CrashPlan console, and any user-level exclusions in the CrashPlan app if users are allowed to edit them.
Check the file selection. Confirm the file is under an included path. Remember that a file matching both an inclusion and an exclusion is excluded.
Rescan after any change. Run Scan for file changes on the device and confirm the file appears in the backup.