Zivid Two Network Configuration

The Zivid Two camera uses Ethernet communication and needs 10 Gbps for best performance. Your computer may not have a port for 10 Gigabit Ethernet. In that case, you can connect to it using a Thunderbolt 3 to 10GbE Adapter. At a reduced performance you can also use USB to 5GbE, 2.5GbE, or 1GbE adapters.

Default Zivid Two network configuration






Optimal (recommended)

10GbE (10Gbps)

PCIe card


Very good


Thunderbolt Adapter



5GbE or 2.5GbE

PCIe/USB/Thunderbolt Adapter



1GbE (1Gbps)

PCIe/USB Adapter



USB-based network adapters have reduced and more variable capture speed, and can occasionally give errors when using the camera.

Default configuration


Subnet mask



Zivid Two

zivid-<serial number>

Possible PC 1


Any IP address in the subnet range is valid, except the network address ( and the broadcast address ( We also choose to avoid the gateway IP (, even though we don’t currently require a gateway.

In order to use the camera with the default IP address your PC’s IP address must be in the same subnet, as listed in the table above. Go to Static IP Network Configuration - PC.

How do I find the camera?

From Zivid SDK 2.7, it is straightforward to find the IP address of your Zivid Two camera. However, the firmware needs to be upgraded for the following to work.

You can ping it via default hostname zivid-<serial number>, followed by domain local (e.g., zivid-2152D404.local):

Camera discovery using ping and hostname.local

You can also discover the camera using ZividNetworkCameraConfigurator tool:

Camera discovery using ZividNetworkCameraConfigurator and hostname.local


This tool is installed alongside the Zivid SDK on Windows, and with the zivid-tools package on Ubuntu. If you are unsure whether this tool has been installed, follow the Software Installation guide.


ZividNetworkCameraConfigurator allows getting camera info:

Camera info using ZividNetworkCameraConfigurator and hostname.local

How does Zivid SDK find the camera?

The Zivid SDK knows the default IP address of the camera. In addition it will check all hostnames and IP addresses listed in Cameras.yml

pseudo code to show how Zivid SDK looks for a connected camera

def find_camera():
  if exists(Cameras.yml):
    for IP in Cameras.yml:
    for hostname in Cameras.yml:
Sample Cameras.yml file (host names)
__version__: 1
        - NetworkCamera:
              Host: zivid-2152D404.local
        - NetworkCamera:
              Host: zivid-20205M19.local
        - NetworkCamera:
              Host: zivid-21389K63.local
Sample Cameras.yml file (IP addresses)
__version__: 1
        - NetworkCamera:
        - NetworkCamera:
        - NetworkCamera:

Path to Cameras.yml

move %HOMEPATH%\Downloads\Cameras.yml %LOCALAPPDATA%\Zivid\API\


Zivid configuration files must use .yml file extension ( not .yaml).

Custom configuration, single or multiple cameras

If you want to change the IP address of a single camera, you need to reconfigure the network settings. The same applies if you want to use multiple Zivid Two cameras connected to the same network card (each of them must have their unique IP address).


There may be multiple reasons for why one wants to use custom static IPs. One may want to connect multiple cameras to the same network card or there may be an IP conflict with the IP range used by one’s internal network.


Two cameras connected to two separate network interface cards can potentially provide higher speed. This is because they will not have to share network bandwidth. There may be a bottleneck on the PC driver/application side, but at least the cameras do not share the same physical network.

Network configuration for two Zivid Two cameras connected to two separate network interface cards.


The Zivid Two also supports automatic IP configuration using either DHCP or link-local. When configured to use an automatic IP (configured to DHCP using ZividNetworkCameraConfigurator), the camera will first try to obtain an IP address using DHCP (within ~45 seconds). Getting an IP address from a DHCP server requires a DHCP server running either on a router on the network or locally on the PC. If no DHCP server is available, the camera will fall back to a link-local IP address (after ~45 seconds).

It is possible to connect to the camera via a hostname.


From SDK 2.7, connection via hostname no longer requires a NetBIOS Naming Service.


It is highly recommended to use hostnames when using a dynamic IP. If not you have to list all possible IP addresses in Cameras.yml, or find the IP address assigned to the camera and list that. When you use hostnames you only have to list the expected hostnames, and it doesn’t matter if the IP address is reassigned.


If you are not careful it is easy to run into issues with DHCP. For example, running more than one DHCP server with overlapping address range on the same network.

The following guides walk through each configuration option step by step.