Properties2
| Type | Practice |
| Note created | Apr 24, 2026 |
Helium does not include the Widevine Content Decryption Module by default, so DRM-protected streaming services (Netflix, Disney+, Spotify web player, Prime Video, many corporate e-learning platforms) will refuse to play. The fix is to copy the WidevineCdm framework from a Google Chrome install into Helium — and the cleanest way to do that on macOS is with Neon, which also re-patches automatically when either browser updates.
Prerequisites
- Helium installed at
/Applications/Helium.app. - Google Chrome installed at
/Applications/Google Chrome.app— Neon copies the CDM out of it. - Homebrew.
Install Neon
Tap the formula and install:
brew install nicholasraimbault/neon/neonPatch Helium
Quit Helium first, then run:
neon-installThis downloads the latest WidevineCdm, patches every supported browser it finds, and registers a launchd daemon that re-applies the patch on browser updates. macOS will prompt for the sudo password.
Verify
Open Helium and try playback at bitmovin.com/demos/drm, or just open Netflix. If it plays, Widevine is active.
Other useful commands
neon-patch— patch browsers right now (e.g. after installing a new Chromium-based browser).neon-patch --force— re-patch even if already patched.neon-update-widevine— pull the latest WidevineCdm.neon-uninstall— remove the daemon and cached files.
Caveats
- This installs Widevine L3 (software-level), enough for Netflix at 720p, Spotify, Disney+. Studio-provisioned L1 (1080p / 4K) requires per-browser certification that Helium does not have.
- Chrome must remain installed (or at least its
WidevineCdmdirectory) as the CDM source. - This is a gray area under Widevine’s license terms — fine for personal use, do not redistribute the patched binaries.
Alternatives
If you’d rather not depend on a daemon, the same patching can be done one-shot with helium-drm-fixer (a Bun CLI), or manually:
cp -R "/Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Libraries/WidevineCdm" \
"/Applications/Helium.app/Contents/Frameworks/Helium Framework.framework/Libraries/"Both require re-running after every Helium update, which is why Neon is the recommended path.