Comparing h.264 vs h.265 video playback on the Fire TV 1, 2, and Fire TV Stick


In the video above, I show how the Amazon Fire TV 1, Fire TV 2, and Fire TV Stick 1 each handle playing video encoded with the h.264 and h.265 codec. I run all three devices through several different test videos at various bit rates. The purpose is to show that, as long as the video codec being used is supported by the device’s dedicated hardware decoder, the CPU of the device is nearly irrelevant when it comes to playing high quality video. This is why, even though the Fire TV Stick has a fairly weak CPU, it can still play video as well as the Fire TV boxes. Continue on if you’d like to read the transcript of the video.

Video Transcript

This is a quick video comparing the 1st-gen Fire TV Stick, 1st-gen Fire TV, and 2nd-gen Fire TV relative to how they each handle h.264 encoded video vs h.265 encoded video. I’m often asked if the Fire TV Stick is a good device for video playback, since it has a much weaker CPU than the Fire TV boxes, so I put together this video to show you that as long as you’re playing video using the right codec, the CPU is almost irrelevant for video playback, because all of these devices have dedicated hardware decoders.

On the left of the screen is the 1st-gen Fire TV Stick, in the middle is the 1st-gen Fire TV, and on the right is the 2nd-gen Fire TV. All videos are being played using the latest stable version of Kodi on stock devices running the latest Fire OS software version. At the top I’ve indicated the video codec being used, the bit rate of the video, and I’ve enabled Kodi’s codec overlay so you can see each device’s CPU usage and player bit rate.

What you’re watching right now is a 40 Mbps h.264 video. This is around the quality you can expect from a Blu-ray video and, as you can see, all three devices are playing the file smoothly without overwhelming the CPU. That’s because all three devices have dedicated hardware designed to decode h.264 video.

If we bump up the bit rate to 60 Mbps, you can see the playback is still smooth and the CPU usage stays pretty much unchanged. At this bit rate we’re already way above the quality of video streamed by services like Netflix and Amazon, which both stream 1080p at less than 10 Mbps. Notice that the bit rate reported by the player is right around 60 Mbps, which is where we expect it to be.

Moving up to the extreme case of a 100 Mbps video, which nobody would realistically use, we start seeing the 1st-gen Fire TV Stick and Fire TV struggle. Notice that even though the devices can’t keep up with the video, their CPU usage hasn’t changed much. You might expect to see 100% CPU usage, but the dedicated video decoder is still the one handling the daunting task of decoding the video, so the CPU doesn’t have much to do. You can see the bit rate reported by the player on the 1st-gen Fire TV Stick and Fire TV is not reaching 100 Mbps, this indicates the hardware decoder is just not capable of decoding this much data fast enough, but the bit rate reported by the player on the 2nd-gen Fire TV is reaching high bit rates, which is why playback is still smooth even at this high of a bit rate.

Now we’ll move to a video encoded with the h.265 codec and start things off at a measly 3 Mbps. Immediately you can see the 1st-gen Fire TV Stick and Fire TV are struggling. That’s because neither device has a hardware decoder capable of decoding h.265 video. The CPU on both devices is pretty much maxed out because it has to take on the task of decoding this video since the dedicated hardware decoder does not support h.265 video. The 1st-gen Fire TV, with it’s more powerful 1.6 Ghz quad-core CPU, is able to almost keep up with the 2nd-gen Fire TV’s dedicated h.265 hardware decoder, resulting in smoother playback than the much weaker 1 Ghz dual-core Fire TV Stick. Neither device was made for h.265 encoded video, so even though it’s just a 3 Mbps bit rate video, it results in a relatively bad viewing experience.

The 2nd-gen Fire TV, on the other hand, does have an h.265 capable hardware decoder. That’s because it’s a 4K device and h.265 is the prefered codec for 4K video streams from Netflix and Amazon Video. Just like with the h.264 videos from before, the 2nd-gen Fire TV’s CPU isn’t doing much work because all the heavy lifting is being done by the dedicated hardware decoder.

Moving up to a 15 Mbps h.265 video, which is around the quality used by Netflix and Amazon for 4K streaming, we can see the 2nd-gen Fire TV handles this without any issues because it was designed with dedicated hardware to handle this exact codec and bit rate. With the previous 3 Mbps h.265 video, the 1st-gen Fire TV was almost watchable due to its CPU capabilities alone, but now at 15 Mbps, the 1st-gen Fire TV’s CPU just can’t keep up anymore, and the Fire TV Stick just has no hope of processing this much data using it’s CPU alone.

Lastly, we’ll bump up the bit rate to 100 Mbps, which again, nobody would realistically use. The 1st-gen Fire TV Stick and Fire TV have no hope of processing this amount of data using their CPU alone, so they’re practically displaying a slideshow of static images at this point. The 2nd-gen Fire TV is handling this 100 Mbps h.265 video without a sweat, thanks to its h.265 capable hardware decoder.

For comparison, let’s switch back to the h.264 video at the same bit rate of 100 Mbps to remind you how well even the relatively weak 1st-gen Fire TV Stick was able to handle this extreme bit rate when a codec that the hardware was designed for is used.

I hope this video was able to demonstrate that, when it comes to playing high quality video, the CPU of a device is not nearly as important as the capabilities of the dedicated hardware decoder. If you enjoyed this video, be sure to hit that like button on YouTube to let me know you’d like to see more videos like this one, and while you’re there, be sure to subscribe to my YouTube channel. I host a weekly series called the AFTVnewscast where I discuss the Fire TV and topics like this on a weekly basis. And of course, keep it locked to for all things Fire TV.

  1. Tony says:

    Thanks for the explanation of h265 and its relationship/usage with 4K material from Netflix etc. Now I understand what they mean by 4K enabled player–it just means it has a hardware decoder for smoother playback of 4k thanks to h265 decoders.

    I’ve also noticed that the cheap Chinese made Android Kodi boxes write 4K on the box. So this explains it has the h265 hardware decoder within it while older generation devices lack this decoder. Now it’s all becoming standard on all newer devices made today.

    • Tony says:

      hmm, I just noticed the new Firetv2 stick lacks 4k playback, so it must lack the h265 decoders (despite being a newer device).
      It seems like they could have easily made it 4k but decided to keep costs down & give this a reason to buy the box. Maybe they’re saving it for firetv3 stick in 2018.

      I don’t plan to own a 4k tv anytime soon, so it doesn’t really matter to me, but good to keep in mind for those with 4k tvs.

      • clocks says:

        The new Fire tv stick does x265. x265 is a compression scheme, and can be used for any resolution.

      • AFTVnews says:

        Having an h265 hardware decoder does not mean the device is 4K. It’s just that h265 is the most common codec used for 4K video, so pretty much all 4K devices have an h265 decoder.

        The Fire TV Stick 2 does have an h265 decoder, but it is not a 4K device. This is because h265 is much more efficient than h264, so even 1080p devices will likely have h265 hardware decoders from now on. Streaming h265 video is cheaper than streaming h264 video for Amazon because h265 can produce smaller file sizes, which saves on bandwidth costs, without reducing the image quality.

        All h265 hardware decoders are not equal. The hardware decoder in the Fire TV 2 can decode up to 2160p video at 30fps, while the h265 hardware decoder in the Fire TV Stick 2 can only decode up to 1080p at 30fps.

  2. Masterblaster says:

    H.265 will be standard in all streaming services due to it’s high compression / lower bandwidth requirements. Dedicated H.265 hardware chips will replace current H.264. So don’t think that if you don’t have a 4K TV you won’t need a box without H.265. Netflix, Playstation vue , Vudu want it.

  3. Joe says:

    Great video comparison! Would you also do one with the Mi Box included.

  4. clocks says:

    How do you open the codec overlay in Kodi. I know in SPMC and MrMC you can just click the MENU button during playback, but that does not seem to work in Kodi. thanks

    • IcHip says:

      Using your Fire Tv Android remote(probably iOS works too,I only have Android devices to work with), while video is playing, bring up the virtual keyboard and press “O”(a in “owel”).

  5. Ailyn says:

    Thank you for the excellent post. Is love to see similar comparisons with other products if ever possible. Items like the new MI box would be great. Keep up the good work!

  6. Rob P says:

    Thanks for the great post. That was one of the main reasons I upgraded to the Fire TV 2. A lot of my files are x265 8 bit 1080P. I want to start experimenting with x265 10 bit files and see how the box does.

  7. Chris Lucchesi says:

    Hey Rob, 10bit X265 doesnt go to well. The FTV2 cant keep up. 8bit no problem, 10bit, youll start to see the stutter….

  8. scofield27 says:

    i just got my mi box,
    i was very disappointed that it doesn’t play 10 bit hevc, just regular hevc files…
    is it going to change ? maybe a hardware update in the future ?

  9. tagteam3283 says:


  10. Sunrise 495 says:


  11. Richard says:

    this has been in the back of my head for awhile and I’ve finally crystallized my question. For those of us without 4k displays it would be interesting to see how the various fTV’s do with 720p and 1080p encodes using x265.
    The reduced file size would be worth it if the CPU in the first gen boxes can keep up.
    Any chance of doing a comparison like that?

  12. Liz says:

    Why can’t my Gen 1 Fire TV box playback 1080/60p mp4 files without stutter, freezing, etc? Tried VLC player, Archos and others with no luck. My files are 4gb fat32 recorded on a Panasonic 770v..from reading article above it would seem playback should not be an issue. Thx

Leave a Reply

Your email address will not be published. Required fields are marked *


Get AFTVnews articles in your inbox!

Get an email anytime a new article is published.
No Spam EVER and Cancel Anytime.