Three USB3 cameras on one hub look like three ports, but electrically they share a single 5 Gbit/s link back to the computer. Line coding takes 20% of that link, leaving about 4 Gbit/s — 500 MB/s — for image data, and every stream you add draws from the same pool. This guide gives you the arithmetic to budget that pool before you buy: one formula, a worked example with three real cameras, and the decision between one 5 Gbit/s hub, two hubs, a 10 Gbit/s link or separate root ports. Five minutes with a calculator here prevents the most common multi-camera failure: frames that only start dropping once the last camera joins.
How much bandwidth does one USB 3 hub really give you?
Every port on a USB 3 hub shares one upstream link of 5 Gbit/s, and the 8b/10b line coding on that link leaves about 4 Gbit/s — 500 MB/s — of usable throughput for every attached camera combined.
SuperSpeed USB, sold as USB 3.0 and later as USB 3.1 Gen 1, signals at 5 Gbit/s per lane and encodes every 8 data bits into a 10-bit symbol, so the payload ceiling is 4 Gbit/s before protocol and hub overhead take a few more percent (USB 3.0). Plan the budget at 4 Gbit/s and the bench holds no surprises.
The hub never multiplies bandwidth. Four downstream ports still drain one upstream pipe, and anything else on that host root port — a disk, a capture device — draws from the same 4 Gbit/s. If your frames already stutter on a shared hub, USB hub drops camera frame rate: budget the bandwidth first works the same numbers from the symptom backwards.
How do I calculate one camera's data rate?
Multiply sensor width by height by frame rate by bytes per pixel, then by 8 for bits: a 1280 × 1024 sensor at 30 fps in mono8 moves 314.6 Mbit/s.
Bytes per pixel is set by the pixel format the camera exports, not by the sensor's converter:
- Mono8 and raw 8-bit Bayer: 1 byte
- YUV422 packed: 2 bytes
- RGB8: 3 bytes
- 10-bit packed: 1.25 bytes
- 12-bit packed: 1.5 bytes
- any format delivered unpacked at 16 bits: 2 bytes
A 10-bit sensor exporting mono8 still costs 1 byte per pixel on the wire — ADC bit depth vs pixel format: why 10-bit sensors ship 8-bit images explains why 8-bit is the usual default. When the aim is cutting one camera's rate rather than sharing one link, reduce USB3 camera bandwidth: the per-camera budget math lists the levers in order.
Will three cameras fit on one 5 Gbit/s hub?
Add the three stream rates and compare the total with the 4 Gbit/s budget: three 1.3 MP mono8 cameras at 30 fps total 0.94 Gbit/s and fit, while three 12 MP cameras at 30 fps total 8.64 Gbit/s and do not.
Start with the heavy case, the LS-CMR-0166: a 12 MP USB3 camera with a 4000 × 3000 sensor at 30 fps. One mono8 stream is 4000 × 3000 × 30 × 1 byte = 360,000,000 B/s, or 360 MB/s, or 2.88 Gbit/s. Three of them: 3 × 2.88 = 8.64 Gbit/s against a 4 Gbit/s budget — 216% of what the hub carries. No setting rescues that. If the frame rate is negotiable: 4,000 Mbit/s ÷ 3 cameras = 1,333 Mbit/s each, ÷ 8 = 167 MB/s, ÷ 12,000,000 pixels ≈ 13.9 fps, so cap each camera at 13 fps and all three run on one hub.
The light case: the LS-BCM-0043 binocular module, a 1.3 MP unit delivering 1280 × 1024. At 30 fps in mono8 that is 1280 × 1024 × 30 × 8 = 314.6 Mbit/s per stream, and three modules total 0.94 Gbit/s — 24% of the budget. One hub carries them with margin.
The middle case is the brutal one: the LS-BCM-0003, a 3.1 MP global-shutter board camera that runs 120 fps. Full speed in mono8 is 3,100,000 × 120 × 8 = 2.98 Gbit/s, which is 74% of the budget from one camera. A second identical unit would need 5.95 Gbit/s together, so it gets its own hub or its own root port.
| Set-up, all mono8 | Stream total | Share of 4 Gbit/s budget | Decision |
|---|---|---|---|
| 3 × 1.3 MP at 30 fps | 0.94 Gbit/s | 24% | One 5 Gbit/s hub |
| 1 × 3.1 MP at 120 fps | 2.98 Gbit/s | 74% | One camera per hub |
| 3 × 3.1 MP at 60 fps | 4.46 Gbit/s | 112% | Two hubs or lower fps |
| 3 × 12 MP at 30 fps | 8.64 Gbit/s | 216% | 10 Gbit/s link or a port each |
The three cameras used above, side by side:
| Specification | LS-CMR-0166 | LS-BCM-0003 | LS-BCM-0043 |
|---|---|---|---|
| Sensor model | Sony IMX226 | Sony IMX252 | PYTHON |
| Resolution | 4000 × 3000 (12MP) | 2048 × 1536 (3MP) | – |
| Max. frame rate | 30 fps | 120 fps | – |
| Pixel size | 1.85 μm | 3.45 μm | 4.8 μm x 4.8 μm |
| Sensor size | 1/1.7" | 1/1.8" | – |
| Shutter | rolling shutter | Global | – |
| Data interface | USB 3.0 | USB3.0 | – |
| Pixel bit depth | 10-bit | 10-bit | 8bit |
| Sensor type | – | CMOS | CMOS |
| Power supply | – | 5 V via USB3.0 port | 5 V, USB bus power supply |
| Lens mount | – | C-mount | M12 lens holder can be installed |
| Weight | – | 50 g | <75 g |
| Price | $560.00 | $690.00 | $179.00 |
Values as printed in each product's data sheet; open a part for its drawing and full specifications.
How much does a depth or stereo camera add to the budget?
Count every stream the device sends, because depth, infrared and colour images each ride the link separately: a stereo module outputting depth plus two infrared streams costs three streams, not one.
Work the module's own numbers. A 1280 × 1024 stereo camera at 30 fps sends depth in 16 bits (1280 × 1024 × 30 × 2 × 8 = 629 Mbit/s) and two 8-bit infrared streams (2 × 314.6 = 629 Mbit/s). That is 1.26 Gbit/s before colour; an RGB8 stream adds 944 Mbit/s, for 2.2 Gbit/s per camera. Two such cameras with colour need 4.4 Gbit/s and miss the budget; drop the colour stream and the pair runs at 2.52 Gbit/s on one hub.
Depth cameras add two wiring questions beyond the sum. Multiple USB cameras on one host: bandwidth and power budget covers the combined plan, and selecting each depth camera by serial number keeps three identical units addressable. The 3D sensors range covers laser profilers, structured-light and ToF cameras.
When is a 10 Gbit/s link the right answer?
Move up when the combined streams sit between about 4 and 9.5 Gbit/s: a 10 Gbit/s upstream link carries roughly 1,212 MB/s of payload after its 3% line-coding overhead, which is 9.7 Gbit/s for the whole hub.
USB 3.1 Gen 2 runs the upstream at 10 Gbit/s with about 3% coding overhead, an effective 1,212 MB/s — call it 9.5 Gbit/s of planning budget. The three 12 MP cameras from the worked example total 8.64 Gbit/s, which is 89% of that: all three fit on one 10 Gbit/s hub, with the margin watched on the bench.
Two conditions decide success. First, the host port must be Gen 2 — a Gen 1 port caps the whole chain at 5 Gbit/s no matter what the hub claims. Second, most 10 Gbit/s hubs still offer 5 Gbit/s downstream ports, which is fine here: each camera stays under 5 Gbit/s while the shared upstream carries the sum.
Above 9.5 Gbit/s, USB stops being the answer: give cameras separate 5 Gbit/s root ports, or change interface. The area scan cameras finder filters by 10GigE and CoaXPress for exactly that step, and 4K machine vision at 60 FPS: bandwidth and interface limits compares the interfaces when a single camera outgrows USB on its own.
What limits three cameras before bandwidth does?
Power usually does: the USB 3 specification allows a downstream port to supply 900 mA at 5 V — 4.5 W — and a bus-powered hub forwards only what it receives, so three industrial cameras need a hub with its own supply.
Industrial USB3 cameras typically draw 2–4 W each, so three of them sit at 6–12 W against the 4.5 W a bus-powered hub can pass on. Feed them from a self-powered hub with its own mains adapter.
The host controller matters as much as the hub. Every controller root port brings its own 5 Gbit/s, so three root ports are three budgets; the device tree in the operating system shows which port feeds which camera. On Linux, the default size of the USB transfer buffers also caps multi-camera streaming — USB3 Vision cameras on Linux: usbfs and file limits that need tuning covers the setting, and two USB3 cameras at full resolution: raise the host USB buffer shows the symptom. Keep passive cable runs short — about 3 m at 5 Gbit/s — and keep disks and other bulk devices off the camera hub entirely.
What should I check before buying the hub?
Buy a self-powered hub whose upstream speed matches the plan — 5 Gbit/s for totals under 4 Gbit/s, 10 Gbit/s between 4 and 9.5 Gbit/s — and give every camera its own downstream port with nothing else attached.
- Self-powered, with a mains adapter. The per-port current rating must sit above each camera's draw; 900 mA per port is the specification floor, not the plan.
- Upstream speed you can actually use. A 10 Gbit/s upstream only pays off behind a 10 Gbit/s host port.
- One camera per downstream port. A second hub chained behind the first adds ports, never bandwidth.
- Nothing else on the hub. Storage and capture devices compete for the same 4 Gbit/s.
- Locked connectors on the machine. Screw-secured USB 3 connectors hold where vibration works plug friction loose.
The camera finder filters USB3 models by resolution and interface, so the streams you budget here match parts you can actually order. Board-level cameras also keep the per-camera power draw low, which is why embedded machines favour them.
Parts that bracket the budget, lightest stream to heaviest:
- Sensor format
- 1/1.7"
- Interface
- USB3
- Sensor format
- 1/2"
- Lens mount
- M12
- Sensor format
- 1/1.8"
- Lens mount
- C-mount
Compact cameras to build in
120 models · from $179.00How do I prove the budget on the bench?
Run each camera alone at its target pixel format and frame rate, then add cameras one at a time: incomplete frames or a sagging frame rate mark the moment the shared link saturates.
- Bring the first camera up at full settings and record the delivered frame rate and pixel format — what the driver reports, not what was requested.
- Add the second camera; confirm both hold their target rates for a minute.
- Add the third. Watch for incomplete frames, retries or a rate drop on any stream: that is the 4 Gbit/s line being crossed.
- If it saturates, lower the frame rate or crop the region of interest at the source — camera ROI cropping at the source: reduce bandwidth before the host — and retest.
- Let the final line-up run an hour. Buffer growth and cable heating show up late, not in the first minute.
When a stream that ran fine yesterday starts dropping today, camera FPS drops suddenly: exposure, USB link, bandwidth triages the other causes. With the budget closed, the camera configurator walks the rest of the chain — lens, light, controller — or send the three stream rates through the contact page and we will size the ports with you. More wiring and budgeting guides sit under systems.
The configurator matches a camera, lens, light, light controller and cables to each other, step by step, and lists only parts that fit what you already picked.
Questions
Does daisy-chaining two USB 3 hubs give more bandwidth?
No. The upstream link of the last hub in the chain is still one shared 5 Gbit/s pipe to the host, and every camera on every hub draws from it. The USB standard allows up to five hubs in a chain, which adds ports but never bandwidth. When the stream total passes 4 Gbit/s, split the cameras across separate host root ports instead of chaining hubs.
How much bandwidth do 10-bit and 12-bit images add?
Count bytes per pixel: mono8 and raw Bayer8 are 1 byte, 10-bit packed is 1.25, 12-bit packed is 1.5, and any format delivered unpacked at 16 bits is 2. A 3.1 MP camera at 60 fps needs 1.49 Gbit/s in mono8 but 2.98 Gbit/s in 16-bit unpacked — the difference between two cameras per hub and one.
Is a 10 Gbit/s hub enough for three 12 MP cameras at 30 fps?
Yes, with the margin watched. Three mono8 streams of 4000 × 3000 pixels at 30 fps total 8.64 Gbit/s, and a 10 Gbit/s upstream link carries about 1,212 MB/s (9.7 Gbit/s) of payload, so you sit near 89% of it. The host port must also run at 10 Gbit/s — a Gen 1 port silently caps the whole chain at 5 Gbit/s.
Why does the third camera work alone but drop frames with the others?
Each camera alone sits below the link's saturation point of roughly 4 Gbit/s on a 5 Gbit/s hub. The third stream pushes the sum past that line, the hub buffers fill, and whole frames start arriving late or incomplete. Cap the frame rate — 4 Gbit/s across three cameras is about 1.33 Gbit/s each — crop the region of interest, or move one camera to another port.
Should three cameras share one hub or use separate root ports?
Separate root ports whenever the host has them: every controller root port brings its own 5 Gbit/s, so three ports give three budgets instead of one. One hub makes sense for light streams under 4 Gbit/s total, or as wiring convenience when its 10 Gbit/s upstream carries the combined load. Read the device tree in the operating system before buying, not after.