Skip to main content

Want to switch from the Mole Mac site to the Windows site?

Go to the Windows site
Mole
MacWindows
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT NederlandsNL
Buy Download

    Help, documentation, releases, and articles.

    Blog

    How to Stop suggestd From Using So Much CPU on Mac

    PerformancePublished November 12, 2026Updated November 14, 20266 min read

    suggestd is the macOS daemon behind Siri Suggestions. It reads content from Mail, Messages, Spotlight and other apps, finds things like contacts, events and addresses in it, and feeds features such as Found in Apps and QuickType predictions. It runs from the CoreSuggestions framework under your own account and is usually idle. When it uses a lot of CPU, it is normally working through a pile of new content, for example after a migration, a fresh Mail download or a macOS update, and it calms down once that is done. If you want it to do less, you can turn Siri suggestions off for specific apps.

    What it does

    Its manual page (man suggestd) describes a daemon that "processes user content in order to detect contacts, events, named entities, etc." It receives content "from Spotlight, Mail, Messages and various other apps" to power Found in Apps, Proactive QuickType, and keyboard, Siri and News personalization.

    The process lives inside a framework, which is why the path is long:

    /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Support/suggestd
    

    On the Mac used for this page, after almost four days of uptime, it showed 0.0% CPU, about 84 MB of memory and 1 minute 12 seconds of CPU time in total. Its own store, ~/Library/Suggestions, was 3.4 MB.

    Why it spikes

    Its launchd job, /System/Library/LaunchAgents/com.apple.suggestd.plist, lists more than a dozen scheduled tasks. Several are marked CPU intensive: a background harvest every eight hours, a daily cache rebuild, a daily identity analysis and a daily precomputation for its entity store. Almost all of them have AllowBattery set to false, so the heavy work tends to run while the Mac is on power, often when you have stepped away.

    lsof on this Mac showed it reading harvesting streams named after the apps it learns from: ProactiveHarvesting.Mail, ProactiveHarvesting.Messages, ProactiveHarvesting.Notes, ProactiveHarvesting.Notifications and others. More new content in those apps means more to read. That explains the common patterns:

    • After Migration Assistant, years of mail and messages arrive at once.
    • Adding a mail account, or Mail re-downloading a large mailbox, hands it thousands of new messages.
    • After a macOS update, its caches and models may be rebuilt.
    You see Likely cause Try
    High CPU for a few hours after setting up a Mac Reading migrated mail and messages Leave it on power overnight
    Busy right after adding a mail account New messages to process Wait for Mail to finish downloading
    Busy only while charging Scheduled tasks that skip battery Normal, nothing to do
    Busy for days with no new content A stuck job Restart, then install pending updates
    Busy together with mds_stores or corespotlightd Spotlight is indexing the same content See corespotlightd high CPU

    How to check it

    In Activity Monitor, search for suggestd and watch % CPU and CPU Time for a few minutes. CPU time that keeps climbing tells you more than one high reading. From Terminal:

    ps -axo user,pid,%cpu,time,rss,args | grep '[s]uggestd'
    

    If Mail is still downloading a mailbox, waiting for that to finish is usually the fix.

    How to make it do less

    There is no switch for suggestd itself, but you can decide which apps Siri learns from:

    1. Open System Settings › Siri.
    2. Click Suggestions.
    3. Turn suggestions off for the apps you suspect, such as Mail or Messages.

    On earlier versions the pane is Apple Intelligence & Siri on Macs that support it (macOS Tahoe), the button is Siri Suggestions & Privacy…, and each app in its list has Learn from this application and Show Siri Suggestions in application; for Contacts the second option reads Show Siri Suggestions for contacts, and for FaceTime Show Siri Suggestions when calling. Click Done when you finish. Turning these off means fewer suggested contacts, events and addresses in that app. It is a fair test: if the load stops after you turn it off for Mail, you know what was driving it. Turn it back on if you miss the suggestions.

    Two other things help on a Mac that just moved over: keep it plugged in and awake for a night so the scheduled work can run, and install any macOS point update, since background process bugs are fixed there.

    What not to do

    • Do not delete ~/Library/Suggestions while the Mac is running. suggestd keeps a database there with a write-ahead log, and some guides suggest removing it, but Apple does not document that, and the daemon would read all of your content again to rebuild it.
    • Do not repeatedly kill it from Activity Monitor or a script. launchd restarts it and the work resumes.
    • Do not turn off Spotlight indexing to stop it. That breaks search, and Mail and Messages are separate sources it reads.

    Is it malware

    The real binary is signed by Apple:

    codesign -dv /System/Library/PrivateFrameworks/CoreSuggestions.framework/Versions/A/Support/suggestd 2>&1 | grep Identifier
    

    It should print com.apple.suggestd. A copy running from anywhere outside /System/Library deserves a closer look.

    Where Mole fits

    Mole lists suggestd in Status with its CPU and memory when it is busy, and the table's search finds it when it is not. Why is this running? in its menu shows the executable, the launchd service that started it and its disk reads and writes, which helps you see whether it is chewing through a large mailbox. Because it runs from a system folder, Mole shows no Terminate or Force Quit for it. Mole does not change Siri Suggestions settings, and Clean does not list ~/Library/Suggestions. If the real problem is a huge mailbox, see how to reduce Mail storage.

    FAQ

    What is suggestd on Mac?

    It is the CoreSuggestions daemon that reads content from Mail, Messages, Spotlight and other apps to find contacts, events and other details for Siri Suggestions, Found in Apps and QuickType.

    Why is suggestd using so much CPU?

    It is processing a lot of new content, usually after a migration, a new mail account or a macOS update. Its heavy tasks are set to run on power, so you often see it while charging.

    How do I stop suggestd?

    There is no switch for the process. Under Siri › Suggestions, turn suggestions off for the apps you don't want it to read, such as Mail; on earlier versions, use Learn from this application under Siri Suggestions & Privacy….

    Can I delete the Suggestions folder?

    Apple does not document it as a fix. The daemon would rebuild it by reading your content again, which is the same work you were trying to stop.

    Is suggestd a virus?

    The real one runs from the CoreSuggestions framework under /System/Library and is signed by Apple as com.apple.suggestd.

    If your Mac is slowing down, use Mole to see what is running and which apps are using the most resources.

    Try Mole

    Keep reading

    • PerformanceWhy Your Mac Is Slow and How to Diagnose It7 min read
    • PerformanceWhich Account Is Making contactsd Use High CPU on My Mac?6 min read
    • PerformanceWhy Is knowledge-agent Using High CPU on My Mac?6 min read

    Mole · 鼹

    Keep your Mac clean and light.

    v1.21.0 (384) · Release notes

    Product

    Mac Cleaner App Uninstaller Mac Optimizer Disk Analyzer System Monitor

    Support

    Help Documentation Releases Blog

    Legal

    Terms of Service Privacy Policy Refund Policy

    Resources

    For Windows CLI Tool Storage Cost Affiliate Program

    More Apps

    Yado 宿 Pake 殼 MiaoYan 語 Kaku 書

    Connect

    Twitter hi@mole.fit

    Mole’s only official website mole.fit, avoid installers from unknown sources

    The CLI stays free for terminal workflows.