Discord Screen Share Audio Not Working? Complete Fix Guide
Struggling with Discord screen share audio not working? This step-by-step troubleshooting guide covers every fix—from permissions to hardware settings—for Windows, macOS, and Linux.
September 10, 2026 · 1377 views
If you've ever tried to share your screen on Discord only to realize no audio is coming through—whether it’s game sounds, video playback, or system notifications—you're not alone. Discord screen share audio not working is one of the most common yet frustrating setup issues users face during live demos, study sessions, gaming streams, or remote collaboration. The good news? In over 90% of cases, it’s not a Discord bug—it’s a configuration, permission, or driver issue that can be resolved quickly with the right steps.
This complete fix guide walks you through everything—from basic checks to advanced troubleshooting—across Windows, macOS, and Linux. Whether you're a streamer, educator, student, or team lead setting up your first Discord server, this tutorial gives you the clarity and control you need to get audio sharing working reliably. 🎧✨
Why Discord Screen Share Audio Fails (Common Causes)
Before diving into fixes, understanding why audio fails helps you diagnose faster:
- ❌ Missing audio capture permission (especially on macOS Ventura+ and Windows 11)
- ❌ Incorrect audio source selection in Discord’s Voice & Video settings
- ❌ Outdated or buggy audio drivers (e.g., Realtek, Intel SST, or USB headset firmware)
- ❌ Hardware-accelerated GPU scheduling or exclusive mode conflicts (Windows)
- ❌ macOS Screen Recording + Microphone permissions not granted together
- ❌ Linux PulseAudio or PipeWire misconfiguration
- ❌ Discord running in compatibility mode or as administrator (breaks audio hooking)
Let’s tackle each systematically.
✅ Step-by-Step Fixes (By OS)
🔹 Windows: Full Audio Capture Setup
Discord relies on Windows’ built-in audio loopback API to capture system audio during screen share. Here’s how to verify and enable it:
- Open Discord Settings → Voice & Video → Scroll down to Screen Sharing
- Ensure "Share computer sound" is toggled ON (this is the #1 missed step!)
- Under Audio Subsystem, try switching from
StandardtoLegacy(or vice versa)—some Realtek drivers respond better to Legacy mode - Go to Windows Settings → Privacy & Security → Microphone → Confirm Discord has microphone access ✅
- Also check Windows Settings → Privacy & Security → App Permissions → Screen Recording → Enable for Discord
- Update audio drivers: Press
Win + X→ Device Manager → Expand Sound, video and game controllers → Right-click your audio device → Update driver - (Advanced) Disable exclusive mode: Right-click the speaker icon → Sounds → Playback tab → Double-click your default device → Advanced tab → Uncheck "Allow applications to take exclusive control"
💡 Pro Tip: If you’re using NVIDIA ShadowPlay or OBS simultaneously, close them—they often hijack audio endpoints and block Discord’s loopback.
🔹 macOS: Permissions & Architecture Gotchas
Apple’s strict privacy model means Discord needs two separate permissions—and both must be granted after installation (not just once):
- Open System Settings → Privacy & Security → Screen Recording
- Toggle ON Discord ✅
- Still in Privacy & Security, scroll down to Microphone
- Toggle ON Discord ✅
- Restart Discord completely (not just quit—use
Cmd + Q, then relaunch) - In Discord: User Settings → Voice & Video → Set Input Device to your system output (e.g., "MacBook Pro Speakers") — yes, input device should reflect your output for system audio capture
- Try selecting "Application Audio" instead of "System Audio" in the screen share pop-up (available in Discord Stable v1.0.9000+)
- If using macOS Sonoma or later, ensure "Use Hardware Acceleration when available" is enabled in Discord Settings → Advanced
⚠️ Note: On M-series Macs, some third-party audio utilities (like SoundSource or Boom 3D) interfere with loopback. Temporarily disable them to test.
🔹 Linux: PulseAudio & PipeWire Deep Dive
Linux users often hit audio routing walls because Discord doesn’t natively support PipeWire’s new API yet—but there’s a reliable workaround:
- First, confirm your audio server: Run in terminal:
pactl info | grep "Server Name"
- If it says
PulseAudio, skip to Step 2 - If it says
PipeWire, installpipewire-pulse(if missing) and restart your session
- Install
pavucontrol(PulseAudio Volume Control):
sudo apt install pavucontrol # Debian/Ubuntu
sudo dnf install pavucontrol # Fedora
- Start a screen share in Discord → immediately open
pavucontrol - Go to the Recording tab → Find Discord → Change its monitor source from Built-in Audio Analog Stereo to Monitor of [Your Output Device] (e.g., Monitor of Built-in Audio Analog Stereo)
✅ This redirects Discord to capture what your speakers are playing—not your mic.
- Bonus: For persistent fixes, add this to
~/.profile(for PipeWire users):
export PULSE_SERVER=unix:/run/user/$(id -u)/pulse/native
Then log out/in.
🛠️ Universal Quick-Fix Checks (All Platforms)
Try these before diving into OS-specific steps:
- Restart Discord — Fully quit (
Ctrl/Cmd+Q), wait 5 sec, reopen - Test in a new voice channel — Sometimes cached channel settings break audio routing
- Disable all other audio apps (Zoom, Spotify, Teams, etc.)
- Check Discord’s audio test feature: In Voice & Video → scroll to Input Sensitivity → Click Let’s Check → Speak and play system audio (e.g., YouTube) → see if bars move for both mic and system
- Switch to the Discord Canary or PTB build — These often include early audio stack patches not yet in Stable
📊 When It’s Not You: Known Discord Bugs & Workarounds
As of September 2026, Discord’s audio subsystem has two documented edge cases:
- Bug #DC-8842: Audio drops after >12 minutes of continuous screen share on Windows 11 23H2+ (fixed in Canary v1.0.9215+)
- Bug #DC-8901: M1/M2 Macs fail to capture Safari tab audio unless "Application Audio" is selected before joining voice
📌 Workaround: Use DiscordCraft’s community-maintained audio troubleshooting checklist—it includes real-time status updates on active bugs and verified patch workarounds used by 12K+ server admins.
## Quick Tips for Long-Term Stability
- 🎯 Always use the latest stable Discord client—auto-updates are critical for audio reliability
- 🎯 Assign a dedicated audio device (e.g., USB DAC) only for Discord—avoid shared Bluetooth headsets for screen share
- 🎯 In large servers, mute yourself before starting screen share—prevents echo loops
- 🎯 Use
@everyonesparingly during audio shares—notification pings cause brief audio stutters - 🎯 Bookmark Discord’s official Audio Troubleshooting Page for fast reference
❓ FAQ: Top Questions Answered
Q: Does Discord screen share audio work on mobile? A: No—iOS and Android screen share only transmits video. System audio capture is desktop-only due to OS restrictions.
Q: Can I share audio from one app only (e.g., just Chrome, not Slack)? A: Yes! On macOS (v1.0.9000+) and Windows (with Discord Canary), select "Application Audio" before sharing, then choose the target app window—not full screen.
Q: Why does my mic cut out when I enable "Share computer sound"? A: Discord defaults to either mic or system audio—not both—unless you enable "Use Dual Audio" in Voice & Video > Advanced. Toggle it ON to transmit both simultaneously.
Q: Is there a way to record Discord screen share with audio locally? A: Yes! Tools like OBS Studio (with Virtual Audio Cable on Windows or BlackHole on macOS) let you route Discord’s output into a local recording track—great for tutorials and moderation logs.
Final Thoughts
Fixing Discord screen share audio not working doesn’t require coding skills or deep system knowledge—it just takes methodical verification and awareness of platform-specific guardrails. Whether you’re launching your first study group, onboarding a remote teammate, or streaming code live, getting audio right builds trust, clarity, and engagement in your Discord server.
And remember: if you manage a growing community, consider documenting your audio setup in a pinned channel or wiki—saving future members (and yourself!) hours of troubleshooting. 🌐🔧
Got a unique setup (e.g., dual GPUs, VM-based Discord, or custom audio routing)? Drop it in the comments—we’ll help tailor a fix. And for ongoing best practices, DiscordCraft offers free, community-vetted setup templates for education, dev teams, and creative studios.