Video Bitrate: What It Is and the Best Settings for Streaming

By the WpStream Editorial Team

Last updated: June 28, 2026

The same 1080p stream can look razor sharp or look like wet cardboard, and bitrate is the lever that decides which one your viewers get. Set the number too low and the picture smears the moment anything moves; set it too high for your connection and viewers sit through buffering. Video bitrate is the master control on streaming quality, but it is not a single magic number you can copy off a forum post. The right value depends on what you are streaming, how fast it moves, and how you are sending it. Learn those factors and you can dial in a setting that holds up on your connection.

A quick disclosure first: WpStream is the WordPress live streaming and pay-per-view plugin that publishes this blog, so we reference it where relevant. The bitrate guidance itself works with any encoder or platform.

What is video bitrate?

Video bitrate is the amount of data used to represent one second of video, measured in bits per second. You will almost always see it written as kilobits per second, or kbps, and megabits per second, or Mbps. One Mbps equals 1,000 kbps. Think of it as video density: the more bits you spend per second, the more visual detail survives compression.

One trap trips readers up constantly. Bitrate is measured in bits, with a lowercase b. Your file sizes and the number your internet provider quotes are usually in bytes, with an uppercase B. The two differ by a factor of eight: 8 bits make 1 byte, so a 6 Mbps stream is about 0.75 MB of data per second. Keep the units straight and the rest is easy.

The core tradeoff sits right here. A higher bitrate means a better looking picture, but also more bandwidth and more buffering risk if the connection cannot keep up. Quality and deliverability pull against each other. Starve a stream of bitrate and you get the classic symptoms: blockiness and smearing whenever the scene moves, worst on fast motion. Encoders call that macroblocking, the visible cost of spreading too few bits across a busy frame.

One more distinction matters: bitrate is not resolution. Resolution is the pixel count; bitrate is how much data describes those pixels each second. Think of it as the canvas versus the paint. A starved 1080p stream is a large canvas with almost no paint.

Why the right bitrate is never one number

The correct bitrate is a function of four things, and once you see them you stop chasing a single universal answer. The lens to use is quality per bit: how much visible quality each bit actually buys you.

Resolution. 1080p has 2.25 times the pixels of 720p, so it needs a good deal more bitrate to look equally clean.

Frame rate. 60 fps sends double the frames of 30 fps, but it does not need double the bitrate. Plan for roughly 1.3 to 1.5 times as much, because consecutive frames are similar and inter-frame compression exploits that overlap.

Content and motion. Fast motion, film grain, confetti, water, quick camera pans, and gameplay all spike the bits needed. A static talking head needs far less data than esports. This is why every honest recommendation comes as a range, not a fixed value.

Codec. A newer codec extracts more quality from the same bits, a big enough lever to get its own section below.

Raising resolution without raising bitrate often looks worse than staying at a lower resolution, because too few bits spread across too many pixels. A 1080p stream at 2 Mbps can look worse than 720p at 2 Mbps. Match resolution to the bitrate you can actually feed; do not just crank the resolution and hope.

Recommended bitrate by resolution

The table below gives general live-streaming ranges for H.264 with constant bitrate, which is the universal baseline almost every platform and encoder agrees on. Treat them as starting points: push higher for high-motion content, lower for static scenes. These ranges were checked in June 2026; platform caps change, so confirm current limits before going live. For a deeper walkthrough of how bitrate fits together with frame rate and resolution, see our guide to the best settings for your broadcast (FPS, bitrate, resolution).

Two platform examples add context. YouTube Live publishes its own recommended range per tier in its official Help article on choosing live encoder settings, with figures a bit higher than the table above: around 10 Mbps for 1080p30 in H.264, up to 35 Mbps or more for 4K60. Its codec list includes H.264, HEVC, and AV1, with a keyframe interval of 2 seconds. Those numbers sit higher because YouTube re-encodes every ingest and benefits from a richer source.

Twitch sits at the conservative end. Its Broadcasting Guidelines set a hard standard-ingest cap of 6,000 kbps, require constant bitrate, and ask for a 2-second keyframe interval. Its newer Enhanced Broadcasting path, rolling out through 2026, lets eligible streamers push higher, with a sweet spot near 8,000 kbps. Read Twitch as the ceiling for a single live ingest, not a target to chase. Both figures were checked in June 2026; confirm current platform limits before you rely on them, since caps like Enhanced Broadcasting are still moving.

CBR, VBR, and CQP or CRF: which to use when

Rate control comes down to one question: what is the encoder allowed to vary? There are three answers, and the right one matters more than people realize.

CBR, constant bitrate, holds the data rate fixed second to second. That predictability is exactly what live ingest servers and adaptive packagers want, which is why it is the right choice for live, specified by YouTube, Twitch, and the major encoder guides. It is also the OBS default, so most broadcasters already use it without thinking about it. Set your rate control to constant bitrate, set the keyframe interval to 2 seconds, and move on. Our OBS settings guide shows where these live in the encoder.

VBR, variable bitrate, lets the rate flex by scene: more bits for complex frames, fewer for static ones, around a target average. That buys better quality per megabyte, a good fit for recorded files where encoding time is not a constraint. YouTube’s own upload recommendation for finished, non-live files is 2-pass VBR.

CRF or CQP, constant quality, flips the relationship. You set a quality target and the encoder spends whatever bitrate it takes to hold it. On the x264 and x265 scale, lower numbers mean higher quality, and CRF 23 is the x264 default. The output size floats and is hard to predict, which is fine for archiving a VOD and wrong for live. CQP is the cruder GPU-encoder cousin of CRF.

CBR fixes the bitrate and lets quality move; CRF and CQP fix the quality and let bitrate move; VBR aims for an average in between. Use CBR for live, and VBR or CRF for on-demand.

What you upload vs what viewers receive

Read two bitrate guides and you will catch them disagreeing: one says 1080p needs 6 Mbps, another insists on 8 Mbps. Both are right, because they answer two different questions: what you send to a live platform, and what you upload as a finished file.

Live ingest is capped lower. Twitch standard ingest tops out around 6,000 kbps, and live platforms want a predictable, modest input they can process in real time. A VOD upload targets higher, around 8 Mbps for 1080p, because the platform re-encodes it offline and a richer source survives that process better. Same content, two pipelines, two ideal numbers.

The rule that matters most for your own setup is about your connection. Your live stream bitrate should be no more than about 70 to 80 percent of your measured, sustained upload speed. A 10 Mbps upload, for example, caps the stream near 6,000 to 7,500 kbps. That headroom absorbs background traffic and the dips every connection has. Exceed it and the ingest server starts discarding frames, because it cannot buffer data your connection never delivered, which viewers see as stutter.

Two details matter. Test your upload speed, not your download, because home connections are usually asymmetric and upload is what limits streaming. Test at the time you actually stream, since an evening when everyone nearby is online behaves nothing like a quiet midday test. For this we recommend the WpStream speed test at speedtest.wpstream.live, because it measures against real streaming ingest infrastructure rather than a generic endpoint, which is a truer number to size your bitrate against. Whatever it reports, stay conservatively below it.

Newer codecs, same quality for fewer bits

Every number in the table above assumes H.264. Change the codec and the math changes, which is worth a short detour before you over-spend on a modern encoder or under-spend on an old one.

The codec generations form a ladder. H.264, also called AVC, then H.265, also called HEVC, then AV1. Each generation reaches roughly the same visual quality at meaningfully fewer bits. H.264 is the universal baseline every device can decode, exactly why the table uses it. H.265 cuts the bitrate by roughly 40 to 50 percent at equal quality, with broad but not universal decode support; licensing is encumbered. AV1 is royalty-free and lands in the same neighborhood, roughly 40 to 50 percent better than H.264 at equal quality (NVIDIA cites about 40 percent savings at 1080p60), but it needs newer hardware, such as RTX 40-series cards, to encode and decode efficiently.

The practical translation is simple. If a guide says 1080p60 needs 6 to 9 Mbps in H.264, the same quality lands closer to 3.5 to 5 Mbps in HEVC or AV1, with the biggest gains on complex, high-motion footage. There is a catch that keeps H.264 the safe default for live: you can only use a codec the viewer’s device can decode and the live platform accepts on ingest, with HEVC and AV1 emerging wherever both ends support them. Which codec each viewer can actually play is part of why platforms send more than one version of your stream, the idea behind adaptive bitrate streaming.

Adaptive bitrate: one upload, many renditions

Here is where the question “what is the best bitrate” splits cleanly in two. You upload one stream at a single ingest bitrate. The platform then transcodes that one ingest into several renditions, for example 360p at 800 kbps up through 1080p at 5 to 6 Mbps. That stack of resolution and bitrate pairs is the adaptive bitrate ladder.

The player on each viewer’s device does the rest. It continuously measures that viewer’s bandwidth and buffer and switches up or down the ladder as conditions change. A viewer on a weak mobile connection gets 360p without buffering while a viewer on fiber gets 1080p, both from your single upload. One upload cannot fit every viewer, so the platform fans it out instead.

This is where WpStream fits. It delivers across a multi-CDN network spanning multiple continents with adaptive bitrate built in, taking your single ingest and automatically serving the right rendition to each viewer. So your job as the creator is to send one clean, well-sized ingest, governed by the table and the headroom rule above, and WpStream handles the multi-rendition delivery to every viewer at a quality their connection can hold.

Key Takeaways

• Video bitrate measures data per second of video in kbps or Mbps; more bits mean sharper detail and higher bandwidth use.
• Match your bitrate to your resolution and frame rate, then keep it under 70 to 80 percent of your measured upload speed.
• Use constant bitrate for live streaming and variable bitrate or CRF for recorded file uploads.
• HEVC and AV1 deliver equal quality at roughly 40 to 50 percent fewer bits than H.264, with the biggest gains on high-motion content.
• Send one clean ingest; adaptive bitrate platforms fan it out to every viewer at the right quality for their connection.

Frequently asked questions

What is a good bitrate for streaming?

Match it to your resolution and frame rate using the table above, then keep it under about 70 to 80 percent of your measured upload speed. WpStream’s speed test at speedtest.wpstream.live helps you size that number against real ingest infrastructure.

Is 6,000 kbps too high?

It is the Twitch standard-ingest ceiling and is plenty for 1080p30 through 1080p60 in H.264. It is only too high if your upload cannot sustain it with headroom. On WpStream, send a clean ingest and let adaptive bitrate fan it out to viewers.

Does a higher bitrate always mean better quality?

No. Past the point your resolution, codec, and upload can support, extra bits are wasted and can trigger dropped frames. WpStream’s adaptive delivery means a sensible, stable ingest beats an overcooked one.

Should I stream in 720p or 1080p?

If your upload cannot comfortably feed 1080p with headroom, a clean 720p will look better than a starved 1080p. WpStream serves whichever resolution you send across its multi-CDN network.

CBR or VBR for live?

CBR, every time, for live; save VBR or CRF for recorded uploads. WpStream’s live pipeline, like every major live platform, expects a steady constant-bitrate ingest.

Dialing in your own number

Measure your upload at the time you actually stream, pick a resolution and frame rate, and start at the low end of that tier’s range. Watch the dropped-frame counter and nudge the bitrate up only while frames stay clean; the moment they start dropping, step back below that ceiling. As AV1 adoption climbs, the same quality keeps getting cheaper in bits, but H.264 with constant bitrate remains the dependable live default today. You handle the one clean ingest; WpStream handles getting it to every viewer at the right quality.