← All processes

macOS process library · Photos and media

What is VTDecoderXPCService on Mac?

VTDecoderXPCService decodes video on behalf of apps. When a browser plays a video, or you’re on a video call, the app hands the compressed stream to macOS’s VideoToolbox framework, and this service turns it into frames, using your Mac’s dedicated media hardware when the format allows.

Part of
VideoToolbox, macOS’s video encoding and decoding framework.
Safe?
Yes. It lives inside macOS’s VideoToolbox framework in /System/Library.
Can I quit it?
Yes, but whatever video is playing stops or stutters until the app starts it again. Close the video instead.

The short answer

VTDecoderXPCService runs whenever something plays video, so seeing it is normal. High CPU means it’s doing a lot of decoding, often several videos at once, very high resolutions, or a format your Mac has to decode in software. Closing or pausing the video brings it down immediately.

Normal use

What VTDecoderXPCService usually looks like.

Watching a single video, it typically uses a few percent of CPU, because Apple silicon decodes common formats like H.264 and HEVC in hardware. You may see more than one copy, one for each app playing video.

It’s busier with 4K and higher resolutions, several videos at once, and formats your Mac’s media engine doesn’t support.

Why VTDecoderXPCService uses so much CPU or memory

How to calm VTDecoderXPCService down

Start at the top. Each step is more disruptive than the one before.

  1. Pause or close video you aren’t watching

    Background tabs with autoplaying video are a common cause. Closing them stops the decoding.

  2. Lower the resolution

    On streaming sites, choosing 1080p instead of 4K cuts the decoding work considerably.

  3. Try Safari for streaming

    Safari uses macOS’s hardware decoding directly. If a video is heavy in another browser, compare it in Safari.

  4. Check your browser’s graphics acceleration

    In Chrome, Settings → System → Use graphics acceleration when available should be on, so video can use hardware decoding.

Seeing it in Spare

Find what it’s reacting to.

VTDecoderXPCService does work for whichever app is playing video, so its numbers make more sense next to that app. Spare shows your browsers and video call apps with all their helpers counted together, so you can see which one is behind the decoding.

Spare lists VTDecoderXPCService as part of macOS and never offers to stop it.

SpareMemory pressure · Normal
◎
VTDecoderXPCServicemacOS · Photos and media
14% CPU120 MB
◎
Google ChromeApp · 28 processes
22% CPU3.8 GB
◇
zoom.usApp · 4 processes
16% CPU690 MB
Illustration with example readings

Common questions

About VTDecoderXPCService

Why are there several VTDecoderXPCService processes?

Each app that plays video can get its own copy, so a browser, a video call app, and Photos may each have one.

Is VTDecoderXPCService safe?

Yes. It’s part of Apple’s VideoToolbox framework. It only does the decoding that apps ask macOS to do.

Why does it use more CPU on some websites?

Sites choose which video format to send. If they send one your Mac decodes in software, or a very high resolution, decoding costs more.

What’s the difference from VTEncoderXPCService?

The encoder does the opposite job: compressing video, for screen recording, video calls from your camera, or exporting.

Related processes

Sources: Apple Developer: VideoToolbox. Reviewed October 13, 2026.

Get Spare

Free to use. Yours to explore.

Download Spare for Apple silicon, or explore the MIT-licensed source on GitHub. Free to use, with no subscription or account.

macOS 14+ · Apple silicon · Signed and notarized