WebKit Web Content Process
A background helper that Apple's WebKit engine uses to load and run each web page on your Mac. WebKit is the engine behind Safari and many other Apple apps — Mail, the App Store, News, and more — and it runs each open website in its own separate process so that one bad page can't bring down the whole browser. You'll often see several of these in Activity Monitor at once, one per open site or web-capable app; that's completely normal.
com.apple.WebKit.WebContent — owned by Apple Inc..
- When it runs hot
- One of three things is usually going on: a single page with heavy video, ads, or a live web app is consuming a lot of power; a page's process has got stuck and kept running long after you closed its tab or quit Safari; or a Safari extension is running on every site you visit and adding up across processes. Seeing many of these processes is expected — it's the one that stands far above the rest that points to the problem.
- Safety tier
- Safe — User-owned and reversible — acting carries no real risk.
- Safe action
quit- Worst case
- A stuck or extremely heavy page holds on to several gigabytes of memory and multiple CPU cores for hours, making the whole Mac feel sluggish and hot — but closing or stopping the process loses only that page's content, never any of your files.
Sources
- Introduction to WebKit – WebKit Documentation (official)
- WebKitWebContent High CPU or Memory on Your Mac? The Fix (2026) – Noah
- WebKit/Introduction.md – WebKit on GitHub (official source repository)
Sourced by Anomalous — this is the published corpus entry that grounds the
com.apple.WebKit.WebContent diagnosis card, not a language-model guess.
Browse the whole process corpus.