Thrum

What is com.apple.WebKit.WebContent, and why is it using so much CPU?

Last reviewed: 19 November 2026. Path, bundle ID and code signature checked on macOS 26.3.1 with Safari 26.3.1.

com.apple.WebKit.WebContent is the WebKit process that runs web pages for Safari and for other apps that show web content; Activity Monitor names it after the app, for example Safari Web Content. It gets busy when a page runs heavy scripts, plays video or animates constantly, and each open page adds memory. Closing or reloading the busy tab brings it back down.

com.apple.WebKit.WebContent at a glance

com.apple.WebKit.WebContent
Made byApple (part of macOS, WebKit)
TypeXPC service (WebKit web content process)
Location/System/Library/Frameworks/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent
Runs asyour user
Bundle IDcom.apple.WebKit.WebContent
Can you quit it?Yes. The page or pages it was showing stop working until you reload them, and anything unsaved in those pages is lost.

What is com.apple.WebKit.WebContent?

WebKit, the engine behind Safari, splits browsing into several processes. The app itself draws the window and tabs, one shared Networking process loads everything from the internet, and Web Content processes parse HTML, run JavaScript and lay out the pages. WebKit's documentation describes the Web Content process as tightly sandboxed: it cannot read your files unless you grant access, and it has no direct access to the clipboard, microphone or camera.

Activity Monitor shows these processes with the owning app's name, such as Safari Web Content. WebKit also uses two variants: Web Content (Prewarmed), started ahead of time so the next page opens faster, and Web Content (Cached), kept for a while after a page closes so that going back is quick. The executable name, which ps shows, is always com.apple.WebKit.WebContent.

Is com.apple.WebKit.WebContent safe?

Yes. It is an XPC service inside the WebKit framework in /System/Library/Frameworks, signed by Apple, and it runs under your own account. When it uses a lot of CPU, the cause is the web page it is running, not the process itself.

Why does com.apple.WebKit.WebContent use so much CPU, energy and memory?

How much CPU is normal for com.apple.WebKit.WebContent?

A Web Content process showing a static article you are reading sits at or near 0% CPU. Short spikes while a page loads, scrolls or plays a video are expected.

Memory depends on the page. A plain text page needs little; a web app with a large document, a map or a long chat history open can hold far more. Several Web Content processes at once is normal when several tabs or windows are open.

How do you find and calm the busy web page?

  1. Identify which app owns it. In Activity Monitor, the name in the Process Name column starts with the app that owns the process, such as Safari Web Content. If it is another app's Web Content process, that app is showing the page, and quitting it ends the process.
  2. Find the tab by elimination. Sort the CPU tab by % CPU, then close or reload Safari tabs one at a time, starting with web apps, video and pages you opened most recently. The busy process drops or disappears when you reach the right tab.
  3. Turn off extensions to test. Choose Safari > Settings, click Extensions, and deselect the checkbox of each extension. If CPU use falls, turn them back on one at a time to find the one responsible.
  4. Stop a process that will not settle. Select it in Activity Monitor, click the Stop button in the toolbar, and choose Quit or Force Quit. The tabs it served show an error; reloading them starts a new Web Content process.

When should you worry about com.apple.WebKit.WebContent?

Look closer if a Web Content process stays high after you have closed every tab and window of its app, or if its memory keeps climbing while the page is idle. Quitting and reopening the app clears both cases; if it comes back with the same site, the site itself is the cause.

A process with this name running from anywhere other than the WebKit framework path above would not be Apple's. You can confirm the path with ps or with Open Files and Ports in Activity Monitor.

How do you check com.apple.WebKit.WebContent in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type com.apple.WebKit.WebContent in the search field. The CPU tab shows its % CPU. The Energy tab shows its Energy Impact. 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 com.apple.WebKit.WebContent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'com.apple.WebKit.WebContent' | grep -v grep
pmset -g assertions    # shows processes keeping the Mac awake

How can Thrum help with com.apple.WebKit.WebContent?

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 com.apple.WebKit.WebContent 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 com.apple.WebKit.WebContent 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 com.apple.WebKit.WebContent

Why are there several com.apple.WebKit.WebContent processes?

WebKit runs web pages in separate processes, so tabs and windows, prewarmed processes kept ready for the next page, and cached processes for recently closed pages each appear as their own entry. Other apps that display web pages through WebKit add their own.

What happens if I force quit Safari Web Content?

Only the pages in that process are affected. They stop working until reloaded, and text you had typed into a form on those pages is lost. The rest of Safari keeps running.

Is com.apple.WebKit.WebContent the same as Safari?

No. Safari is the app that draws the window, tabs and toolbar; Web Content processes run the pages inside it. Its CPU is usually counted against the Web Content process, not against Safari.

Sources