You record a useful tutorial, a video call, or a problem on your phone, then play the recording and discover that the sound is missing. The screen recorder clearly captured the picture, so it can seem as though audio should have been recorded automatically too.
Screen video and audio are separate inputs. A recorder can capture the pixels being shown while recording no sound at all, or it can capture one audio source but not another. The exact choices depend on the device, operating system, app, and content being recorded.
Understanding those separate paths makes silent recordings much easier to explain and helps you check the right settings before an important recording.
Think of a screen recording as several possible tracks
A simple mental model is to imagine the recorder building a file from separate tracks.
One track contains the changing image of the screen. Audio can come from other sources, commonly the microphone or the device audio produced by apps and the operating system. Some systems can combine more than one source, while others expose fewer choices.
These sources are not interchangeable.
If you enable the microphone, the recorder can capture sound reaching the device’s microphone: your voice, people nearby, and possibly sound coming from the device’s speakers. That does not necessarily mean it is directly recording the audio stream produced inside an app.
Internal or device-audio recording works differently. When supported, the operating system supplies eligible playback audio to the recorder without relying on the microphone to hear the speakers.
That distinction explains a common surprise: a recording can contain your narration but not the app’s sound, or the app’s sound but not your voice.
Recording the screen does not automatically grant access to every sound
The operating system controls which audio sources a screen recorder can use. An app that can see the screen for recording purposes does not automatically receive unrestricted access to the microphone or to every audio stream produced by other apps.
Microphone recording normally depends on microphone permission and on the recording option being enabled. Device-audio capture depends on what the platform supports and what the source app or content allows to be captured.
As a result, the video portion can work normally even when an audio path is unavailable. The recorder is not necessarily malfunctioning; it may simply be receiving video frames and no usable audio source.
Microphone audio and device audio fail in different ways
If microphone audio is missing, first consider the microphone path. The microphone may have been disabled in the recorder, permission may not have been granted, or another condition on the device may have prevented the recorder from using it. The available controls and behavior vary by platform and version.
If device audio is missing while microphone narration is present, the problem is different. The recorder is clearly able to write audio, but the internal playback stream may not be available for capture.
This can happen because the operating system does not support that capture mode in the current situation, because the source app does not expose its audio for recording, or because protected content is deliberately restricted.
The useful troubleshooting question is therefore not simply “Is audio on?” It is which audio source was the recorder supposed to capture?
Some apps and content can restrict capture
Not every sound that reaches your speakers or headphones is necessarily available to a screen recorder.
Operating systems provide mechanisms that can limit capture of certain app audio or protected media. The details vary across platforms and applications. Streaming services, communication apps, games, and other software can therefore behave differently even when you use the same screen-recording settings.
This is why a test recording from one app does not prove that another app’s audio will be captured in the same way.
Restrictions can also affect the picture. Some protected content may appear blank or otherwise be unavailable to the recorder. That is a separate issue from audio capture, but it comes from the same general principle: what you can play on a device is not automatically something the operating system allows another process to record.
Speaker volume is not the same as recording level
Another common mistake is to treat the volume buttons as if they control all recorded audio.
They usually control how loudly playback is sent to a speaker, headphones, or another output. A direct device-audio recording can use the underlying audio stream rather than listening to that physical output through the microphone. Depending on the platform and recording method, changing playback volume may therefore affect what you hear without changing a directly captured audio track in the same way.
Microphone recording is different. If the microphone is physically picking up sound from the speakers, then speaker volume, distance, room noise, and microphone placement can all affect the result.
This difference also explains why turning the volume up is not a reliable fix for missing internal audio. If the recorder has no access to that audio source, making the speakers louder does not create the missing digital path.
Headphones can change what a microphone hears
Suppose you are narrating a screen recording while a video plays. If the recorder is capturing only the microphone, sound from the phone’s speaker may leak into that microphone and become part of the recording.
Connect headphones and the situation changes. The playback sound is now delivered close to your ears instead of into the room, so the microphone may capture little or none of it. Your voice may still be present.
It can then appear that the headphones “removed” the video’s audio. In reality, the recorder may never have been capturing internal device audio. It was recording the microphone, which previously happened to hear the speaker.
This is one reason to identify the selected audio source instead of judging the setup only by what you can hear while recording.
Calls can be a special case
Screen recording is not a dependable substitute for a dedicated call-recording feature.
Voice and video calls involve microphones, speakers, communication audio paths, application rules, operating-system restrictions, and sometimes legal or policy requirements. Whether a screen recorder captures your voice, the other participant, both, or neither can vary substantially between devices and apps.
Do not assume that because a screen recorder can capture ordinary media playback it will capture a call in the same way. If recording a conversation is permitted and necessary, use a recording method designed for that purpose where available and follow the applicable consent and legal requirements.
Why an existing silent recording usually cannot be repaired
If the finished file contains no audio track, or contains only a microphone track when you needed device audio, the missing sound was generally never written into that file.
Editing software can amplify quiet audio that exists. It can reduce some noise or combine the recording with another audio source. It cannot reconstruct the exact original sound merely from a video track when that sound was never captured.
That makes a short test especially valuable. Discovering the problem before a long presentation or demonstration is much easier than trying to recover audio afterward.
Test the exact setup before an important recording
Before recording something you cannot easily repeat, make a short sample using the same app, audio route, and accessories you plan to use.
Check the screen recorder’s audio options and identify whether you need microphone sound, device sound, or both. Names and available choices differ between operating systems and versions, so focus on the meaning of the option rather than expecting one universal menu label.
Then record a few seconds containing the sounds you care about. Play the file back and verify each source separately. If you need narration, confirm that your voice is present. If you need app audio, confirm that the app itself can be captured. If you will use headphones, test with those headphones connected.
Also remember that a successful test with one application does not guarantee identical behavior in another. Test the actual source when the recording matters.
The practical takeaway
A screen recorder does not simply copy everything you see and hear into one file. Screen video, microphone input, and device audio can travel through different recording paths, and the operating system or source app can limit which paths are available.
When a recording is silent, identify the missing source first. If your voice is absent, investigate the microphone path. If app sound is absent, investigate device-audio capture and whether that app permits it. If both are missing, check the recorder’s audio selection before assuming the video file itself is faulty.
The most reliable habit is simple: for any recording that matters, make a short test with the exact app, audio source, and accessories you intend to use, then listen to the result before starting the real recording.