Hardware vs Software Decoding: Which Setting Your Player Needs

Use hardware decoding by default. Your streaming device’s video chip decodes H.264, HEVC and, on newer models, AV1 efficiently, including 4K. Switch to software decoding only for a channel that shows green blocks, a black picture or will not start, and mainly for HD or lower. On a stick’s processor, software decoding struggles with 4K, heats the device and can let the sound drift.

This guide explains what decoding is, which codecs live channels use, how to recognize the wrong setting from what you see, and where the option sits in common players. Change one thing at a time, and you will know exactly what fixed the problem.

What a video decoder does

A live channel reaches your device compressed. Compression removes most of the data by describing how each frame differs from the ones around it, which is why an HD channel fits through a home internet connection. Before anything appears on screen, the device has to rebuild every frame from that description. That job is decoding.

The format of the compression is called a codec, such as H.264 or HEVC. The part of the device that rebuilds the frames is the decoder. There are two places it can run.

• Hardware decoding: a dedicated video block inside the device’s chip, built only for this task. It is fast, uses little power and handles 4K, but only for the codecs and profiles it was designed for.
• Software decoding: a program running on the device’s main processor. It can be updated to handle unusual streams, but it competes with everything else the device is doing.

Android’s own developer documentation for MediaCodecInfo sums up the trade-off: software-only codecs run in a tighter security sandbox, but they do not provide any performance guarantees. That last part is what you notice on a streaming stick.

The codecs used in live TV

Most channels use one of four codecs. Your device needs a decoder for each one it plays, ideally in hardware.

H.264 is the workhorse. Wikipedia describes it as by far the most commonly used format for recording, compressing and distributing video. HEVC is its successor; according to the HEVC article on Wikipedia, it achieves 25% to 50% better compression at the same quality, which is why 4K channels use it. AV1 is an open, royalty-free format from 2018 that newer devices decode in hardware.

On Android, the platform itself lists decoders for these formats. The Android supported media formats page shows HEVC decoding from Android 5.0 and AV1 from Android 10, mandatory from Android 14, while noting that support on devices other than phones and tablets may vary. Whether a given decoder runs in hardware is up to the device maker.

Which devices decode what in hardware

Device makers publish their codec lists, and they are worth a look before you blame a player. Amazon’s Fire TV device specifications list the video codecs for each stick.

The pattern is simple. H.264 and HEVC are everywhere, while AV1 needs a device from roughly the last few years. If a channel uses a codec your device lacks in hardware, the player either falls back to software or fails, and that is when the decoder setting starts to matter.

Why “supports HEVC” is not the whole story

A codec name on a spec sheet hides two more details: the profile and the level. The profile describes which compression tools the stream uses, and the level sets limits such as resolution and frame rate. A hardware decoder supports specific combinations, not the codec in general.

Android’s format page shows this in its minimum requirements. For HEVC it asks for Main Profile Level 3 on phones and Main Profile Level 4.1 on Android TV devices. Samsung’s TV specifications list HEVC Main and Main10 separately, because Main10 is the 10-bit profile used for HDR and needs extra support.

In practice, that explains a puzzling symptom. A device can play every HD HEVC channel perfectly and still show a black screen on one 4K HDR channel, because that channel uses a profile or level beyond what its hardware handles. Software decoding will not save a 4K HDR stream on a stick; the HD version of the channel, or a more capable device, will.

Interlaced channels and deinterlacing

Some live channels, especially older broadcast feeds, are interlaced. Each frame is sent as two half-frames of alternating lines, a format from the days of tube TVs. Before a modern flat screen can show it, the player or the device has to combine the halves. That step is called deinterlacing.

On many devices, deinterlacing happens in the same hardware video path as decoding. When you force software decoding, the player may deinterlace in software instead, or not at all. The tell-tale sign is fine horizontal comb lines along the edges of anything that moves, such as a scrolling news ticker or a player running across a field.

If you see comb lines only after switching to software decoding, switch back. If you see them in both modes, look for a deinterlacing option in the player’s video settings, and tell us the channel name so we can check the feed.

When software decoding helps

Software decoding is a repair tool, not an upgrade. It helps in a small number of situations, all of them specific to a channel rather than to your whole setup.

• A stream with errors. Hardware decoders are strict. When a stream has damaged or unusual data, some chips show green or pink blocks, freeze, or give up. A software decoder is often more forgiving.
• An unusual format. Older MPEG-2 feeds, interlaced video or uncommon profiles may not be supported by the hardware block on a particular stick.
• A device bug. A system update occasionally breaks hardware decoding for one format until the next fix. Software decoding bridges the gap.

In each case, the channel is SD or HD. At those sizes, even a modest processor keeps up, so the fallback works well.

When software decoding hurts

The trouble starts when software decoding is left on for everything, or used on demanding channels. A 4K frame has four times the pixels of a 1080p frame, and a channel at 50 or 60 frames per second doubles the work again compared with 25 or 30.

A streaming stick’s processor is designed to run menus and apps, not to rebuild millions of pixels sixty times a second. When it cannot keep up, frames are dropped, motion stutters, and the device heats up. A hot stick slows itself down to protect the chip, which makes the stutter worse the longer you watch.

Software decoding also needs working memory for the frames it rebuilds. On a 1 GB stick that already holds a large channel list and a full guide, that extra demand can push the player past its limit, and the system closes it. If a player closes only when you play a 4K channel in software mode, memory is the likely reason; our guide on an IPTV app that keeps crashing covers the other causes.

There is also the audio. Players usually keep sound and picture together by timing the video to the audio. When the video decoder falls behind, the picture lags behind the sound, and after a while you see lips moving out of step. If that happens, check the decoder before changing any audio delay settings; our guide to IPTV audio out of sync covers the other causes.

Symptoms of the wrong decoder setting

You can usually tell which way to switch from what you see. Use the table to match the symptom, then test on the same channel.

The last row matters most. A spinning circle means the player is waiting for data, and no decoder setting can speed up the network. Our nine buffering fixes deal with that case, and our guide to IPTV buffer size settings explains the buffer itself.

How resolution, frame rate and HDR change the choice

The higher the quality of the channel, the stronger the case for hardware decoding. Think of it as a ladder.

SD and 720p at 25 or 30 fps

Both decoders work on nearly any device. This is the safest place to use software decoding when a channel misbehaves.

1080p at 50 or 60 fps

Hardware is clearly better. Software decoding may work on a stronger box but often drops frames on a 1 GB stick, which shows up as uneven motion during sports.

4K

Keep 4K on hardware. If a 4K channel will not play in hardware mode, the device likely lacks support for that stream’s codec or profile, and switching to software rarely rescues it. Watch the HD version of the channel instead, or consider a device with full support.

HDR

Keep HDR channels on hardware decoding too. The hardware video path is the one device makers design and test for passing HDR to the TV. If HDR looks wrong or the screen goes black, the cause is more often the HDMI connection or the TV’s HDR mode than the decoder; our 4K HDR requirements guide covers that chain.

If you have an IPTV subscription with 4K channels, this is the setting to get right first: hardware decoding on a device that lists HEVC, and a wired or strong 5 GHz connection.

Where the decoder setting lives in common players

Every major player has the option, but the name and the menu differ. The paths below come from each app’s own documentation or source where available.

VLC for Android

VLC’s own description of the options is a good summary of the whole topic: Disabled gives better stability, Decoding may improve performance, and Full may improve performance further. Leave it on Automatic. Choose Disabled only to test a problem channel, and Decoding acceleration if Full causes display glitches on your device.

Kodi

Kodi’s documentation lists hardware acceleration options in the Processing section of the video player settings, named after each platform’s decoder: DXVA2 on Windows, VAAPI or VDPAU on Linux, and VTBDecoder on Mac. They appear only when the settings level is set to Advanced or higher, so raise the level at the bottom of the settings screen if you cannot see them.

MX Player, TiviMate and TV apps

The players below make the choice in different ways. Some let you switch per video, some only globally, and TV apps mostly leave it to the device.

MX Player

MX Player’s store listing highlights two things: its HW+ hardware decoder, which handles more videos in hardware, and multi-core decoding for software playback. Try HW+ first, then software for a stubborn file or stream.

TiviMate

TiviMate keeps its decoder choice in the playback settings, next to the buffer size and frame rate options. Our TiviMate Fire TV setup guide lists the playback settings worth changing and the order to try them.

Smart TV and Apple TV apps

Apps on Samsung, LG and Apple TV usually rely on the device’s built-in video system and offer fewer decoder choices, if any. If a channel fails there, try another player or the HD version of the channel rather than looking for a hidden setting.

Phones, tablets and computers

Phones and tablets have capable hardware decoders, because video playback is one of the main things people do with them. Software decoding works on a recent phone, but it drains the battery faster and makes the phone warm, so keep hardware on unless a specific channel needs the fallback.

On a computer, the graphics chip does the hardware decoding. Kodi’s documentation shows the option names by system: DXVA2 on Windows, VAAPI for Intel graphics and VDPAU mainly for NVIDIA graphics on Linux, and VTBDecoder on Mac. A computer’s processor is much stronger than a stick’s, so software decoding is a more realistic fallback there, even for HD at 60 frames per second.

Laptops on battery are the exception. Power-saving modes can limit the processor, and a stream that played fine on the charger may stutter on battery with software decoding.

How to see which decoder is in use

Guessing is slower than looking. Many players can show a stream information screen during playback, with the codec, resolution, frame rate and the decoder actually in use. Kodi calls its version Player process info, and its documentation refers to it when explaining refresh rate settings.

That screen answers three useful questions at once. Is this channel H.264 or HEVC? Is it 50 or 60 frames per second? And did the player really use hardware, or did it quietly fall back to software because the hardware could not handle the stream?

If your player has a dropped-frames counter, watch it for a minute. A number that climbs steadily means the decoder cannot keep up, which points to software decoding or an overheating device. A number that stays near zero while the picture still pauses points to the network instead.

A simple test routine

Decoder problems are easy to misread, because streams change from minute to minute. This routine keeps the test fair.

1. Pick one problem channel and note exactly what you see, and when: on start, after a few minutes, or during fast motion.
2. Check a second channel of the same quality. If it has the same issue, the cause is probably not the decoder.
3. Change only the decoder and leave every other setting as it was.
4. Watch for ten minutes. Some problems only appear once the device warms up or a scene gets busy.
5. Keep the change only if it clearly helped. If nothing changed, switch back to hardware, so you do not carry a slower setting into every other channel.

Some players let you choose the decoder per channel or per stream. When yours does, use software decoding only on the channel that needs it and keep everything else on hardware.

Heat, power and the device itself

Decoding problems and heat feed each other. Software decoding raises the processor load, the stick gets hot, and a hot stick slows down to protect itself. Even hardware decoding can stutter on a stick that is overheating for other reasons.

• Use the HDMI extender that came with the stick, so it hangs away from the TV’s warm back panel.
• Use the original power adapter, not a TV USB port. An underpowered stick can show playback errors that look like decoder faults.
• Close apps you are not using, and restart the stick once a week if you leave it on standby.

If the stick is slow everywhere, not only in your player, our guide to a slow Fire TV Stick with full storage covers storage, cache and background apps.

When it is time for a different device

If you find yourself switching decoders often, the device may simply be short of hardware support for the channels you watch. A stick that lacks AV1, or a TV from 2018, will meet more streams it cannot handle in hardware as services adopt newer codecs.

Before you buy, check the maker’s codec list for H.264, HEVC and AV1, and make sure the device runs the player you want. Our streaming device buying guide compares current options, including memory and Ethernet, which matter as much as codecs.

Still seeing problems? What to tell us

If a channel misbehaves in both decoder modes, the stream itself may have an issue, and we want to know. Try the same channel on a second device. If it fails there too, the problem is on our side; if it plays, the first device or player is the cause.

Send Online Support the channel name, your device model, the player and its version, the decoder settings you tried, and a phone photo of the screen if you see blocks or colours. With that, we can check the stream and tell you whether a setting, a player or a device change is the real fix. For other devices and players, the setup guide has step-by-step pages.

Questions people ask