> 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/guides/how-to-stream-4k-video-using-vdo.ninja.md). # How to stream 4K video using VDO.Ninja Stream 4K video with VDO.Ninja by setting custom resolution, bitrate, and CPU-aware quality settings. {% hint style="warning" %} Sending a 4K video feed with VDO.Ninja is very CPU intensive. Be prepared to use all of 8 real cpu cores (not threads). {% endhint %} ## How VDO.Ninja handles video quality VDO.Ninja has 3 predefined [`&quality`](/advanced-settings/video-parameters/and-quality.md) levels: * `&quality=0` targets 1080p (1920x1080). * `&quality=1` targets 720p (1280x720). * `&quality=2` targets 360p (640x360). * also there's `&quality=-1` , which will use the device's default resolution, but this could be anything, low or high, so it's a niche option. If `&quality` is omitted, VDO.Ninja chooses an initial tier based on the device and whether it is joining a room. Frame rate is device- and browser-dependent unless you set [`&fps`](/advanced-settings/video-parameters/and-fps.md) or [`&maxframerate`](/advanced-settings/video-parameters/and-maxframerate.md). By “trying”, I mean that if the resolution is not available, VDO.Ninja defaults to another resolution that the camera supports instead. This way, no errors are thrown and a compatible stream is sent, even if it’s not exactly what you might have desired. VDO.Ninja is however capable of doing higher resolutions and custom resolutions however; you just need to manually specify the resolution you want. When you manually specify a resolution, if it doesn’t work, an error is thrown. While I could make a selectable option for 4K in the user interface, another problem with 4K is that it requires a LOT of CPU power to encode. Most users will always select the highest resolution allowed, not understanding that it might actually be a bad idea. Maxing out your CPU can actually result in worse quality with lower frame rates than selecting a lower, safer, resolution. ## Pushing 4K resolution ![4k comparison chart with lesser resolutions](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2FO6f1dFEklMdvBjvBaQ6X%2F4KComparison?alt=media) That all said, you can give “4K” a go by adding [`&width=3840`](/advanced-settings/video-parameters/and-width.md)[`&height=2160`](/advanced-settings/video-parameters/and-height.md) to the invite link. For example then, If the guest does not support 4K, this will give an error to the guest, stating that the video device is over-constrained. The available frame rate depends on the camera, capture type, browser, and encoder. If you strictly specify a frame rate that the source cannot provide, capture may fail; use `&maxframerate` when fallback is acceptable. ### Smartphones If streaming from a smartphone, not all phones can do 4K; my old LG V30 I believe could do 4K30 via [VDO.Ninja](https://vdo.ninja), but my Pixel 4a seems stuck at 1080p30. As well, an iPhone 11 might only be able to 1080p30, an iPhone 12 might be able to do 1080p60, while an iPhone 15 might be able to do 4K30. It might depend on the iOS version, where older iOS versions are pretty limited, so things will change overtime. A common question I also get is that a certain phone can record 4K60 in the native phone app, so why not also in VDO.Ninja? Well, just because you can record to disk at 4K does not mean the manufacture has added support for 4K streaming via the browser. It requires additional development, nor is it always possible if the hardware encoder used does not support the advanced requirements of WebRTC. Samsung devices can sometimes use the built in Samsung Internet browser instead of Chrome to get access to higher resolutions and frame rates; 1080p60 for example with new flagship devices. Sometimes changing cameras or video codecs can allow for higher resolutions as well. The native mobile app version of VDO.Ninja may at some point support additional cameras that the browser does not, but at present there are not enough development resources available for this. It's desired however. ## What about the bitrate? Next, while you might have selected 4K, with the exception of static video screen shares, you cannot transfer 4K video with the default video bitrates set. For action, you will need closer to 40-mbps video bitrates set on the viewer’s end. For talking head videos, you will want over 10-mbps and possibly even more. Without a high enough bitrate set, the video will not stream at 4K and more than likely not maintain 60-fps. To set a target bitrate add [`&videobitrate=20000`](/advanced-settings/video-bitrate-parameters/bitrate.md) for 20-mbps for example. This goes on the viewer link. ## Scaling You may need to add [`&scale=100`](/advanced-settings/video-parameters/scale.md) to the view link to have the video stream at 4K, if the playback window is smaller than 4K. VDO.Ninja by default resizes incoming videos to fit the playback area, and [`&scale=100`](/advanced-settings/video-parameters/scale.md) overrides that, requesting 100% of the available resolution; so unscaled if possible. ### Codec A bit like bitrate and scaling, changing the video codec can sometimes help with achieving 4K video. [`&codec=av1`](/advanced-settings/video-parameters/codec.md#av1) can help if the bandwidth is limited, as it is more efficient than other codecs. [`&codec=vp8`](/advanced-settings/video-parameters/codec.md#vp8) is universal, while [`&codec=h264`](/advanced-settings/video-parameters/codec.md#h264) can often trigger the hardware encoder to be used. Using a hardware encoder can help reduce CPU load, allowing for 4K if the system would otherwise be CPU-bottlenecked. Normally you shouldn't need to change codecs, but sometimes it does make a difference. ## Performance issues As a result, to successfully stream 4K video, you generally need a computer system with 8 real CPU cores or more, running at 3.6GHz or higher. A modern AMD 3900X-series CPU or Intel 9900K CPU are ideal for this task, but a quad-core laptop will not be. You might be able to get away with lesser bitrates and lesser CPU requirements if just screen-sharing text, but it still is not for the faint of heart. Lastly, macOS users may find that 4K is simply not possible or very difficult. If you do manage to get it working, it might only operate at 5-fps or so. I don’t quite know why this is, but if you intend on sharing 4K video, you might be better off using a Windows PC. It seems to perform better. We've successfully streamed 4K50 over 5G cellular Internet at 65-mbps using a MacBook Air M1 and VDO.Ninja. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.vdo.ninja/guides/how-to-stream-4k-video-using-vdo.ninja.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.