Image payload
Width × height × transmitted bits per pixel ÷ 8.
Knowledge · GigE cameras
Does your PC start losing images as the line speeds up? Calculate the camera’s data rate and check every link that carries it. Use the formula and worked example below, then test whether the complete system can sustain your production rate.
Image payload
Width × height × transmitted bits per pixel ÷ 8.
Data rate
Multiply bytes per image by the number of frames per second.
System test
Check overhead, simultaneous transfers and host processing.

Collect transmitted width, height, pixel format and frames per second. For a camera region of interest (ROI), use the actual transmitted dimensions. Cropping after reception on the PC does not reduce network traffic. Include any extra data carried with the image, such as timestamps or other chunk data.
Sensor bit depth does not necessarily equal the transmitted bit count. A 12-bit sample may be packed or carried in a 16-bit field. Raw Bayer8 colour data normally occupies one byte per pixel; RGB8 contains three channels and occupies three bytes. Converting Bayer to RGB on the host increases host memory traffic while leaving the original network transfer unchanged. Check the selected transport format.
Where available, read PayloadSize for the selected configuration. It reports the image and additional payload bytes per acquisition, excluding network packet headers, and is useful for checking a manual calculation.
MB/s = width × height × transmitted bytes per pixel × frames/s ÷ 1,000,000
For an uncompressed image without additional data: bytes per image = width × height × transmitted bits per pixel ÷ 8. Multiply by frames per second to obtain the average image payload rate. Use the camera's actual packing rules and PayloadSize when they differ from this simplified calculation.
Here, 1 MB means 1,000,000 bytes and 1 Mbit means 1,000,000 bits. Multiply MB/s by 8 to obtain Mbit/s. A 1 Gbit/s connection therefore has a nominal rate equivalent to 125 MB/s, before protocol overhead and on-wire gaps.
| Mono8 | 100.27 MB/s | 80.2% of the nominal link, before overhead. |
|---|---|---|
| 12-bit packed | 150.41 MB/s | Exceeds the nominal capacity of 1 Gbit/s. |
| 16-bit | 200.54 MB/s | Exceeds the nominal capacity of 1 Gbit/s. |
Consider an uncompressed 2448 × 2048 image in Mono8 at 20 frames per second. The calculation below shows the demand on a 1 Gbit/s link. These are calculated data rates rather than measurements from a camera model.
Each image contains 2448 × 2048 × 8 ÷ 8 = 5,013,504 bytes. At 20 frames per second, that becomes 100,270,080 bytes/s: 100.27 MB/s or 802.16 Mbit/s. Image payload alone occupies about 80.2% of a nominal 1 Gbit/s link. Whether the remaining capacity is sufficient depends on packet settings, retransmission demand and the host.
At the same dimensions and rate, a format genuinely packed to 12 bits per pixel requires 150.41 MB/s. A 16-bit-per-pixel transport requires 200.54 MB/s. Both exceed the nominal 125 MB/s of a 1 Gbit/s link before overhead. Reduce the data rate or select a faster connection.
Two cameras using the Mono8 example produce 200.54 MB/s together. A shared 1 Gbit/s switch uplink cannot carry that sustained load. Separate camera-facing ports on the switch do not remove the uplink limit.
Ethernet, IP, UDP and image-transport structures add bytes beyond the image payload. Frame leaders and trailers and any retransmitted packets also consume capacity. The overhead fraction depends on transport and packet size, so a single universal reserve percentage cannot guarantee operation.
Jumbo frames reduce the packet count for a given payload and may ease processing load when every device supports the selected size. Increasing the interval between packets spreads transmission over time. It also extends transfer duration and may limit the achievable frame rate.
Average rate does not describe a short traffic burst. Cameras acquiring and transmitting together may overflow a switch buffer even when their average total is below link capacity. Assess both the sustained load and the timing of individual transfers.
A smaller camera ROI can reduce traffic if it still covers the required product area. Reducing frame rate is acceptable only if every product can still be captured on time. A different pixel format must retain the information the inspection needs. Repeat defect-detection tests after changing these settings.
For a higher required data rate, consider a faster interface or separate connections. Check aggregate adapter capacity, the PCIe path into the PC and image processing throughput. If images are stored, sustained storage write speed matters too. Replacing the cable alone does not increase the speed of a 1 Gbit/s camera port.
Run every camera with the final settings and the shortest required trigger interval. Count requested acquisitions, complete received images and inspection results delivered on time. Monitor retransmissions and adapter, CPU and storage load. Include simultaneous triggers and the heaviest product recipe.
Agree on the permitted latency and the machine response to a missing image before testing. A run without missing images supports the tested conditions and duration. Record those conditions and settings with the results.
Compare the cost of a faster link with additional ports, a different PC or a reduction in image data. Include engineering and maintenance. Measured downtime, rejects and operator intervention time provide the inputs for the investment decision.
Consult the GigE manual for power, network configuration, packet size, packet interval and pixel format. Available features depend on the camera model and software release. Check the exact model manual for timing features.
A practical benefit of VC-series industrial PCs is built-in PoE on supported models. One Ethernet cable carries image data and powers the camera, removing the need for a separate PoE injector. Choose the model and power budget to match your cameras.

Industrial vision PC with PoE options for multiple cameras. Compare network ports and PC configurations by variant.
Four PoE ports listed for MV-VC5525-256G70-2T and MV-VC5715-256G70-2T.

Vision controller with four GigE ports. Select a VC2143 variant for integrated PoE; VC2140 variants do not include PoE.
VC2143: 20 W total PoE loading according to the product specification.
Provide image dimensions, transport pixel format and maximum trigger rate for each camera, together with a network diagram. These inputs allow us to identify the limiting connection and define a useful test.
Discuss your camera setup