Uncompressed Video Bandwidth Calculator
The Uncompressed Video Bandwidth Calculator estimates how much data the active picture in an uncompressed video stream produces each second. Enter the frame dimensions, frame rate, and pixel format to see the Video Payload Bandwidth in gigabits per second (Gbit/s).
This estimate is useful when comparing video formats or planning a PC setup with capture cards, displays, video interfaces, or storage. It describes the video payload only. A real connection may need more capacity because audio, blanking intervals, pixel packing, and transport overhead are excluded.
What the Uncompressed Video Bandwidth Calculator does
The calculator multiplies the number of pixels in each frame by the number of frames per second and the number of bits used for each pixel. It then converts the result from bits per second to decimal Gbit/s, where one gigabit equals 1,000,000,000 bits.
For example, a larger frame contains more pixels, while a higher frame rate sends more frames each second. A pixel format that uses more bits per pixel also increases the amount of data. Changing any of these inputs changes the estimated payload rate.
The calculation assumes full, uncompressed frames and uses the frame dimensions as the active picture area. It does not estimate the bandwidth of a compressed stream such as a typical online video or a hardware-encoded recording.
How to use the Uncompressed Video Bandwidth Calculator
- Enter the frame width. This is the horizontal size of the active picture in pixels. For a 1920 × 1080 picture, enter 1920.
- Enter the frame height. This is the vertical size of the active picture in pixels. For the same picture, enter 1080.
- Enter the frame rate. Use frames per second (fps), such as 60 or 59.94. The calculator accepts frame rates from 1 to 240 fps.
- Select the pixel format. Choose the option that matches the video format you want to estimate. Each option has an associated average number of bits per pixel.
- Read the Video Payload Bandwidth. The result is displayed in Gbit/s to three decimal places.
The allowed frame width and height each range from 1 to 16,384 pixels. Use the actual active picture dimensions and frame rate for your intended signal. The default values are illustrative and should not be treated as the specifications of every monitor, capture card, or video source.
The available pixel format assumptions are:
- 8-bit RGB or 4:4:4: 24 bits per pixel.
- 10-bit RGB or 4:4:4: 30 bits per pixel.
- 8-bit 4:2:2: an average of 16 bits per pixel.
These options describe the data used in the calculation. The 4:2:2 option uses chroma subsampling, so its average is lower than the 8-bit RGB or 4:4:4 option. Actual transport formats can use different packing rules and may require more bandwidth than the calculated payload.
How the Uncompressed Video Bandwidth Calculator formula works
The formula is:
Video Payload Bandwidth (Gbit/s) = frame width × frame height × frame rate × bits per pixel ÷ 1,000,000,000
First, multiplying width by height gives the number of pixels in one frame. Multiplying that value by frames per second gives the number of pixels sent each second. The selected bits-per-pixel assumption converts that pixel rate into bits per second. Dividing by one billion expresses the result in decimal Gbit/s.
Worked example: 1080p at 60 fps
Assume an active picture of 1920 × 1080 pixels, a frame rate of 60 fps, and the 8-bit RGB or 4:4:4 option at 24 bits per pixel. These are the calculator’s illustrative default values.
- Pixels per frame: 1920 × 1080 = 2,073,600.
- Pixels per second: 2,073,600 × 60 = 124,416,000.
- Bits per second: 124,416,000 × 24 = 2,985,984,000.
- Decimal Gbit/s: 2,985,984,000 ÷ 1,000,000,000 = 2.985984.
The calculator rounds this example to 2.986 Gbit/s. That is the estimated active video payload, not the minimum rated speed of a cable, interface, or network connection.
Use cases for the Uncompressed Video Bandwidth Calculator
Compare resolution and frame rate choices. If you are choosing between display or capture settings, the calculator shows how the active video payload changes when you adjust the resolution or frame rate. With the other inputs held constant, doubling the frame rate doubles the result. Doubling both frame dimensions produces four times as many pixels per frame and therefore four times the payload.
Explore pixel format trade-offs. For the same dimensions and frame rate, the 10-bit RGB or 4:4:4 assumption uses 30 bits per pixel, compared with 24 for the 8-bit option. Its estimated payload is therefore 25% higher. The 8-bit 4:2:2 assumption uses 16 bits per pixel, so its estimated payload is lower than either of those options.
Plan a capture or editing workflow. A payload estimate gives PC builders and video editors a starting point for understanding the volume of uncompressed picture data. Check the capture device’s supported modes and the recording format as well: a device may compress video, use a different pixel format, or add data that this calculation does not include.
Compare production formats. As another illustrative assumption, 3840 × 2160 video at 30 fps using 10-bit RGB or 4:4:4 has a calculated payload of 7.46496 Gbit/s, displayed as 7.465 Gbit/s. A 1280 × 720 stream at 30 fps using 8-bit 4:2:2 has a calculated payload of 0.442368 Gbit/s, displayed as 0.442 Gbit/s. These examples use the calculator’s stated bits-per-pixel assumptions.
Other factors to consider when calculating Video Payload Bandwidth
Interface and transport overhead: The payload result does not include the extra capacity a video interface or network may need to carry the signal. Blanking intervals, protocol overhead, audio, and other transport requirements can increase the total. Consult the relevant device and interface specifications before deciding whether a connection supports a particular mode.
Pixel packing and alignment: The calculator applies the selected average bits per pixel directly. It does not account for format-specific packing or chroma-subsampling alignment. In particular, the 8-bit 4:2:2 option assumes an average of 16 bits per pixel; the actual transport rate can be higher.
Active picture versus signal timing: Enter the dimensions of the visible picture. Some video signals transmit additional timing information outside that active area, which is excluded from this estimate.
Fractional frame rates: Use the frame rate that applies to your source. For example, 59.94 fps produces a slightly lower payload estimate than 60 fps with the same dimensions and pixel format. The calculator accepts frame rates to three decimal places.
Storage calculations: Gbit/s measures a data rate, while storage capacity is commonly expressed in bytes. Eight bits equal one byte, so an idealized conversion to decimal gigabytes per second divides the Gbit/s figure by eight. Actual recording needs can differ because of file formatting, additional streams, packing, and whether the recording is compressed.
Frequently asked questions
What does uncompressed video bandwidth mean?
It is the rate at which video data is produced when frames are represented without compression. This calculator estimates the data for the active picture using the selected bits-per-pixel assumption.
Is the result the connection speed I need?
No. The result is the active video payload rate. A real connection can require additional capacity for blanking, audio, packing, and protocol overhead, and it must also support the specific video mode.
Why does 10-bit video have a higher estimated bandwidth?
In the available RGB or 4:4:4 options, 10-bit video is calculated at 30 bits per pixel, while 8-bit video is calculated at 24 bits per pixel. With the same frame size and frame rate, the higher bits-per-pixel value produces a higher payload rate.
Does this calculator estimate compressed video bandwidth?
No. It assumes full frames with no compression. Compressed video rates depend on the codec and encoding settings, so they cannot be determined from these inputs alone.
Can I use the result to estimate recording size?
You can use it as a starting point for an idealized uncompressed picture-data estimate. Convert bits to bytes and multiply by the recording duration, then account separately for file overhead, audio, packing, and any compression used in the actual workflow.