What is Code Helper (Renderer), and why is it using so much CPU?
Last reviewed: 19 November 2026. Helper bundles and bundle IDs checked in Visual Studio Code 1.138 on macOS 26.3.1.
Code Helper (Renderer) is the Visual Studio Code process that draws a window: the editor, sidebars, panels and the integrated terminal's display, with one renderer per open window. It uses CPU when the window has a lot to draw or update, such as very large files, many decorations, an animated theme or a fast-scrolling terminal. CPU from extensions usually appears under Code Helper (Plugin) instead, so check which helper is busy first.
Code Helper (Renderer) at a glance
| Code Helper (Renderer) | |
|---|---|
| Made by | Microsoft (part of Visual Studio Code) |
| Type | Helper process (Electron renderer) |
| Location | /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Renderer).app/Contents/MacOS/Code Helper (Renderer) |
| Runs as | your user |
| Bundle ID | com.microsoft.VSCode.helper |
| Can you quit it? | Quitting it makes the VS Code window it draws stop working. Close the window from VS Code instead. |
What is Code Helper (Renderer)?
VS Code is built on Electron, which inherits Chromium's multi-process design: one main process, and a separate renderer process for the web content of each window. VS Code's workbench (the whole editor interface) runs in that renderer. On a Mac, Electron starts renderers from the Code Helper (Renderer).app bundle inside VS Code.
VS Code's own Process Explorer (Help > Open Process Explorer) lists each process by role, such as window, extension host, shared process and terminal, with live CPU and memory, which maps the Activity Monitor PIDs to their jobs.
Is Code Helper (Renderer) safe?
Yes, when it runs from inside Visual Studio Code.app, which is signed with Microsoft's Developer ID (Microsoft Corporation, team UBF8T346G9).
Why does Code Helper (Renderer) use so much CPU and memory?
- Very large files. Opening huge log, JSON or minified files makes the editor tokenize, highlight and lay out far more text than usual.
- Busy terminal output. A command printing thousands of lines per second into the integrated terminal keeps the window redrawing.
- Many editors and windows. Each window has its own renderer, and many open editor tabs, diff views and previews add memory to it.
- Webviews and previews. Markdown previews, notebook outputs and extension webviews render web content inside the window and add drawing work.
How much CPU is normal for Code Helper (Renderer)?
Low CPU while you read or type, with short bursts when you open files, search or scroll. One renderer per window.
Memory in the hundreds of megabytes per window is common for large workspaces.
How do you find what makes a VS Code window busy?
- Open Process Explorer. Choose Help > Open Process Explorer. It updates continuously and shows which window or process is using CPU;
code --statusin Terminal prints the same as a snapshot. - Rule out extensions. Run Help: Start Extension Bisect from the Command Palette. It disables half your extensions at a time to find one that causes the problem; the first round disables all of them.
- Close large files and extra windows. Close very large files, previews and windows you are not using; each window has its own renderer.
- Profile the window. VS Code's performance guide describes recording a profile of the renderer with Developer Tools (Help > Toggle Developer Tools) to see what it is doing.
When should you worry about Code Helper (Renderer)?
A renderer that stays at high CPU with the window idle and extensions disabled is worth reporting to the VS Code project with a profile.
A Code Helper (Renderer) outside Visual Studio Code.app is not Microsoft's. Other editors built on VS Code use their own helper names.
How do you check Code Helper (Renderer) in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Code Helper (Renderer) 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 Code Helper (Renderer) process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Code Helper (Renderer)' | grep -v grep
How can Thrum help with Code Helper (Renderer)?
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 Code Helper (Renderer) 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 Code Helper (Renderer) 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 Code Helper (Renderer)
What is the difference between Code Helper (Renderer) and Code Helper (Plugin)?
The renderer draws a window. Extensions run in a separate extension host process, which VS Code starts through the Code Helper (Plugin) helper.
Why are there several Code Helper (Renderer) processes?
One runs for each VS Code window, and webviews or previews may add more.