Code42 CrashPlan Background Service Explained

Updated 14 November 2026 · Standard formula, shown below

The Code42 CrashPlan background service is a core system process that runs continuously on your computer to back up files to the cloud and local destinations. It handles scheduled backups, real-time file monitoring, and communication with Code42 servers, and it is the component you may see running as CrashPlanService or Code42.service in your task manager. This article explains what the service does, why it might use high CPU or memory, and how to manage it effectively.

What Is the CrashPlan Background Service?

CrashPlan (now part of Code42) is a backup application that protects files by copying them to a cloud destination or to another computer you control. The background service is the engine that performs this work. Unlike the CrashPlan desktop app, which provides a user interface for settings and restore operations, the service runs even when you are not logged in or when the app window is closed. This ensures backups continue in the background without requiring user interaction.

The service is installed as a system daemon (on macOS and Linux) or a Windows service (on Windows). On Windows, it appears as Code42.service or CrashPlanService in Services. On macOS, it is a launch daemon named com.code42.service. The service is responsible for:

Scanning your file system for changes and new files
Compressing and encrypting data before transmission
Uploading backup data to Code42 cloud servers or a local destination
Managing bandwidth throttling and scheduling
Handling backup verification and integrity checks

How the Background Service Works

When you install CrashPlan, the background service registers itself to start automatically at boot. It reads configuration files (usually in /Library/Application Support/CrashPlan/ on macOS or C:\ProgramData\CrashPlan\ on Windows) to determine which folders to back up, how often, and to which destination. The service then performs an initial full backup, after which it switches to incremental backups—only uploading changed or new files.

The service uses a watchdog mechanism to detect file changes in real time. On macOS, it uses the FSEvents API; on Windows, it uses the ReadDirectoryChangesW API. When a change is detected, the service queues the file for backup. It also runs scheduled full backups (often weekly) to re-verify the integrity of the backup archive.

Data is compressed (using a standard zip algorithm) and encrypted with AES-256 before transmission. The service also handles deduplication, meaning it only uploads unique blocks of data, which reduces bandwidth usage.

Why Does It Use High CPU or Memory?

It is common for users to notice the CrashPlan background service consuming significant CPU or memory, especially during the initial backup or after a large number of file changes. The service is doing CPU-intensive work: compressing, encrypting, and hashing files. Memory usage can also spike because the service keeps a file index in RAM to track what has been backed up.

Typical causes of high resource usage include:

Initial backup: The first backup can take days and will use high CPU.
Large file changes: If you move or modify many files at once (e.g., a photo library import), the service will process them all.
File index corruption: If the backup database becomes corrupted, the service may re-scan the entire drive, causing high CPU.
Multiple destinations: Backing up to both cloud and a local drive doubles the work.

To reduce CPU usage, you can pause backups temporarily or adjust the backup window in the app settings. However, note that the service will continue to monitor file changes even when paused, so CPU usage may not drop to zero.

How to Manage the Background Service

You can control the service through the CrashPlan app or through your operating system’s service manager. Here are the common actions:

Pause backups: Open the CrashPlan app, go to the backup status, and click “Pause.” This stops uploads but keeps the service running.
Stop the service: On Windows, open Services (Win+R, type services.msc), find Code42.service, and stop it. On macOS, run sudo launchctl unload /Library/LaunchDaemons/com.code42.service.plist in Terminal.
Restart the service: This is often the first troubleshooting step. Restart the service to resolve stuck backups or high CPU.
Change backup frequency: In the app, you can set a backup window (e.g., only at night) to avoid resource contention.

Common Problems and Troubleshooting

Users frequently encounter issues with the background service. Here are the most common ones and how to address them:

Service not running: If backups stop, check that the service is running. On Windows, look for Code42.service; on macOS, use ps aux | grep Code42. If it is not running, start it manually or reboot.
High CPU after a system update: Sometimes a system update triggers a full re-scan. Let it finish; if it persists, restart the service.
Backup stuck at “Preparing”: The service may be building the file index. Wait a few hours; if it remains stuck, delete the backup cache (in Library/Application Support/CrashPlan on macOS) and restart the service—this forces a fresh index but does not delete your backup.
Port conflicts: The service uses port 443 for cloud communication. If another program uses it, backups fail. Check your firewall settings.

Security and Privacy Considerations

Because the background service runs with elevated privileges (as a system service), it has broad access to your files. This is necessary for backing up all user data. However, it also means that if an attacker gains control of the service, they could read your files. Code42 encrypts data in transit and at rest, but the encryption keys are stored locally. To protect your data:

Use a strong password for your Code42 account.
Enable two-factor authentication if available.
Keep your operating system and CrashPlan software updated.
If you no longer use CrashPlan, uninstall it completely to remove the service.

Note that the service runs as the root user on macOS and Linux, and as SYSTEM on Windows. This is required to read all user files. If you are concerned about privacy, you can restrict which folders are backed up in the app settings.

Alternatives to CrashPlan

If you find the background service too resource-intensive or you are looking for a different backup solution, consider these alternatives:

Backblaze: A cloud backup service with a similar continuous backup model, but its background service is often lighter.
Carbonite: Another cloud backup service with a simpler interface.
Local backup tools: For local backups, you can use built-in tools like Time Machine (macOS) or File History (Windows), which do not run a separate background service—they rely on system features.
Open-source options: Tools like Restic or Duplicati can be scheduled to run periodically, not continuously, which reduces resource usage.

When choosing a backup solution, consider your needs: continuous vs. scheduled backups, cloud vs. local, and resource usage. CrashPlan’s strength is its flexible destination options (cloud, another computer, or external drive) and unlimited backup plans, but its background service can be heavy.

Frequently Asked Questions

Can I disable the CrashPlan background service?

Yes, you can stop or disable the service, but doing so will stop all backups. To disable it permanently, you would need to uninstall the app or change the service startup type to “Disabled” on Windows, or unload the launch daemon on macOS. However, this is not recommended unless you are using a different backup solution.

Why does CrashPlan run even when I close the app?

The background service is separate from the app. Closing the app window only hides the interface; the service continues to run to ensure backups happen. This is by design—backups should not depend on you keeping the app open.

How do I check if the CrashPlan service is running?

On Windows, open Task Manager (Ctrl+Shift+Esc) and look for Code42.service or CrashPlanService under the Services tab. On macOS, open Activity Monitor and search for Code42. You can also use the command line: ps aux | grep -i code42 on macOS/Linux, or sc query Code42.service on Windows.

Why is CrashPlan using 100% CPU?

This usually happens during the initial backup or after a large number of file changes. It can also happen if the backup database is corrupted, causing a re-scan. Try restarting the service; if the problem persists, contact Code42 support or consider reducing the backup set.

Does CrashPlan work if I am not logged in?

Yes, because the background service runs as a system service, it starts at boot and does not require a user login. This ensures backups continue even if you are at the login screen.

How do I uninstall CrashPlan completely?

Use the uninstaller provided by Code42, or manually remove the application and the service. On Windows, run msiexec /x {product code} or use Settings > Apps. On macOS, drag the app to Trash and run sudo launchctl unload /Library/LaunchDaemons/com.code42.service.plist and delete the plist file. Also delete the data folders in /Library/Application Support/CrashPlan and ~/Library/Application Support/CrashPlan.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.