> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/common-errors-and-known-issues/overheating.md).

# Overheating

Mobile and laptop devices may overheat under prolong use

[VDO.Ninja](https://vdo.ninja/) offers a lot of power and unconstrained video quality. Some devices however will overheat if pushed for prolonged periods though, as they were not designed necessary for professional streaming video applications in mind.\
\
Still, there are steps you can take to minimize the heat generated by devices with software settings and configurations.

### Lowering the quality

For long games, conferences, and other events, use the [event preparation checklist](https://docs.vdo.ninja/guides/streaming-sports-and-events.md#prepare-for-a-full-event) to test power and cooling before going live.

The viewer has control over the requested quality. 1080p video on a mobile device uses up a lot of power, including by data-transmission and the video encoding itself. Try using a lowering resolution, either by adding [`&quality=2`](https://docs.vdo.ninja/advanced-settings/video-parameters/and-quality.md) to the publisher's link or by adding [`&scale=50`](https://docs.vdo.ninja/advanced-settings/video-parameters/scale.md) to the viewer link.

Lowering video bitrate can also reduce load. Try a lower target, such as `https://vdo.ninja/?view=MYSTREAM&codec=h264&scale=50&bitrate=1500`, and compare motion quality and temperature. [Defaults depend on the capture mode and device](https://docs.vdo.ninja/guides/default-resolution-and-bitrate.md).

### Hardware encoders on mobile devices

Hardware encoding can reduce CPU load and heat. If the normal codec is expensive on the phone, compare [`&codec=h264`](https://docs.vdo.ninja/advanced-settings/video-parameters/codec.md) on the direct viewer link. H.264 is often hardware-encoded on phones, but the device, browser, capture mode, and available encoder resources decide what is used.

Compare temperature and sustained frame rate with the actual setup. A codec request does not guarantee hardware acceleration or a particular resolution. See [hardware-accelerated video encoding](https://docs.vdo.ninja/guides/hardware-accelerated-video-encoding.md) for details.

### Meshcast.io and server-based restreaming

VDO.Ninja is peer-to-peer-based, which works great for linking one camera to one viewer. The more viewers though, as mentioned, the more load is created on that guest. Just the act of uploading data uses power, so mobile devices are also quite poor at restreaming to multiple viewers even if encoding video wasn't already an issue. This is why the video quality on mobile devices between guests is set very low by default.

First close duplicate viewers and pause unused director previews. If several viewers still need the feed, [Meshcast](https://docs.vdo.ninja/guides/meshcast-setup.md) can distribute one upload through a server. Check its current plan limits for the intended audience and event length.

### Group rooms, multiple-scenes, or multiple viewers

Every viewer of a stream adds to the heat and load experienced by the publisher of that stream. To reduce heat as much as possible, only allow one viewer of a stream to be active. Group-scenes, multiple-guests in a room, and multiple view-links each consistent as an active viewer. There are ways to optimize in these situations, but they may not be obvious. ([`&optimize=0`](https://docs.vdo.ninja/advanced-settings/video-bitrate-parameters/optimize.md), for example).

In the case of an iOS device, since it only has 3 hardware encoders, the device will switch to VP8-software mode or just stop working all together if those get exhausted. iOS devices are rather poor at software-encoding video, especially at higher resolutions, so be careful.

You can force-limit the number of connections and viewers with the [`&maxconnections=1`](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-maxconnections.md) parameter, added to the publisher's URL. If you are accidentally viewing the video stream multiple times, this will help prevent more than one viewer from having access.

### Start with a full-battery

Charging a mobile phone creates heat. If you start charging your device after you've already started streaming, that will increase the heat. Try starting with the phone already at a 100% full-charge to avoid even more unnecessary heat.

### Smartphone add-on heatsink and fan

Professional cameras do often include a small fan inside them to reduce heat. Consider buying a heatsink that can be mounted onto the back of your smartphone, with an optional fan to turn on if it starts getting hot. These are not super common, probably not super effective, but they can be had for not much money.

![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MZHXv1G8N0MDxwotaT9%2F-M_PzwZo9g2PX_c78CO-%2F-M_QI4EBP5bH8MY3SthZ%2Fimage.png?alt=media\&token=de73abe7-7703-401f-afb1-46be8300868c)

Sometimes a thick protective case can insulate a smartphone, making it hotter than needed, too.

I've done a YouTube video demoing how cooling your smartphone can reduce heat and also improve performance, as a hot phone my throttle the performance. See below:

{% embed url="<https://www.youtube.com/shorts/kH2Y3kAysv4>" %}

### Web apps are intentionally limited on mobile devices

It is not possible to change between apps, screen-share, or turn off the display when using a web-app, like VDO.Ninja. You can turn down the screen brightness manually on your phone though, which will be nearly as effective.

Also, If you use `?push=STREAMIDGOESHERE&cleanoutput&nopreview&chroma=000&view` as a publishing link, you can hide pretty much everything on the screen, and if using an OLED display, this should reduce power usage. This is a great option if you wanted to set your phone up as a dedicated webcam and were worried about the screen generating heat.

### Native mobile app of VDO.Ninja

The [Android and iPhone apps](https://docs.vdo.ninja/steves-helper-apps/native-mobile-app.md) provide camera controls, local recording, and optional server outputs. Compare the normal app camera mode with the browser using the same resolution, frame rate, viewers, and test duration. Lower its [capture quality](https://docs.vdo.ninja/guides/improving-quality-of-the-native-app.md) if the phone gets hot; switching protocols alone does not solve overheating.

### Laptops and MacBooks

Older 2011-era Apple notebooks are prone to overheating. Even newer generation Macbooks can overheat if stressed. Normally these systems throttle the CPU to be MUCH slower when they get too hot, so it may appear like there is a network issue.

Ensure you are not running a laptop at 100% CPU load, make sure it has plenty of cool ventilation, ensure the fans are clean and not full of dust, start with a full battery and keep the computer plugged in

![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MZHXv1G8N0MDxwotaT9%2F-M_PzwZo9g2PX_c78CO-%2F-M_QIPasZQzQiavD2xbM%2Fimage.png?alt=media\&token=73788c98-7542-41f1-9505-e5383591b87c)

### Raspberry Pi, NVIDIA Jetson, and dedicated hardware-encoders

VDO.Ninja has limited support for hardware encoders. Hardware encoders greatly reduce heat, but they are often poorly suited for low-latency video that requires tolerant packet-loss capabilities and dynamic resolutions. Green/purple/grey coloring of video, lost frames, and distorted video blocks are common when using hardware-encoders at very-low latencies.

There is support for the Raspberry Pi, both software-encoder and hardware-encoder options, but the hardware-encoded option is the most limited and challenging. The current project supporting this offering is here: <https://github.com/steveseguin/raspberry_ninja>

For supported capture modes and connections, follow the [Raspberry.Ninja guide](https://docs.vdo.ninja/steves-helper-apps/raspberry.ninja.md). Use Ethernet where possible and test sustained playback with the camera and encoder you plan to use.

Using a Chromium browser with a Raspberry Pi, in software-encoded mode, will probably give more reliable results, but also generate a lot of heat and limit the maximum video resolution a lot.

![](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MZHXv1G8N0MDxwotaT9%2F-M_PzwZo9g2PX_c78CO-%2F-M_QJ-38b8GNPMER9Qdh%2Fimage.png?alt=media\&token=578d1e46-ee3a-4f2f-8ab3-0a3b68e6f7f6)

Just as a consideration though, the NVIDIA Jetson development boards support higher resolutions and seem to have better support for dynamic video and packet loss recovery. These products are a bit more expensive, but tend to work better than a Raspberry Pi when it comes to encoding HD video. I have a support for the Hardware-encoding capabilities of a Jetson here, buried away alongside the files for the Raspberry Pi: <https://github.com/steveseguin/raspberry_ninja> It's pretty basic support also currently, but has a lot of potential.

In the future, more professional video-centric hardware encoding options with built-in LTE/5G transmitters will support VDO.Ninja in a basic publish-only mode. This advancement will be due to the adoption of community standards for publishing low-latency video, although don't hold your breath for progress here.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdo.ninja/common-errors-and-known-issues/overheating.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
