WallpaperVideoExtension is eating your CPU — here's what that process actually is
WallpaperVideoExtension is the macOS system extension that decodes video wallpapers. It lives on the read-only signed system volume, so you cannot delete it, and quitting it in Activity Monitor only makes it respawn. On macOS 26 it may not even be the process you are looking at — check the exact name first.
What Activity Monitor actually shows you (and why the name doesn't match)
Start with the name, because that is where most people lose the thread. In Activity Monitor the row burning your CPU is often not labelled WallpaperVideoExtension: it carries the name of the wallpaper itself, followed by (Wallpaper). On the MacRumors thread where users first compared readings, it appears as “Ventura (Wallpaper)” holding 2.9 GB and later 4 GB of memory, as “Message (Wallpaper)” climbing to 20 GB and, in one posted reading, 57.84 GB, and plainly as Wallpaper.app at 1.40 GB. That thread opens in June 2023 — “seems to have starting happening after Beta 2”, the Sonoma betas — and readings were still being posted against macOS 15.3.1 (24D70) in March 2025. Search the process list for the full extension name and you can conclude, wrongly, that you do not have the problem.
The binary sits at /System/Library/ExtensionKit/Extensions/WallpaperVideoExtension.appex/Contents/MacOS/WallpaperVideoExtension. Nothing suspicious about that address: as Howard Oakley wrote in April 2025, macOS appexes are “stored as bundles inside dedicated collections such as /System/Library/ExtensionKit/Extensions”, several wallpaper extensions among them. It also has company, and telling those apart is half the diagnosis.
| Process | What it renders | Where it lives |
|---|---|---|
| WallpaperVideoExtension | Video wallpapers | /System/Library/ExtensionKit/Extensions/ |
| WallpaperImageExtension | Still wallpapers | /System/Library/ExtensionKit/Extensions/ |
| WallpaperAerialsExtension | Tahoe’s aerial clips (macOS 26) | /System/Library/ExtensionKit/Extensions/ |
| WallpaperAgent | Drives the whole set | /System/Library/CoreServices/WallpaperAgent.app/ |
One piece of arithmetic before you panic at a number: a row showing 120 % is not using 120 % of your Mac. The % CPU column adds up activity across several cores, so anything above 100 % means more than one core is busy. Apple’s Activity Monitor guide defines System, User and Idle only, never the per-process column — so treat that as an observation, not a documented rule.
Why the extension runs even when your wallpaper isn't a video
The most disorienting report on Apple’s own forums comes from a user who had ruled the obvious cause out. On the Sonoma thread opened in October 2023, watching the process take “up to 1GB of RAM”, they write: “I’m not using any of the Apple video wallpapers/screen savers, and haven’t d/l any of them.”
Apple’s documentation reconciles that. On the macOS Tahoe 26 version of Change the desktop wallpaper on Mac: “By default, the aerial wallpaper you select is also used as your screen saver.” One pick in the Wallpaper pane arms two video consumers rather than one — which is how the video path stays live on a Mac whose owner is certain they only chose a picture.
“I never downloaded any of that” is not proof either. Users tracking Tahoe’s aerial storage report that macOS “downloads screensavers dynamically when first viewed”: nothing in your Downloads folder, several hundred megabytes of video on disk regardless. And keep the labels on as you read this. Every published measurement of the process is macOS 14.0 to 14.6.1, plus one macOS 15.3.1 reading. There is none for macOS 26.
What macOS 26 Tahoe changed in the wallpaper subsystem
This is where guides written for Sonoma quietly stop applying. On macOS 26 the aerials are handled by a different extension: WallpaperAerialsExtension, at /System/Library/ExtensionKit/Extensions/WallpaperAerialsExtension.appex/. It was identified in a 17 September 2025 write-up on Tahoe’s video wallpapers, and a community utility restarts it by name on lock and unlock because “aerial wallpapers get stuck/stop animating on newer macOS versions” — its README lists Sonoma, Sequoia and Tahoe. On 26.x, searching Activity Monitor for the video extension alone means missing this name entirely.
WallpaperVideoExtension has not disappeared from Tahoe, though. The evidence is a community patch described, verbatim, as “a patch for the WallpaperVideoExtension to not glitch when you use custom aerials (For MacOS 26)”. Its trigger is narrow: it targets people who replace Apple’s .mov files with their own. Its method is to terminate WallpaperAgent at every login, and it is honest about the cost — “there will be a gray (or black) wallpaper when you login for around 2 seconds”.
The files moved as well. On macOS 26 the aerial videos live in ~/Library/Application Support/com.apple.wallpaper/aerials/videos/; on macOS 15 and earlier they sat in /Library/Application Support/com.apple.idleassetsd/Customer/. Upgrading does not clean up behind itself: a user posting in September 2025 found both copies retained, deleted the old folder by hand and recovered “an additional 50G of disk space” — though another contributor cautioned that some of it may be shared space, and that macOS purges unused wallpapers over time anyway. The files are 4K HDR .mov, roughly 450–500 MB each, 1.82 GB for the four Tahoe Day, Morning, Evening and Night variants alone.
Before you blame the wallpaper: on 26.x the usual suspect is called WindowServer
Here is the part no competing page will tell you: as of today there is no public report documenting WallpaperVideoExtension on macOS 26. Not one measurement, not one thread. What ranks for “Tahoe” on this query is recycled Sonoma content, sometimes with a 2026 date stamped on top.
What is documented on 26.x is a different process. macReports, on 4 October 2025, describes Tahoe overheating across M1 to M4 and Intel Macs with “WindowServer using 20–40% CPU and 35–50% GPU” alongside Spotlight indexing — and never mentions wallpapers in its recommendations. An Apple Developer Forums thread from September 2025 has a MacBook Pro M4 owner reporting WindowServer above 45 % during video playback in Safari and Edge; a MacRumors thread on long uptimes has users at 40–50 % CPU with memory climbing to 3–3.5 GB.
The remedy people report there is not a wallpaper setting. Users describe CPU “dropping roughly in half” after enabling Reduce Transparency and Reduce Motion, and an April 2026 write-up attributes the load to the interface itself: “the Tahoe Liquid Glass interface is heavy on visual effects”. Note what that fixes — WindowServer, not your wallpaper. If WindowServer sits above the wallpaper process in your own list, you are troubleshooting the wrong line.
Why quitting it in Activity Monitor never sticks
Every “kill it” guide ends at the same wall, and the wall is architectural. Since macOS 10.15 Apple keeps system content on “a dedicated, isolated volume”, and from macOS 11 that volume is cryptographically signed: the SSV “features a kernel mechanism that verifies the integrity of the system content at runtime and rejects any data without a valid cryptographic signature from Apple”. Deleting an extension that lives there is not a difficult operation — it is not an available one.
Quitting it is available, and it lasts seconds. On the Apple Community thread a user describes the process “restarting, almost immediately” after each Force Quit. The one report of a lasting result is blunter: “what worked for me was a full system restart” (August 2024, macOS 14).
That is also why the Tahoe-era patch aims at WallpaperAgent rather than the extension. Its README claims “the service was renamed to WallpaperAgent” — and that claim is wrong, worth correcting because it is being copied. WallpaperAgent already appeared in the Ventura and Sonoma-era process listings, side by side with WallpaperVideoExtension, at /System/Library/CoreServices/WallpaperAgent.app/. The agent and the extension coexist, and have since 2023. Killing either buys a reprieve, not a fix.
What Mac+ changes, and what it doesn't
The reason this process shows up in a CPU list at all is that a video wallpaper has to be decoded frame after frame for as long as it plays. Mac+ takes the other route: its scenes are drawn live on the GPU with Metal, so there is no file being decoded and no clip to fetch. The full comparison, with measurements, is handled separately in do animated wallpapers drain your MacBook’s battery?
Now the honesty. Mac+ does not disable WallpaperVideoExtension, does not patch it and could not touch it if it wanted to — the signed system volume applies to every app equally. It removes the reason to run an Apple video wallpaper; it does not remove the extension. And if the load comes from WindowServer or anything else above, a wallpaper app changes precisely nothing. Diagnose first, install second.
For the record: free to use, €1.99/month or €9.99 once for the paid tier, macOS 13 or later, Apple Silicon and Intel. If the native route is what you want, setting a video as your wallpaper and live wallpaper on multiple monitors cover it in detail.
Bring the load down, in order
- Identify the real line. Open Activity Monitor, choose the CPU tab and sort by % CPU, then look for four possible names: WallpaperVideoExtension, WallpaperAerialsExtension, WallpaperAgent, and a row carrying your wallpaper’s own name followed by “(Wallpaper)”. Double-click the row to open the process inspector.
- Note your exact macOS version, from the Apple menu > About This Mac. Without the build number no community report is comparable to yours — everything published so far is 14.x or 15.x.
- Check WindowServer in the same list. If it sits above the wallpaper process, your problem is not the wallpaper and the rest of this list does not apply to you.
- Turn on “Show on all Spaces” in System Settings > Wallpaper — Apple’s own label on macOS Tahoe 26. Wait about two minutes, then read Activity Monitor again. This is the most-cited workaround, reported on Sonoma in May 2025 by a user whose CPU “went down to zero”; free to try, unconfirmed on macOS 26, and no source explains why it would work.
- Decouple the screen saver. If your wallpaper is an aerial, Apple states it is used as your screen saver by default — picking a different screen saver separates the two consumers.
- Switch temporarily to a still image and read the load again. This is not the fix, it is the causality test: if the load drops, the video subsystem is genuinely responsible.
- Restart the Mac. One user on the Apple thread reports that only a full restart resolved his case. If the load returns in every session, you are looking at a bug to report to Apple, not a setting to find.
- Reclaim disk space knowingly. The .mov files run 450–500 MB each; on macOS 26 they sit in ~/Library/Application Support/com.apple.wallpaper/aerials/videos/, and the older /Library/Application Support/com.apple.idleassetsd/Customer/4KSDR240FPS/ can survive the upgrade. Back up first, touch only the folder inside your home directory, expect macOS to re-download on demand — and note that this frees disk, not CPU.
macOS 13 or later. Apple Silicon and Intel. Free tier, no account required — €1.99/month or €9.99 once for the paid tier.
Frequently asked questions
What is WallpaperVideoExtension on Mac?
It is an Apple system extension that renders video wallpapers on macOS. The binary lives at /System/Library/ExtensionKit/Extensions/WallpaperVideoExtension.appex/Contents/MacOS/WallpaperVideoExtension, alongside WallpaperImageExtension for still wallpapers and, on macOS 26, WallpaperAerialsExtension for Tahoe's aerial clips. It is started and managed by macOS, not by anything you installed.
Why is WallpaperVideoExtension using so much CPU?
Because a video wallpaper has to be decoded continuously while it plays. Users on Apple's forums reported 20 to 100 % CPU on macOS 14 (readings posted between March and August 2024, on M1, M2 Pro and M3 machines) and up to 1 GB of RAM in October 2023. All those figures are Sonoma-era: there is no published measurement of this process on macOS 26.
Can I delete or disable WallpaperVideoExtension?
No. It sits on the signed system volume, which Apple describes as verifying system content at runtime and rejecting “any data without a valid cryptographic signature from Apple”. You cannot remove or edit it. Quitting it in Activity Monitor works for a moment — users describe it “restarting, almost immediately” — so the practical levers are your wallpaper and screen saver choices, not the process.
Is WallpaperVideoExtension a virus?
No, it is a signed Apple component that ships with macOS. You can confirm it yourself from the path: legitimate copies live inside /System/Library/ExtensionKit/Extensions/, on the read-only system volume that nothing can write to. A file with a similar name anywhere else — your home folder, /Applications, a downloads directory — would not be this extension.
What's the difference between WallpaperVideoExtension, WallpaperAerialsExtension and WallpaperAgent?
WallpaperVideoExtension decodes video wallpapers and WallpaperAerialsExtension handles Tahoe's aerials on macOS 26, which is why searching only for the first name on 26.x often finds nothing. WallpaperAgent is the service that drives the set; contrary to a widely copied claim, it is not a renamed extension — it appeared in process listings back in the Ventura and Sonoma era, side by side with WallpaperVideoExtension.