Audio File Won't Play? Here's How to Fix It

The fastest way to solve 'no audio' is to figure out which half of the problem you have, because the fixes are completely different. Test one thing: does other audio play right now? Play a YouTube video or a different music file. If nothing plays through your chosen output, it is a device/routing problem — the wrong output is selected, a Bluetooth device grabbed the audio, volume is muted, or drivers are misbehaving — and the specific file is innocent. If other audio plays fine but this one file does not, it is a file problem — format incompatibility, corruption, or DRM. Second test: does the problem file play in a different app (especially VLC)? If VLC plays it but your target app does not, it is a format/app issue, not a broken file. Those two quick checks — other audio, and the file in VLC — split every 'audio not playing' case into the right category in under a minute, so you can jump straight to the relevant section below instead of guessing.

The most common file-side cause is that your player does not support the format. Check the extension: WMA does not play on Mac without VLC; OGG does not play in Safari; FLAC may fail on older devices and some apps; Opus is unsupported in many legacy players. The universal fix is to convert the file to MP3 or WAV, which play essentially everywhere — AudioUtils does this in your browser in seconds, and if the file opens and converts successfully, that also proves the audio itself is intact and the problem was purely compatibility. Watch for a disguised cause too: a file with an audio-looking name might actually be a video format (an .mp4 or .mov whose audio you want), or an extension that has been renamed without actually converting the contents, which fools apps that trust the extension. If you do not recognize the extension, look it up before assuming corruption — often the format is simply one your app cannot open, and a quick conversion is the whole fix.

If a file will not play in any app — including VLC — corruption is likely. Files get damaged by interrupted downloads, incomplete transfers, failing drives, and apps crashing mid-write. Tell-tale signs: playback stutters, clicks, or stops partway through; the file size looks far too small for its supposed duration; or the duration displays as 0:00 and the file will not seek. VLC is the best first test because it tolerates damage and plays whatever valid audio exists — if VLC gets partial sound, the data is at least partly recoverable. Try re-downloading or re-transferring the file, and verify the copy completed fully by comparing file sizes with the source. If the file came off a USB stick or SD card that is slow or throwing errors, the storage may be failing, so copy it somewhere safe immediately. Genuine corruption is a separate repair job — converting the file through FFmpeg or an online converter rebuilds the header and salvages readable audio, which fixes a good share of cases; the rest need dedicated recovery.

Digital Rights Management deliberately locks files to specific apps or accounts, and it masquerades convincingly as a playback failure. Symptoms: the file plays in one official app but nowhere else; you get a licensing or authorization error rather than a format error; the file came from a store or streaming service. Common culprits are pre-2009 iTunes Store purchases (which used FairPlay DRM), audiobooks from certain platforms, and old WMA files from defunct download stores. There is no 'convert your way out' of DRM with a normal converter — the protection blocks access to the audio, so an ordinary conversion simply fails. The legitimate routes are to re-download a DRM-free version if the service now offers one (Apple made its music catalog DRM-free in 2009, so re-downloading old purchases through the Music app or iTunes Store yields clean files), or to play the content in its authorized app. For WMA files whose original license server no longer exists, the file may be permanently locked with no recovery path — a hard limit worth recognizing early so you stop trying converters that cannot succeed.

A very common, specific case: audio not playing inside editing software even though the file is fine. In Premiere Pro and DaVinci Resolve, silent playback usually has one of a few causes. Wrong audio hardware: the app has its own audio-device setting separate from the OS — check Preferences > Audio Hardware (Premiere) or the audio settings in Resolve and select your actual output. Unsupported codec in the clip: editors are pickier than players, and a clip with an exotic audio codec (or VFR video whose audio confuses the timeline) may import with no sound — transcoding the source to a clean format (audio to WAV, or the whole clip to a CFR MP4 with standard AAC/PCM audio) fixes it, which is why editors prefer WAV. Muted or routed track: a muted track, a solo on another track, or output routed to a disabled bus silences playback — check the mixer. Cache issues: clearing the media cache and re-conforming resolves audio that imported but will not sound. Sample-rate conflicts between clip and sequence can also drop audio. The pattern: editors demand clean, standard formats, so converting a problem clip's audio to WAV before importing prevents most of these.

When audio plays but not through the device you want, it is a routing problem, not a file problem. Wired headphones with no sound: confirm they are fully seated in the jack, and check that the OS output is set to headphones rather than speakers. AirPods and Bluetooth headphones: the classic issue is that audio is being sent somewhere else — open your output/volume control and explicitly select the AirPods or Bluetooth device, since phones and computers silently keep routing to the last device or to internal speakers; re-pairing, toggling Bluetooth off and on, or 'forget device' then reconnect resolves stuck connections, and a low headphone battery or being out of range drops audio too. CarPlay/Android Auto with no sound: check the car's source is set to the phone, the car volume (separate from phone volume) is up, and the cable or wireless connection is stable — unplugging and reconnecting, or restarting both phone and head unit, clears most CarPlay audio glitches. Across all of these, the universal first checks are: is anything muted, is the volume up on both the device and the app, and is the correct output actually selected? Routing and volume account for the large majority of 'plays on speakers but not my headphones' complaints.

For stubborn cases, work through the software stack. Restart the media player or app — the oldest fix, and it clears transient glitches. Clear the app's cache and update it to the latest version, since codec support and playback bugs are fixed in updates. Check system audio settings and confirm the correct output device is selected and not muted. On Windows, verify the Windows Audio service is running (services.msc) and try the built-in audio troubleshooter; a corrupted or outdated audio driver is a frequent cause of system-wide silence, so update or reinstall it. On Mac, if all audio has stopped, resetting Core Audio (restarting the coreaudiod process, or simply rebooting) revives it. Test with a different audio file to confirm the app itself works, and test the problem file in a different app — VLC remains the best diagnostic, since it plays almost anything and isolates whether the fault is the file or the app. This methodical stack-walk — restart, update, check output, check drivers, cross-test — resolves the device-side problems that are not simple routing mistakes.

When the file plays somewhere (like VLC) but not in the app you actually need, converting it is the dependable fix. MP3 is the universal fallback that every app and device accepts; WAV is the universal choice for editors. Convert the problem file to MP3 or WAV with AudioUtils — entirely in your browser, no upload, no install — and two useful things happen at once: you get a file your target app will accept, and the successful conversion confirms the audio was intact all along, meaning the issue was pure format compatibility. This single step resolves the large category of 'won't play here but plays there' problems. If the conversion itself fails or produces silence, that is meaningful information: the file is genuinely corrupted or DRM-protected rather than merely incompatible, and you should move to file recovery, a backup, or re-downloading from the source. Converting is the fix that both solves compatibility problems and diagnoses the ones it cannot solve — which is why it belongs at the end of the checklist as the reliable catch-all.