Camera Bandwidth Calculator

Size camera links and zonal backbones: resolution, frame rate, bit depth and compression in, Automotive Ethernet speed grade out.

How fast does the link from a camera to the central computer need to be? Move the sliders to estimate the data rate of a single camera and of several cameras sharing a zonal backbone, and see which Automotive Ethernet speed grade fits.

Required per camera link
0 Gb/s
Pixels per frame–
Raw sensor rate–
All cameras on backbone–
Suggested backbone (30% headroom)–

Estimate only: real links also carry control traffic, embedded metadata and line coding. Use as a first-order sizing aid.

How the calculation works

The raw data rate of an image sensor is width × height × frames per second × bits per pixel. A 2.9-megapixel ADAS camera at 30 frames per second with 12-bit RAW output therefore produces about 1.06 Gb/s before any protocol overhead. Compression divides that figure; protocol overhead (Ethernet, IP/UDP or IEEE 1722 headers, inter-frame gaps, metadata) adds a few percent back.

Suggested speed grades come from the Automotive Ethernet ladder: 1000BASE-T1 (IEEE 802.3bp), 2.5/5/10GBASE-T1 (IEEE 802.3ch) and 25/50/100GBASE-T1 (IEEE 802.3cy). For the backbone we keep 30 % headroom for other traffic, redundancy and future growth.

Typical results

CameraFormatApprox. raw rateFits on
Surround-view, 1.3 MP, 30 fpsYUV422 (16 bit)~0.6 Gb/s1000BASE-T1
ADAS front, 2.9 MP, 30 fpsRAW12~1.1 Gb/s2.5GBASE-T1
8.3 MP, 30 fpsRAW12~3.0 Gb/s5GBASE-T1
8.3 MP, 60 fpsRAW12~6.0 Gb/s10GBASE-T1
12.6 MP, 60 fpsRAW20 HDR~15 Gb/s25GBASE-T1

Because camera traffic flows overwhelmingly in one direction, these links are ideal candidates for Asymmetrical Ethernet.

The calculator gives a first-order estimate for architecture studies; final link budgets depend on the sensor interface, metadata, coding and the specific PHY. See our Disclaimer.