HandBrake No Audio After Encode: How to Fix It

You finish an encode, open the new video, and discover that it is completely silent or that an expected audio track is missing. When HandBrake produces no audio after an encode, the cause usually falls into one of four categories: HandBrake did not include the intended source track, the chosen audio codec is incompatible with the player or device, passthrough copied an unsupported stream, or playback is muted or routed incorrectly. The steps below help Windows, macOS, and Linux users identify which category applies without changing unrelated settings.

This guide focuses on missing or silent audio in the output. It does not cover audio and video gradually drifting out of sync. Begin with a short test rather than repeatedly encoding an entire movie or recording. Once a test file contains a playable audio stream, stop changing settings and apply the same configuration to the full encode.

1. Confirm the Symptom With a Small Test Encode or Preview

Before adjusting codecs, determine whether the output truly lacks an audio stream or whether one particular player cannot reproduce it. These conditions can look identical during playback but require different fixes.

1.1 Test the output in more than one player

Open the encoded file in at least two players. For example, compare your operating system's default player with VLC or another player known to support a broad range of formats. Also inspect the player's audio-track menu. A file may contain several audio streams while the player has selected a silent commentary track, an unsupported track, or no track at all.

• If the file has sound in one player, HandBrake probably created an audio stream successfully. Focus on codec support, track selection, or playback configuration in the failing player or device.
• If every player lists an audio track but produces silence, check volume, output routing, channel layout, and decoder compatibility.
• If no player lists an audio track, inspect HandBrake's Audio tab and Activity Log.

Success means that at least one player detects the expected stream and plays audible sound. At that point, do not keep changing HandBrake settings unless the file must work on another specific device.

1.2 Create a short representative test

Set a short range that contains dialogue, music, or another clearly audible section. Use the Range controls to encode a chapter, a small number of seconds, or a limited set of frames where supported. Make sure the selected segment is not naturally silent.

A preview can reveal obvious problems, but a saved short encode is more useful because it can be opened in multiple applications and copied to the target television, phone, console, or media box. Keep the source, selected title, audio track, and output container identical to the planned full encode.

1.3 Separate muted playback from a missing stream

Check the player's volume control, the operating system's per-application mixer, and the selected output device. Bluetooth headsets, HDMI displays, USB interfaces, and disconnected monitors can take over audio output. On a television or receiver, confirm that the correct input and speaker mode are active.

A muted application or incorrect output device is a playback problem, not an encode failure. If changing the playback destination restores sound, the output does not need to be encoded again.

2. Check the HandBrake Settings Directly Related to This Problem

The Audio tab controls which source streams are included and how they are stored in the output. A video preset does not guarantee that the particular language, commentary, surround format, or alternate track you need has been selected.

2.1 Verify the Audio tab contains a track

After opening the source and selecting the correct title, choose the Audio tab. There should be at least one row in the audio list. That row should identify a source track and an output encoder. If the list is empty, add the desired track before starting the encode.

Read the source-track description carefully. It may include a language, codec, channel count, and track number. Do not assume the first stream is the main program audio. Some files place commentary, descriptive audio, or another language first.

Success means that the Audio tab shows the intended source track and an encoder or compatible passthrough option. Once the correct track is present, make a short test instead of changing unrelated video filters.

2.2 Confirm the correct title and source track

DVD, Blu-ray, camera, and multi-program sources can contain several titles. Selecting a menu, bonus feature, camera proxy, or short duplicate title can expose different audio streams from the main program. Check the title duration and preview the picture to confirm that it represents the intended content.

Then compare the available source tracks. If two tracks have similar labels, test each one in a short encode. Language metadata can be missing or incorrect, so channel count and listening tests may be more reliable than the language label alone.

Only work with discs and media that you have the legal right to process. HandBrake is not designed to defeat copy protection, and this troubleshooting guide does not cover bypassing DRM.

2.3 Use AAC stereo as a safe compatibility test

For diagnosis, choose AAC as the audio encoder and select a stereo mixdown. Use a normal bitrate offered by the current interface or preset. AAC stereo in an MP4 container is widely supported by computers, phones, browsers, televisions, and streaming devices, making it a useful baseline test.

This is not necessarily the final quality or surround configuration. It is a controlled test that removes passthrough, uncommon codecs, and multichannel speaker layouts from the equation. If the AAC stereo test works, the source audio is readable and HandBrake can encode it. The original problem is likely compatibility with the previous codec, passthrough stream, channel layout, or playback device.

2.4 Understand conversion and passthrough

Audio conversion decodes the source and creates a new audio stream, such as AAC. Passthrough does not convert the compressed audio. It copies an eligible source stream into the output container. Passthrough can preserve formats such as AC3, EAC3, DTS, or other supported streams, but the final player, container, television, receiver, and connection must all handle that format.

Change passthrough to AAC conversion when the output has a track but the target device remains silent, when the destination container does not suit the copied stream, or when the file works on a computer but not on a television. If surround sound is required, test a compatible multichannel format after establishing that AAC stereo works.

Success means the target device plays the converted test. Stop troubleshooting HandBrake at that point. Choose the final codec based on the target device's documented capabilities rather than assuming passthrough is always more compatible.

2.5 Match the codec to the destination

Common audio formats have different compatibility profiles:

• AAC: A practical default for MP4 files and broad consumer-device playback.
• AC3: Common in home-theater workflows, but support still depends on the container, player, television, and receiver.
• EAC3: Supports modern surround workflows, although older televisions and software may not decode it.
• DTS: Frequently found in disc sources, but many televisions, mobile devices, browsers, and applications do not support direct playback.
• FLAC: Lossless and useful for archival or desktop playback, but not universally supported in every container or consumer device.
• Passthrough: Retains a compatible source bitstream, but does not make that bitstream playable on unsupported hardware.

A track appearing in a file does not prove that a device can decode it. If AAC stereo plays but DTS or EAC3 passthrough does not, the encode is not necessarily corrupt. The target playback chain lacks support somewhere.

3. Check Source, Destination, System, and Playback Factors

If the Audio tab looks correct, examine the full path from the source file to the speakers. The video encoder receives most of the attention in HandBrake, but silent output is usually tied to source selection, audio configuration, container support, or playback.

3.1 Verify the source already contains usable audio

Play the source outside HandBrake and select the same title or track if the player exposes those choices. Screen recordings may contain microphone audio but no system audio, or the reverse. Phone and camera files can include multiple streams or unusual channel layouts. A recording application may also have created a silent stream if it lacked permission to capture a microphone or desktop audio.

If the source is silent in every player, HandBrake cannot reconstruct sound that was never recorded. If the source plays correctly but HandBrake does not list its audio, the Activity Log may reveal an unsupported or damaged stream.

3.2 Test a local destination with a simple filename

Save a short test to a local folder with sufficient free space and a straightforward filename. This avoids cloud-sync interruptions, network-share behavior, removable-drive errors, and permission complications. Confirm that you are opening the newly encoded file rather than an older file with a similar name.

An incomplete write can produce a file that opens but lacks expected data or indexing. If the log reports a successful completion and the local test works, the original destination or file-management process deserves attention.

3.3 Inspect operating system audio routing

Windows can assign different output devices and volumes to individual applications. macOS can route sound to displays, AirPlay endpoints, aggregate devices, or Bluetooth hardware. Linux audio systems can similarly direct application streams to different sinks. Check the system's sound panel while the silent file is actively playing.

If other files have sound in the same application but only the HandBrake output is silent, routing is less likely. However, surround output over HDMI may behave differently from ordinary stereo playback. That is another reason an AAC stereo test is valuable.

3.4 Consider the player, television, receiver, and connection

A television may accept AAC from its built-in media player but reject DTS, or it may pass some formats through HDMI while refusing others from USB playback. A receiver may support a codec even though the television between the player and receiver does not pass it through. Browser playback has its own container and codec limitations.

Test the file directly on the final destination. If it works on the computer but not on that destination, consult the destination's supported audio formats and container requirements. Converting the audio is usually more dependable than passthrough when compatibility is uncertain.

3.5 Determine whether hardware encoding is relevant

Hardware encoder settings normally control video encoding rather than the selected audio encoder. Therefore, switching between a hardware and software video encoder is not the first fix for missing audio. It can still be useful in a clean diagnostic test if the entire job fails, crashes, or produces a damaged file.

If an encode completes normally and only a passthrough audio track is silent on one device, focus on audio compatibility. If the log shows a broader hardware-related failure or the output is incomplete, repeat a short test with a standard software video encoder and AAC stereo to isolate the problem.

3.6 Do not confuse subtitles with audio

Subtitle and audio tracks are separate. Adding, removing, burning, or selecting subtitles does not add sound. However, selecting the wrong source title while looking for a subtitle track can indirectly result in the wrong audio selection. Reconfirm the title and then inspect the Audio and Subtitles tabs independently.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake's Activity Log records what it detected, which title it scanned, which tracks it selected, which encoders it used, and whether the job completed. Its location and presentation vary by operating system and interface, but it is available from HandBrake's application menus or activity window.

4.1 Find the audio track lines

Open the log for the affected encode and search for terms such as audio, track, AAC, AC3, EAC3, DTS, FLAC, passthru, or encoder. Exact wording can differ, so focus on the meaning rather than expecting one fixed line.

Look for evidence of these facts:

• The source scan detected one or more audio streams.
• The selected title was the intended title.
• The job configuration included the expected source audio track.
• The track was converted with an encoder or copied using passthrough.
• The job reached normal completion without read, decode, muxing, or write errors.

If the log lists no selected audio track, return to the Audio tab. If it shows the wrong source track, select the correct one. If it shows passthrough and the file is silent only on the destination device, convert to AAC for the next test.

4.2 Interpret warnings in context

A warning matters when it corresponds to the symptom. Audio decode failures, repeated read errors, unavailable passthrough selections, or muxing failures can explain a missing stream. A harmless informational line about an unrelated video feature usually cannot.

If the log ends abruptly or reports that the job failed, fix that failure before evaluating audio quality. If the log reports successful audio encoding and normal completion, inspect the output with another player or a media-information utility. The likely issue then shifts toward playback compatibility or output-device routing.

4.3 Preserve the log before another attempt

Save or copy the affected job's log before running several experiments. Label each short test with its important settings, such as AAC stereo, AC3 conversion, or DTS passthrough. This prevents results from becoming mixed together and provides useful evidence if you later request support.

5. Run a Clean Temporary Encode With Minimal Settings

A controlled encode is the fastest way to determine whether HandBrake can read and convert the source audio. Avoid modifying ten settings at once because a successful result will not reveal which change mattered.

5.1 Build the baseline test

1. Open the source again and select the correct title.
2. Choose a standard built-in preset appropriate for the source resolution.
3. Select MP4 as the container for a broad compatibility test.
4. Open the Audio tab and remove unintended tracks.
5. Add the known main audio track.
6. Select AAC conversion rather than passthrough.
7. Select stereo mixdown.
8. Encode a short section containing obvious sound to a local folder.
9. Play the output in two players and on the intended destination if practical.

If this test has sound, HandBrake is functioning for that source. Reintroduce only the features you require, one at a time. For example, test a surround mixdown next, then a different container, and finally passthrough if the target equipment explicitly supports it.

5.2 Know when to stop changing settings

Stop when the short output contains the intended track and plays correctly on the final device. A player that reports AAC stereo and produces clear sound confirms the baseline fix. Additional changes create new variables and are unnecessary unless you need surround sound, multiple languages, lossless audio, or a specific home-theater format.

If the clean test remains silent and the log shows audio decode errors, test another known-good source. When other sources encode correctly, the original file or track is likely damaged or unsupported. When every source fails despite correct track selection, reset HandBrake's preferences, try a current official build, and gather logs before seeking support.

6. Quick Fix Checklist

• Play the source and confirm that the intended section contains sound.
• Select the correct title, especially for discs and multi-title sources.
• Open the Audio tab and verify that at least one track is present.
• Choose the intended language or main-program track, not commentary.
• Test with AAC conversion and stereo mixdown instead of passthrough.
• Encode a short segment to a local folder.
• Open the output in at least two players.
• Check the player's audio-track menu and volume.
• Check operating system output routing, HDMI, Bluetooth, and per-app volume.
• Test the file on the actual television, phone, receiver, or media box.
• Review Activity Log lines for audio selection, encoding, passthrough, and errors.
• Stop changing settings once the target device plays the short test correctly.

7. Frequently Asked Questions

7.1 Why does the HandBrake file have sound in VLC but not on my TV?

VLC includes support for many codecs that a television may not decode. The file probably contains audio, but the television does not support its codec, channel layout, or container combination. Create a short MP4 test with AAC stereo. If that works on the television, use conversion instead of the previous passthrough or codec setting.

7.2 Why is the Audio tab empty?

The selected title may not contain an audio stream, HandBrake may not have detected the source stream, or the current configuration may not have added a track. Confirm that the source plays with sound, choose the correct title, rescan it, and add the intended stream in the Audio tab. Check the Activity Log if no audio streams are detected.

7.3 Should I use passthrough for better audio quality?

Passthrough avoids re-encoding an eligible compressed stream, but it is useful only when the container and complete playback chain support that stream. It does not improve compatibility. If passthrough produces silence on the destination, convert to a supported format such as AAC, or to another format explicitly supported by your equipment.

7.4 Can the wrong mixdown cause silent playback?

It can contribute to playback problems, particularly with multichannel output and unusual speaker configurations. A device may mishandle a layout even though it recognizes the codec. AAC stereo is the best diagnostic mixdown because it removes most channel-routing uncertainty. Once it works, test the required surround layout separately.

7.5 Does reinstalling HandBrake fix missing audio?

Usually not. Track selection, passthrough compatibility, and player support are more common causes. Reinstallation or a preference reset becomes reasonable only when multiple known-good sources fail, the Audio tab behaves incorrectly, or logs indicate a broader application problem. Preserve the Activity Log and test a clean built-in preset first.

7.6 What should I include when asking for HandBrake troubleshooting help?

Include the operating system, output container, selected source audio description, chosen audio encoder, mixdown, whether passthrough was enabled, players or devices tested, and the complete Activity Log for a short failed encode. Do not share copyrighted source material or private recordings. A log generally provides far more diagnostic value than a screenshot of a silent player.