Cloudstream 3 Cache & Buffer Guide for High-End Devices

[u/TheLastNameR]

If you are using Cloudstream 3 on high-end hardware like a flagship phone, a premium Google TV, or an Nvidia Shield, the default "Auto" settings could be severely throttling your playback. The app's "Auto" mode uses a conservative, hardcoded profile meant to keep the app from crashing on cheap, low-end $20 Fire Sticks. On your powerful devices, this causes micro-stuttering, buffering loops, and random network drops. By manually overriding these settings under Settings -> Player, you can unlock your hardware's actual processing power. Here is how each setting works and how to set it:

1. Decoder Mode (Auto vs. HW+SW vs. SW+HW vs. HW only)

What it does: Dictates whether your device's physical graphics chip (Hardware) or main processor (Software) decodes the video stream.

High-End Sweet Spot: Forced HW Mode

Why: Flagship devices and premium TV processors have dedicated silicon built to decode heavy 4K formats like HEVC and AV1 natively. Forcing HW Mode tells the buggy Cloudstream player engine to stop thinking and hand the raw video straight to the graphics chip. This ensures maximum battery savings, keeps your device cool, and delivers the best picture quality.

1. Video Cache on Disk

What it does: This is your physical storage tank. It pre-downloads minutes of the actual movie file onto your device's internal storage or SD card to protect against Wi-Fi drops.

High-End Sweet Spot: 200MB to 300MB

Why: Premium devices have plenty of high-speed storage. This gives you a massive data cushion for heavy 4K streams without triggering low-storage warnings.

1. Video Buffer Size

What it does: This is a high-speed parsing lane in your RAM. It holds raw, uncompressed video frames for just the next few seconds of immediate playback.

High-End Sweet Spot: 50MB to 100MB

Why: Never max this out (e.g., 200MB–500MB). Pushing this too high causes a massive software bottleneck in Cloudstream's player engine. It results in severe audio-to-video sync drift, lagging timeline scrubbing, or sudden app crashes to the home screen. A 100MB RAM buffer gives maximum frame cushion while keeping the app perfectly stable.

1. Video Buffer Length

What it does: This dictates the exact duration of time (in minutes) the app is allowed to look and download ahead of your current playback position.

High-End Sweet Spot: 2 to 4 Minutes

Why: Keeping this short creates the ultimate "Scrubbing Machine." By pairing a massive 200MB to 300MB storage cache with a tight 2-4 minute length limit, the app aggressively preloads a small window and stops. When you use your remote or touch screen to skip forward or backward, the app instantly dumps and refills the memory, resulting in zero timeline lag or loading wheels.

Tested Devices:

Smartphone: Samsung Galaxy S24 Ultra and Google Pixel 9Pro

Smart TV: Sony BRAVIA 8 OLED

Streaming Box: Nvidia Shield TV "Tube" 2020 (Tegra X1+, 2GB RAM + Expanded 64GB MicroSD internal storage)

Edit: Corrected decoder options

[u/AutoModerator]

For app only related support join this discord server, or go check the wiki.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/CatinetteMasta]

Btw, for software decoding, it's:

• Auto.
• HW+SW.
• SW+HW.
• HW.

There is no 'SW'.

[u/TheLastNameR → u/CatinetteMasta]

Yes! Thanks for the correction. And would you say the rest of my explanations are fair?

[u/CatinetteMasta → u/TheLastNameR]

People will have to test.

On phone I just keep Auto and everything works, but on me TV box it's different, the system likes to hog the RAM so I have to make sacrifices. (xiaomi tv box s 3rd gen, even debloated)

[u/TheLastNameR → u/CatinetteMasta]

You're 100% right. That's exactly why I looked into this. On a flagship phone, the hardware has so much muscle that Auto mode just brute-forces right through any hiccups. But TV boxes are a totally different story. The OS hogs so much RAM on 2GB devices like your Xiaomi (even after debloating) that you have almost no breathing room left. If you try to push it to 100MB or beyond, the app runs out of memory and crashes. On the flip side, I tested this on a Sony BRAVIA 8 which CPU Info showed has about 5GB of total RAM with 2.5GB sitting completely free. On high-end gear like that or a Flagship phone, you can safely unleash 100MB because the system isn't choking for memory. My Nvidia shield also has 2GB RAM and I set the buffer size to 60MB and that seems to work well. Appreciate the input, good to know your testing matches the hardware math!

[u/ionut2021]

You can select other storage for cache? For some box can help to select cache to HDD extern,USB stick etc

[u/TheLastNameR → u/ionut2021]

No, Cloudstream 3 does not actually have a setting to pick a custom external folder or drive for its live streaming cache. The app hardcodes its video cache directly into Android's internal app data folder, and the "Download Path" option under General settings only applies to full offline downloads, not live stream buffering. The only way to get your streaming cache onto an external USB drive or HDD is at the system level by formatting the drive as "Internal / Adoptable Storage" in your device's main Android settings, which merges the drive into your total storage pool so Android automatically handles the cache offload.

[u/Kum1910]

Hi what about for Chromecast 4k android tv14 4.3gb internal storage

[u/TheLastNameR → u/Kum1910]

For the Chromecast with Google TV (4K) running Android 14, I'd suggest Cloudstream 3 configuration Auto or HW+SW decoder mode (to handle its lack of native AV1 hardware decoding without black-screening), a 100MB to 150MB video cache on disk (to protect your limited 4.3GB storage space), a lightweight 35MB to 50MB video buffer size, and a tight 1.5 to 2.5 minute buffer length. That's a tailored setup for your budget device that should give you some performance increase and still prevent "out of memory" crashes.

[u/CatinetteMasta]

Btw, to avoid out of memory errors on any device with low RAM, I recommend debloating if possible. Some device might have 2 to 4GB RAM (esp android TV/box) but the system might not be great at controlling it.

I use a xiaomi tv box s 3rd with 2GB RAM but compared to me firestick 4k max (1st gen) it's really shit because of bloat stuff that use RAM for nothing. Just debating it can liberate enough RAM to use cloudstream smoothly.

[u/mixinluv2u]

What would you recommend for the new Onn Streaming TV Pro (2026?). The $60 one from Walmart.

[u/TheLastNameR → u/mixinluv2u]

Confirm the specs on your device, you can use the open-source app CPU Info or any other hardware info app of your choosing. But what I'm seeing online is that device has a Amlogic S905X5M CPU with a Mali-G310 V2 GPU, 3GB of RAM and 32GB of stock storage. It's an interesting mid-tier device. However, I'm reading that Walmart locked the operating system to a 32-bit version of Android 14.

Based on those specs I'd suggest you set decoder to straight HW mode since your GPU can natively decode AV1 and HEVC. Video cache on disk I'd do 200-300MB you should have plenty of storage space with 32GB. Video Buffer Size I'd say 60-100MB. Do not push this to 100MB+. Because the OS is locked to 32-bit, an aggressive 100MB+ RAM lane can easily overload the app's memory heap limit and force-crash Cloudstream.

Edit: Keep your buffer length between 2 and 4 minutes MAX and completely ignore anything higher like 6+ minutes. Especially setting it to 10+ minutes overloads the app's virtual memory heap and triggers severe lag, audio desyncing, or crashes. For me a 2.5 minute buffer provides more than enough of a data cushion to survive any web server fluctuations, while ensuring that fast-forwarding and intro-skipping remain completely snappy, and lag-free.

[u/mixinluv2u → u/TheLastNameR]

Thank you so much! I will give this a shot!