If you opened a system monitor and found cups-browsed pinning a CPU core, sometimes showing 100%, 200%, or even 300%, the cause is almost always network printer discovery stuck in a loop. The service keeps scanning and re-scanning printers on your network and never settles down. The quickest fix is to stop the service. If you don’t print to shared network printers, you can disable it for good and never think about it again.
Here’s the short version, then the details. Your laptop fan roars, the case gets hot, the battery drains, and one core sits at full load doing nothing useful. Below you’ll find how to confirm it’s cups-browsed, how to stop it in seconds, and how to make the fix permanent without losing your printers.
What cups-browsed does, and why it burns CPU
cups-browsed is a small background service that comes with CUPS, the Linux printing system. Its job is to watch your local network for shared printers and automatically create print queues for them, so a printer just “appears” in your print dialog without you setting it up.
That sounds handy, and often it is. The trouble starts when the discovery process gets caught in a busy loop. Instead of checking for printers every minute or so and then resting, the service checks constantly, hammering one CPU core.
A few things push it into that state:
- A busy network. On an office or campus network with dozens of shared printers, the service can spend many minutes at startup querying every one, then re-querying them over and over.
- A printer that vanishes. If a machine sharing a printer suspends (someone closes a laptop lid), the printer disappears without a clean “goodbye” signal. cups-browsed can fail to recover and spin instead.
- Rapid network signals. When your network manager sends many connection signals per second, such as when you join a new network, cups-browsed can get flooded and stall in a poll loop.
You may see cupsd, the main print daemon, spike alongside it. That’s because cups-browsed keeps sending it add and remove commands for queues, so the two feed each other.
Key point: cups-browsed only causes trouble when there are printers advertised on your network. On a home network with no shared printers, it usually sits quiet. The pain shows up on shared or busy networks.
How to confirm cups-browsed is the culprit
Before you change anything, confirm what’s actually eating the CPU. Open a terminal and check the running process:
top -o %CPU
# or, if you have it installed:
htop
Look for cups-browsed or cupsd near the top of the list. A healthy system shows them at or near 0% most of the time. If one of them sits at 90% or more, or bounces to 100% every 20 to 30 seconds, you’ve found it.
You can also check the service status directly:
sudo systemctl status cups-browsed
That tells you whether the service is running and shows recent log lines. If you want to watch what it’s doing, the debug log is where the repeated printer queries show up, which is the fingerprint of the discovery loop.
One more clue worth checking: the CPU usage in your monitor can read above 100%. Numbers like 200% or 300% are normal on multi-core machines, where 100% means one full core. A cups-browsed process sitting at 200% is using two cores’ worth of work to do nothing but scan for printers, which is exactly the runaway state you’re trying to stop.
If you want to be sure the load tracks your network, watch the process while you connect and disconnect from Wi-Fi. If the spike appears right after you join a network with shared printers and fades when you leave it, you’ve confirmed the cause and can move straight to the fix.
Quick fix: stop it right now
If your fan is screaming and you just want relief, stop the service. This takes effect immediately and does not uninstall anything:
sudo systemctl stop cups-browsed
Give it a moment. The process can take up to a minute to wind down, and the CPU should drop back to normal. One warning: don’t try to kill it with killall. On some versions that makes it use more CPU, not less. Use the systemctl stop command above instead.
Stopping the service is temporary. It will come back the next time you reboot. If that’s all you need for now, you’re done. If you want it to stay gone, keep reading.
Do you actually need cups-browsed?
This is the question that decides your permanent fix, so answer it before you disable anything.
You probably don’t need cups-browsed if:
- You print to a printer connected directly by USB.
- You added your network printer manually and it works.
- You use a modern printer that supports driverless IPP printing, which most printers made in the last several years do, since your system can find those without cups-browsed.
- You don’t print at all on this machine.
You might want to keep it if you rely on printers shared from another computer’s CUPS server, or you’re on a network where printers are advertised the old way and you don’t want to add each one by hand.
For the large majority of home and single-user setups, disabling cups-browsed changes nothing you’ll notice, except a quieter fan. That’s why the fixes below default to turning it off.
If you’re not sure which camp you fall in, try a simple test. Disable the service, reboot, and print the way you normally do. If everything still prints, you didn’t need it. If a network printer stops showing up, you can turn the service back on in one command, so nothing is lost by checking. This test takes two minutes and settles the question for good.
Permanent fix: disable or mask the service
There are two levels here. Pick based on how stubborn the service is on your system.
Disable it (the normal way)
Disabling stops the service now and keeps it from starting at boot:
sudo systemctl stop cups-browsed
sudo systemctl disable cups-browsed
Reboot, and cups-browsed should stay down. On most systems this is all you need. Your existing printers keep working, because disabling only turns off the auto-discovery service, not printing itself.
Mask it (when disable won’t stick)
On some setups the service gets re-enabled by an update or another package, so disable doesn’t hold. Masking is the stronger option. It points the service at nowhere, so nothing can start it, not even another program:
sudo systemctl mask cups-browsed
This is the reliable way to make sure the service stays off. You can still install and use network printers after masking it, since printing runs through cupsd, not cups-browsed. If you ever want the auto-discovery back:
sudo systemctl unmask cups-browsed
sudo systemctl enable –now cups-browsed
Remove it entirely
If you’re certain you’ll never want it, you can uninstall the package. On Debian, Ubuntu, and Mint:
sudo apt purge cups-browsed
# then reboot
Removing it is clean and easily reversed later with a reinstall. Masking is usually enough, though, and leaves the door open without any CPU cost.
Rule of thumb: disable first. If it won’t stay off, mask it. Only purge if you’re sure you’ll never need network printer auto-discovery on this machine.
Keep network printers but tame the CPU
Maybe you actually rely on auto-discovered printers and can’t just switch the service off. You can keep cups-browsed running but slow its scanning right down by editing its config file, /etc/cups/cups-browsed.conf. Open it with a text editor as root:
sudo nano /etc/cups/cups-browsed.conf
A few directives control how hard it works. The BrowseInterval directive sets the seconds between browsing cycles. Raising it means fewer scans and less CPU. The default is 60 seconds; you can push it higher:
BrowseInterval 300
If the trouble comes from the old CUPS browsing protocol rather than modern discovery, you can limit which protocols the service listens for with BrowseRemoteProtocols. Setting it to only dnssd (the modern method) drops the legacy CUPS protocol that has caused both CPU and security problems:
BrowseRemoteProtocols dnssd
Save the file, then restart the service so your changes take effect:
sudo systemctl restart cups-browsed
The full list of directives is documented in the cups-browsed.conf manual page, and the OpenPrinting cups-browsed README explains how the service talks to your local CUPS daemon. Those are the right places to check if you need finer control.
The security reason to turn it off
There’s a second reason to disable cups-browsed that has nothing to do with CPU. In late 2024, a group of vulnerabilities in the CUPS printing stack, tracked as CVE-2024-47176 and related IDs, showed that cups-browsed listening on the network could let an attacker advertise a fake printer and, if you then printed to it, run their code on your machine.
The practical advice from security teams matched the fix for high CPU: if you don’t need network printer discovery, turn the service off. The same two commands cover both problems at once:
sudo systemctl stop cups-browsed
sudo systemctl disable cups-browsed
The upstream response also involved dropping the risky legacy CUPS browsing protocol from the defaults, which is why setting BrowseRemoteProtocols dnssd shrinks your exposure if you keep the service running. Keeping your system updated matters too, since distributions shipped patched packages after the disclosure. So the CPU fix and the security fix point the same direction: unless you specifically need it, cups-browsed is better off.
Frequently asked questions
Will disabling cups-browsed stop me from printing?
No. Printing runs through cupsd, not cups-browsed. Disabling it only turns off automatic discovery of shared network printers. Printers you added manually, USB printers, and modern IPP printers all keep working.
Why does cupsd show high CPU too, not just cups-browsed?
They feed each other. cups-browsed keeps sending cupsd commands to add and remove printer queues during its scanning loop, so cupsd spikes alongside it. Stopping cups-browsed usually calms cupsd down as well.
Is it safe to mask cups-browsed?
Yes. Masking just prevents the service from starting. Your printing setup stays intact, and you can reverse it anytime with systemctl unmask. Masking is the reliable choice when plain disable keeps getting undone by updates.
Why does the CPU spike only at my office and not at home?
cups-browsed only works hard when printers are advertised on the network. A busy office or campus network with many shared printers triggers heavy scanning, while a home network with none leaves the service idle.
Do I need cups-browsed for a modern USB or Wi-Fi printer?
Usually not. Directly connected USB printers and most printers made in the last several years support driverless IPP printing, which your system finds without cups-browsed. You can safely disable it and add your printer manually if needed.
Conclusion
High CPU from cups-browsed is a printer discovery loop, not a broken system. Stop the service for instant relief, then disable or mask it to keep it off, or raise BrowseInterval and limit protocols if you need auto-discovered printers. A good result looks simple: cups-browsed and cupsd sitting near 0% CPU, a quiet fan, and printing that still works. For most machines, turning the service off costs you nothing and fixes both the heat and a real security risk.
Recommended Articles:
Intel System Usage Report High CPU: What It Is and How to Stop It
Is CS2 CPU or GPU Intensive? What Really Limits Your FPS
CPU Load Line Calibration: What It Does and What to Set It To
Max CPU Boost Clock Override: What It Does and When It Helps
IIS Worker Process High CPU: How to Find the Cause and Fix It
