What is the esbuild process, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path and parent process of a running esbuild checked on macOS 26.3.1.
esbuild is a fast JavaScript and TypeScript bundler written in Go, and JavaScript tools run its native executable as a child process of node. It uses CPU while it bundles, and in watch mode it keeps checking files for changes until the tool that started it stops. Its parent node process tells you which project and tool it belongs to.
esbuild at a glance
| esbuild | |
|---|---|
| Made by | The esbuild project (open source); installed by npm packages |
| Type | JavaScript bundler (native binary) |
| Location | [project]/node_modules/@esbuild/darwin-arm64/bin/esbuild |
| Runs as | your user |
| Can you quit it? | Yes, but the build, dev server or watch mode that uses it stops or reports an error. |
What is esbuild?
esbuild's documentation says it is written in Go and installs a platform-specific native executable through npm, for example @esbuild/darwin-arm64 on Apple silicon. Its JavaScript API runs that executable in a child process, so an esbuild process always has a node (or other tool) process as its parent. On the Mac used for checking, esbuild ran from an npx cache folder under a node parent.
Many tools use esbuild internally, so it often appears without you having installed it directly: a dev server, a TypeScript runner or a build script may all start it.
Is esbuild safe?
Yes, when it runs from a node_modules or npm cache folder of a project or tool you use. It reads and writes files only in the project it was given.
Why does esbuild use so much CPU and memory?
- Bundling. A build parses, transforms and bundles every file reachable from the entry points, using several cores for a short time.
- Watch mode polling. esbuild's watch mode uses polling instead of macOS file system events. Its documentation says it checks a random subset of files on each scan and fully rescans large projects about every 2 seconds.
- Serve mode rebuilds. In serve mode, each request from the browser triggers a rebuild if one is not already running, so a page that reloads often keeps it busy.
- Long-running build contexts. Tools that keep an esbuild context open for incremental builds hold the parsed project in memory until the context is disposed.
How much CPU is normal for esbuild?
Bursts of CPU during builds and a low, steady level while a watch or serve session is idle are normal.
esbuild exits when the tool that started it disposes of its context or exits.
How do you find which project esbuild belongs to?
- Find its parent. Double-click esbuild in Activity Monitor, or run
ps -o ppid= -p <PID>, thenps -o args= -p <PPID>to see the node command that started it. - Read its path.
ps -o args= -p <PID>shows the folder it runs from, which is inside the project's or tool'snode_modules. - Stop the dev server or watcher. Press Control-C in the Terminal window running the dev server, or stop the task in your editor. esbuild exits with it.
- Narrow what it watches. Watch-mode cost grows with the number of files the build includes. Keeping generated output and large asset folders out of the build reduces polling work.
When should you worry about esbuild?
An esbuild process with launchd (PID 1) as its parent was left behind by a tool that exited without stopping it; quitting it is safe.
An esbuild binary outside any node_modules or package cache folder is unusual and worth checking.
How do you check esbuild in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type esbuild 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 esbuild process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'esbuild' | grep -v grep
How can Thrum help with esbuild?
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 esbuild 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 esbuild 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 esbuild
Why is esbuild running when I did not install it?
It is a dependency of many JavaScript tools, which install it automatically into node_modules and start it when they build.
Does esbuild watch mode use file system events?
No. Its documentation says watch mode polls for changes for portability, checking a subset of files on each pass.