Hardware Acceleration Firefox: Fix Flicker, Black Screens, and Crashes

Leave hardware acceleration enabled unless Firefox shows a repeatable graphics fault. It lets Firefox use your computer's graphics processor (GPU) for compositing, WebRender, animation, and some video decoding, taking that work away from the CPU.

Usually, that is better. Scrolling should feel smoother, demanding web applications can render faster, and video playback may consume less CPU power. Mozilla enables the feature where its compatibility checks approve the GPU and graphics driver, although its Firefox performance settings documentation↗ says disabling it may resolve video trouble and driver-related crashes.

Keep it enabled if pages render correctly, YouTube runs smoothly, and Firefox does not produce unexplained power use. Seeing a GPU process in Task Manager is normal. The browser has graphics work to do.

Test it disabled if the same fault returns after a restart:

• A window, menu, or web page flickers.
• Video turns black while audio continues.
• Firefox crashes when opening video or WebGL content.
• Text, tabs, or page content render as blocks or corruption.
• GPU usage or laptop power consumption stays high on an idle page.

Do not disable acceleration merely because GPU activity appears in a system monitor. That proves almost nothing. The setting will not repair buffering, a slow connection, a broken extension, or a damaged video file either, because none of those failures begins in the browser's graphics pipeline.

Disable acceleration once, restart Firefox, and reproduce the exact page or action that failed. If the symptom vanishes with acceleration off and returns after you re-enable it, the graphics path is the likely cause.

Restart first. Changing the checkbox does not rebuild the running browser instance, so a test conducted in the same session tells you very little.

1. Open Mozilla Firefox.
2. Open the menu and select Settings.
3. In General, scroll to the Performance section.
4. Clear Use recommended performance settings.
5. Clear Use hardware acceleration when available.
6. Quit every Firefox window, reopen the browser, and repeat the failing action.

Keep the conditions fixed: same URL, same video resolution, same window size, same monitor. A vague impression that Firefox “seems better” is not a diagnosis. Black video that occurs only in fullscreen, for example, may implicate a display overlay, a multi-monitor configuration, or the graphics driver rather than video decoding itself.

Now open about:support. Under Graphics, record Compositing, WebRender, Decision Log, GPU 1, GPU 2, and any failure reason before changing more settings. Mozilla identifies about:support as the browser's Troubleshooting Information page↗, and its decision log is more useful than guessing whether hw acceleration is running.

No change? Re-enable acceleration. Try Troubleshoot Mode next, since an extension or custom theme can damage page content and video behavior without involving the GPU at all.

Update the graphics driver, Firefox, and the operating system before settling for software rendering. If corruption persists after those updates, the cause is probably a driver regression, an unsupported graphics configuration, or failing hardware rather than the checkbox itself.

Begin with the driver supplied by Intel, AMD, Nvidia, or the computer manufacturer. Windows Update may offer a functional package that is months behind the vendor release. Laptop makers complicate matters further, because switchable graphics sometimes depends on their customized driver.

Check the common causes in this order:

• Old or damaged driver: install the current supported package, reboot, then test with acceleration enabled.
• Two-GPU mismatch: on a laptop with integrated and discrete graphics, assign Firefox to the other GPU under Windows Settings > System > Display > Graphics.
• Extension interference: open Help > Troubleshoot Mode. It temporarily disables extensions, hardware acceleration, and some customizations, so run a separate acceleration test afterward to isolate the variable.
• Corrupt Firefox profile: create a temporary profile through about:profiles. Do not refresh or delete the working profile until the clean instance proves the problem is profile-specific.
• System-wide artifacts: if corruption also appears on the desktop, in games, in Chromium, or on firmware screens, stop tuning Firefox. Check the cable and temperatures. If artifacts remain, repair or replace the GPU.

Mozilla's graphics driver repair instructions↗ cover the usual update routes on Windows, macOS, and Linux. Avoid random driver-download sites. An unsigned installer is a much larger problem than choppy scrolling.

A very old GPU can remain blocked even after receiving its newest available driver. The block is deliberate. Forcing WebRender or another disabled feature through about:config may exchange visible corruption for crashes, while leaving behind a custom config change that muddies every later test.

Black video after acceleration is disabled usually points to decoding, DRM, an extension, or the display path rather than Firefox compositing. Test a normal non-DRM clip and Troubleshoot Mode before changing obscure media preferences.

Audio still playing is a useful clue. Check whether every player fails or only one protected streaming service, because DRM content takes a different route from an ordinary HTML5 video and may be disrupted by a privacy extension, an ad blocker, or a damaged Widevine component without displaying an obvious GPU error.

Split the fault this way:

• One site fails: clear that site's cookies and cache, disable extensions for it, and compare another browser.
• Only protected content fails: open Settings > General > Digital Rights Management (DRM) Content and confirm protected playback is allowed.
• Every video fails: inspect about:support, update the driver, and test a fresh profile.
• Only fullscreen fails: use one monitor, temporarily disable variable refresh features, and try another display refresh rate.
• The whole Firefox window turns black: treat compositing or the graphics driver as the leading suspect.

Do not begin by flipping media.*, WebRender, or VA-API preferences copied from an old forum answer. Firefox changes which config variables are implemented. A stale override, meanwhile, can survive several upgrades and keep doing damage long after you have forgotten setting it. Modified preferences appear in bold within about:config and can be reset with the curved-arrow button.

Did the failure begin directly after an update? Preserve the about:support graphics details, then test the current release with a clean profile. Do not keep an old browser version as the fix, since a downgrade also discards later security changes.

Linux needs a supported OpenGL stack for WebRender and a functioning VA-API path for hardware video decoding. Firefox requires a GPU with support for OpenGL 3.2 or newer for its accelerated rendering path, but successful page rendering does not prove that video decode is GPU-powered.

That distinction matters. WebRender handles page rendering and compositing. VA-API video decoding moves a supported codec from the CPU to graphics hardware. Either path can work while the other remains blocked.

Open about:support and inspect Compositing along with the HARDWARE_VIDEO_DECODING entry in the media or decision information. Software decode during YouTube playback may be entirely correct if the GPU cannot handle the codec being delivered, since AV1, VP9, and H.264 support changes with the GPU generation, graphics driver, Linux distribution, packaging format, and sandbox setup.

Keep the normal browser settings at their defaults before adding config preferences or environment variables. Then inspect the platform beneath Firefox:

• Mesa users should update the distribution's Mesa and VA-API packages together.
• Proprietary Nvidia drivers need a compatible decoding setup; instructions written for Intel VA-API are not interchangeable.
• Wayland and X11 can expose different render paths, so record the Window Protocol listed in about:support.
• Flatpak and other sandboxed installations need matching runtime graphics components, not just drivers installed on the host.

The Arch Linux Firefox reference↗ documents WebRender, VA-API, Wayland, and driver-specific complications in one maintained page, though its package names and defaults do not transfer unchanged to Fedora, Ubuntu, or every other platform.

Green frames or crashes after a VA-API change mean stop. Reset the preferences you altered and accept software decoding until the driver stack is repaired. A forced decoder that corrupts content is no acceleration at all.