- Identify whether microphone capture, system audio, or playback is failing.
- Match ShareX audio sources with active Windows input and output devices.
- Use short local tests to isolate permissions, routing, and workflow problems.
A ShareX screen recording with no audio usually points to one of four problems: ShareX is capturing the wrong audio source, Windows is blocking microphone access, the intended device is muted or unavailable, or the recording contains audio that is not playing correctly in the current media player. Microphone audio and system audio are separate capture paths, so a setting that records your voice will not necessarily record application sounds, and vice versa. Work through the tests below in order, checking the result after each change. Once a short test recording contains the audio you need, stop changing settings.

Start with free Canva bundles
Browse the freebies page to claim ready-to-use Canva bundles, then get 25% off your first premium bundle after you sign up.
Free to claim. Canva-ready. Instant access.
1. Confirm the Symptom With a Simple Test
Before editing several ShareX or Windows settings, identify exactly what is missing. This prevents a microphone problem from being mistaken for a system audio problem.
1.1 Record a controlled sample
Create a short recording of about 10 seconds. During the recording, speak into the microphone while playing a recognizable sound through the computer, such as a local video or a Windows notification. Keep the test simple and avoid using a confidential meeting or an important presentation.
Play the resulting file and classify the symptom:
- No microphone and no system audio: ShareX may have no usable audio source selected, the recording configuration may exclude audio, or playback may be failing.
- System audio works but the microphone is missing: check the selected input device, microphone permissions, mute controls, and Bluetooth microphone mode.
- Microphone works but system audio is missing: ShareX is probably capturing only an input device rather than the computer's playback stream.
- The wrong microphone or application is recorded: ShareX may be following a default device that changed after a headset, dock, monitor, or webcam was connected.
- The file appears silent in only one player: the recording may be valid, but the player may not be decoding or routing its audio correctly.
1.2 Test the file in another media player
Open the same recording in another current media player. Also confirm that the player's volume is above zero and that Windows has not muted that specific application in the volume mixer.
If the file plays with audio elsewhere, ShareX successfully recorded it. Stop changing ShareX capture settings and troubleshoot the original player, its output device, or its per-app volume instead. If the file is silent in multiple players, continue with the recording-source checks.
2. Check the ShareX Settings Directly Related to Audio
Open the screen recording options from ShareX. The exact path and labels can vary with the installed build and recording configuration, but the relevant controls are the screen recorder's audio source and encoding options. Confirm that the selected source matches what you intend to record.
2.1 Choose the intended audio source
ShareX uses its configured recording source rather than automatically copying the audio behavior of a conferencing application. Inspect the available audio sources and select the specific microphone, playback-capture source, or combined configuration you need.
Use the following distinction:
- Microphone capture records an input device, such as a laptop microphone, USB microphone, webcam microphone, or headset microphone.
- System audio capture records sound being played by Windows or a selected playback path. It is not the same as selecting a physical microphone.
- Combined capture records both your microphone and computer sound, but it requires a supported and correctly configured combination of sources. Selecting only one source does not automatically include the other.
If several devices have similar names, disconnect unnecessary headsets, webcams, docks, or USB audio adapters temporarily. Reopen the recording options and choose the remaining intended device. This reduces the chance of selecting an inactive endpoint.
Success means a new short recording contains the expected source. If your voice is present and system sound is intentionally absent, or system sound is present and the microphone is intentionally absent, the selected source is working. Do not keep changing unrelated settings.
2.2 Watch for devices that changed identity
Windows can expose multiple endpoints for the same hardware. A monitor connected through HDMI or DisplayPort may become the default output, while a Bluetooth headset may appear as separate stereo-output and hands-free communication devices. USB microphones and docking stations can also return under a different device entry after reconnection.
If ShareX was configured before a hardware change, reselect the audio source even when its old name still appears. A saved source can point to an endpoint that is disconnected or no longer active.
2.3 Confirm that the recording format includes audio
If the selected recording workflow or custom command was created for video-only capture, choosing a Windows device elsewhere may not add an audio stream. Review the screen recorder configuration and ensure audio is enabled for the recording output. Users who customized FFmpeg parameters, presets, or post-capture workflows should temporarily return to a standard recording configuration before troubleshooting custom arguments.
A useful verification is to inspect the finished file in a media player that can display stream information. If the file contains a video stream but no audio stream, focus on ShareX's recording source and encoding configuration. If an audio stream exists but cannot be heard, focus on device levels, channel routing, decoding, and playback.

3. Check Windows Audio Devices and Permissions
ShareX depends on audio devices and permissions exposed by Windows. A microphone can work in one application while remaining unavailable to another because conferencing software may use its own selected device, saved permissions, or communications mode.
3.1 Allow microphone access
Open Windows Settings and find the microphone privacy controls. Confirm that microphone access is enabled for the device and that desktop applications are allowed to access the microphone. ShareX is a desktop application, so the desktop-app permission is particularly relevant.
If organizational policy controls these settings, the option may be unavailable or managed by an administrator. In that case, changing ShareX settings cannot override the Windows restriction.
After enabling access, close and reopen ShareX before making a new test recording. Success means the newly recorded file contains your voice. Permission changes cannot restore audio to recordings that have already been created.
3.2 Verify the default input device
In Windows sound settings, inspect the input section and select the microphone you actually intend to use. Speak normally and watch the input-level meter. If the meter does not move, ShareX is unlikely to receive useful microphone audio from that endpoint.
Check the following items:
- The microphone is connected and enabled.
- A hardware mute switch or headset mute button is not active.
- The input volume is high enough to register speech.
- The selected device is not an unused webcam, controller, monitor, or disconnected headset.
- The device works in Windows' own microphone test or recording utility.
Once the Windows input meter responds, select that same device in ShareX and record another sample. If the meter responds but ShareX remains silent, the issue is more likely ShareX source selection or the recorder configuration than the physical microphone.
3.3 Verify the default output device
For system audio, confirm where Windows is sending sound. Speakers, an HDMI monitor, a USB headset, and a Bluetooth device can all be separate outputs. If the sound is playing through one endpoint while ShareX is configured to capture another, the recording can be silent even though you hear audio somewhere.
Set the desired playback device, play a test sound, and confirm its output meter moves. Then choose the corresponding system-audio or playback-capture source in ShareX. Make a new recording after any device change.
3.4 Check mute controls and the volume mixer
Open the Windows volume mixer while the relevant applications are running. Check both the application producing the sound and the application playing the finished recording. An application can be muted independently of the main speaker volume.
For microphone capture, inspect the input level rather than relying only on speaker volume. Raising speaker volume does not increase microphone recording level. For system audio, make sure the source application is routed to the same output path ShareX is expected to capture.
3.5 Handle Bluetooth headset quirks
Bluetooth headsets often expose separate playback and communications profiles. The high-quality stereo output may be presented separately from the hands-free profile used by the headset microphone. Activating the microphone can cause Windows to change profiles, alter sound quality, or route audio through a different endpoint.
For a clean diagnosis, try one of these tests:
- Record system audio while using the computer's built-in microphone instead of the Bluetooth microphone.
- Use a wired or USB microphone while keeping the Bluetooth device only for playback.
- Temporarily disconnect the Bluetooth headset and test with built-in speakers and microphone.
- Reselect ShareX audio sources after the Bluetooth device connects because endpoint names or availability may have changed.
If audio works without the Bluetooth headset, ShareX itself is probably functioning. Reconnect the headset and configure the exact input and output endpoints deliberately rather than relying on defaults.
4. Run a Clean Temporary Test With Minimal Settings
A clean test separates the basic recording path from custom hotkeys, automated uploads, custom FFmpeg arguments, region workflows, and post-capture actions. You do not need to delete your normal ShareX setup.
4.1 Simplify the recording path
- Close conferencing, streaming, voice-changing, and virtual-audio applications that may hold or reroute audio devices.
- Use a normal screen recording task rather than a custom workflow.
- Select one known-working microphone as the only intended audio source.
- Record 10 seconds while watching the Windows microphone input meter.
- Play the local output file in two media players before uploading or processing it.
If microphone audio works, repeat the test with the intended system-audio source. Test combined audio only after each source works independently. This staged approach identifies which capture path fails.
4.2 Bypass destination and workflow complications
Evaluate the local file created immediately after recording. Do not judge the result only after it has been uploaded, converted, embedded in a browser, sent through a messaging service, or processed by another program. A later workflow step can transcode, replace, or fail to play the audio stream.
If the local file has audio but the uploaded or processed version does not, stop adjusting the recording source. The failure occurs after capture. Check the destination's format support, any conversion step, and the exact file that was uploaded.
4.3 Reintroduce settings one at a time
After a minimal test succeeds, restore your preferred source combination, hotkey, format, automation, or upload action one change at a time. Record a short sample after each change. The first change that removes audio identifies the setting or workflow stage responsible.
5. Review History, Errors, and Recent Output
ShareX task history can help confirm whether a recording completed, where its local file was saved, and whether a later action failed. Open the most recent task and make sure you are testing the latest output rather than an older silent recording with a similar filename.
5.1 Separate capture failures from upload failures
An upload or network error does not normally explain why the original local file lacks an audio stream. Conversely, a successful upload does not prove that the recording contained the intended audio. Always inspect the local recording first.
If ShareX reports a recorder, FFmpeg, device, or encoding error, preserve the exact message. Device-not-found or unavailable-source messages point toward a stale audio selection. Encoding errors point toward the recording configuration or custom parameters. Upload authentication and network errors belong to a later stage and should be handled separately.
5.2 Consider what changed recently
Check whether the problem began after connecting a dock, installing a headset, changing the Windows default device, enabling a virtual audio cable, modifying privacy settings, or editing ShareX recording options. Reversing the most recent relevant change is usually more useful than reinstalling ShareX immediately.
A reinstall should not be the first step because it may leave Windows permissions, default-device routing, Bluetooth profiles, or user configuration unchanged. Prove that the selected device works in Windows and in a minimal ShareX test first.
6. Quick Fix Checklist
- Record a 10-second sample containing speech and computer sound.
- Play the local file in a second media player.
- Decide whether microphone audio, system audio, both, or only playback is failing.
- Select the intended audio source in ShareX screen recording options.
- Confirm audio is enabled in the recording configuration.
- Allow desktop applications to access the microphone in Windows privacy settings.
- Verify that the Windows input meter moves when you speak.
- Match ShareX system-audio capture to the active Windows output device.
- Unmute the microphone, source application, media player, and relevant volume-mixer entries.
- Temporarily disconnect Bluetooth, HDMI, dock, and virtual-audio devices that create extra endpoints.
- Test microphone and system audio independently before combining them.
- Inspect the original local file before testing uploads, conversions, or embeds.
Stop troubleshooting as soon as a repeatable short test contains the expected audio. Further changes can replace a working source or introduce a new routing problem.
7. Frequently Asked Questions
7.1 Why does ShareX record video but no microphone audio?
The most common causes are an incorrect audio source, blocked Windows microphone access, a muted or inactive input, or a recording configuration that does not include audio. First verify that the Windows input meter moves, then select that same microphone in ShareX and create a new test recording.
7.2 How do I record system audio instead of my microphone?
Select a system-audio or playback-capture source in the ShareX screen recording options rather than a physical microphone input. Also verify that Windows is playing sound through the output endpoint associated with that source. The available source names depend on your Windows audio devices and recording setup.
7.3 Can ShareX record microphone and computer audio together?
It can be configured to capture the sources supported by the recorder and available audio setup, but selecting a microphone alone does not automatically include system sound. Test each source separately first, then use an appropriate combined configuration. If combination causes failure, return to the last successful single-source test.
7.4 Why does my microphone work in a meeting app but not in ShareX?
Meeting applications often remember their own microphone, use communication-device defaults, request permissions separately, or manage Bluetooth profiles automatically. ShareX uses its screen-recording audio configuration. Compare the exact device selected in the meeting app with the device selected in ShareX, and verify desktop-app microphone permission in Windows.
7.5 Why is the ShareX recording silent only in one player?
The player may be muted, routed to another output, or unable to handle the file's audio stream correctly. Test the same local file in another current player and inspect the Windows volume mixer. If another player produces sound, the recording succeeded and ShareX does not need to be reconfigured.
7.6 Why did audio stop working after connecting a headset or monitor?
The new hardware may have become the default input or output device. HDMI monitors, USB docks, webcams, and Bluetooth headsets can add several audio endpoints. Confirm the active Windows devices, reselect the intended ShareX source, and make another short recording.