What is nehelper on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
nehelper is the Apple daemon that hands out and saves Network Extension settings, the configurations used by VPN apps, content filters and DNS proxies. It runs when an app or System Settings reads or changes those settings. It is part of macOS and normally uses almost no CPU.
nehelper at a glance
| nehelper | |
|---|---|
| Made by | Apple (part of macOS, Network Extension) |
| Type | System daemon |
| Location | /usr/libexec/nehelper |
| Runs as | root |
| Started by | launchd job com.apple.nehelper |
| Can you quit it? | Not usefully. launchd starts it again when an app reads or changes Network Extension settings. |
What is nehelper?
The man page says nehelper is part of the Network Extension framework and is responsible for vending the Network Extension configuration to clients and applying changes to it. Apple's developer documentation describes Network Extension as the framework that lets apps create VPN configurations, implement on-device content filters, manage DNS settings and proxies, and change Wi-Fi configuration.
nehelper is the part that owns those saved configurations. The VPN connection itself is run by nesessionmanager, and a VPN or filter app's own code runs inside neagent or its own system extension.
Is nehelper safe?
Yes. nehelper lives in /usr/libexec on the read-only system volume and is started on demand by an Apple launch daemon.
Why does nehelper use so much CPU?
- VPN and filter apps checking their settings. VPN clients, security tools and parental-control apps read their configuration when they start and often while running.
- Installing or updating a VPN or filter app. Adding, removing or changing a configuration goes through nehelper and may show a permission prompt.
- Opening VPN settings. System Settings reads every configuration through nehelper when you open the VPN or filter settings.
How much CPU is normal for nehelper?
Typical use is 0% CPU. It starts, answers a request and exits.
Repeated CPU use usually follows an app that reads or rewrites its configuration in a loop.
What can you do if nehelper keeps using CPU?
- List the configurations. In System Settings, search for VPN to see installed VPN configurations, and search for Filters to see content filters. Each one belongs to an app.
- Quit the VPN or filter apps. Quit those apps one at a time and watch nehelper in Activity Monitor.
- Update or remove the app. If one app keeps nehelper busy, update it or remove its configuration and the app.
When should you worry about nehelper?
Steady CPU use with no VPN or filter apps installed is unusual. A copy of nehelper outside /usr/libexec would not be Apple's.
How do you check nehelper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type nehelper in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every nehelper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'nehelper' | grep -v grep
How can Thrum help with nehelper?
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 nehelper 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. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
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 nehelper
Is nehelper a VPN?
No. It stores and applies the settings; the VPN tunnel is run by nesessionmanager and the provider app.
Why is nehelper running when I do not use a VPN?
Other Network Extension features, such as content filters and DNS proxies, and System Settings itself also read configurations through it.
Sources
- nehelper(8) man page: run man nehelper in Terminal
- Apple Developer: Network Extension