Skip to main content
uPlayVideo

Hardware Acceleration

Stop burning 40 watts of CPU power to decode a video.

Why GPU Decoding Matters

When a video plays via Software Decoding, your CPU does the math required to unpack the compressed frames. This is highly inefficient. When playing a 4K HEVC file via software, a laptop CPU might draw 30-50 watts, causing fans to spin up and batteries to drain in 90 minutes.

Hardware Decoding passes that math to dedicated silicon on your GPU (like Intel QuickSync, NVDEC, or Apple's Media Engine). The power draw drops to 2-5 watts.

How to Verify Hardware Decoding in Chrome/Edge

You don't have to guess if it's working. Chromium-based browsers give you direct diagnostic tools.

  1. Open a new tab and navigate to chrome://media-internals/ (or edge://media-internals/).
  2. In another tab, open uPlayVideo and start playing your file.
  3. Go back to the internals tab. You will see an active player listed. Click it.
  4. Scroll down the property list and look for video_decoder.

If it says:

MojoVideoDecoder or D3D11VideoDecoder ← Hardware Acceleration is ACTIVE.

VpxVideoDecoder or FFmpegVideoDecoder ← Software Decoding is ACTIVE (CPU).

Common Reasons for Software Fallback

  • Unsupported Codec: Your GPU is too old to support AV1 or HEVC decoding, so the browser falls back to CPU.
  • Disabled in Settings: Ensure "Use hardware acceleration when available" is checked in your browser's system settings.
  • Driver Issues: Outdated Nvidia or AMD drivers on Windows can cause Chromium to blacklist your GPU for media decoding.