
Whether you are streaming a beach cam over fiber or a mountain cam over 4G, two questions decide whether it will work and what it will cost: how fast does my upload need to be? and how much data will it use? Both come from one number, the bitrate. This page gives you the formula, ready-made tables and a small calculator you can use right here.
What bitrate means
Bitrate is how much compressed video (plus audio) a stream sends every second, usually in megabits per second (Mbps). It is set in your camera or encoder. Higher bitrate means more detail, especially in busy scenes like waves, rain, snow or crowds, but also more upload speed and more data.
One unit trap catches almost everyone: bits vs bytes. Internet speeds are in megabits per second (Mb, small b). File sizes and data plans are in megabytes and gigabytes (MB and GB, capital B). There are 8 bits in a byte. So a 8 Mbps stream sends 1 MB every second.
The formula
Because 1 Mbps for one hour = 3,600 seconds x 1 megabit ÷ 8 = 450 MB = 0.45 GB. This page uses decimal units (1 GB = 1,000 MB), as most mobile carriers do.
And for upload speed:
The 50% headroom covers network overhead and the dips every connection has. On 4G or busy Wi-Fi, use 2x.
Calculator
Result: about 43.2 GB per day, about 1,296 GB per 30-day month. Plan for at least 6 Mbps of steady upload.
The calculator runs entirely in your browser; nothing you type is sent anywhere.
Monthly data by bitrate, streaming 24/7
| Bitrate | Per hour | Per day (24 h) | Per 30-day month | Upload to plan (wired) |
|---|---|---|---|---|
| 0.5 Mbps | 225 MB | 5.4 GB | 162 GB | 0.75 Mbps |
| 1 Mbps | 450 MB | 10.8 GB | 324 GB | 1.5 Mbps |
| 2 Mbps | 900 MB | 21.6 GB | 648 GB | 3 Mbps |
| 4 Mbps | 1.8 GB | 43.2 GB | 1,296 GB | 6 Mbps |
| 6 Mbps | 2.7 GB | 64.8 GB | 1,944 GB | 9 Mbps |
| 8 Mbps | 3.6 GB | 86.4 GB | 2,592 GB | 12 Mbps |
| 14 Mbps | 6.3 GB | 151.2 GB | 4,536 GB | 21 Mbps |
Streaming only in daylight? Multiply by your hours. A 12-hour daylight stream uses exactly half of the 24-hour figures.
What bitrate should a webcam use?
YouTube's encoder settings page recommends, for H.264, about 8 Mbps for 720p, 14 Mbps for 1080p and 42 Mbps for 4K at 30 fps (checked on the date at the bottom of this page). Those figures are generous because they cover fast-moving content like gaming and sports. A scenic webcam is mostly still, and still scenes compress far better. Practical ranges many webcam owners use:
| Scene | Resolution / fps | Typical webcam bitrate | Notes |
|---|---|---|---|
| Skyline, mountains, calm harbor | 1080p / 15 to 25 fps | 2 to 4 Mbps | Little motion; looks clean at modest rates |
| Beach with waves, busy square | 1080p / 25 to 30 fps | 4 to 8 Mbps | Waves and people need more bits |
| Snowfall, rain, fireworks | 1080p / 30 fps | 6 to 10 Mbps | Hardest scenes to compress |
| 4K scenic | 2160p / 25 to 30 fps | 12 to 25 Mbps (H.264) | Needs a strong upload; H.265 cuts this a lot |
| 4G remote site | 720p to 1080p / 15 fps | 1 to 2.5 Mbps | Balance quality against monthly data |
These are starting points, not rules. Stream for a day, look at the picture on a big screen at the busiest moment (sunset over the waves is a good test) and adjust.
Constant vs variable bitrate
Encoders offer two main modes. Constant bitrate (CBR) sends about the same amount of data every second, whatever happens in the picture. Variable bitrate (VBR) sends less when the scene is still and more when it gets busy. VBR can look better for the same average data, but it makes monthly totals harder to predict and can spike well above the average during a storm, a festival or fireworks. Streaming platforms generally prefer a steady input; YouTube's live settings are written around CBR. For a webcam, especially on 4G, CBR at a sensible cap is the safe default.
Do not forget audio
Audio is small next to video but not zero. YouTube recommends 128 kbps for stereo audio, which adds about 1.4 GB a day, or roughly 41 GB a month, to a 24/7 stream. Many public webcams stream without sound, which saves that data and avoids the legal questions that come with recording conversations in public places (see US filming and audio laws). If you want ambience such as waves or birdsong, a low mono bitrate is usually plenty, and some platforms expect an audio track to be present, so a silent one is a common workaround.
Why resolution alone does not decide quality
A 4K stream at too low a bitrate can look worse than a 1080p stream at a healthy one. When the encoder runs short of bits, it smears fine detail into blocks, and fine detail is exactly what 4K was supposed to show. A rough rule: if your upload cannot comfortably carry the bitrate a resolution needs, step the resolution down rather than starving it. Viewers on phones, which is most of them, rarely see a difference between good 1080p and 4K on a scenic view anyway.
Frame rate works the same way. Thirty frames per second of a still mountain is mostly the same picture thirty times. Dropping to 15 or 20 frames frees bits for detail in each frame, which often looks better than a high frame rate at the same bitrate.
A worked example on 4G
A ski area wants a summit webcam on a 4G router. The plan allows 500 GB a month. How much quality can it afford?
- Lifts run from 8 a.m. to 5 p.m., and people check the view mostly in daylight, so stream 10 hours a day.
- Monthly budget ÷ (hours x 30 x 0.45) = 500 ÷ (10 x 30 x 0.45) ≈ 3.7 Mbps.
- Leave a margin for overhead and test sessions: set the encoder to 3 Mbps CBR, 1080p at 20 fps.
- Upload needed on cellular, with 2x headroom: about 6 Mbps. Speed tests at the summit at 9 a.m. and 4 p.m. confirm 10 Mbps or more, so it fits.
Result: a clear daytime 1080p stream for about 405 GB a month, with room to spare for a powder-day rush of viewers (which costs the ski area nothing extra, because the platform serves them).
Ways to use less data without ruining the view
- Stream in daylight only. Half the hours, half the data, and nobody misses a dark beach.
- Lower the frame rate. 15 to 20 fps looks almost the same as 30 for a landscape and saves a good share of the bits.
- Use H.265 or AV1 where the whole chain supports it. Roughly half the data of H.264 for similar quality. YouTube accepts newer codecs on some ingest methods; check your encoder.
- Use constant bitrate with a cap. It keeps data predictable; variable bitrate can spike during storms.
- Crop to the interesting part. A sky-heavy frame wastes bits on clouds; tilt to show more of the scene people want.
- Offer snapshots for low-value hours. A still image every minute uses almost nothing.
- Turn off audio unless it adds real value, which also avoids privacy issues.
Recording and storage: the same math
The formula also tells you how much storage a recorder or SD card needs. A camera recording continuously at 4 Mbps fills 43.2 GB a day; a 256 GB microSD card holds about 6 days, and a 4 TB recorder drive about 92 days for that one camera. Motion-only recording uses far less, depending on how busy the scene is. Recording and streaming can run side by side: the camera's main stream goes to the recorder on your local network, and a separate stream (or the same one through an encoder) goes out to the platform.
Where these numbers apply
- Your upload: you send one copy of the stream to the platform, however many people watch. Viewers' data is the platform's cost, not yours.
- Your data plan: on 4G and satellite internet, monthly data is often the limiting factor. See 4G/LTE cameras and internet for remote cameras.
- Self-hosting: if you serve the video from your own server, every viewer adds the full bitrate to your bandwidth. 100 viewers of a 4 Mbps stream need 400 Mbps of server upload, which is why most owners use a platform.
Checking your real upload speed
Run a speed test from a device wired to the same router as the camera, several times across the day, including in the evening. Look at the upload number and the lowest result, not the best one. If the lowest upload is under 1.5 times your planned bitrate, lower the bitrate before you go live. On 4G, test at the camera's exact spot and height.
Ready to stream? Follow how to stream an IP camera to YouTube 24/7, and see how live streaming works for the bigger picture.
Do these next
- Run upload speed tests at different times of day.
- Pick a bitrate from the table and check it in the calculator.
- Start your stream and fine-tune after a day.
Questions people ask
How much data does a 24/7 live stream use?
About 324 GB per 30-day month for every 1 Mbps of bitrate. A 2 Mbps stream uses about 648 GB and a 4 Mbps stream about 1.3 TB a month.
What upload speed do I need to live stream a camera?
About 1.5 times the stream bitrate on a wired connection and about 2 times on 4G or Wi-Fi. A 4 Mbps stream wants a steady 6 Mbps upload, more on cellular.
What bitrate should I use for a 1080p webcam?
Calm scenic views often look good at 2 to 4 Mbps; busy scenes with waves or people need 4 to 8 Mbps. YouTube recommends higher figures for fast-moving content.
Does having more viewers use more of my data?
Not when you stream to a platform like YouTube. You upload one copy and the platform serves everyone. Self-hosted streams are different: each viewer adds the full bitrate.
What is the difference between Mbps and MB?
Mbps is megabits per second, used for speeds. MB is megabytes, used for data and files. One byte is 8 bits, so 8 Mbps moves 1 MB each second.
Sources
- YouTube Help: Choose live encoder settings, bitrates and resolutions (checked 2026-10-07)
- Apple: HLS authoring specification for Apple devices (checked 2026-10-07)
- RFC 8216: HTTP Live Streaming (IETF) (checked 2026-10-07)
- YouTube Help: Create a live stream with an encoder (checked 2026-10-07)
- Reolink RLC-810A specifications (resolution, frame rate, storage) (checked 2026-10-07)
Last reviewed October 7, 2026 by the LiveLocation team. General information, not legal or electrical advice.
