Streaming Bitrate Calculator (YouTube Recommended Settings)

Background.

This page answers one narrow question: what bitrate should you type into your encoder, and will your upload connection actually carry it? It is not a file-size calculator and it does not ask how long your video is. You pick a resolution and a frame rate, it reads the recommended bitrate straight out of YouTube's own published table, adds your audio track, adds the headroom you want to keep in reserve, and tells you whether the upload speed you measured is enough.

The bitrate numbers are not estimates or rules of thumb. They are transcribed from two YouTube Help pages and nothing between them is interpolated. The live table, headed "Recommended Bitrate setting (Mbps)" for H.264, gives 4 Mbps at 720p30, 6 at 720p60, 10 at 1080p30, 12 at 1080p60, 15 at 1440p30, 24 at 1440p60, 30 at 2160p30 and 35 at 2160p60. The upload page publishes two further tables, SDR and HDR, split into a standard frame-rate column (24, 25 or 30 fps) and a high frame-rate column (48, 50 or 60 fps). Those upload figures are different from the live figures, and mixing them up is why people arrive at a 1080p bitrate anywhere between 8 and 15 Mbps depending on which page they happened to read.

Only four resolutions are offered, and that is deliberate. 720p, 1080p, 1440p and 2160p are the only ones defined in all three tables at both frame-rate classes. YouTube's live table has no separate 360p or 480p row at 60 fps — its lowest entry reads "240p - 720p @30fps" — so offering those options would have meant inventing values the platform never published. Twitch is absent for the same reason: its broadcasting-guidelines page could not be retrieved to verify, and an unverified number is worse than a missing one.

Headroom is the part no standards body settles for you. Every encoder vendor and platform tells you to leave spare upload capacity, but none publishes a required percentage, so it is an input here rather than a hidden constant. Twenty percent is a reasonable default. It absorbs TCP and RTMP protocol overhead, the phone in the next room syncing photos, and the short congestion spikes that make a stream drop frames long before the average bitrate looks like a problem. Cloudflare's own live-streaming guidance points the same way from a different angle: prefer constant bitrate over variable, because a variable-bitrate encoder briefly exceeds its own average exactly when a busy scene is hardest to deliver.

Enter a measured upload speed, not the one on your bill, and measure it at the hour you actually go live. Both figures are in megabits per second, so they compare directly with no conversion — the factor of eight only appears in the last output, data used per hour, which converts bits to decimal gigabytes for anyone streaming under a data cap. The margin is shown as a plain multiple: below 1.0 the stream does not fit, 1.0 to 1.5 fits with little to spare, and 1.5 or more is comfortable. Those three bands are a presentation choice, derived from a ratio you can see and check, not a threshold anyone has standardised.

What is streaming bitrate calculator?

Streaming bitrate is the number of bits per second your encoder pushes out, and it is the single setting that decides both how good a live stream looks and whether it survives your connection. It is quoted in megabits per second for video and kilobits per second for audio, and the two must be added on the same scale before you compare them with an upload speed. Platforms publish recommended bitrates per resolution and frame-rate class rather than a single figure, because the pixel count and the number of frames per second together determine how much data an encoder needs to hold quality at a given codec. This calculator reads those published recommendations, adds your audio track, applies the headroom margin you choose, and compares the result against your real upload speed. It answers "what do I set and can I sustain it" — a different question from "how big will my exported file be", which is bitrate multiplied by runtime and lives on the video bitrate page.

How to use this calculator.

1. 01Choose the table that matches what you are doing. Use YouTube Live for anything going out through an encoder in real time. Use the SDR or HDR upload table when you are exporting a file to publish afterwards, and pick HDR only if you are genuinely delivering high dynamic range — the HDR figures are 25 to 40 percent higher and wasted on an SDR master.
2. 02Pick the resolution and frame-rate class you are actually encoding at, not the resolution of your camera. Streaming at 1080p from a 4K sensor uses the 1080p row.
3. 03Enter the audio bitrate your encoder is set to. YouTube's live guidance is 128 kbps for stereo and 384 kbps for 5.1 surround; its upload guidance is 128 kbps mono, 384 kbps stereo and 512 kbps for 5.1.
4. 04Set the headroom you want in reserve. Twenty percent is a sensible starting point; raise it if the connection is shared, on Wi-Fi, or on a cable line that congests in the evening.
5. 05Enter your measured upload speed. Run the speed test at the time of day you stream, from the machine that will be encoding, and use the upload figure rather than the download figure that dominates most advertising.
6. 06Read the margin. Under 1.0x you must drop a resolution or a frame-rate class; between 1.0x and 1.5x the stream will run but has no room for a spike; 1.5x or better is comfortable. Then check data used per hour against any cap on the connection.

The formula.

There is no derivation to do on the video bitrate itself — it is a lookup, and the whole value of the page is that the lookup is transcribed from a primary source rather than remembered. Everything after the lookup is four lines of arithmetic.

First, put the two rates on the same scale. Video bitrate is published in megabits per second and audio in kilobits per second, so the audio figure is divided by 1,000 before it is added. A 128 kbps stereo track is 0.128 Mbps, not 128 Mbps and not 12.8. This is the step people skip, and skipping it either overstates the requirement by three orders of magnitude or omits the audio entirely.

Second, apply the headroom. Required upload equals the total stream rate multiplied by (1 + headroom ÷ 100). At 20 percent that is a multiplication by 1.2. Headroom is applied to the total, not to the video component alone, because the connection has to carry both.

Third, compare. The margin is your upload speed divided by the required capacity, and because both sides are already in megabits per second the division is direct. This is the reason no factor of eight appears: internet speeds and stream bitrates are both bit-rates. The factor of eight belongs to storage, which is measured in bytes.

Fourth, convert to data volume. Multiply the total stream rate by 10⁶ to get bits per second, by 3,600 for an hour, divide by 8 for bytes and by 10⁹ for decimal gigabytes. NIST defines the decimal gigabyte as exactly 1,000,000,000 bytes and the binary gibibyte as 2³⁰ = 1,073,741,824 bytes; ISPs and data caps use the decimal one, so that is what this output reports.

Where YouTube publishes a range rather than a single value — every 2160p upload row does — the calculator carries both ends but sizes the requirement from the top of the range. You provision for the worst case you are told to expect, not the best. The two ends are shown separately so you can see which rows are genuinely ranges and which are single published values.

A worked example.

Frequently asked questions.

References& sources.

1. [1]YouTube Help, "Choose live encoder settings, bitrates, and resolutions". Source of every live bitrate on this page. Column header verbatim: "Recommended Bitrate setting (Mbps)" for H.264. Rows confirmed on fetch: 2160p 30 Mbps at 30 fps and 35 Mbps at 60 fps; 1440p 15 and 24; 1080p 10 and 12; 720p 4 and 6, with the lowest row written "240p - 720p @30fps". Audio guidance verbatim: "128-Kbps for stereo or 384 Kbps for 5.1 surround sound".
2. [2]YouTube Help, "Recommended upload encoding settings". Source of both upload tables. SDR confirmed on fetch: 2160p 35-45 Mbps standard frame rate and 53-68 high; 1440p 16 and 24; 1080p 8 and 12; 720p 5 and 7.5. HDR confirmed: 2160p 44-56 and 66-85; 1440p 20 and 30; 1080p 10 and 15; 720p 6.5 and 9.5. Audio: 128 kbps mono, 384 kbps stereo, 512 kbps for 5.1.
3. [3]National Institute of Standards and Technology, "Prefixes for binary multiples". Confirms the decimal definition used for the data-per-hour output: one gigabyte, 1 GB = 10^9 B = 1 000 000 000 B, as distinct from one gibibyte, 1 GiB = 2^30 B = 1 073 741 824 B.
4. [4]Cloudflare Stream documentation, "Start a live stream". Source of the constant-bitrate and keyframe guidance quoted in the headroom discussion: creators should "use an appropriate bitrate for their live streams, typically well under 12Mbps (12000Kbps)", should "select CBR (constant bitrate) instead of VBR (variable bitrate) as CBR helps to ensure a stable streaming experience while preventing buffering and interruptions", and should use a GOP duration of 2 to 8 seconds.