HandBrake DTS Audio Not Playing: How to Fix Compatibility

You finish an encode, open the video, and discover that the picture works but the DTS audio is silent. In many cases, HandBrake has not lost the audio. The more likely explanation is that DTS was passed through correctly, but the television, phone, browser, streaming device, or media player cannot decode it. Other common causes include selecting the wrong source track, using a container that does not suit the target device, or playing an alternate audio track by default. The fastest HandBrake DTS audio not playing fix is to test the output in more than one player, inspect the audio settings, and create an AAC or AC3 compatibility track when DTS support is uncertain.

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

Before changing a full conversion, determine whether the problem is in the encoded file or the playback device. A short test saves time and prevents unrelated settings from complicating the diagnosis.

1.1 Test the same output in two players

Open the affected file in a capable desktop player such as VLC, then test it on the device where the silence occurs. If VLC produces sound but the television, phone, browser, or streaming application does not, the file probably contains audio that the second device cannot decode.

This behavior is especially common with DTS passthrough. VLC includes its own support for many media formats, while a television or browser may depend on a narrower set of built-in decoders. A player successfully opening DTS does not prove that every other device will support the same track.

Success at this stage means identifying a clear difference between players. If the DTS track works in one player, stop investigating source corruption and move directly to compatibility settings.

1.2 Encode a short chapter or range

In HandBrake, choose a short chapter, a brief time range, or Preview if it is available for the selected workflow. Keep the test long enough to include speech or other obvious sound. Encode that sample using the same preset and audio choices as the failed output.

Test the sample on the intended playback device. If it is silent, create a second sample with the audio converted to AAC or AC3. Do not change the video, filters, subtitles, dimensions, and audio simultaneously. A controlled comparison makes the result meaningful.

If the converted sample plays correctly, you have confirmed a DTS compatibility problem. There is no reason to keep changing video encoder settings.

1.3 Verify that silence is not limited to one section

Some sources contain silent introductions, commentary tracks, multiple languages, or damaged segments. Seek to several points in the video and inspect the player’s audio menu. Confirm that an audio track is enabled and that the expected language or channel layout is selected.

If another track produces sound, HandBrake may have included multiple tracks and the player selected the wrong one. Correct the default track in the player first. Re-encode only if the file needs to behave consistently on devices that do not remember track selections.

2. Check the HandBrake Settings Directly Related to DTS

The Audio tab is the center of this troubleshooting process. DTS passthrough preserves compressed DTS data without converting it, whereas AAC or AC3 encoding creates a new track that is more broadly compatible. Passthrough is not automatically the best choice merely because it preserves the original stream.

2.1 Understand DTS passthrough versus conversion

With DTS passthrough, HandBrake copies the source DTS bitstream into the output when the selected container and source permit it. This avoids lossy audio re-encoding and retains the source channel structure. However, the final device must support the DTS format, the chosen container, and the way audio is delivered.

With conversion, HandBrake decodes the source audio and encodes it as another codec. AAC is commonly suitable for phones, computers, browsers, and MP4-oriented playback. AC3 can be a useful choice for home-theater equipment and televisions that advertise Dolby Digital support. Device documentation should decide between them.

Choose conversion when the target device does not explicitly support DTS, when browser playback is required, or when the file must work across varied consumer devices. Choose passthrough when the destination player and audio equipment are known to decode DTS.

2.2 Replace DTS passthrough with AAC or AC3

Open the Audio tab and locate the DTS source track. Change the codec from DTS passthrough or an automatic passthrough option to AAC or AC3. Select an appropriate channel mix supported by the playback device. Stereo is the safest test because it removes surround-output limitations from the first experiment.

For a permanent file, you may choose a surround mix if the target device supports it. Avoid assuming that a device accepting six-channel audio over one connection will accept it through every application or output path.

Run another short encode. Success means the same device that was silent now plays the AAC or AC3 track. Once that happens, stop changing settings. The diagnosis is complete.

2.3 Keep DTS plus a compatibility track when useful

An MKV file can be useful when you want to preserve the original DTS track and add a broadly compatible track. Add the source audio twice in HandBrake, configuring one entry for DTS passthrough and the other for AAC or AC3 conversion. Place the compatibility track first if simple players tend to select the first audio stream.

This arrangement allows a home-theater player to use DTS while a less capable device selects AAC or AC3. It increases file size, but not by as much as duplicating the video. Labeling tracks by codec or purpose can make manual selection easier in players that display track names.

Success means both tracks appear in the player’s audio menu and each works on its intended equipment. If the file is only for a phone or browser, keeping DTS is usually unnecessary.

2.4 Review automatic passthrough behavior

Automatic passthrough can preserve a compatible source codec while using a fallback encoder for unsupported formats. That behavior is convenient, but it can also produce a DTS track when the source and container allow it, even though the eventual playback device cannot decode DTS.

For a diagnostic encode, select AAC or AC3 explicitly rather than relying on automatic behavior. This removes uncertainty about which codec HandBrake will place in the output.

3. Check the Container, Source, Track, and Playback Path

DTS silence is often caused by the combination of codec, container, player, and output connection rather than by one broken component. Check the factors that apply to the actual destination instead of applying unrelated HandBrake troubleshooting steps.

3.1 Compare MP4 and MKV compatibility

MP4 is widely supported for web, mobile, and consumer playback, particularly when paired with H.264 or H.265 video and AAC audio. DTS support in MP4 playback is inconsistent across applications and devices. A file can be structurally valid while remaining unusable on the intended television or browser.

MKV accommodates a broad range of audio streams and is generally the more practical container when preserving DTS or storing multiple audio tracks. However, some televisions and editing applications have limited MKV support. Changing to MKV can solve a container limitation, but it cannot make a device decode DTS if the device lacks a DTS decoder.

• Use MP4 with AAC for broad phone, browser, and general consumer compatibility.
• Use MKV when preserving DTS or keeping multiple audio formats is important.
• Use AC3 only when the target equipment and container workflow support it.

Success means the selected codec and container are both documented or demonstrated to work on the destination. Once a short test succeeds, use the same pairing for the complete encode.

3.2 Confirm the correct source audio track

DVD, Blu-ray, camera, and downloaded source files may contain multiple languages, commentary, stereo mixes, descriptive audio, or several surround formats. In the Audio tab, verify that the selected track matches the expected language and source codec.

If the desired track is absent from HandBrake’s list, rescan or reopen the source and examine the scan results in the Activity Log. When using a disc source, work only with media you own or are authorized to process, and do not bypass copy protection.

If HandBrake sees and encodes the expected DTS stream, but the destination remains silent, return to codec compatibility. If HandBrake never detects the stream, investigate the source rather than repeatedly changing the output codec.

3.3 Check the player’s selected audio track

A file containing DTS and AAC may open with DTS selected even on a device that cannot decode it. Open the player’s audio, language, or track menu and select the AAC or AC3 stream manually. Also check whether audio is muted inside the application rather than at the operating-system level.

If manual selection restores sound, the encode is usable. You can stop there, set a preferred track in the player, or create a new output with the compatibility track listed first for easier distribution.

3.4 Examine the complete playback path

A television may support DTS through its internal media player but not through a browser application. A streaming box may decode DTS itself, pass it to a receiver, or convert it depending on its audio mode. HDMI, optical audio, Bluetooth, and built-in speakers can expose different format and channel limitations.

Test the television speakers before involving a receiver or soundbar. If local speakers work but external equipment is silent, the encode may be valid and the failure may be in passthrough or output negotiation. Select PCM or another supported output mode temporarily to isolate that path.

Operating-system audio drivers can matter when every application using a particular output is silent. They are less likely to be responsible when only DTS files fail and AAC files work. Update or reconfigure drivers only after confirming this codec-specific pattern.

3.5 Know which settings are unlikely to cause DTS silence

A hardware video encoder processes video and normally does not determine whether DTS can be decoded by the playback device. Switching between software and hardware video encoding is therefore not a useful first fix for DTS-only silence.

Subtitle tracks also do not control audio, although selecting the wrong title or preset can coincide with selecting the wrong audio stream. The destination folder and queue matter only if you accidentally test an older file, an incomplete output, or a job encoded before settings were changed. Confirm the output filename, completion status, timestamp, and queue entry before drawing conclusions.

4. Use the Activity Log to Separate Guesswork From Evidence

HandBrake’s Activity Log records what it detected and what it attempted to encode. It is especially useful when the Audio tab does not match the final file or when several source tracks have similar labels.

4.1 Find the relevant audio details

Open the Activity Log for the completed job and look for source scan information, selected audio streams, codec names, language identifiers, channel layouts, passthrough decisions, fallback encoders, muxing messages, and errors. The exact wording can vary by platform and build, so focus on the meaning rather than searching for one fixed phrase.

The log should help answer three questions:

1. Did HandBrake detect the expected DTS source stream?
2. Did it pass through DTS or encode AAC or AC3 as requested?
3. Did the job finish and write the selected track into the output?

If the log shows successful DTS passthrough and VLC plays it, the destination device is the leading suspect. If the log shows AAC conversion and the output is silent everywhere, verify track selection and inspect the source or job errors.

4.2 Save the log before repeating the job

Copy or save the relevant log while the failed job is still easy to identify. Compare it with the log from the short compatibility test. A useful comparison changes only the audio codec, leaving the source range, container, and video choices consistent where possible.

Success means the log confirms the expected output codec and the destination plays it. Once evidence and playback agree, avoid making additional changes that could introduce new variables.

5. Run a Clean Temporary Encode With Minimal Settings

If previous edits, presets, queue entries, or multiple tracks make the result unclear, create a clean temporary test. This is not a recommendation to reset everything permanently. It is a controlled way to prove which part of the workflow is failing.

5.1 Build the diagnostic encode

1. Open the original source directly in HandBrake.
2. Select the correct title, chapter, or short time range.
3. Choose MP4 for a broad-compatibility test.
4. Select a common video preset appropriate for the destination.
5. Remove unneeded audio tracks from the test.
6. Add the desired source audio once and encode it as AAC stereo.
7. Leave subtitles out unless they are required to identify the correct title.
8. Choose a new filename in a writable local folder.
9. Start the job directly or clear unrelated queue entries first.

Play the completed sample on the original problem device. If it works, add complexity one item at a time. Try surround AAC or AC3 if needed, then consider MKV, a second DTS track, subtitles, and other final settings.

If AAC stereo remains silent in every player, the problem is no longer specifically DTS compatibility. Check the Activity Log for source decoding errors, confirm the correct audio stream, and test the unconverted source. At that point, broader HandBrake not working diagnostics may be appropriate.

5.2 Know when to stop changing settings

Stop when a short encode plays on the intended device with the required language and channel layout. Record or save that preset, then run the full encode. Do not change the video encoder, frame rate, filters, and subtitle behavior after audio is fixed unless those settings have separate problems.

For maximum portability, a successful endpoint is often MP4 with AAC. For archival or home-theater use, it may be MKV containing original DTS plus AAC or AC3. The correct endpoint depends on where the file must play.

6. Quick Fix Checklist

• Test the file in VLC and on the intended device.
• Confirm the expected language and audio track are selected.
• Replace DTS passthrough with explicit AAC or AC3 conversion.
• Use AAC stereo for the simplest compatibility test.
• Prefer MKV when retaining DTS or multiple audio tracks.
• Prefer MP4 with AAC when broad playback matters most.
• Add DTS and a compatibility track when both quality and portability are needed.
• Check the Activity Log for the detected and encoded audio codecs.
• Verify that you opened the newest completed queue output.
• Stop changing settings after a short sample works on the target device.

7. Frequently Asked Questions

7.1 Why does DTS work in VLC but not on my television?

VLC supports many codecs through its own playback components. A television’s built-in player may support fewer codecs, may accept DTS only in certain containers, or may require compatible external audio equipment. If VLC works and the television does not, convert the track to AAC or AC3, or add one of those formats as a second track.

7.2 Should I use DTS passthrough in HandBrake?

Use DTS passthrough only when the destination player and audio system are known to support DTS. Passthrough preserves the original compressed stream but does not improve compatibility. For phones, browsers, mixed devices, or uncertain television support, explicit AAC or AC3 conversion is safer.

7.3 Is MP4 or MKV better for DTS audio?

MKV is generally the more flexible choice for preserving DTS and storing multiple audio streams. MP4 is often more portable when combined with AAC. Container support and codec support are separate, so placing DTS in MKV will not help a device that cannot decode DTS at all.

7.4 Can I keep the original DTS track and add AAC?

Yes. Add the same source audio twice, configure one entry for DTS passthrough, and configure the other for AAC. MKV is commonly suited to this arrangement. Put the compatibility track first if the simplest playback devices should choose it automatically.

7.5 Why is the output silent even after adding AAC?

The player may still be selecting the DTS stream, or HandBrake may have encoded a different language or commentary track. Select AAC manually in the player and check the Activity Log. If an AAC-only stereo test is silent in every player, investigate source decoding, job errors, and operating-system output rather than DTS support.

7.6 Does changing the hardware video encoder fix DTS audio?

Usually not. Hardware encoder options primarily affect video encoding. For a DTS-specific silence problem, concentrate on the Audio tab, codec conversion, track selection, container, Activity Log, and playback device. Change the video encoder only when the video itself has a separate problem.