Discord integration can mean showing a Discord widget in your stream, including call audio in the mix, or giving subscribers and members roles in your server. These are separate tasks: choose the outcome you need before changing OBS or Discord settings.
For a visual overlay, Discord’s Streamkit provides status, chat and voice widgets that you can add to OBS as browser sources. The Streamkit guide covers those visual widgets, not how to route call audio into OBS. Account integrations, meanwhile, manage community roles rather than stream overlays.
Choose the Discord integration you need
Start with what you want viewers or community members to experience. If viewers should see who is in a Discord voice channel, or see selected chat activity, use a Streamkit widget. If people should hear your Discord conversation in the broadcast, that is an audio-routing job and needs a separate setup. If paying supporters should receive access to a Discord server or channel, use the relevant Twitch or YouTube integration, if your account is eligible.
| Goal | Route | What it does not do |
|---|---|---|
| Show voice activity, chat or status | Streamkit widget in an OBS Browser Source | Does not route call audio into OBS |
| Include a Discord call in the programme mix | Separate audio capture and routing configuration | Does not create server member roles |
| Give eligible supporters Discord access | Twitch or YouTube connection and server integration | Does not add an OBS overlay |
A visible voice widget and audible call are especially easy to confuse. The widget can show voice-channel activity, but that display does not mean participants’ voices are present in your OBS audio mix. Test the sound path separately before you go live.
For an always-on YouTube channel, consider whether Discord belongs in every scene or only in a live host or community segment. A devotional loop, study stream or ambience station may benefit from a quiet status display, while an open call may distract from the programme. If you are changing the broadcast mix, review the separate considerations in this guide to adding background music without losing the audio mix.
Add a Streamkit status, chat or voice widget
Discord’s OBS Streamkit Overlay offers three widget types: Status, Chat and Voice. Pick one based on the information you intend to show. A status widget can display server information; chat is for text activity; and voice is for channel and participant status. Their exact presentation depends on the widget options you select.
Open Discord’s OBS Streamkit Overlay instructions and choose the OBS overlay. The instructions call for a current OBS Studio installation. Authorise the overlay through the Discord client when prompted. Discord says this permits the overlay to perform an action in the client; for example, it can generate an invite for a status widget if you choose that feature. You can review connected apps in Discord under User Settings, Connections and Authorized Apps.
Select the server you want to display, then choose Status, Chat or Voice. Adjust the available options and check the preview before copying the installation link. If you want more than one widget, configure each one separately: every widget has its own installation code. Discord says all three can be used together, but that does not mean you need to show all of them. A small, readable display is usually more useful than a crowded scene.
Take care with what a widget exposes. A server name, channel name, participant list or message may reveal information you did not intend to put in a public broadcast. Choose the server and channels deliberately, and review the preview as a viewer would see it. Do not assume a visual element is private simply because it is small on your monitor.
Install the widget in OBS
Once you have the Streamkit installation link, add it to OBS as a Browser Source. Create a new source for each widget you intend to display, paste the relevant link into its URL field, and set the width and height to match the dimensions shown on the Streamkit page. The source is a browser-rendered visual element in your scene; it is not an audio capture source.
Name each source for its purpose, such as “Discord voice status” or “Discord chat”. Clear names make it easier to find the right source later, especially if your scene collection contains several versions of the same overlay. Keep the widget sources distinct from your game, video or audio sources so you can hide or adjust them without disturbing the rest of the scene.
After creating the Browser Source, inspect it in the OBS preview. If it appears blank, check that the correct installation link was copied, the source is visible, and the source dimensions match the Streamkit preview. Give the client a moment to load before concluding that it has failed. If you use a particular scene collection for an always-on broadcast, verify that the source exists in the active collection rather than only in a test scene.
Do not copy the same installation link into every source if you expect separate widget behaviour. Return to Streamkit for each widget and use its own code. Also note that Discord’s support article dates from 2021; interface labels can change. Follow the current page and your current OBS controls rather than relying on an old screenshot if a menu has moved.
Style and position the overlay
A widget should remain legible without competing with the content. In OBS, drag it to a part of the frame that does not cover subtitles, faces, important visual detail or other information. For a landscape video, a narrow side area or an unoccupied corner may work; for a vertical layout, there may be less spare space, so consider using only one widget or omitting it.
Use the Streamkit preview and the OBS canvas together. A widget can look balanced in its own preview but become intrusive when placed over your actual scene. Check it against the brightest and darkest portions of the background, and consider whether small text will remain readable on a phone. Keep enough margin from the frame edges that the display does not look clipped or cramped.
Treat the widget as part of the programme, not as proof of audio. If you hide the visual source, call audio routing is unaffected; if you show a voice widget, that still does not add participants’ sound. Keep those controls separate in your OBS scene design. If the overlay is intended for a live conversation, a scene transition can make it clearer when the audience should expect Discord activity.
Before exposing a Discord client window itself, review Streamer Mode. Discord documents controls to hide personal information and invite links, and to disable desktop notifications and sounds. Its Streamer Mode guidance says it can be toggled manually, by keybind, or automatically when Discord detects OBS or XSplit. Check the current settings on your own device, because the article and interface may not match exactly in every detail.
Route Discord call audio separately
If viewers need to hear people in a Discord call, configure an audio path separately from the Streamkit overlay. The sources used here explain how to display widgets, not how to capture or route the sound of a call into an OBS mix. The right method depends on your operating system, Discord output device, OBS audio configuration and any other audio tools you use, so do not treat a voice widget as an audio setup guide.
Before changing devices, map the signal you want: Discord call output should reach the broadcast mix, while your own microphone and programme audio remain at the intended levels. Use a private test recording or unlisted test broadcast to check that the call is audible, that your microphone is not duplicated, and that other programme sound has not been muted. Listen back rather than relying only on the OBS meters; a meter can show signal without telling you whether the result is intelligible or balanced.
Avoid sending a call to the public stream until everyone on the call knows it may be broadcast. Check for notification sounds, private conversation and unexpected channel activity. For a channel that runs unattended, decide whether call audio should be present at all times or only in a host-led segment. A disconnected participant, muted output or changed default device can alter the mix, so make the audio test part of your pre-stream check.
If your main concern is a long-running broadcast stopping rather than a Discord call, diagnose the stream separately. These checks for a YouTube 24/7 stream that stops after a few hours address broadcast continuity; they do not replace testing the Discord audio path.
Connect creator accounts for server roles
Discord also supports account integrations that can give eligible Twitch subscribers or YouTube channel members roles in a server. These workflows take place in Discord account and server settings, not in OBS. Linking an account is only part of the process: you must also configure the integration for the server.
For Twitch, Discord’s Twitch Integration FAQ says the subscriber integration is for Twitch Partners and Affiliates. First connect Twitch in Discord User Settings, Connections. Then open the server’s Server Settings, Integrations and follow the Twitch setup prompts. Discord notes that the feature is unavailable when the channel has no subscription option.
Discord creates managed Twitch Subscriber and tier roles, and subscriber lists can sync automatically; admins can also trigger a manual sync. You can rename the managed roles and adjust their permissions. Discord’s documentation also describes a grace period before a former subscriber loses the role or is removed from the server. Because the integration manages these roles, you cannot manually assign or delete them as if they were ordinary roles. Consider which channels those permissions expose before enabling the integration.
For YouTube, Discord’s instructions for connecting a YouTube channel require a YouTube Partner whose channel memberships are enabled. Connect the YouTube account under User Settings, Connections, then go to Server Settings, Integrations, select YouTube and enable the channel. You can choose whether membership access applies to the whole server or selected channels.
Discord creates managed YouTube Member and tier roles, with membership syncing normally handled automatically and a manual sync option available. Server admins can adjust role names, colours and permissions. The integration also offers a grace period and a choice about removing someone’s role or kicking them when their membership ends. Check those settings before launch so a member’s access matches your intended community policy.
Twitch and YouTube eligibility are not interchangeable. If your channel does not meet the requirements Discord lists for its platform integration, linking the account alone will not create supporter roles. Discord’s Server Integrations page brings together server integrations, bots, webhooks and apps, and lets admins inspect permissions requested by installed apps. Review it periodically as well as during setup.
Test the result in your scene
Test each result independently. For a widget, confirm the correct server and widget appear in the intended OBS scene, that the source is positioned well, and that the information shown is appropriate for a public audience. For call audio, test the audio path and listen to a recording. For server roles, use Discord’s integration settings to confirm the correct account and server are connected and that the role permissions match the channels you meant to protect.
A short scene-by-scene check prevents a common mistake: verifying an overlay in one scene and then going live from another. In OBS, move through the scenes you actually use, including any holding screen or alternate layout. Make sure a Discord source is not visible where it should be hidden, and make sure an intended voice or chat display is not obscured by another source.
For privacy, consider enabling Streamer Mode before opening Discord or showing its window. Check that personal details, invitations and notifications are not exposed. If you are streaming from a dedicated playback computer, the relevant issue is still the public scene and its sources, not simply which machine is running the stream. A routine check can also catch changes after Discord or OBS updates.
If your Discord segment is only occasional, keep a test scene that mirrors the live layout. That lets you confirm the widget and call mix without altering the always-on programme. If you change your channel’s video or audio arrangement, test the loop and scene transitions too; these notes on switching between prerecorded videos on a cloud YouTube stream are relevant when the Discord segment sits alongside scheduled or looping content.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I show Discord chat on OBS?
Choose the Chat widget on Discord’s Streamkit Overlay page, select your server and configure the display. Copy that widget’s installation link into a new OBS Browser Source, then set the source dimensions to match the Streamkit page and check it in your scene preview.
Does the Discord voice widget add call audio to my stream?
No. The voice widget is a visual display of voice-channel activity and participant status; it does not route participants’ call audio into OBS. Configure and test audio capture separately for your operating system and OBS setup.
How do I connect Twitch to Discord for subscriber roles?
Connect Twitch under Discord User Settings, Connections, then configure Twitch under the server’s Server Settings, Integrations. Discord documents the subscriber integration for Twitch Partners and Affiliates, and the channel needs a subscription option.
How do I sync YouTube members to my Discord server?
Connect YouTube in User Settings, Connections, then enable the channel in Server Settings, Integrations. Discord requires a YouTube Partner with channel memberships enabled; it creates managed member roles that you can configure for access.