TL;DR: Check discordstatus.com first. For audio: User Settings > Voice & Video > check input/output device. For screen share black screen: disable hardware acceleration. For login: check 2FA, then submit ticket.
I’ve been using Discord since it launched, back when it was mostly just for gaming. These days it’s turned into a general-purpose communication platform for everything from dev teams to book clubs, and the number of ways it can break has grown accordingly. I’ve personally hit most of these issues at some point — and I’ve dug through enough Discord support threads to know which fixes actually work versus which ones just send you in circles.
Let’s get into it.
Fix 1: Voice Chat Not Working / Mic Not Detected
This one trips people up constantly. You join a voice channel, nobody can hear you, and you’re staring at a silent microphone icon wondering what happened.
Open User Settings (the gear icon at the bottom left near your username) > Voice & Video. This is the primary control panel for all audio in Discord.
First check: Input Device. Look at the dropdown under “Input Device.” If it says “Default,” Discord is using whatever Windows or macOS considers the system default. That’s fine unless your system default is wrong — which happens all the time after connecting a new headset, Bluetooth device, or USB audio interface. Change it from “Default” to your specific microphone by name.
Second check: Input Volume and Sensitivity. Below the input device, there’s an input sensitivity slider. If “Automatically determine input sensitivity” is checked, Discord is making a judgment call about what counts as voice versus background noise. Sometimes it gets this badly wrong. Uncheck it and manually set the threshold — drag it left to make it more sensitive.
Still nothing? Try this:
- Switch Input Mode from Voice Activity to Push to Talk. This confirms whether Discord is receiving audio at all. If you hold the push-to-talk key and people can hear you, the sensitivity setting was the culprit.
- Check microphone permissions on your OS. On Windows: Settings > Privacy & Security > Microphone — confirm “Let apps access your microphone” is on AND that Discord is specifically allowed. On Mac: System Settings > Privacy & Security > Microphone — Discord should be listed and enabled.
- Completely restart Discord, not just close and reopen. Right-click the Discord icon in the system tray (Windows) or the menu bar (Mac) and choose Quit Discord, then relaunch.
One thing that catches people off guard: on Windows, after changing privacy settings, Discord often needs a full quit-and-relaunch to pick up the new permissions. Don’t just click the X — use Quit.
Fix 2: Can’t Log In to Discord
Login failures are annoying because there are several different causes and the error messages Discord shows don’t always tell you which one you’re dealing with.
Step one: check discordstatus.com. Not a joke. Discord has real outages, sometimes affecting login specifically. If you see a yellow or red status indicator, you’re just waiting. Bookmark the status page — it’s saved me a lot of troubleshooting time.
If it’s not an outage, check your 2FA. Discord’s two-factor authentication uses an authenticator app (usually Google Authenticator or Authy). If you switched phones and didn’t migrate your authenticator, or if time sync is off on your device, the codes won’t work.
If your codes aren’t working and you have backup codes: enter one of those at the 2FA prompt. Discord gives you 10 when you enable 2FA — they’re single-use, but they’ll get you in.
If you don’t have backup codes: this is where things get slow. Discord’s account recovery for lost 2FA is a support ticket process. Go to discord.com/support and submit a ticket explaining you’ve lost 2FA access. They’ll verify account ownership through your phone number or email and manually disable 2FA. Expect it to take a few days. There’s no shortcut.
Account lockout from failed attempts is the other common one. If you (or someone else) tried the wrong password too many times, Discord will temporarily lock the account. The lockout usually clears after 15-30 minutes. If you’re not sure what your password is, hit “Forgot your password?” on the login page and reset it through your email.
Fix 3: Screen Share Black Screen
Black screen during screen share is almost universally a GPU conflict on Windows. It affects NVIDIA and AMD cards both. The fix is disabling hardware acceleration.
Method 1 (Discord settings): Open User Settings > Appearance. Scroll to the bottom. Find Hardware Acceleration and turn it off. Discord will warn you that this might affect performance — click “Okay.” Fully quit and restart Discord.
Method 2 (Windows compatibility): Right-click the Discord shortcut on your desktop or taskbar. Go to Properties > Compatibility tab. Check “Disable fullscreen optimizations.” Also try “Run this program as an administrator.” Click Apply, then relaunch Discord.
Method 3: GPU overlay conflicts. NVIDIA GeForce Experience’s in-game overlay and NVIDIA Share conflict with Discord’s screen capture in certain driver versions. Open GeForce Experience > Settings (gear icon) > General and turn off In-Game Overlay. Same story with AMD Radeon Software’s overlay — open Radeon Software > Settings > Graphics > Radeon Overlay and disable it.
Method 4: Administrator permissions. Right-click Discord and select “Run as administrator.” On managed or corporate machines, Discord sometimes can’t capture screen content without elevated permissions due to UAC settings.
The hardware acceleration toggle fixes this for most people. If you’ve done all four and still see black, check whether the specific app you’re trying to share uses DRM content protection — Netflix in a browser, for example, will always show black when screen shared. That’s intentional, not a bug.
Fix 4: Notifications Not Showing
Discord’s notification system has multiple layers, and any one of them being misconfigured kills your alerts.
Layer 1: OS notifications. On Windows: Settings > System > Notifications — scroll down to the app list, find Discord, make sure it’s toggled On. Also check that “Focus Assist” isn’t suppressing notifications — Settings > System > Focus Assist. On Mac: System Settings > Notifications > Discord — set alert style to “Alerts” or “Banners,” not “None.”
Layer 2: Discord’s global notification settings. Open User Settings > Notifications. Make sure “Enable Desktop Notifications” is turned on. Also check “Enable Unread Message Badge” if you want the badge count on the app icon.
Layer 3: Server-level notification settings. This is the one people miss. Discord defaults to muting @everyone and @here pings for all servers — but it also defaults to muting regular messages entirely for most servers. To change this: right-click a server name in the left sidebar > Notification Settings. Change “Server Notification Settings” from “Only @mentions” to “All Messages” if you want notifications for everything. Or go channel by channel by clicking the bell icon that appears when you hover over a channel name.
Layer 4: Do Not Disturb / Custom Status. If you set yourself to Do Not Disturb mode (the red circle), Discord suppresses all notifications until you switch back. Click your avatar at the bottom left, and make sure your status isn’t set to DND.
Fix 5: Discord Keeps Crashing
Crashes happen. Usually it’s either corrupted cache files or a memory issue with the Electron app that Discord runs on.
Clear the cache. On Windows: press Win+R, type %appdata%\discord and hit Enter. Find the Cache folder and delete it (or delete everything inside it). On Mac: open Finder, press Cmd+Shift+G, type ~/Library/Application Support/discord and navigate to the Cache folder. Delete it. Discord will rebuild the cache next time it launches.
Delete the GPU cache too. While you’re in that same directory, also delete the GPUCache folder if it exists. GPU cache corruption is a less common cause of crashes but real.
After clearing, restart Discord and see if the crashes stop. Most of the time they do.
If clearing cache doesn’t fix it: Update Discord. The app usually updates automatically when you launch it, but if updates have been failing, you might be running an old build with known bugs. On Windows, open the %localappdata%\Discord folder and look for the Update.exe file. Run it directly to force an update. On Mac, download a fresh installer from discord.com.
If crashes persist: Full reinstall. On Windows, uninstall Discord through Control Panel/Settings, then also manually delete the %appdata%\discord and %localappdata%\discord folders before reinstalling. This clears everything. On Mac, drag Discord to trash and also delete the ~/Library/Application Support/discord folder. Then reinstall from scratch.
Fix 6: Bot Not Responding
Your Discord bot sits there silently, ignoring commands. A few things could be going on.
Slash commands vs. prefix commands. Discord migrated to slash commands (like /help, /play) for verified bots back in 2022, but some servers are still running older bots that use prefix commands (like !help or .play). If a bot isn’t responding to prefix commands, check the bot’s documentation or the server’s pinned messages for the current command format. The bot may have updated and you’re using the old style.
Bot permissions. The most common cause of a bot not responding in a specific channel is missing permissions. The bot needs Read Messages and Send Messages permissions in that channel at minimum. And for some commands — like playing audio in a voice channel — it needs Connect and Speak permissions in the voice channel.
To check: open Server Settings > Roles, find the bot’s role, and check its permissions. Then go to the specific channel’s settings (right-click the channel > Edit Channel > Permissions) and check whether the bot’s role has been restricted at the channel level. Channel-level overrides trump server-level role permissions, so a restriction at the channel level will block the bot even if the server role has full permissions.
Bot is offline. Check whether the bot’s status shows as online in the server member list. If it’s offline, it’s not running — that’s a hosting issue, not a permissions issue. The bot’s developer or the server admin needs to restart the bot’s host.
Wrong server. Sounds obvious, but: bots have to be added to each server separately. If you’ve seen a bot work in another server and expect it in yours, it might not have been invited yet.
Fix 7: Can’t Hear Others
You can talk, but everyone else sounds like silence. Different problem from Fix 1, different fix.
Open User Settings > Voice & Video. This time look at Output Device. Same situation as the input — if it’s set to “Default,” check whether Default is actually pointing to the right device. If you have a headset and speakers both connected, Windows might have recently switched its default output without telling you. Select your headset or speakers explicitly by name.
Check individual user volume. Right-click any user in a voice channel. You’ll see a volume slider specific to that person. If someone accidentally got dragged to 0%, you won’t hear them even if everything else is working fine. Set it back to 100% and see if that’s the issue.
Server deafen. If you see a headphones icon with a line through it next to your username at the bottom, you’ve deafened yourself. Click the headphones icon at the bottom left near your username to toggle deafen off.
Voice region. Occasionally a voice channel’s server region causes audio issues. Server admins can change this: Server Settings > Server Regions > pick a different region geographically closer to most of the users.
Fix 8: Go Live / Streaming Issues
Discord’s Go Live feature (streaming to a voice channel) has its own set of failure modes.
Game not detected. Discord’s Go Live requires Discord to recognize what game you’re running. Open User Settings > Activity Privacy and make sure “Display current activity as a status message” is on. Then check User Settings > Registered Games — your game should appear here automatically when running. If it doesn’t, click “Add it!” and manually select the game’s executable.
Some games don’t get detected because their executable name is non-obvious. For example, some games launch a launcher EXE, not the game itself. You may need to select the actual game process, not the launcher.
Streaming quality settings. Discord limits stream quality based on your Nitro tier. Without Nitro, you’re capped at 720p/30fps. With Nitro Basic, you get 1080p/30fps. Nitro standard goes up to 4K/60fps. If your stream looks blurry to viewers, this is why — it’s not a bug, it’s a tier cap. You can’t work around it without Nitro.
Black screen on stream (different from screen share black screen). Make sure the game isn’t running in exclusive fullscreen mode. Windowed or borderless windowed is what Discord captures most reliably. Some games in exclusive fullscreen can’t be captured at all. Change the game’s display mode to borderless windowed in the game’s graphics/display settings.
Audio not going through on stream. Viewers can hear you speak but not the game audio? Go to User Settings > Voice & Video, scroll to Video Settings, and when the Go Live window is open, check that “Share audio” is enabled. On Mac this requires Discord to have been granted Screen Recording permission in System Settings > Privacy & Security.
If none of this has fixed your specific issue, discordstatus.com should still be your first sanity check on any given day. When Discord itself is having problems, no amount of local troubleshooting is going to help. And honestly — for truly broken login or account issues, Discord’s support ticket system is the only real option. It’s not fast, but it works.
If you’re exploring alternatives to Discord for a team or community, take a look at our rundown of the best Zoom alternatives in 2026 — several of them have voice chat and streaming features worth knowing about.