Resources and requirements

It’s impossible to give a single answer about what the requirements are for you to run Owncast, or what it will cost. It’s your server, and it’s completely up to you how you choose to configure it, and in what environments you choose to run it. Every environment has different performance, prices and features.

Base knowledge

It’s very helpful for you to understand the basics included in video streaming.

  • CPU: Used to transcode the video to multiple qualities so viewers can watch it on different speed networks.
  • Network bandwidth: Used to distribute the video to your viewers.

Viewer count does not impact CPU use

Knowing this, you see that CPU usage is the same regardless of how many viewers you have. 0 or 100, the CPU is still performing the work. Think of it like creating a zip file. If you have a 100MB file, and you zip it, and it becomes 70MB, you can send that 70MB file to as many people as you want without zipping that file again for each person. But you still need to send the file to each person seperately, requiring network bandwidth for each time you send it. However, if you want to send some people a 70MB version and others a 50MB version, you’ll need to create two seperate files. That 50MB version will take longer and use more CPU to create, because of the additional work it takes to compress the file more. This is the same with video. The more work required to encode your video, the more CPU that’s required. Generally, the more you need to reduce the size and bitrate of your video, the more CPU that will be used. But offering low bitrate/lower quality versions of your stream is important to enable more viewers to watch it from across the world, on any kind of network.

Now that you understand the basics, let’s use an example to illustrate how your configuration can impact your server’s resources, and most importantly, your viewers’ experience. It’s a little simplistic and the actual numbers can vary in real life, but it could help answer the question of “approximately how much bandwidth and CPU will Owncast use?”

Example Scenario

You’ve configured your broadcasting source (such as OBS) to stream to your Owncast instance at 5000kbps. You have 25 viewers. 5 of them are on slow or mobile networks, 17 of them have fast, stable internet, and 3 of them have fast internet most of the time but the speed fluctuates. All 25 viewers watched an entire stream that lasts two hours. You have a hosting provider that gives you 4TB of bandwidth per month.

Offer a high and low quality option

You decide to offer both a high and low quality option, and you set the high quality option to 5000kbps and the low quality option to 1500kbps.

How much bandwidth is used on your server for this stream?

BitrateDurationViewersTotal
0.000625 Gigabytes per second (5000kbps)7200 seconds1985 Gigabytes
0.0001875 Gigabytes per second (1500kbps)7200 seconds68.1 Gigabytes
Total: 93.1 Gigabytes

How much CPU?

QualityCPU Usage
5000kbpsSome (It matches the input)
1500kbpsMore (CPU needs to be used to compress the video)

How is the viewer experience?

QualityViewersExperience
5000kbps20Good
1500kbps5Good

Result: You’ve provided both a high and low quality option for your viewers so those with a slow network have an option, and those with a fast network that might periodically slow down can dip down into the low quality when needed. Additionally, in this case you saved almost 20G of bandwidth traffic due to offering a lower quality. You’re using more CPU for a much better experience. You would be able to stream 43 times in a month before you hit your bandwidth limit.

Offer a single high quality option using the least amount of CPU

You’ve decided you want to use as little CPU on your Owncast server as possible so you enable “Video Passthrough” mode as the only output available. This means the exact video you’re sending from your local broadcasting software is what is sent to your viewers.

How much bandwidth is used on your server for this stream?

BitrateDurationViewersTotal
0.000625 Gigabytes per second (5000kbps)7200 seconds25112.5 Gigabytes

How much CPU?

QualityCPU Usage
5000kbpsLittle

How is the viewer experience?

QualityViewersExperience
5000kbps17Good
5000kbps3Bad
5000kbps5Unwatchable

Result: You’re not using much CPU, but only 65% of your viewers are having a good experience. The other 35% are having a bad experience with frequent buffering, and 20% of them cannot watch your stream at all. You would be able to stream 35 times in a month before you hit your bandwidth limit.

Use a S3 compatible storage provider for bandwidth

If you have concerns about your hosting plan, bandwidth allocation or viewership growth you can use a S3 storage provider instead of your server for bandwidth responsibilities. In this example you again decide to offer both a high and low quality option, and you set the high quality option to 5000kbps and the low quality option to 1500kbps. The CPU used is the same as the above example for the high+low quality option. Learn more about S3 compatible storage.

How much bandwidth is used on your server for this stream?

BitrateDurationTotal
0.000625 Gigabytes per second (5000kbps)7200 seconds4.5 Gigabytes
0.0001875 Gigabytes per second (1500kbps)7200 seconds1.35 Gigabytes
Total: 5.85 Gigabytes

How much outbound bandwidth is used on your S3 provider for this stream?

BitrateDurationViewersTotal
0.000625 Gigabytes per second (5000kbps)7200 seconds1985 Gigabytes
0.0001875 Gigabytes per second (1500kbps)7200 seconds68.1 Gigabytes
Total: 93.1 Gigabytes

Result: You’ve provided both a high and low quality option for your viewers so those with a slow network have an option, and those with a fast network that might periodically slow down can dip down into the low quality when needed. However, these video qualities are not being served from your Owncast server, but instead an external S3 compatible storage provider. This allows for increasing your viewership and adding additional video qualities without concern of you exhausting your server’s bandwidth allocation. You would be able to stream 24/7 without worry using this configuration, however you’d be using the same amount of your server bandwidth if you had zero viewers or 100 viewers. Your CPU usage would be the same as if you were serving the video directly from your server.

Summarized FAQ

How much bandwidth will Owncast use?

It depends on your configuration and how many viewers you have. If you offer more video quality options you will often reduce your network transfer requirements. Look into object storage (S3) to reduce your server’s network requirements.

How much CPU will Owncast use?

It depends on how many different quality output options you are offering your viewers and what those qualities are.

Does CPU usage increase with more viewers?

Not in a meaningful way. There are limits when you’re talking tens of thousands of chat participants, however.

How much CPU is used for each output quality?

It depends on your configuration, but generally if you said one CPU core for each quality you’re offering, that’s a good rule of thumb. But it’s not a hard rule and can be less.

How does frame rate affect CPU usage?

The fewer frames, the less CPU that is used. If you want to reduce the CPU being used on one of your video qualities you can reduce the frame rate. If you want to reduce the CPU being used for all of Owncast you can reduce the frame rate of your inbound source content in your broadcasting software, such as OBS.

How much disk space will Owncast use?

Almost none, as the live stream is cleaned up in real-time as you stream.

Can I just offer one quality, the highest possible, to lower the CPU requirements? I only want people to see the best quality video, anyway.

It’s not about you, your bandwidth, or your CPU. It’s about your viewers. Not everyone can watch the highest quality. If they can’t watch your stream because you didn’t have them in mind then it’s not worth streaming in the first place.

Learn more

Visit the detailed video documentation to learn more about how Owncast handles video.