Recording File Has No Sound on a Phone but Sound on a PC? Codec, Container and Player Compatibility Diagnosis Guide

2026-11-19 | GPU Repair | 22 minutes | HK GPU Fix Editorial Team

Recording File Has No Sound on a Phone but Sound on a PC? Codec, Container and Player Compatibility Diagnosis Guide

Key takeaway: If a recording plays with sound on a computer but silently on a phone, the file is probably not damaged. The phone's built-in player may simply lack the decoder for the audio codec inside the file, while VLC on a computer carries its own decoders. Check the codec with MediaInfo and compare players before assuming the recording failed.

A recording file can look perfectly normal and still be silent in one place and audible in another. The picture moves, the length is correct, and nothing about the file looks broken. On a phone, the built-in player shows the video and produces no sound at all. On a computer, the same file plays with sound. That split — silent on the phone, audible on the computer — is the whole problem this guide addresses, and the split itself is the first piece of evidence.

The instinct in this situation is usually to blame the recording. The recording software, the graphics card, or the file itself is assumed to have failed at the moment of capture. That conclusion is premature. A file that plays with sound on a computer has an audio track, and that audio track contains usable data. The question is not whether sound was recorded. The question is whether the player being used on the phone can decode the audio track that is inside the file. Those are two different questions, and they need two different kinds of evidence.

This guide covers only a narrow shape. Four conditions must all be present. First, the same recording file plays with a normal picture and no sound at all in the phone's built-in player — the Photos or Files app on an iPhone, or the gallery or Files app on an Android phone. Second, the same file plays with sound on a computer, in VLC or in the computer's built-in player. Third, the phone itself is not silent: other videos, music, and online video all play with sound on the same phone. Fourth, MediaInfo shows that the file contains an audio track. If any of these conditions is missing, the diagnosis changes. A phone that is silent for everything is a phone volume, mute switch, or output-device problem, not a file problem. A file that MediaInfo shows has no audio track is a different problem, covered by the guide for a recording file with no sound at all. A file that starts with sound and goes silent part-way through is a different problem again.

A container is a box; a codec is the key

A video file can be thought of as a box. The style of the box is the container: MP4, MOV, MKV, or AVI. What is packed inside the box is compressed in its own way, and that compression method is the codec. The video track may use H.264, HEVC, or AV1. The audio track may use AAC, AC3, E-AC3, DTS, Opus, or PCM. The file extension only names the style of the box. Two files that are both called MP4 can contain completely different audio codecs inside.

That distinction matters because a player does not play a container. It opens the container, then decodes the video track and the audio track separately. If it can decode the video track but not the audio track, the result is exactly the symptom in this guide: the picture moves and there is no sound. Nothing about that result means the file is damaged. It means the player does not have the key for that particular audio codec.

Players differ in which keys they carry. VLC carries a large set of decoders of its own and does not need to ask the operating system for them. A phone's built-in player, by contrast, can generally only use the formats built into the phone's system. The same file can therefore be audible in VLC on a computer and silent in the built-in player on a phone, with neither player behaving incorrectly. Each player is doing what its own decoder set allows it to do. The computer result proves that VLC can decode the file. It does not prove that the phone's built-in player can decode it, and it should never be written as proof that the file is fine for every device.

Which audio tracks are most likely to fail on a phone

External sources consulted for this guide describe the same high-risk combinations. One of them, XConvert, calls AC-3, E-AC-3, and DTS leading causes of silence after conversion; that ranking is XConvert's, reported here with attribution, and this guide does not adopt it as its own conclusion. The other sources cited here do not rank the causes, and this guide makes no ranking of its own.

AC3 and E-AC3, also known as Dolby Digital and Dolby Digital Plus, are used in television recordings, disc-based material, and the output of some recording software. StellarInfo states that AC3 and DTS are "Not native on iOS or Android", and that phone apps commonly show an "Audio Codec Not Supported" error for them. XConvert states that AC-3 is a codec that Windows itself no longer includes after Windows 11 24H2, and that browsers do not support it either. There is a conflict in the sources on the iPhone and AC3 that should be stated openly rather than resolved by choosing one side: StellarInfo also states that the iPhone handles Dolby audio at the system level, while at the same time describing AC3 as not native on iOS. Whether a given file plays depends on the app, the phone model, the system version, and the details of the file. No support list should be written as fixed for a particular phone model or system version, because support changes with system updates. The current official documentation for the device in question is the place to check.

DTS is common in movie files. StellarInfo states that the iPhone does not include DTS support at the system level, and that Android is the same in this respect. A file with a DTS audio track can therefore play normally on a computer in VLC and be silent in a phone's built-in player.

The MKV container deserves separate attention. LifeEasyTools states that MKV files are often not played by iPhones, many televisions, WhatsApp, and some video editors, and that an MKV file often contains H.264 or H.265 video with AAC, AC-3, DTS, or Opus audio, plus more than one audio track. An MKV file that is silent on a phone may therefore be failing at the container layer rather than at the audio-track layer: the phone's built-in player may not open the box at all, or may open the picture and not recognise the audio track inside it.

HEVC 10-bit and AV1 video mainly affect the picture, not the sound. A single file can, however, fail on both layers at once: HEVC 10-bit video that the phone cannot decode, and an AC3 audio track that the phone cannot decode. The two failures should be kept apart in the diagnosis. A picture problem and a sound problem in the same file are two separate findings, and they should not be combined into one cause.

Multi-track files are another separate layer. Recording software such as OBS can record more than one audio track in a single file, and a player normally plays only the first track by default. If the track the phone plays is not the track that carries sound, the surface symptom is silence, even though a sounding track exists in the file. MediaInfo shows how many tracks there are and which codec each one uses; which track carries sound is a separate question from which codec is used, and the two should be checked as two different sets of facts.

Why sound on a computer does not mean the file is fine everywhere

Sound in VLC on a computer proves three things: the file has an audio track, the audio data is not damaged in a way that prevents decoding, and VLC can decode it. It does not prove a fourth thing: that the phone's built-in player can decode it. That boundary should be written down explicitly at the start of any diagnosis, because a common error in this area is to treat the computer result as a general verdict on the file. The same warning applies in the other direction. Silence on a phone does not prove that the recording failed, that the file is damaged, or that the graphics card is at fault. The file has already demonstrated, on the computer, that it contains audible sound.

Transcoding belongs in this guide only as a comparison, not as a repair. Converting a copy of the file to H.264 video with AAC audio in an MP4 container, and then playing that copy on the phone, is a test. If the converted copy plays with sound on the phone, the result points to the compatibility layer: the original audio codec or container was the barrier. The original file itself is not damaged and does not need to be repaired, and transcoding should not be described as having fixed the original file. It has produced a copy that the phone can play. The original file should be kept unchanged as comparison material, and it should not be deleted or overwritten. A related caution comes from UnlimFiles, which states that no codec works everywhere. H.264 with AAC is the most widely compatible combination described in the sources, but it is not a guarantee for every device, and this guide does not present it as one.

Renaming a file does not change what is inside it. Changing a file extension from .mkv to .mp4 changes only the label. It does not change the container and it does not change the codec. HDVideoConverter-Mac states this explicitly: renaming does not change the container or the codec, and a conversion tool must rewrite the file for the contents to change. A file that is silent after renaming was never going to become audible by renaming alone.

The five suspect layers

LayerWhat it meansDecisive comparison
Audio codecThe audio track uses AC3, E-AC3, DTS, Opus, or another codec the phone's built-in player cannot decodeMediaInfo audio codec reading, plus an H.264 and AAC transcode comparison
ContainerAn MKV or other container the phone's built-in player does not open, or opens without recognising the audio trackThe same file remuxed to MP4, plus the phone VLC comparison
Multi-track and channel layoutThe file has more than one audio track and the phone plays a silent one, or a 5.1 channel layout the phone's stereo player does not downmixMediaInfo track count, plus playing each track in turn in phone VLC
PlayerThe phone's built-in player is limited by its system version or app version, while phone VLC plays the same file with soundBuilt-in player against phone VLC on the same file
File and transferThe file was truncated during transfer, cloud synchronisation had not finished, or the phone lacked storage space so the copy is incompleteFull-file playback in computer VLC, file size and duration comparison, and a fresh transfer

Each layer has its own comparison, and no single comparison covers all five. MediaInfo separates the codec layer from the player layer. The phone VLC comparison separates the player layer from the file layer. The transcode comparison separates the compatibility layer from the transfer layer. The order in the seven steps below is the order that wastes the least time.

Seven diagnostic steps

Step 1 — Define the shape

Confirm the four shape conditions: the phone's built-in player is silent, the computer plays the same file with sound, the phone plays other material with sound, and MediaInfo shows an audio track. Write down the baseline before changing anything: where the file came from, which recording tool or editing software produced it, the container, the video codec, the audio codec, the channel count, the sample rate, the duration, the phone model and system version, and which player is being used on the phone. A diagnosis built on a vague description such as "the phone has no sound" cannot be checked later, because it does not say which player, which file, or which track was tested.

Step 2 — Play the same file in VLC on the computer

Play the same file on the computer in VLC, and write down which track was played and at which point in the file sound was heard. Sound in VLC proves that the file has an audio track and that the audio data can be decoded, which narrows the problem to the compatibility layer, and the diagnosis continues to Step 3. Silence in VLC on the computer as well is not this problem: it points to a file with no audio track or with a damaged audio track, and a different diagnostic path applies. The computer player used, the track played, and the time point should all be recorded, because a later comparison is only meaningful if the same part of the same file was tested.

Step 3 — Read the audio codec with MediaInfo

This is the most important single step in the whole guide, and without it everything that follows is guesswork. Open the file in MediaInfo and read the audio codec, the channel count, the sample rate, and the number of audio tracks. AC3, E-AC3, DTS, or Opus points to the codec layer. An MKV container points to the container layer. More than one audio track points to the multi-track layer. Write down the exact codec name as MediaInfo shows it, rather than paraphrasing it from memory. The codec name is the fact that the rest of the diagnosis depends on, and a paraphrase can turn one codec into another.

Step 4 — Play the same file in VLC on the phone

Install VLC on the phone and play the same file in it. Sound in phone VLC with silence in the built-in player points to the player layer: the built-in player is limited, while VLC's own decoders can handle the file. Silence in phone VLC as well points away from the player app and toward the codec, container, or multi-track layer. This triple comparison — built-in player on the phone, VLC on the phone, and VLC on the computer — is the decisive fork in this guide. The three results together say far more than any one of them alone, and no one result should be read as a verdict on the file.

Step 5 — Check each audio track in turn

If MediaInfo showed more than one audio track, play each track in turn in phone VLC and listen to each one separately. One track with sound and the others silent points to the multi-track layer: the phone was playing a track that carries no sound. All tracks silent excludes the multi-track layer and returns the diagnosis to the codec or container layer. This step should be done track by track, not by switching a setting and guessing. The number of tracks and the result for each one should be written down.

Step 6 — Make an H.264 and AAC comparison copy

Convert a copy of the file to H.264 video with AAC audio in an MP4 container, and play that copy in the phone's built-in player. Sound in the converted copy confirms the compatibility layer: the original codec or container was the barrier. Silence in the converted copy as well means the problem is not in the codec or container, and the diagnosis should return to the file and transfer layer in Step 7. This step is a comparison, not a recommended setting and not a repair of the original file. The converted copy is a separate file made for testing. The original file is not changed by this step, and describing the conversion as having fixed the original file is an error. Note also that conversion cannot rebuild an audio track that does not exist: if the original file has no audio track, a converted copy will have none either.

Step 7 — Check the transfer, then stop if the fault is still undivided

If the converted copy is still silent, check the file and transfer layer. Compare the file size and duration of the copy on the phone with the original on the computer. Play the whole file in computer VLC, not just the first few seconds, to confirm that sound lasts for the full duration. Transfer the file again, and confirm that any cloud synchronisation has finished before playing the copy on the phone. If the fault still cannot be divided after these steps, or if the file also crashes players, MediaInfo cannot read the file, or the converted copy is still silent, stop and bring the written record to Room 1209, Dali Plaza, Shek Mun for inspection. The telephone number is 2186 8010 and WhatsApp is 6558 6806. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection. Do not delete or overwrite the original file; it is the comparison material.

Boundary cases

A file that is silent in VLC on the computer as well is a different problem: the file itself has no audio track or a damaged audio track, and it is not a compatibility problem. A file that starts with sound and goes silent part-way through is a different problem. A file that plays with sound in an editing program but whose audio track is not recognised there is a different problem, at the editing software's reading layer rather than the phone player layer. A file that stutters on a phone but plays smoothly on a computer is a decoding-load problem, not a silence problem, even though it shares the same phone-against-computer structure. A phone that is silent for everything is a phone mute, volume, or output-device problem, not a file problem. The reverse direction — sound on the phone and silence on the computer — is also a different problem, connected with the removal of AC-3 from Windows after Windows 11 24H2, and it is not covered by this guide. A live stream with no sound while the recording has sound is a streaming-output problem, not a file-playback compatibility problem. A finished export with sound but no picture is the opposite direction, at the video-track layer.

Six common misconceptions

  1. "The computer plays it, so the file must be fine." Wrong. Sound in computer VLC proves only that VLC can decode the file. It does not prove that the phone's built-in player can decode it. VLC carries its own decoders; the phone's built-in player can only use the formats built into the system.
  2. "The phone is silent, so the recording must have failed." Wrong. A file that plays with sound on a computer was not recorded silently. Silence on the phone can mean the player cannot decode the audio track, not that the recording itself failed.
  3. "Renaming .mkv to .mp4 will make it play." Wrong. Renaming changes only the label. It does not change the container and it does not change the codec. A conversion tool must rewrite the file for the contents to change.
  4. "Transcoding fixed the video." Wrong. Transcoding produces a copy that the phone can play. It is a comparison and a preventive step, not a repair of the original file. The original file was not damaged and does not need repairing.
  5. "If VLC plays it, the phone's built-in player will play it." Wrong. VLC and the phone's built-in player are two different sets of decoding ability. HDVideoConverter-Mac states that a file playing in VLC does not mean the iPhone's built-in app will play it.
  6. "AAC is universal, so converting to AAC will always work." Wrong. H.264 with AAC is the most widely compatible combination described in the sources, but UnlimFiles states that no codec works everywhere. No combination should be presented as a guarantee for every device.

Sources and what they do and do not establish

StellarInfo, in "Audio Codec Not Supported? Try Fixes for Windows, Mac, Smartphone & TV", describes the division of labour between container and codec, states that AC3 and DTS are "Not native on iOS or Android", notes that the iPhone handles Dolby audio at the system level while not supporting DTS, and suggests phone VLC and similar players as a comparison. Its two statements about the iPhone and AC3 point in different directions, and both are reported here rather than one being chosen over the other.

XConvert, in "Why Does My Video Have No Sound After Converting?", states that AC-3, E-AC-3, and DTS are leading causes of silence after conversion, that Windows 11 24H2 no longer includes AC-3, that sound in VLC means the file is not the problem in the sense that the file contains decodable audio, and that converting to AAC is the most widely compatible approach.

MediaPlayerCodecPack, in "Audio Codec Not Supported Fix", advises checking which audio codec a file uses first, notes AC3, EAC3, DTS, and TrueHD inside MKV files, and describes H.264 with AAC as the most widely compatible combination, with HEVC and AV1 needing newer player support.

UnlimFiles, in "MP4 Audio Codec Not Supported? Convert It to AAC", states that a player can decode the video track while refusing the audio track, describes AAC-LC stereo with H.264 as a compatible copy, states that no codec works everywhere, and notes that conversion cannot rebuild an audio track that does not exist.

LifeEasyTools, in "MKV to MP4 Converter", states that MKV files often contain H.264 or H.265 video with AAC, AC-3, DTS, or Opus audio plus more than one audio track, that MKV files are not played by iPhones, many televisions, WhatsApp, and some video editors, and that an MKV file often has no sound in some players because it uses AC-3 or DTS surround audio tracks that phones cannot decode.

HDVideoConverter-Mac, in "Why Your Mac Plays a Video in VLC but Your iPhone Won't Open It", states that a file playing in VLC does not mean the iPhone's built-in app will play it, that three things should be checked — container, video codec, and audio codec — that renaming an extension does not change the container or the codec, and that H.264 with AAC is a widely compatible choice.

XConvert does rank the causes: it calls AC-3, E-AC-3, and DTS leading causes of silence after conversion, and that ranking is reported here as XConvert's, not as this guide's conclusion. No source cited here gives a numerical ranking of the causes, and this guide makes no ranking of its own. No percentage, case count, success rate, or fee beyond the site's published three-tier fee of HK$400–780, HK$480–1,380, and HK$680–2,800 appears in this guide, because none is supported by the sources used.

FAQ

Why does my recording have sound on my computer but no sound on my phone?

The audio track is probably encoded in a codec the phone's built-in player cannot decode, such as AC3, E-AC3, or DTS, while VLC on the computer carries its own decoders and can decode it. The file is not necessarily damaged. Open the file in MediaInfo, read the exact audio codec, and compare the built-in player with VLC on the phone before deciding what the cause is.

What is the difference between a container and a codec?

The container is the style of the box — MP4, MOV, MKV, or AVI — while the codec is the compression method used for what is inside the box. The video track may use H.264 or HEVC, and the audio track may use AAC, AC3, DTS, or Opus. The file extension only names the container. Two MP4 files can contain completely different audio codecs, so the extension alone says nothing about whether a phone can play the sound.

Does sound in VLC mean the file is fine?

No. Sound in VLC on a computer proves that the file has an audio track, that the audio data can be decoded, and that VLC can decode it. It does not prove that the phone's built-in player can decode it. VLC carries its own decoders, while the phone's built-in player can only use the formats built into the phone's system. The two players should be compared on the same file, not treated as interchangeable.

Will renaming a file from .mkv to .mp4 make it play with sound?

No. Renaming changes only the label on the file. It does not change the container and it does not change the codec inside it. A conversion tool must rewrite the file for the contents to change. If the file is silent because of its codec or container, renaming it will leave it silent.

Does converting to H.264 and AAC repair the original file?

No. Converting produces a separate copy that the phone can play, and it is used here as a comparison to confirm that the problem is in the compatibility layer. The original file is not damaged and does not need repairing. The original should be kept unchanged as comparison material, and it should not be deleted or overwritten.

What should I bring if the fault still cannot be divided after all seven steps?

Bring a written record of the file's source, the container and codecs shown by MediaInfo, the number of audio tracks, the results of the three-player comparison — built-in player on the phone, VLC on the phone, and VLC on the computer — and the result of the H.264 and AAC comparison copy. Bring that record to Room 1209, Dali Plaza, Shek Mun for inspection; the telephone number is 2186 8010 and WhatsApp is 6558 6806. The site's published three-tier fee is HK$400–780, HK$480–1,380, and HK$680–2,800, an overall range of HK$400–2,800, with the actual fee quoted after inspection.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: