What is naturallanguaged on my Mac?
Last reviewed: 19 November 2026. Path, launchd job and man page checked on macOS 26.3.1.
naturallanguaged is a macOS agent that Apple's man page calls the system post-editing daemon: it handles requests from apps to check text that the user wrote. It is started on demand in your login session and exits when idle. It is a small, short-lived process.
naturallanguaged at a glance
| naturallanguaged | |
|---|---|
| Made by | Apple (part of macOS, Natural Language) |
| Type | Per-user agent |
| Location | /usr/libexec/naturallanguaged |
| Runs as | your user |
| Started by | launchd job com.apple.naturallanguaged |
| Can you quit it? | Yes. launchd starts it again when an app sends it text to check. |
What is naturallanguaged?
The naturallanguaged(8) man page names it the system post editing daemon and says it handles post editing requests from applications to check user text. The man page does not list which apps or features send it requests.
It runs as your user through the launchd agent com.apple.naturallanguaged, which provides a single service of the same name. On the Mac checked here it had been started once since login and was not running.
Is naturallanguaged safe?
Yes. It is part of macOS at /usr/libexec/naturallanguaged and is signed by Apple.
Why does naturallanguaged use so much CPU and memory?
- Apps checking your text. An app that sends text you wrote for checking starts it and gives it work.
- Long documents. Checking more text takes longer, so large documents mean longer bursts.
- Language data. Language resources are loaded while it works and released when it exits.
How much CPU is normal for naturallanguaged?
Typical: not running, or a short burst of CPU while you type or edit, then idle.
Continuous CPU use while you are not writing would be unusual.
What can you check if naturallanguaged is busy?
- Find the app you were writing in. Note which app was in front when naturallanguaged got busy, and quit it to see whether it settles.
- Sample it. Select naturallanguaged in Activity Monitor and choose View > Sample Process to see what it is doing.
- Quit it. Quitting it in Activity Monitor is harmless; it starts again on the next request.
When should you worry about naturallanguaged?
naturallanguaged is not a concern. A copy outside /usr/libexec would not be Apple's.
How do you check naturallanguaged in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type naturallanguaged in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every naturallanguaged process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'naturallanguaged' | grep -v grep
How can Thrum help with naturallanguaged?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when naturallanguaged is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click naturallanguaged in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about naturallanguaged
Does naturallanguaged send my text to Apple?
Its man page only says it checks user text for applications. It does not describe sending text anywhere, and this page does not claim it does.
Is it the same as AppleSpell?
They are separate processes. AppleSpell is the spelling checker service; naturallanguaged is described as a post-editing daemon.
Sources
- naturallanguaged(8) man page: run man naturallanguaged in Terminal