boxsync-daemon

Box Sync Daemon

CPU Usage

N/A

Memory

N/A

Location

N/A

Publisher

N/A

Notes

This document provides a focused reference for boxsync-daemon on Windows, macOS, and Linux, detailing safety, operation, common issues, and verification steps. Always install from Box's official site and maintain up-to-date software to minimize risk and ensure reliable sync.

What is boxsync-daemon?

boxsync-daemon is the persistent background service that maintains the connection between your local file system and Box cloud storage. It monitors configured sync folders, queues file changes, negotiates updates with the Box service, and applies local and remote edits. The daemon ensures real-time sync, scheduled rechecks, and robust conflict handling so that your Box Drive mirrors your local workflow.

The daemon runs as a background process in the OS, listening for filesystem events on registered sync roots, using the Box API over TLS to upload new/modified files and download remote changes. It maintains a local index database, handles retries, and respects selective sync settings to minimize bandwidth.

Is boxsync-daemon Safe?

boxsync-daemon is the legitimate background service used by Box to sync your local files with Box cloud storage. It runs under system privileges only as part of the Box Sync installation, authenticates with Box credentials, uses TLS for data transfer, and stores a local index in a dedicated directory. When installed from Box's official installers, the binary is digitally signed, and common security controls apply to protect its operation.

Is boxsync-daemon a Virus?

No, boxsync-daemon is not a virus when installed from Box's official packages. It is a signed, authenticated component of Box Sync that runs in the background to manage file transfers and conflict resolution. If you notice unexpected behavior, verify the installation source, check digital signatures, scan for malware, and compare file hashes against Box's published checksums to rule out tampering.

How to Verify Legitimacy

Check File Location: Windows: C:\\Program Files\\Box\\Box Sync\\boxsync-daemon.exe; macOS: /Applications/Box Sync.app/Contents/MacOS/boxsync-daemon; Linux: /usr/bin/boxsync-daemon. Ensure the file resides in the Box installation folder.
Verify Digital Signature: On Windows: right-click boxsync-daemon.exe > Properties > Digital Signatures; signatory should be Box. On macOS: spctl -a -vv /Applications/Box Sync.app; verify result is accepted.
Check File Hash: Compute SHA-256 of the executable: e.g., certutil -hashfile 'C:\\Program Files\\Box\\Box Sync\\boxsync-daemon.exe' SHA256 and compare to Box's published hash.
Scan for Malware: Run a full system antivirus/malware scan or use a reputable scanner to ensure the binary has not been modified by malware.

Red Flags: Unsigned builds, executables located outside the Box Sync folders, unexpected new startup entries, or changes in behavior without a corresponding Box Sync update are red flags. If you see multiple copies of the daemon running, suspicious network activity, or altered config files, investigate immediately.

Why is it Running?

Reasons it's running:

Active sync of folder changes: The daemon watches configured roots and starts transfers as soon as a file is created, modified, or renamed, keeping your Box cloud in near real-time sync.
Post-install initial index: During first run or after a reinstall, the daemon builds its local index of files and folders to determine what needs uploading or downloading.
Network reconnect and conflict resolution: When the network re-establishes after disruption, the daemon reconciles local changes with remote versions, which may trigger transfers and conflict handling.
Selective sync and cache maintenance: If you use selective sync, the daemon may scan and prune caches to reflect the chosen folders, which can cause brief spikes in resource use.
Routine health checks and retries: The daemon periodically validates connectivity, credentials, and transfer queues, retrying failed transfers with backoff to ensure eventual consistency.

Can I disable boxsync-daemon?

Common Problems

Common Causes & Solutions

: Check for a large number of local file changes, exclude non-synced directories, and restart the service after ensuring the latest Box Sync version is installed.
: Limit concurrent transfers in settings, disable persistent thumbnails for synced folders, and verify that antivirus isn't scanning Box Sync temp folders too aggressively.
: Resolve conflicting edits by choosing the most recent change, enable conflict resolution settings to keep both versions, and avoid editing the same file from multiple devices simultaneously.
: Check network projection, verify credentials, refresh tokens, and ensure Box Sync endpoints are reachable. Re-authenticate if necessary.
: Verify the local sync root exists, reselect the folder in Box Sync preferences, and ensure the destination path is not removed or mounted incorrectly.
: Restart the daemon, clear the transfer queue, and ensure the Box service status is green. Check for pending items in iCloud/Dropbox that might hold locks.

Frequently Asked Questions

What is the boxsync-daemon and why is it running on my computer?

It is the background process that keeps your local folders synchronized with Box Cloud, monitoring changes and uploading or downloading updates as configured.

Is boxsync-daemon safe to run?

Yes, when installed from Box's official sources, it is digitally signed and uses TLS for transfers. Verify the installer source to avoid counterfeit software.

Can I disable boxsync-daemon and still use Box?

Disabling the daemon pauses synchronization. You can stop it temporarily via the OS service manager, but Box Drive features relying on sync will be unavailable until re-enabled.

Why does boxsync-daemon use so much CPU?

Initial indexing or many small file changes can spike CPU. After the initial sync, activity should stabilize; check for large folders or exclusions that improve performance.

How do I verify boxsync-daemon's integrity?

Check file location, verify digital signature, compare SHA-256 hashes to Box's published values, and run a malware scan if you suspect tampering.

What should I do if Box Sync isn't syncing after an update?

Restart the daemon, re-authenticate if needed, and verify that network access is available and the correct sync roots are configured.