Modern Android smartphones and tablets have turned into powerful multimedia centers capable of reproducing the highest quality content. However, when trying to open a downloaded movie or a specific audio track, users often encounter the “The file cannot be played” error. This occurs due to the incompatibility of the built-in player with a specific video codec or container. Understanding which formats are supported by the system out of the box and which require third-party software will save you a lot of time and nerves.
The Android ecosystem is not monolithic in this matter. The set of supported codecs depends on the version of the operating system, processor (SoC) and the policy of the device manufacturer. While basic formats like H.264 and AAC work everywhere, new compression standards can only be available on flagships of recent years.
In this article we will analyze in detail the hardware and software capabilities of the platform, compile a compatibility table and give recommendations on choosing a player for complex cases. You'll learn why the same file can open on one phone and not work on another, even if they have the same version of Android.
Hardware and software decoding
A key factor in playback is the presence of a hardware decoder in your device's chipset. When you start a video, the system first tries to process the stream through a dedicated processor unit (DSP or GPU), which ensures high performance and minimal power consumption. If there is no hardware decoder for a given format, Android switches to software decoding, using the power of the central processor.
Software decoding allows you to open almost any file, but at the cost of high battery consumption and possible overheating of the device. Heavy formats like 8K HEVC or AV1 on older processors can cause severe slowdowns and sound desynchronization. This is why support for new codecs at the hardware level is so important for comfortable viewing.
Chipset manufacturers, such as Qualcomm, MediaTek and Samsungregularly update the lists of supported formats in their new lines. For example, 2026 flagship models often include hardware support for AV1, while budget devices may be limited to basic H.264/HEVC.
⚠️ Warning: Forcing software decoding for 4K video on devices with weak processors may lead to critical overheating and automatic screen shutdown to protect components.
To check the decoding type, install an application like "CPU-Z" or "AIDA64" and look at the "SoC" or "Device" section, where support for video standards is often indicated.
Basic video codecs: universal compatibility
There is a set of formats that are guaranteed to work on the vast majority of Android devices, starting with the earliest versions. These codecs have become the industry standard for web streaming, video calling, and local media storage. If you plan to share the video with friends or upload it to different platforms, using these formats will ensure maximum compatibility.
The leader here is H.264 (also known as AVC). It provides an excellent ratio of quality to file size, and its hardware implementation is found in almost every smartphone released in the last 10 years. The container for it most often is .mp4 or .mkv.
The second most popular is H.265 (HEVC). This codec allows you to compress video twice as efficiently at the same quality, which is critical for content in 4K resolution and higher. However, HEVC support became widespread only in devices released after 2016-2017. On older state devices, an attempt to open such a file may result in an error.
- 🎬 H.264 (AVC) —the most common format, works on 99% of devices.
- 📹 H.265 (HEVC) —standard for 4K HDR, requires modern hardware.
- 📺 VP9 —native format for YouTube, widely supported in the Google ecosystem.
Also worth note the codec VP9developed by Google. It is actively used in the YouTube service and is often found in web broadcasts. Hardware support for VP9 is present in most mid- and high-end chips, which allows you to watch 4K video in a browser or application without unnecessary load on the system.
New standards: AV1 and the future of compression
The industry is moving towards even more efficient compression, and the codec is becoming the new leader AV1. Developed by the Open Media Alliance, it offers better performance than HEVC and VP9 while being free to use. This makes it extremely attractive to streaming services such as Netflix and YouTube, which are already actively introducing AV1 into their broadcasts.
However, AV1 support at the Android level is still in the process of being introduced. Starting with Android 10, the system provides an API for working with this codec, but the actual possibility of smooth playback depends on the presence of the corresponding block in the processor. Flagship chips such as Snapdragon 8 Gen 2 and newer, as well as some solutions from MediaTekhave already received hardware support for AV1.
If your device does not have a hardware AV1 decoder, playback is only possible using software. This is an extremely resource-intensive task: even powerful processors may not be able to cope with decoding high-definition video in real time, which will lead to jerks and dropped frames.
🔍 Spoiler: Why is AV1 so important?
AV1 allows you to transmit 4K quality video at a bitrate 30-50% lower than H.265. This means significant savings in mobile traffic for users and reduced server costs for content providers.
Audio codecs and containers
Video is only half the story. The audio track must also be decoded correctly. Android has excellent native support for modern audio formats, which allows you to enjoy surround sound even through built-in speakers or connected headphones.
The de facto standard is AAC (Advanced Audio Coding). It is used everywhere: from voice recorders to movie soundtracks. The system also works without problems with the format MP3, although it is considered obsolete due to less efficient compression.
For lovers of high quality sound (Hi-Res), Android supports codecs FLAC and ALAC without data loss. Starting with Android 5.0, FLAC support is built into the system's media stack, so you can simply copy files to the phone's memory and open them with a standard player.
| Codec | Compression type | Android support | Application |
|---|---|---|---|
| AAC | Lossy | Full (all versions) | Streaming, video, calls |
| MP3 | Lossy | Full (all versions) | Music, podcasts |
| FLAC | Lossless | Android 5.0+ | Hi-Res audio, archives |
| Opus | Lossy | Android 5.0+ | VoIP, low bitrate |
| Vorbis | Lossy | Full | Games, WebM video |
The codec deserves special mention Opus. It provides excellent voice quality even at very low bitrates, which is why it is widely used in instant messengers (Telegram, WhatsApp) and video conferencing applications. Android decodes it without any additional settings.
For maximum music quality, use FLAC, but remember that such files take up 5-10 times more space than MP3 or AAC.
Problematic formats and containers
Despite widespread support, there are many outdated or specific formats in the world, which Android “dislikes” by default. Most often, the problem lies not in the video codec itself, but in the container or audio track embedded in the file.
A classic example is the container .avi. By itself, it may contain H.264 video, which the phone can read, but if there is an audio track inside in the format AC3 (Dolby Digital) or DTS, the standard player will display a “No sound” error or refuse to launch the file at all. This is due to licensing restrictions: Android manufacturers do not always include AC3/DTS decoders in the base firmware.
Another category of problematic files is video with a very high bitrate or a specific encoding profile. For example, files encoded in 10-bit color using the Main 10 profile may not open on devices whose decoder only supports 8-bit color.
⚠️ Warning: The .wmv and .rmvb formats have little or no support on Android. To play them, you almost always need to convert or use specialized software with your own codecs.
You should also be careful with files that have the extension .mkv. While the MKV container itself is well supported, it is often used as a "container for everything." There may be subtitles in PGS format or TrueHD audio tracks inside, which the built-in player will simply ignore or cannot process.
☑️ Diagnosis of the problem file
Solution: Third-party players and conversion
If you encounter a file that cannot be played by standard means, do not rush to delete it or look for a converter on your computer. The modern Android application market offers powerful solutions that include their own sets of codecs, bypassing system limitations.
The undisputed leader in this niche is the application VLC for Android. It is free, contains no ads and has built-in support for almost all known audio and video codecs, including AC3, DTS, MKV and older formats like DivX. VLC uses software decoding, so it can run the file even on a device that doesn't have a hardware decoder.
Another great option is MX Player. In the free version it supports most formats, while the paid version (or with a third-party codec installed) opens even the most exotic options. The advantage of MX Player is excellent optimization of control gestures and the possibility of hardware acceleration for many formats.
Recommended procedure in case of a playback error:1. Install VLC for Android from Google Play.
2. Open the file via VLC.
3. If the video slows down, go to the VLC settings and disable “Hardware acceleration.”
4. If there is no sound, check the audio output settings in the player.
As a last resort, if no player can cope (for example, the file is damaged or uses a proprietary codec of a surveillance camera), you will have to use a converter. Apps like Video Transcoder allow you to transcode video into a compatible H.264/AAC format directly on your phone, although this process can take a long time.
💡 Tip: Where can I get codecs for MX Player?
Previously, for MX Player you had to download separate codec packages (ARMv7, ARMv8, x86) from the 4PDA or XDA forum. In modern versions of the application, most codecs are already built-in, but for older devices, searching for a specific package may still be relevant.
Frequently asked questions (FAQ)
Why is 4K video slow on my new phone?
Perhaps the video is encoded in HEVC format with a high bitrate (100+ Mbps) that exceeds the memory or decoder bandwidth of your specific processor. Try using a player with hardware acceleration or reducing the file quality.
Does Android support Dolby Atmos sound?
Yes, starting with Android 9, the system has native support for Dolby Atmos, but its operation requires both the appropriate hardware (speakers or DAC) and a license from the device manufacturer. There should be a “Dolby Atmos” item in the sound settings.
Is it possible to watch AV1 video on an old Android?
Technically, it is possible through software decoding in a player like VLC, but the performance will be low. For comfortable viewing of AV1, it is advisable to have a device running Android 10+ with a processor that has hardware support for this standard.
How to find out which codec is used in a video file?
Use file inspector applications such as “MediaInfo” or the built-in functions of advanced file managers. They will show the exact name of the codec (for example, V_MPEG4/ISO/AVC for H.264) and bitrate parameters.
Why does the MKV file have a picture, but no sound?
Most likely, the audio track is encoded in AC3 or DTS format, licenses for which are not available in your system player. Install VLC or MX Player to solve this problem without converting.