Recommended Free Tools
To stop a Raspberry Pi from thermally throttling during an FFmpeg YouTube stream, first confirm that throttling is happening while the stream runs. Then reduce avoidable encoding load, improve airflow, and add model-compatible cooling if needed. A high temperature by itself does not prove that heat caused dropped frames: undervoltage, input decoding, storage, and upload conditions can also affect performance.
Confirm whether heat is causing the problem
Raspberry Pi’s hardware documentation defines 85°C as the SoC temperature limit. Between 80°C and 85°C, Arm cores are progressively throttled; at 85°C, Arm and GPU frequencies are throttled. These protections reduce performance to control temperature. The same documentation says a supply voltage below its specified threshold can also trigger throttling, so check the status rather than diagnosing by temperature alone. Raspberry Pi computer hardware documentation
Check temperature and throttling flags during the stream
- Start the FFmpeg stream you want to diagnose and let it run under representative conditions. Compare readings while streaming with readings at idle.
- In another terminal, run
vcgencmd measure_tempto get an instantaneous SoC temperature reading. Raspberry Pi describes this command as communicating with the GPU and providing an accurate instantaneous reading. - Run
vcgencmd get_throttledto inspect throttling flags on supported systems. Interpret the returned flags using documentation appropriate to your board and software version; the command’s output is not, by itself, a full explanation of a dropped frame. - You can also read
/sys/class/thermal/thermal_zone0/temp; divide its millidegree value by 1,000 for Celsius. Raspberry Pi cautions that Linux-based readings can be inaccurate on some architectures.
Log temperature, clock behavior, and throttling state throughout a representative stream. If clock performance falls without a corresponding thermal rise, investigate the power supply and undervoltage state. If throttling is not indicated, also check CPU load, input decoding, storage access, and upload stability before changing cooling hardware.
Reduce FFmpeg’s workload without guessing at a universal command
The right encoding path depends on the Raspberry Pi generation, the installed FFmpeg build, the input format, and the settings you need to sustain. Raspberry Pi’s H.264 performance paper describes Raspberry Pi 5 software encoding with libx264 and a Raspberry Pi 4 comparison using the hardware encoder h264_v4l2m2m. Do not assume the Pi 4 hardware path is available or equivalent on a Pi 5. Check the encoders and pixel formats available in your own build, then test the selected path under stream conditions. Raspberry Pi H.264 performance paper
#1 Best Overall
- The 30mm fan with 2pin interface connected to the pi motherboard, providing a good cooling effect for Raspberry Pi, The 30x30x7mm computer fan size is 30mm, making it easy to install
- 3007 cooling fan run smoothly(15.92dBA), Long life (30,000 hours) keep CPU safe without overheating
- 30mm case fan unique terminal interface with two terminals, Its connector is separating, 1-to-2 interface connector Interface for dual speed mode (3.3V and 5V DC)
- 3007 case fan compatible with Raspberry Pi B, B+, A+, 2, 3, 4 5 model B and B+ and Pi Zero/Zero W other robotic projects and development boards
- This fan can be installed for most of the standard Raspberry Pi cases and also is compatible with RetroFlag NESPI Case
Tune one variable at a time
- Note the source resolution and frame rate, and begin with the intended output settings. Establish a baseline for temperature, throttling state, frame delivery, and stream health.
- If the Pi cannot sustain the workload, lower resolution or frame rate one step at a time and repeat the test. This can reduce the work needed for input processing and encoding.
- If you use
libx264, test a less computationally demanding preset. Raspberry Pi’s paper showsultrafastwith thezerolatencytune in a Pi 5 low-latency software example; those settings are examples, not a universal best configuration. Faster encoding can trade away compression efficiency or other quality characteristics, so judge the result at your actual output quality and latency target. - If your board and software pipeline support a hardware encoder for the chosen format and pixel format, test it as an alternative. Confirm availability in the installed build rather than copying another model’s command.
- Keep enough upload headroom for the chosen bitrate and monitor YouTube’s stream health during a test broadcast. A Pi that can encode a setting may still fail to deliver it reliably over the available connection.
Keep the output within YouTube’s ingest guidance
YouTube’s live encoder guidance recommends RTMP or RTMPS, supports H.264, and recommends constant bitrate (CBR). It recommends a two-second keyframe frequency and says not to exceed four seconds. Its H.264 bitrate recommendations include 14 Mbps for 1080p30 and 8 Mbps for 720p30. These are ingest recommendations, not guarantees that a particular Raspberry Pi can encode those settings without throttling. Choose a resolution, frame rate, and bitrate the board can sustain while fitting the available upload bandwidth, and check YouTube’s current guidance before going live. YouTube live encoder settings
Improve airflow, then choose compatible cooling
Cooling is worth changing when your measurements show sustained thermal throttling during the workload. Raspberry Pi identifies high ambient temperatures, persistent compute-intensive workloads, airtight enclosures, and more extreme overclocking as situations where extra cooling may help; video processing can be a sustained load that exposes throttling. Start with unobstructed airflow and better ventilation. Positioning the board so air can move over a heatsink can improve its effectiveness.
Rank #2
- This is Official Active Cooler for Raspberry Pi 5
- Combines an Aluminium Heatsink with a Temperature-Controlled Blower Fan to accelerate heat dissipation
- How to Install: Connect the 4pin cable to the fan header on RPi 5, and fix the Active Cooler via spring-loaded push pins
Raspberry Pi’s hardware documentation says, “A heatsink or small fan can reduce thermal throttling and improve performance.” Its cooling white paper advises: “If you find that your Raspberry Pi is throttling during your usual workload, then you may need to add extra cooling.” Raspberry Pi computer hardware documentation · Raspberry Pi cooling white paper
Passive heatsink or active fan?
- Improve passive airflow first if the enclosure is restrictive or air cannot circulate around the board. This avoids adding fan noise or another power connection.
- Consider a compatible heatsink when the board’s sustained workload throttles and the case allows it to fit and receive airflow.
- Consider active cooling when sustained workload or warm surroundings continue to cause throttling despite improved ventilation. Account for fan noise, power, and case compatibility.
Match the cooler and case to the exact Pi model. Raspberry Pi’s guidance on Pi 5 active cooling and Pi 4 case fans applies to those models and their described conditions, not automatically to every board or stream. Its Pi 5 article discusses passive cooling limits under heavy stress-test conditions; it does not establish a universal time threshold for FFmpeg streaming. Raspberry Pi 5 cooling article · Raspberry Pi 4 Case Fan article
Rank #3
- Compatible with Raspberry Pi 5 --- This Armor Lite V5 Aluminum Heatsink is only designed for Raspberry Pi 5 4GB/8GB.
- Support PWM Speed Control --- Different from ordinary fans, this cooling fan supports PWM speed regulation, which is perfectly compatible with Raspberry Pi OS.
- Good Heat Dissipation Effect --- With 3510 ultra-quiet cooling fan and thermal pads, it can lower the temperature of Raspberry Pi Board quickly.
- Lightweight and Easy to Install --- With screwdriver and 2pcs screws, it's easy to fix the heatsinks with Raspberry Pi Board.
- Package Includes: 1 x Armor lite V5 for Raspberry Pi 5, 1 x Screw driver, 2 x Screws, 4 x Thermal Pads, 1 x User Manual;
Do not raise the thermal limit or treat overclocking as a cooling fix. The thermal controls are protective, and nonstandard overclock settings can have consequences. Diagnose the cause, reduce unnecessary encoding load, improve ventilation, and then select compatible cooling if the measured workload still throttles.
Troubleshoot common streaming symptoms
| Symptom | What to check | Next step |
|---|---|---|
| Temperature reaches the 80–85°C range and throttling flags appear during the stream | Compare readings with idle, and note whether the stream’s sustained workload coincides with the flags. | Reduce encoding load and improve airflow; consider compatible active cooling if throttling persists. |
| Clock performance falls, but temperature does not rise with it | Check the supply-voltage and undervoltage state. | Investigate the power supply and connections before buying a cooler. |
| Frames drop but no thermal throttling is indicated | Check CPU load, input decoding, storage, upload bandwidth, and YouTube stream health. | Test a lower output resolution or frame rate, or isolate the part of the pipeline that cannot keep up. |
| Copied FFmpeg command fails or a hardware encoder is unavailable | Check the Pi model, FFmpeg build, encoder list, and supported input pixel format. | Use an encoding route supported by that board and build; the Pi 4 and Pi 5 paths are not interchangeable. |
| The board runs cool at first, then slows during a longer stream | Observe temperature and flags over a representative sustained run, not just at startup. | Reduce sustained compute load and check enclosure ventilation before choosing model-compatible cooling. |
| YouTube reports unstable stream health | Check bitrate against upload capacity and verify encoder settings and keyframe interval. | Test with adequate upload headroom and follow YouTube’s current ingest guidance. |
Or let it run in the cloud
If the aim is to keep uploaded video looping on a YouTube channel, rather than stream from a live camera, StreamNeo avoids running FFmpeg on the Pi: upload a recording or build a playlist, add your YouTube stream key, and go live. Nothing has to stay on at home. Your uploaded video streams at its original quality up to 4K 60fps for one flat price per slot; there are no quality tiers. If YouTube drops the stream, StreamNeo automatically attempts recovery.
Rank #4
- Official RPi 5 Active Cooler -- This is Official RPi Active Cooler for the latest RPi 5 4GB/8GB Board
- Composition--The RPi 5 Active Cooler is composed of Temperature-controlled Blower Fan and Aluminium Heatsink and comes with Thermal Tapes to accelerate heat dissipation
- Input Voltage--5V DC (supplied via four-pin fan header on RPi 5)
- How to Install-- Connect the 4pin cable to the fan header on RPi 5, and fix the Active Cooler via spring-loaded push pins
- NOTE -- RPi 5 Board is NOT Included
The first day is free with no card required. Monthly service is $9.99 per month. StreamNeo is for YouTube and plays uploaded videos; it does not stream from a camera. Learn about StreamNeo or start your free day.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
