Your Camera May Need More Bandwidth Than You Think
Picture a machine-vision line with several high-resolution cameras plugged into one industrial Ethernet switch. Each camera works perfectly on the bench. On the line, when they all transmit at once, you get delays, dropped frames, and unstable inspection results.
So how much bandwidth does each camera actually need? It depends on more than megapixels: resolution + pixel depth + frame rate + pixel format + number of cameras. Estimating industrial camera bandwidth before you choose switches and uplinks is much cheaper than fixing a bottleneck after commissioning.
What Determines an Industrial Camera’s Bandwidth?
- Resolution: More pixels per frame means more data per frame.
- Frame rate: More frames per second means more data per second.
- Pixel depth: 8-, 10-, 12-bit and higher formats change the data per pixel.
- Pixel format: Mono8, Mono16, and RGB8 (24-bit) transmit different numbers of bytes per pixel. Actual transmitted bytes depend on the format and on how the camera packs the data.
- Compression: Some systems support compression or data reduction, but many machine-vision cameras send largely uncompressed image data.
- Number of cameras: Five cameras transmitting together are a different problem from one.
Megapixels alone do not determine bandwidth.
The Basic Industrial Camera Bandwidth Formula
Raw Data Rate ≈ Width × Height × Bits per Pixel × Frames per Second
The result is in bits per second. Divide by 1,000,000 for Mb/s or 1,000,000,000 for Gb/s.
Example (illustrative): 1920 × 1080, 8 bits/pixel, 30 FPS.
1920 × 1080 × 8 × 30 = 497,664,000 bits/s ≈ 498 Mb/s
This is a raw image-data estimate. It is not the exact Ethernet wire rate, because protocol and Ethernet overhead add traffic on top. Treat it as a starting point, not a universal benchmark.
How Resolution Changes Bandwidth
Assumptions: 8-bit monochrome, 30 FPS.
| Resolution | Approx. Raw Data Rate at 30 FPS |
|---|---|
| 1280 × 1024 | 315 Mb/s |
| 1920 × 1080 | 498 Mb/s |
| 2560 × 1440 | 885 Mb/s |
| 3840 × 2160 | 1.99 Gb/s |
Going from 1080p to 4K multiplies the pixel count by four, so the data per frame does too.
How Frame Rate Changes Camera Bandwidth
With everything else constant, bandwidth scales roughly linearly with frame rate. For 1920 × 1080, 8-bit mono:
- 15 FPS: ~249 Mb/s
- 30 FPS: ~498 Mb/s
- 60 FPS: ~995 Mb/s
- 120 FPS: ~1.99 Gb/s
Doubling the frame rate roughly doubles the raw data. Also separate camera acquisition rate from network transmission rate. Buffering, triggering, packetisation, and transport settings can all change how that data appears on the wire.
Monochrome vs Colour: Why Pixel Format Matters
Take 1920 × 1080 at 30 FPS:
| Pixel Format | Bits/Pixel | Approx. Raw Data Rate |
|---|---|---|
| Mono8 | 8 | 498 Mb/s |
| Mono16 | 16 | 995 Mb/s |
| RGB8 (24-bit) | 24 | 1.49 Gb/s |
Same resolution, same frame rate, three times the data between the first and last rows. Not every colour camera sends 24 bits per pixel in every configuration. Some transmit raw sensor data and convert later. Check the camera’s actual pixel format and payload size rather than calculating from resolution alone.
Practical Bandwidth Examples
| Camera Configuration (illustrative) | Approx. Raw Data Rate |
|---|---|
| 1280 × 1024, Mono8, 30 FPS | 315 Mb/s |
| 1920 × 1080, Mono8, 30 FPS | 498 Mb/s |
| 1920 × 1080, Mono8, 60 FPS | 995 Mb/s |
| 2560 × 1440, Mono8, 30 FPS | 885 Mb/s |
| 3840 × 2160, Mono8, 30 FPS | 1.99 Gb/s |
These are simplified raw image-data calculations, not measured Ethernet throughput. Real planning should include overhead and engineering margin.
1 GbE vs 2.5 GbE vs 5 GbE vs 10 GbE
- 1 GbE: suits many moderate-bandwidth camera applications, depending on configuration and traffic pattern. GigE Vision, one machine-vision Ethernet standard, is commonly used here, though not every industrial camera uses it.
- 2.5/5 GbE: adds capacity for higher-throughput cameras where supported.
- 10 GbE: becomes useful for high-resolution, high-frame-rate cameras or multi-camera aggregation.
Don’t assume 4K always requires 10 GbE. The real requirement depends on pixel format, FPS, compression, triggering, camera count, and network architecture. Choose link speed from calculated traffic, not from resolution.
One Camera vs Multiple Industrial Cameras
Four cameras at roughly 500 Mb/s each add up to about 2 Gb/s. A single 1 GbE uplink cannot carry that simultaneous raw traffic without traffic shaping, buffering, reduced transmission rates, or a different architecture.
Camera 1 →
Camera 2 → Industrial Ethernet Switch → High-Speed Uplink
Camera 3 →
Camera 4 →Each camera access port may carry only 500 Mb/s while the uplink carries the sum. Access ports and uplinks have very different requirements.
Why the Industrial Ethernet Switch Matters
A fast camera interface is only half the design. Evaluate the switch for:
- Port and uplink speed
- Switching capacity and forwarding performance
- Buffer capacity
- Jumbo-frame support, where applicable
- QoS, VLAN, and multicast handling, where relevant
- Managed configuration
- Industrial environmental specifications
Not every machine-vision network needs every feature. The right set depends on the camera protocol and network architecture.
Don’t Confuse Port Speed With Usable Camera Bandwidth
A 1 GbE port is not 1 Gb/s of guaranteed application payload. Ethernet framing, inter-packet gaps, and protocol headers consume part of the link capacity before any pixel data is delivered.
That’s why engineers leave headroom instead of running a link continuously at its theoretical maximum. How much margin is a design decision based on traffic patterns, protocol, and tolerance for loss, not a universal percentage.
Triggered Cameras Can Change the Bandwidth Picture
Not every camera streams at full rate all the time. Systems may use hardware or software triggering, burst acquisition, event-based capture, or inspection cycles. A camera may then produce short, intense bursts instead of a constant stream.
That matters for switch buffering, uplink capacity, traffic scheduling, and processing systems, especially when several cameras fire together. Plan for both average bandwidth and peak/burst bandwidth.
Jumbo Frames and Industrial Camera Bandwidth
Some high-throughput machine-vision systems benefit from larger Ethernet frames, provided the camera, NIC, switch, and the entire path support them. Larger frames can reduce certain per-frame overheads.
But jumbo frames do not increase physical link speed, and they don’t automatically fix congestion or packet loss. Many camera systems run fine without them. For more detail, see our guide to jumbo frame support in Industrial Ethernet.
How to Calculate Bandwidth for a Real Camera System
- Find the camera resolution.
- Find the pixel format and bits per pixel.
- Find the maximum frame rate.
- Calculate raw data rate: Width × Height × Bits per Pixel × FPS.
- Account for protocol and network overhead.
- Multiply by the number of simultaneously transmitting cameras.
- Evaluate switch access-port and uplink requirements.
- Consider peak and burst traffic.
- Add appropriate engineering headroom.
- Test the real system under expected operating conditions.
Worked Example: Four-Camera Machine Vision Network
Illustrative setup: 4 cameras, 1920 × 1080, Mono8, 30 FPS.
- One camera: ≈ 498 Mb/s
- Four cameras: 4 × 497.664 ≈ 1.99 Gb/s raw
4 × Industrial Cameras → Managed Industrial Ethernet Switch → High-Speed Uplink → Industrial PCEach camera fits a 1 GbE access port, but the uplink must carry the aggregate. If it’s undersized, expect queue buildup, buffer overflow, dropped packets, and lost frames.
Possible approaches include a higher-speed uplink, traffic scheduling, trigger coordination, camera configuration changes, multiple uplinks or segmentation, and higher-speed Ethernet. The right choice depends on the application.
Common Mistakes When Designing Camera Networks
- Calculating from megapixels alone
- Ignoring frame rate or pixel format
- Forgetting multi-camera aggregation
- Using a 1 GbE uplink for traffic beyond its practical capacity
- Ignoring burst traffic
- Designing with no headroom
- Treating port speed as application throughput
- Overlooking camera/NIC/switch compatibility
- Assuming jumbo frames solve bandwidth problems
Conclusion: Calculate First, Then Choose the Network
There is no single bandwidth requirement for an industrial camera. It depends on resolution × pixel format × frame rate × camera count, plus overhead, peak traffic, switch capacity, uplink capacity, architecture, and headroom. At Comxus, we see industrial Ethernet switch selection as starting with the actual camera traffic requirement, not simply the number of ports.
Read Also: Industrial Ethernet vs OPC UA: What Does Each Do?
Read Also: What Is Jumbo Frame Support in Industrial Ethernet?
