Push-to-talk in OBS lets you send microphone audio only while you hold a chosen key. To make it work, first confirm OBS is listening to the intended microphone, then enable push-to-talk for that source and assign a key to its Push-to-talk action.
Those are separate checks: enabling the feature does not assign a key, and assigning a key to the wrong microphone will not control the input you meant to use. Test the result in the Audio Mixer and in a short recording before relying on it in a stream.
Confirm which microphone OBS is using
Start with the Audio Mixer, not the hotkey. Speak into the microphone you intend to use and watch the meter for the microphone or audio input source. A moving meter confirms that OBS is receiving some signal from that source; it does not, by itself, prove that the signal is clean or that it is the only microphone being captured.
If the expected meter does not move, open Settings → Audio and inspect the microphone or auxiliary audio device selection. Choose the intended device rather than leaving an uncertain selection in place. Device labels can be similar, especially when a computer has a built-in microphone, a webcam microphone and a USB headset connected. Speak again after making a change and confirm which meter responds.
This order matters because a hotkey cannot correct an input-device selection. If OBS is listening to the laptop microphone while you are speaking into a headset, push-to-talk may still be enabled and assigned correctly, but the resulting audio will come from the device OBS selected. Do not assume that a working key means the intended microphone is working.
If no meter responds, check whether the operating system recognises the microphone and whether its input is available to OBS. Confirm any physical mute switch or device control as well. Return to OBS and repeat the meter check after each change; otherwise, you may end up troubleshooting a hotkey when the actual problem is that no usable input reaches the application.
OBS can capture audio globally through Settings → Audio or, on supported systems, through an Audio Input Capture source attached to a scene. The OBS Audio Sources guide describes these source types and warns that capturing the same microphone by both routes can create echo. The guide identifies Audio Input/Output Capture as available on Windows and macOS, not Linux; check the current documentation and your installed version if the source choices differ.
For a scene-specific setup, note which source you intend to control before proceeding. A source name such as “Mic/Aux” may refer to a global device, while a named Audio Input Capture source belongs to a scene. The Push-to-talk setting and hotkey need to be associated with the microphone source you actually use. If you are maintaining a gaming layout or another scene-based setup, the considerations in choosing a setup for a 24/7 YouTube gaming stream are useful context, but the input check still happens inside OBS.
Enable push-to-talk for the microphone
Once you have identified the source and confirmed that its meter responds, open Settings → Audio. Find the relevant microphone or auxiliary device and enable its Push-to-talk option. OBS describes push-to-talk as a setting for each microphone or auxiliary device; this is not a general switch that automatically applies to every audio source in every scene. See the OBS Studio Overview Guide for the overview of audio settings and hotkey configuration.
Enabling the option establishes that this source should use push-to-talk. It does not choose the key. You still need to assign a key to the matching source’s Push-to-talk action under Settings → Hotkeys. Keep the source name in mind as you move between settings pages, especially if the project contains more than one input.
If you use a scene-specific Audio Input Capture source rather than a global microphone device, check that you are configuring the input you intend to use. OBS’s available capture options can depend on your operating system and version. Do not create a second capture path simply to make a setting appear; capturing the same physical microphone globally and in a scene can produce duplicate audio or echo.
The distinction is easy to miss when you are setting this up quickly. You might turn on the option in Audio settings, assume the microphone is now controlled by a key, and then find that the microphone remains open. That is a sign to check the hotkey assignment, not a reason to repeat the device-selection step unless the meter points to the wrong input.
Assign a push-to-talk hotkey
Open Settings → Hotkeys and locate the same microphone source you enabled. Find the action named Push-to-talk and assign a key or key combination. OBS has separate Push-to-talk, mute and unmute actions. Choose the Push-to-talk action for the hold-to-transmit behaviour described here, rather than assigning a key to a general mute or unmute action.
Choose a key that you can hold comfortably and that is not already needed for an action you use at the same time. A key that works while you are testing at the desktop may be awkward during a game, presentation or instrument performance. Think through the actual task: if one hand is on a mouse and the other is occupied, a keyboard key may not suit that arrangement. You do not need to buy a new keyboard just to configure OBS hotkeys.
After entering the key, check that OBS has registered it in the field. Then verify that you assigned it to the correct source and action. If there are multiple microphone rows, a hotkey under one row does not mean that another row has the same configuration. This is a frequent source of confusion when a project has both a headset input and a scene-specific microphone.
There is no universally correct key assignment. Keyboard layout, operating system behaviour, OBS version and other applications can affect which key is convenient or available in a particular setup. Treat the displayed assignment as a configuration to test, not as proof that it will work in every context. A key that overlaps with a game control or a keyboard shortcut may cause an unwanted action even if OBS recognises it.
The OBS Quick Start Guide recommends testing your setup rather than relying on settings alone. That is especially useful here: the key must be available when you need it, OBS must receive it, and the intended microphone must respond to the action.
Test the key and microphone meter
Return to the main OBS window and look at the Audio Mixer. With the microphone source identified, hold the assigned key and speak in a normal voice. Watch the meter for that source. Then release the key and speak again. The expected pattern is meter activity while the key is held and no transmitted microphone activity after release, subject to any other active input or monitoring path.
Repeat the test a few times, with a short pause between presses. This helps distinguish a key that works intermittently from one that is simply assigned to a different source. Keep your attention on the labelled microphone meter, not just on whether the overall programme audio meter moves; other sources such as desktop audio or media can make the overall mix active.
A meter that responds while holding the key is a useful check, but it is not the final one. Make a short test recording and listen back. Confirm that your speech is present while the key is held and that it stops after release. If you are preparing a lesson with timed breaks, the guide to keeping a Pomodoro timer synchronised with a YouTube live lesson covers a different part of the workflow; test your microphone behaviour independently before beginning the lesson.
Test in the same scene and with the same equipment you expect to use. If you switch from a headset to a USB microphone, change scenes, or reconnect a device, repeat the meter and recording checks. A result from one scene or input does not establish that a different source is configured in the same way.
Check mute and mixer behaviour
The Audio Mixer has its own mute button for each source. Check that the microphone source is not muted there when you expect to hear audio. OBS explains that the mixer’s mute control mutes or unmutes the source to the output; it is distinct from enabling push-to-talk or assigning the PTT key. A source muted in the mixer can make a correctly configured hotkey appear to do nothing.
For a straightforward test, make sure the intended microphone source is unmuted in the mixer, hold the key and speak, then release it. Do not use the mixer mute button as a substitute for the PTT action. They serve different purposes: the mixer control changes whether the source is output, while the assigned PTT action controls when that source is transmitted as you hold the key.
Also check whether another mute or unmute hotkey has been assigned to the same source or to a related input. If you press a key that changes the source’s mute state, the resulting behaviour may not match the hold-and-release pattern you expect. Review the actions in Hotkeys and make sure the key intended for PTT is attached to Push-to-talk, not a separate mute or unmute command.
If the meter shows activity but the recording has no microphone audio, check the mixer state and the recording’s audio track configuration as separate questions. The mixer meter shows signal at the source; it does not guarantee that every output or recording track includes that source. Avoid changing several settings at once. Test after each change so you can identify which one affected the result.
Troubleshoot when push-to-talk does not work
Troubleshoot from the input outward. First speak and watch the intended microphone meter without pressing the key. If it does not respond, revisit Settings → Audio, choose the correct device and check that the operating system or microphone itself is not blocking input. There is no reason to focus on the hotkey until OBS is receiving the microphone signal.
If the meter responds without the key but the key does not control it, verify two separate controls: Push-to-talk is enabled for that microphone in Audio settings, and the key is assigned to that same source’s Push-to-talk action in Hotkeys. Do not infer that the feature is fully configured from either step alone. Confirm that you did not assign a key to Mute or Unmute instead.
If you have more than one source, read the source label on both settings pages. A key assigned to a headset will not necessarily control an Audio Input Capture source in a scene, and a setting enabled for one microphone does not establish that another is configured. Return to a simple scene or isolate the intended source if the mixer contains several similar entries.
If the key appears to do nothing, test whether another application or OBS action is using it. Try a different available key as a diagnostic, then test it in the same scene. This is not a promise that the replacement will work in every setup; it is a way to find out whether the original assignment conflicts with another action. Keep the final choice comfortable and compatible with the task you will perform.
If the source meter moves while the key is held but no output is audible, look at the mixer mute button first. Then make a test recording and listen to it. This separates a PTT problem from a muted source or an output/recording routing problem. OBS’s Audio Mixer Guide explains the mixer controls; use the current guide if labels in your version have changed.
For echo or doubled speech, check whether the same physical microphone is active both as a global device and as a scene source. Disable one of the duplicate capture paths and test again. This problem can be mistaken for a PTT fault because speech remains audible through the second path even when the intended source is gated. If you are also building a continuous channel, remote monitoring for an always-on YouTube gaming VOD stream addresses monitoring as a separate operational concern, not a replacement for checking OBS’s input sources.
Verify the setup before recording or streaming
Before a session, check the setup in a predictable order: confirm the microphone device, speak and see its meter move, confirm PTT is enabled for that source, inspect the source’s Push-to-talk hotkey, and check that the mixer source is not muted. Then hold the key while speaking, release it, and make a short recording to listen back. This sequence catches the common cases without changing settings at random.
Repeat the check after a meaningful change, such as connecting a different microphone, altering the active scene, or reopening a project with a different audio device available. Do not assume that the last successful test still describes the current source selection. A quick meter check can reveal a changed input before you begin a recording or go live.
If you run a channel where your computer should not stay on for the entire broadcast, OBS push-to-talk is still a local microphone-control feature, not a way to send live speech from a computer that is switched off. StreamNeo removes the separate pain of keeping a computer running for an uploaded-video YouTube stream, but that does not make it a replacement for OBS microphone controls or a live microphone workflow. For a continuous channel that uses OBS, decide which parts need live input and test those separately from any prepared 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
Does enabling push-to-talk assign a key automatically?
No. Enable Push-to-talk for the microphone in Settings → Audio, then assign a key to that source’s Push-to-talk action in Settings → Hotkeys. Check both settings before testing.
Why does the key work but my microphone is still silent?
First confirm that OBS is using the microphone you are speaking into and that its meter responds. Then check whether that source is muted in the Audio Mixer; the PTT action, input selection and mixer mute are separate controls.
Should I use a global microphone or an Audio Input Capture source?
Use the source arrangement that fits your scene and operating system, and make sure you configure the source you actually want to control. Avoid capturing the same physical input both globally and as a scene source, since duplicate capture can create echo.
How can I be sure the setup is ready?
Hold the assigned key while speaking and watch the intended source’s meter, then release it and make a short recording. Listen back to confirm that speech is present while held and stops after release before relying on the setup in a live session.