Free tools Windows power users keep installed
One-click scans. No signup required.
To stop a Raspberry Pi from thermally throttling during an FFmpeg YouTube stream, first confirm that heat is actually triggering throttling while the stream runs. Then reduce encoding load and improve airflow; add a compatible heatsink or fan if sustained throttling continues. A hot board alone does not prove heat caused dropped frames, and low supply voltage can also trigger throttling.
Confirm that heat is the problem
Raspberry Pi’s hardware documentation defines 85°C as the SoC temperature limit. From 80°C to 85°C, Arm cores are progressively throttled; at 85°C, Arm and GPU frequencies are throttled. These protective controls reduce performance to manage temperature. The same documentation notes that falling below the specified supply-voltage threshold can also trigger throttling, so check both temperature and throttling state before changing the cooling setup. Raspberry Pi computer hardware documentation
As an Amazon Associate I earn from qualifying purchases.
Measure during a representative stream
Run the checks while FFmpeg is doing the same work that normally causes trouble, then compare the readings with the Pi at idle. Repeat the checks over time rather than relying on a single temperature reading.
Recommended Free Tools
vcgencmd measure_tempreports the current SoC temperature. Raspberry Pi describes this GPU-reported reading as an accurate instantaneous temperature.vcgencmd get_throttledreports throttling flags on supported systems. Interpret the flags using documentation appropriate to your board and software version.cat /sys/class/thermal/thermal_zone0/tempreads the Linux thermal-zone value in millidegrees Celsius; divide it by 1,000 to get Celsius. Raspberry Pi cautions that Linux-based readings can be inaccurate on some architectures.
Log temperature, clock, and throttling state while streaming if you need to see whether they change together. If clocks fall without a corresponding temperature rise, check the power supply and undervoltage state. These checks help identify conditions, but no single command proves why frames dropped: capture load, input decoding, storage, upload bandwidth, voltage, and thermal behavior can interact.
#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
Reduce FFmpeg’s encoding load
The correct encoding route depends on the Raspberry Pi model and the installed FFmpeg build. Raspberry Pi’s H.264 performance paper uses libx264 software encoding in its Raspberry Pi 5 examples and compares it with the h264_v4l2m2m hardware encoder on Raspberry Pi 4. Do not assume the Pi 4 hardware path is available on a Pi 5, or that an encoder exists in your particular FFmpeg build. Raspberry Pi H.264 performance paper
Check your board and FFmpeg build first
- Identify the exact Raspberry Pi model and note its case, power supply, source format, and the resolution and frame rate you are encoding.
- Check which encoders your installed FFmpeg build exposes with
ffmpeg -encoders. Look for the software or hardware encoder you intend to use; availability and supported input formats vary by board and build. - Run a representative stream and observe CPU load, temperature, clocks, and throttling state. Test one change at a time so you can tell whether it helped.
Lower the workload in measured steps
- Start with the source’s actual resolution and frame rate. If the Pi cannot sustain the encode, test a lower output resolution or frame rate, changing one at a time.
- For
libx264, a less demanding preset can reduce encoding work, generally at a quality or compression-efficiency trade-off. Raspberry Pi’s Pi 5 low-latency example uses theultrafastpreset andzerolatencytune; treat that as an example configuration, not a universal command for every input or stream. - If the board and software pipeline support it, test an appropriate hardware encoder. Confirm that its supported pixel formats match your input and that the result is stable in a real stream.
- Choose settings the specific Pi can sustain while leaving upload headroom. A stream can suffer even without thermal throttling if encoding, capture, storage, or network capacity is the limiting factor.
Keep YouTube ingest settings in view
YouTube’s current live encoder guidance recommends RTMP or RTMPS, supports H.264, and recommends constant bitrate (CBR). Its H.264 recommendations include 14 Mbps for 1080p30 and 8 Mbps for 720p30. These are YouTube ingest recommendations, not a promise that a Raspberry Pi can encode at those settings without overload. Choose the highest quality your board can sustain while fitting available upload bandwidth, and check YouTube’s guidance before going live because platform requirements can change. YouTube live encoder settings
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
YouTube recommends a two-second keyframe frequency and says not to exceed four seconds. Keep the keyframe interval within that guidance when configuring the encoder. Test the stream and monitor YouTube’s stream health before relying on it live.
Improve airflow, then add compatible cooling
First make sure the Pi has unobstructed airflow: improve ventilation around the board, avoid an airtight enclosure for a sustained compute-heavy workload, and consider orientation and ambient temperature. Airflow over a heatsink makes it more effective.
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;
Raspberry Pi says a heatsink or small fan can reduce thermal throttling and improve performance. Its cooling guidance identifies high ambient temperatures, persistent workloads, and airtight enclosures as situations where extra cooling can help; video processing is a sustained compute-intensive workload that may expose throttling. The 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 cooling guidance · Raspberry Pi cooling white paper
If logs show persistent thermal throttling after you have reduced avoidable encoding load and improved ventilation, consider a model-compatible heatsink or fan. Check that the cooler fits both the exact board and its case; Pi 4 and Pi 5 cooling products are not interchangeable by assumption. A fan can improve cooling under sustained load, but adds noise and requires suitable power and case fit.
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
Raspberry Pi’s Pi 5 cooling article discusses passive cooling becoming insufficient during heavy workloads lasting beyond 200 or 300 seconds in its reported stress-test context. That is not a universal time limit for other models or for this exact streaming workload. The Pi 4 Case Fan article likewise concerns Pi 4 and sustained full-speed operation, not every Pi setup. Raspberry Pi 5 cooling article · Raspberry Pi 4 Case Fan article
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsAvoid unsafe shortcuts
Do not raise the thermal limit or treat overclocking as a cooling fix. The thermal controls are protective, and Raspberry Pi warns that nonstandard overclock settings can have consequences. The safer sequence is to diagnose the cause, reduce avoidable encoding load, improve ventilation, and use compatible cooling if the workload still produces persistent thermal throttling.
Troubleshoot by symptom
| What you observe | What to check | Next step |
|---|---|---|
| Temperature reaches the documented throttling range and throttling flags appear during the stream | Compare temperature, clocks, and flags under the representative workload and at idle | Reduce encoding load and improve airflow; add compatible cooling if throttling persists |
| Clock or performance falls without a corresponding temperature rise | Supply voltage and undervoltage state | Investigate the power supply rather than assuming a thermal cause |
| Frames drop but no thermal throttling is observed | CPU load, input decoding, storage, and upload bandwidth | Test lower resolution or frame rate, verify the encoder path and input format, and check upload headroom |
| A hardware encoder is missing or rejects the input | Board generation, installed FFmpeg encoders, and supported pixel formats | Use a supported software path or adjust the pipeline only after confirming the board and build capabilities |
| The Pi runs cooler after adding a heatsink but still throttles | Airflow, enclosure, sustained load, room temperature, and voltage state | Improve ventilation, reassess encoding complexity, and confirm whether the remaining throttle is thermal or voltage-related |
Or let it run in the cloud
If the goal is a 24/7 YouTube stream of uploaded videos, StreamNeo avoids keeping a Raspberry Pi or home computer running: upload a recording or build a playlist, add your YouTube stream key, and go live. It loops the video from the cloud and automatically recovers if YouTube drops the stream. Your upload streams as made, up to 4K 60fps, at one flat price per slot. The first day is free with no card. Monthly service is $9.99 per month.
See StreamNeo or current plans. Start your free first 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.
