Leave hardware acceleration on unless you have a reason to switch it off. Turn it off when screen shares tear or go black, when Discord crashes alongside the GPU driver, or when streaming while you play costs you frames. Discord’s own guides put the toggle under User Settings, Voice and Video, Video.
At a glance
- Class
- Gaming
Provenance
- Nov 16, 2026Published
TL;DR · Discord hardware acceleration
- Default: leave it on. It moves compositing and video work onto the GPU, which is usually the cheaper place for it.
- Turn it off for a symptom, not for a feeling: broken screen shares, video that will not render, crashes that line up with a driver event, or lost frames while streaming.
- Where it lives: User Settings > Voice and Video > Video tab, then scroll to Hardware Acceleration. Older guides say User Settings > Advanced.
- Relaunch the client and retest the exact thing that failed. One change, one observation.
Discord runs on Chromium, and Chromium draws its interface with the GPU by default. That is the whole point of the hardware acceleration switch: when it is on, the client hands compositing and video decoding to the graphics card instead of doing that work on the CPU. It is a good default, and most people should never touch it.
The exceptions are real, though, and they are specific. When the picture breaks in a particular way, or when the client is fighting a driver for the same GPU you are trying to game on, the switch is the first thing worth changing. What it is not is a general performance setting to flip because a video said so.
What the switch actually changes
Discord describes itself as “based on chromium which has a multi-process model”, and lists the processes you will see in Task Manager: a main process, a renderer, a crash reporter, a GPU process and the overlay. That lineage matters because it tells you what the toggle controls. This is Chromium’s GPU compositing being turned on or off inside a chat application, not a Discord-specific graphics feature.
Chromium’s own design document on GPU accelerated compositing explains the architecture: renderers are sandboxed and cannot call the operating system’s 3D APIs directly, so a separate GPU process receives commands, parses them, and executes them through OpenGL or Direct3D. Content is split into layers, tiled, and rasterized either by software rasterizers in worker threads or directly on the GPU. Turning acceleration off moves that work to the software path.
Two consequences follow, and both are practical:
- The GPU process does not disappear. Discord’s article on its processes says so explicitly: the GPU Process is listed “even with hardware acceleration turned off”. If you disable the option and still see a GPU process, the setting applied. Do not use that as evidence that nothing changed.
- The work moves rather than vanishing. Software compositing keeps CPU cores busy. On a machine that is already CPU-limited, that is a worse trade than a GPU that has headroom.
Electron, the framework that packages Chromium into desktop apps like this one, exposes the same thing as an application-level switch in its API reference. The label in the settings menu is friendlier than the mechanism, but it is the same mechanism.
Turn it off when the picture breaks
Discord’s own troubleshooting documents recommend disabling hardware acceleration for a fairly narrow set of failures, and they are worth reading as a list rather than a slogan.
| Symptom | What Discord’s guides say | What it suggests |
|---|---|---|
| Screen share tears, goes green, or shows black blocks | Disable hardware acceleration under the Video tab when screen sharing fails | The capture and encode path is the suspect |
| Video inside the client will not render | Disable it under Voice and Video, Video tab, Advanced section | Decode path rather than network |
| Stream lags while you play | “If you have Hardware Acceleration on, and you find your stream is lagging, please try disabling this setting” | The game and the stream are competing for the GPU |
| Client freezes on the loading screen | The general guide lists disabling it under User Settings, Advanced | Older UI location, same switch |
That third row is the one that matters most on a mid-range or older graphics card. Streaming a game means the encoder, the game renderer and the client’s compositor all want the same GPU. Discord’s Voice, Video and Streaming guide treats disabling the setting as a legitimate step when a stream lags, and the same guide walks the path: the cogwheel at the bottom left, then Voice and Video, then the Video tab, then the Hardware Acceleration row.
The second row belongs to the Voice and Video troubleshooting guide, which sends video problems to the same place and describes the option as sitting in an Advanced section of that Video tab. If your build shows it there rather than under a top-level Advanced page, that is why.
Crashes deserve their own paragraph, because the evidence standard is higher. A client that closes at the same moment the Windows log records a display driver recovery is a reasonable case for turning acceleration off — the TDR pattern is that the driver was reset, and a renderer that was mid-composite does not always survive it. A client that crashes with acceleration off as well is a different fault, and the Discord not opening guide is the better lane.
Leave it on unless something is wrong
There are four good reasons to leave the setting alone.
Your GPU has headroom. Compositing a chat window is trivial work for any discrete card and for most integrated ones. Moving it to the CPU buys nothing you can see and spends cycles you might want elsewhere.
Your CPU is the limit. On an older quad-core, or on any machine running a game that already pins the processor, software compositing adds work to the component that is already the bottleneck. That is the opposite of what you want.
The UI stays smoother. Scrolling a long channel list, animating the member sidebar, and playing an embedded video all use the same path. Chromium’s document notes that hardware compositing is skipped when drivers are blocklisted or no GPU exists, which is the situation the software path is designed for — not a normal desktop.
Laptops. Turning acceleration off shifts work to the CPU, and on a laptop that trade can cost battery life. Whether it does on your machine is worth measuring rather than assuming, because the result depends on the panel, the refresh rate and the power plan as much as on the client.
None of this means the setting is sacred. It means the default is right until a symptom says otherwise.
The exact path in the current client
- Click the cogwheel next to your name at the bottom left of the window to open User Settings.
- Open Voice and Video.
- Select the Video tab and scroll down to the Hardware Acceleration row.
- Clear the check box to turn it off. Tick it to turn it back on.
- Quit Discord completely — from the tray, not just the window — and reopen it.
Step 5 is not optional. Discord’s streaming sequence lists restarting the app and the device immediately before the hardware acceleration step, and a running client keeps using whatever it started with. If you toggle the box and immediately retest, you are testing the old configuration.
The path has moved over the client’s life, which is why guides disagree. Discord’s general troubleshooting guide still tells readers to “Disable hardware acceleration in User Settings > Advance” for loading-screen freezes. That is not wrong so much as old: it describes where the option sat in earlier builds. The Video-tab path is what the current guides describe, and it is what I would look for first.
Test the change instead of guessing
A settings toggle is only useful if you can tell whether it helped, and the way to do that is to reproduce the original failure deliberately.
- Write down the symptom in observable terms: “screen share of a full-screen game shows green blocks after about two minutes”, not “streaming is bad”.
- Record the client version and the driver version. Both change often, and a fix that depends on one of them is worth knowing about.
- Reproduce it once before you touch anything, so you know it still happens.
- Change only the hardware acceleration setting, then relaunch.
- Reproduce the same scenario with the same game, resolution and window mode.
- Revert if nothing changed. A setting you changed without evidence is a variable you will trip over later.
If the symptom clears with acceleration off and returns when you switch it back on, you have a usable answer and a clean trade to make. If it behaves the same either way, the switch is not involved, and the next suspects are the game’s display mode, the capture path and the driver.
When the toggle is not the answer
Three other problems get mistaken for this one.
A client that will not start. If Discord never reaches the login screen, or closes during its own launch, hardware acceleration cannot be the cause — the setting is loaded later. Follow the launch failure guide instead.
Stutter in the game rather than in the stream. If your frame times wobble whether or not Discord is running, the client is not your problem. The stuttering guide sorts frame pacing from low frame rate, and hardware-accelerated GPU scheduling has its own on-or-off decision that is separate from this one.
A picture problem that only appears in the game. Tearing and sync behaviour are governed by your display settings, not by Discord. The V-Sync decision covers that, and it is a different set of switches in a different place.
My rule is simple: leave the box ticked, and change it only when you can name the symptom it is supposed to fix. If you cannot name the symptom, you do not have a reason yet.
Frequently asked questions
Should Discord hardware acceleration be on or off?
Where is the hardware acceleration setting in Discord now?
Do I need to restart Discord after changing it?
Does turning hardware acceleration off remove Discord’s GPU process?
Will turning it off fix a black or green screen share?
Does hardware acceleration lower Discord’s CPU usage?
Can hardware acceleration cause Discord to crash?
Is this the same as hardware-accelerated GPU scheduling?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 6 cited sources, listed below, each checked against the original page on the date above. The menu paths and the reasons to change this setting come from Discord’s own support articles, all read on 2026-11-16: the general troubleshooting guide, the Voice and Video troubleshooting guide, and the Voice, Video and Streaming guide. Discord’s article on its multiple processes supplies the Chromium lineage and the statement that the GPU process remains with hardware acceleration off. The Chromium design document on GPU accelerated compositing supplies the mechanism, including the software fallback used when drivers are blocklisted, and Electron’s API reference confirms that a Chromium-based application exposes hardware acceleration as an application-level switch. Menu labels are quoted as Discord writes them, and the article names the older Advanced location rather than pretending it never existed. No performance figures are given, because none were measured here.
- Sources
- Discord Support: Discord Troubleshooting Guide (hardware acceleration for loading screen freezes) accessed 2026-11-16
- Discord Support: Discord Voice and Video Troubleshooting Guide (video and screen share hardware acceleration steps) accessed 2026-11-16
- Discord Support: Discord Voice, Video, and Streaming Guide (stream lag and the hardware acceleration steps) accessed 2026-11-16
- Discord Support: Why does Discord have multiple processes? accessed 2026-11-16
- Chromium: GPU Accelerated Compositing in Chrome (design document) accessed 2026-11-16
- Electron: app API reference, disableHardwareAcceleration accessed 2026-11-16
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.