Background Work is how Roon keeps all of this in sync. It’s a broad set of tasks that maintain, enrich, and organize your library: unifying local music, network storage, and streaming services into a single, coherent view.

When new music is added to your library, Roon immediately identifies and analyzes each file to understand its audio characteristics and contextualize it in your library. Over time, Roon periodically revisits every track in your library, to update and improve metadata, fill in missing artwork, and identify any previously unidentified tracks. Roon also re-scans your network storage locations to check for any new additions.

This background work ensures your library stays accurate, up to date, and richly connected to the global music ecosystem. It’s essential for refining the relationships between track files, musical objects, and the rich metadata that power the Roon experience.

Audio analysis has its own setting, separate from this one. Roon analyzes files on demand as soon as you add or play them, and that isn’t affected by your Background Work schedule. The sweep that analyzes the rest of your library is controlled by Background Audio Analysis, further up the same Settings → Library page. See Audio Analysis in Roon for the full picture.

Why Schedule Background Work?

Over time, we’ve heard from users who want more control over when Background Work happens, so Roon can work around each user’s listening habits and usage patterns.

Our goal is to ensure Roon users have clear, predictable control over when library maintenance occurs, preserving their server’s resources when they are actively browsing, listening, or maintaining their collections. This lets users offload background work to a time of day when they aren’t using Roon.

Some users only run their Roon Server while actively listening, or they power their server on and off throughout the day. If it isn’t practical to schedule Background Work around regular downtime, we recommend disabling scheduling.

How Do I Set My Background Work Schedule?

By default, Roon runs Background Work each night between 1 AM and 5 AM. You can move that window to whatever time suits your routine.

1. Go to Settings → Library and scroll to Background Work. Your current window is listed there, for example, “Current schedule: 1 AM-5 AM.”

2. Click Change.

3. Set your START TIME and END TIME. The window must be at least 4 hours long.

4. Click Save.

If a schedule doesn’t fit how you use Roon, you can turn it off. In the same dialog, check Disable schedule (run continuously) and click Save. Roon then performs maintenance throughout the day, as it did before scheduling was introduced.

Scheduling by day of the week, and limiting how many CPU cores Background Work uses, are not yet available. If either would help your setup, please share it in Feature Suggestions.

Will Scheduling Background Work Slow Down My Imports and Edits?

When a user is growing, curating, or editing their library, we don’t consider it “background work”.

If you import local files to Roon or make edits to your library, Roon will continue to retrieve metadata and reflect changes right away, and Roon will also continue to check your streaming services periodically for new additions.

How Will Scheduling Affect My Network Storage?

Network storage devices don’t always report file changes to Roon in real time, so Roon allows users to set an Automatic Re-scan Interval (more details here).

Starting with Roon 2.61, Roon by default re-scans network storage locations during the user-scheduled Background Work window, using the configured interval. Roon will also automatically re-scan network storage on startup.

Users who prefer continuous re-scanning throughout the day can disable scheduling by going to Settings → Storage, clicking the three dots (…), and toggling off Schedule.

What Happens if Roon Server is Offline During the Scheduled Time?

A schedule only runs if your Roon Server is awake for it. If your server is asleep, powered down, or disconnected during the window, that night’s maintenance is skipped.

When Background Work hasn’t completed in a week, Roon tells you twice. A warning appears in Settings → Library, directly under Background Work, reading “Background work hasn’t run in 7+ days! Consider adjusting your schedule.” You’ll also see a warning pop-up in Roon, which you can snooze.

Seeing this warning usually means your schedule and your server’s uptime don’t overlap. A laptop that sleeps at midnight will never reach a 1 AM window. Please either move the window to a time your machine is reliably awake and on power, or disable the schedule so maintenance runs whenever your server is on.

For users hosting Roon Server on laptops, we recommend scheduling background work for a time when your computer is awake and connected to power.

We strongly recommend Roon is regularly able to run background work at least once a week. If your server won’t be on overnight, we recommend disabling the schedule instead, using the steps above.