Watch a 1080p clip in Firefox and the fan spins up, the video stutters, and scrolling the comments feels like dragging through mud. On some setups a few hidden settings close most of that gap. None of it costs money or installs anything.
Why does YouTube run rougher in Firefox than in Chrome? Chrome, Edge, and Brave are all built on the same Chromium engine, and YouTube is primarily developed and tested against Chromium. Firefox uses its own engine, Gecko, so the same page can hit different video, codec, and driver paths. The settings below check or enable hardware paths that can help on some systems. They will not help every machine, because Firefox already turns some of them on by default, but on the setups where they are still off they can make a real difference.
One warning before you touch anything. Most of these live in about:config, Firefox's hidden settings page, which you reach by typing that into the address bar. A couple can cause glitches on some hardware. If video breaks after a change, flip the setting back. That's the whole undo button.
Turn on the layer compositor
The layer compositor hands more of the page-compositing work to the operating system and graphics chip through hardware overlays, instead of having Firefox redraw and composite everything itself. On the systems it helps, scrolling can get smoother and laptops use less battery. Firefox already turns this on by default on Windows, so the tweak mainly matters on the builds where it is still off.
Open about:config, search for "gfx.webrender.layer-compositor", and set it to true. Restart Firefox so it takes effect. The exact name matters here. There is a separate, older setting called "gfx.webrender.compositor.force-enabled" that some guides point at, and it controls a different compositor path, so do not confuse the two. If the page starts rendering wrong after the change, set the layer compositor back to false.
Cut CPU use on AMD chips
Got an AMD graphics chip on Windows, especially the kind built into a laptop? One setting can force Firefox's hardware-decoded zero-copy path, which skips an extra video-frame copy and can cut CPU use on systems where that path is otherwise blocked. Search about:config for "media.wmf.zero-copy-nv12-textures-force-enabled" and set it to true.
This one is a Windows-only path. The "wmf" stands for Windows Media Foundation, so it does nothing on Linux or macOS, and it is aimed at AMD hardware rather than Intel or Nvidia. If playback looks worse afterward, set it back to false.
Drop AV1 on older machines
YouTube often serves video in AV1, a newer format that squeezes files smaller. That is fine if your hardware can decode it directly. The first mainstream GPUs with built-in AV1 decoding shipped around 2020, including Nvidia's RTX 30 cards, AMD's RX 6000 line, and Intel's Tiger Lake laptop chips. Anything older has to decode AV1 in software on the main processor, which can raise CPU use and cause stutter, especially at 1080p or 1440p.
If AV1 is being software-decoded on your machine, turning it off can make YouTube fall back to another supported format, often the older VP9, which may help if your hardware decodes that format directly. In about:config, find "media.av1.enabled" and set it to false. To check what your machine is doing, open about:support and look at the media section. But if your GPU handles AV1 directly, leave it alone, because the hardware AV1 path is the faster option there.
Make sure hardware decoding is on
Hardware video decoding lets your graphics chip handle the video instead of the main processor. It's lighter on battery and keeps the fan quiet during 4K playback. On current Firefox builds this is already on by default, so this step is a check rather than a change. Search about:config for "media.hardware-video-decoding.enabled" and confirm it reads true.
One note for Linux folks. That same setting now covers VA-API, the Linux method for graphics-chip decoding. Mozilla turned on Intel GPU video decoding by default in Firefox 115 in July 2023, though whether it is on out of the box can still depend on your Linux distribution's Firefox package. The old separate "media.ffmpeg.vaapi.enabled" switch some guides still mention is gone. Don't go hunting for it.
Fedora Project Firefox acceleration
Check your process settings on older Firefox
Firefox splits your open tabs across several background processes so a single heavy tab, say a 4K video, is less likely to drag down everything else. On current Firefox the old "Content process limit" box under about:preferences is hidden, because Firefox now isolates each site into its own process and manages the count for you. That UI step only exists on much older builds.
If you are on an older Firefox that still shows it, go to about:preferences, scroll to Performance, uncheck "Use recommended performance settings," and adjust the content process limit. On a weaker machine with under 8 GB of memory, lowering it can help, since spawning extra processes eats RAM and starving the system trades one slowdown for another.
Let extensions clean up the page
YouTube's page itself is heavy, and a couple of add-ons trim the fat. uBlock Origin blocks ads and trackers, which cuts the amount of work the page does, so fewer scripts load. Enhancer for YouTube adds playback controls and lets you kill autoplay and other background clutter.
Don't expect miracles from extensions alone. They can block or hide a lot of the page's ads, trackers, and clutter, but they can't fix a slow video decode path. Pair them with the settings above for the real difference.
What to expect
On the machines where these settings were still off, you can get smoother playback, a quieter fan, lower CPU use, and better laptop battery. None of it is a magic fix. Firefox uses Gecko while YouTube gets the most testing on Chromium browsers, so some difference can remain no matter what you do. These changes are low-effort, but Firefox updates do shift defaults and retire old prefs over time, so a setting that mattered today may not matter on a later build.
If video is still rough after all this, check your graphics drivers next. Old drivers on Windows, or an outdated Mesa version on Linux, are a common cause of whatever's left.
