Stream Bitrate Test
A stream bitrate test measures how many megabits per second your live stream is actually carrying — the single best proxy for delivered quality. StreamTest connects from our servers, samples the stream for ~30 seconds, and reports the measured bitrate alongside codec and resolution. A passing result is a measured bitrate close to your encoder target and steady across the sample window. A bitrate that is far below target, or that sags and spikes, is the root cause behind most "it looks blocky / it keeps buffering" complaints.
Run the test
Paste your stream URL (or run the pre-filled example). StreamProbe probes it from our servers — reachability, codec, resolution, frame rate, and a live bitrate sample.
How to read your Bitrate results
Measured vs. reported
StreamTest distinguishes a bitrate reported in stream metadata from one it actually measured by sampling bytes. A reported number can lie; the measured number is what your viewers receive. When the two disagree, trust the measured value.
Target by resolution
Rough h264 targets: ~1.5–4 Mbps for 720p, ~3–6 Mbps for 1080p, ~8–16 Mbps for 4K. h265/HEVC achieves similar quality at roughly 40–50% less. Measuring well under the resolution-appropriate range means the picture is being starved.
Stability over the sample
The 30-second sparkline shows whether the bitrate holds. A flat line at target is healthy; a sawtooth or a downward drift points at upstream packet loss, an overloaded encoder, or VBR overshooting its buffer. One number hides this — the shape of the curve is the diagnosis.
Bitrate vs. bandwidth
Your stream bitrate must comfortably fit inside the available upload/CDN bandwidth with headroom. A stream measured right at the edge of the link capacity will stutter under any jitter; size the encoder target below the sustained throughput, not at it.
Frequently asked questions
What is a good bitrate for a live stream?
It depends on resolution and codec. For h264: roughly 1.5–4 Mbps at 720p, 3–6 Mbps at 1080p, and 8–16 Mbps at 4K. h265/HEVC reaches comparable quality at about 40–50% lower bitrate. Aim for the measured value to sit near your target and stay steady.
Why is my measured bitrate lower than what I set?
The encoder may be dropping frames to keep up, the upstream link may be losing packets, or a CDN may be transcoding to a lower rung. A measured bitrate well below target, especially one that sags over the sample, points at upstream loss or an overloaded encoder.
Does higher bitrate always mean better quality?
Up to a point. Beyond the resolution-appropriate range you mostly waste bandwidth and risk buffering on constrained viewers. Match bitrate to resolution and codec, keep it steady, and leave bandwidth headroom rather than pushing the link to its limit.