If you’ve ever opened your system monitor and noticed snapd quietly eating up your CPU or RAM, you’re not alone. Many Linux users—especially on Ubuntu and Ubuntu-based distributions—eventually run into this issue and wonder what’s going on behind the scenes.
In this guide, we’ll break down how to fix Snapd consuming high CPU / RAM, explain why it happens, and walk through practical, proven solutions you can apply right away. Whether you want to optimize Snap, limit its behavior, or remove it completely, this article covers everything in one place—without fluff or repeated advice.
What Is Snapd and Why Does It Matter?
Before fixing the problem, it helps to understand what Snapd actually does.
Snapd is the background service that manages Snap packages. Snaps are containerized applications designed to run consistently across different Linux distributions. They bundle dependencies, auto-update in the background, and offer better isolation than traditional .deb packages.
Sounds good in theory—but in practice, Snapd can sometimes become resource-hungry.
Symptoms of Snapd Consuming High CPU or RAM
You might be dealing with Snapd resource issues if you notice:
- CPU usage spiking to 20–100% due to
snapd - High RAM usage even when no Snap apps are running
- Laptop fans running constantly
- System slowdowns or lag
snapd,snapd.seeded, orsnapd-desktop-integrationappearing frequently in system monitor- Disk activity spikes every few hours
If these symptoms sound familiar, it’s time to dig deeper.
Why Is Snapd Consuming High CPU or Memory?
Understanding the root cause makes fixing the problem much easier. Here are the most common reasons Snapd consumes high CPU / RAM.
Automatic Background Updates
Snap packages update automatically by default. While convenient, these background updates can:
- Consume CPU during download and installation
- Use RAM while rebuilding application images
- Trigger disk I/O spikes
On slower systems or older hardware, this is often the biggest culprit.
Snap Package Indexing and Refresh Tasks
Snapd periodically performs:
- Metadata refresh
- Security checks
- Dependency validation
These tasks can cause short but intense CPU spikes, especially when multiple Snap apps are installed.
Corrupted or Stuck Snap Processes
Sometimes Snapd gets stuck in a loop due to:
- Interrupted updates
- Network failures
- Broken Snap packages
This can lead to constant CPU usage without any visible activity.
Heavy Snap Applications
Some applications packaged as Snaps are simply heavier than their .deb or Flatpak counterparts. Browsers like:
- Firefox (Snap version)
- Chromium
- Android Studio
…are frequent offenders when running as Snaps.
Snapd on Low-Resource Systems
Snap works best on modern hardware. On systems with:
- Less than 4GB RAM
- Older CPUs
- HDD instead of SSD
Snapd overhead becomes much more noticeable.
How to Fix Snapd Consuming High CPU / RAM on Linux
Step 1: Confirm Snapd Is the Real Problem
Before making changes, confirm Snapd is actually consuming resources.
Run:
top
or:
htop
Look for processes like:
snapdsnapd.seededsnap-confine
If Snapd consistently appears near the top, you’ve confirmed the issue.
Step 2: Restart Snapd (Quick Temporary Fix)
Sometimes Snapd just needs a reset.
sudo systemctl restart snapd
This often fixes:
- Temporary CPU spikes
- Stuck background jobs
- Incomplete refresh processes
If the problem returns after a few hours or days, move on to deeper fixes.
Step 3: Check What Snap Is Actually Doing
Snapd logs are very helpful.
journalctl -u snapd --no-pager | tail -50
Look for:
- Repeated refresh attempts
- Errors related to specific Snap packages
- Network-related failures
This helps you identify whether one app or Snapd itself is causing the issue.
Step 4: Disable or Delay Automatic Snap Updates
One of the most effective ways to fix Snapd consuming high CPU / RAM is controlling when updates happen.
View Current Refresh Schedule
snap refresh --time
Delay Snap Updates
You can postpone updates for up to 60 days:
sudo snap set system refresh.hold="$(date --date='30 days' +%Y-%m-%dT%H:%M:%S%:z)"
This significantly reduces background CPU and RAM usage.
Limit Update Window
You can also restrict Snap updates to specific hours:
sudo snap set system refresh.timer=02:00-04:00
This way, Snapd runs when you’re not actively using the system.
Step 5: Identify Resource-Hungry Snap Packages
List all installed Snap apps:
snap list
Pay special attention to large apps like:
- Browsers
- IDEs
- Media editors
If you rarely use a Snap app, it may not be worth keeping.
Step 6: Remove Unused Snap Packages
Unused Snap packages still get updated and maintained in the background.
Remove what you don’t need:
sudo snap remove package-name
After cleanup, restart Snapd:
sudo systemctl restart snapd
You’ll often notice immediate performance improvements.
Step 7: Replace Snap Apps with APT or Flatpak Versions
This is one of the most effective long-term solutions.
Example: Replace Snap Firefox
Remove Snap version:
sudo snap remove firefox
Install APT version (if available):
sudo apt install firefox
Or use Flatpak:
flatpak install flathub org.mozilla.firefox
Flatpak apps often consume less background resources compared to Snap.
Step 8: Clean Snap Cache and Old Revisions
Snap keeps multiple old revisions of each app, which can waste disk space and contribute to background activity.
Reduce Stored Revisions
sudo snap set system refresh.retain=2
Remove Old Disabled Revisions
snap list --all | awk '/disabled/{print $1, $3}' |
while read snapname revision; do
sudo snap remove "$snapname" --revision="$revision"
done
This cleans up unnecessary data and reduces Snapd workload.
Step 9: Disable Snapd Desktop Integration (Optional)
If you don’t rely heavily on Snap GUI features:
sudo systemctl disable snapd-desktop-integration
sudo systemctl stop snapd-desktop-integration
This can lower RAM usage on desktop systems.
Step 10: Limit Snapd CPU Usage Using Systemd
Advanced users can limit Snapd’s CPU consumption.
Create an override:
sudo systemctl edit sn
Add:
[Service]
CPUQuota=20%
Then reload:
sudo systemctl daemon-reexec
sudo systemctl restart snapd
This prevents Snapd from hogging your CPU under any circumstance.
Step 11: Completely Remove Snapd (Extreme Option)
If Snap simply doesn’t fit your workflow, removing it is a valid choice.
Remove All Snap Packages
sudo snap remove --purge $(snap list | awk 'NR>1 {print $1}')
Remove Snapd
sudo apt purge snapd
sudo rm -rf ~/snap /snap /var/snap /var/lib/snapd
Note: Some Ubuntu versions rely on Snap for core apps. Make sure you have alternatives installed first.
Step 12: Prevent Snapd from Reinstalling Automatically
On Ubuntu:
sudo apt-mark hold snapd
This ensures Snapd doesn’t come back during system upgrades.
Best Practices to Avoid Snapd High CPU / RAM in the Future
- Keep Snap apps minimal
- Replace heavy Snap apps with APT or Flatpak
- Restrict update windows
- Regularly clean old Snap revisions
- Monitor Snapd logs occasionally
Following these habits keeps your system fast and predictable.
Final Thoughts
Snapd isn’t inherently bad—it just isn’t optimized for every system or user. If you value control, performance, and predictability, it’s important to actively manage Snapd rather than letting it run unchecked.
By following this guide, you now know exactly how to fix Snapd consuming high CPU / RAM, whether through optimization, replacement, or complete removal. Choose the approach that best fits your hardware and workflow.
You can also refer to the official Snapd documentation.
How to Fix Snapd Consuming High CPU / RAM
Why is Snapd consuming high CPU even when I’m not using Snap apps?
Snapd runs background services such as automatic updates, security checks, and metadata refresh tasks. Even if you’re not actively using Snap applications, these processes can temporarily consume high CPU or RAM, especially on low-resource systems.
Is Snapd supposed to use so much RAM?
Under normal conditions, Snapd should use minimal RAM. However, when multiple Snap packages are installed or updates are running in the background, memory usage can increase noticeably. This is more common on systems with limited RAM or slower storage.
How do I check if Snapd is causing high CPU or RAM usage?
You can confirm this by running tools like top or htop in the terminal. If processes such as snapd, snapd.seeded, or snap-confine consistently appear at the top of the list, Snapd is likely the source of the issue.
What is the easiest way to fix Snapd consuming high CPU / RAM?
The quickest fix is restarting the Snapd service using sudo systemctl restart snapd. If the problem keeps returning, delaying automatic updates or removing unused Snap packages usually provides a more permanent solution.
Can I disable Snap automatic updates to reduce CPU usage?
Yes, Snap allows you to delay or schedule updates. By limiting updates to specific time windows or postponing them for several days, you can significantly reduce unexpected CPU and RAM spikes during active work hours.
Which Snap apps usually consume the most resources?
Large applications such as web browsers, IDEs, and development tools tend to be the most resource-intensive when installed as Snaps. Firefox, Chromium, and Android Studio are commonly reported to cause higher Snapd activity.
Is replacing Snap apps with APT or Flatpak safe?
Yes, replacing Snap apps with APT or Flatpak versions is safe and often improves performance. Many users switch to traditional package formats to reduce background resource usage while maintaining the same functionality.
Does removing unused Snap packages really help?
Absolutely. Even unused Snap packages continue to receive updates and maintenance tasks in the background. Removing unnecessary Snaps reduces Snapd workload, leading to lower CPU and RAM usage.
Can Snapd be limited to use less CPU?
Advanced users can limit Snapd’s CPU usage using systemd settings. By setting a CPU quota, Snapd is prevented from consuming excessive processing power, even during updates or refresh operations.
Is it safe to completely remove Snapd from Ubuntu?
It is safe if you understand the consequences. Some Ubuntu versions rely on Snap for certain default applications. Before removing Snapd, make sure you install alternative versions of essential apps using APT or Flatpak.
Why does Snapd keep coming back after removal?
On some Ubuntu releases, Snapd may be reinstalled during system updates. To prevent this, you can place Snapd on hold using the package manager, ensuring it does not reinstall automatically.
Is Snapd bad for performance on older systems?
Snapd is not inherently bad, but it can feel heavy on older hardware or systems with limited RAM and slower disks. In such cases, minimizing Snap usage or switching to lighter package formats usually results in better performance.
Will disabling Snapd affect system stability?
Disabling or removing Snapd does not affect system stability as long as no critical applications depend on it. Always verify dependencies before making permanent changes.
How often should I clean old Snap revisions?
Cleaning old Snap revisions every few months is generally enough. This helps free disk space and reduces unnecessary background processing by Snapd.
What is the best long-term solution for Snapd high resource usage?
The best long-term approach is a combination of limiting automatic updates, removing unused Snaps, replacing heavy Snap apps, and monitoring Snapd behavior occasionally. This ensures performance without sacrificing system functionality.
How to Fix SSH Connection Refused Error on Linux: 10 Simple Ways