Contact Us

You can always reach out to Zivid via If you prefer to perform some local troubleshooting we have a number of troubleshooting guides, as well as a set of FAQ.

If the issue is not listed in our Knowledge Base, or if you still encounter it, please contact us at


To speed up the support case and to maximize the chance of solving your issue it is recommended to provide a standalone reproducer and steps on how to use it.

To help us determine the cause and find a solution, please provide the following:

Log Files

Launch the Command Prompt (press Win + R keys on the keyboard, then type cmd and press Enter) and navigate to:


Send us a couple of log files created just after the issue occurred.

System Info

Launch Zivid Studio, then click on the buttons in the following order:

HelpAbout Zivid StudioSystem InfoCopy to Clipboard

Operating System

  • Ubuntu (16.04, 18.04, 20.04)

  • Windows 10

ZDF file

If the issue is related to artifacts in the point cloud or color image, providing a .zdf file will go a long way. To maximize the effectiveness of Zivid’s support, enable Diagnostics before capturing, to collect additional data when saving a .zdf file.

There are three ways to capture with diagnostics enabled.

  1. From Zivid Studio:

    In Zivid Studio the setting is at the bottom of the control panel.

  2. From the SDK:

    Enable the diagnostics setting as any other setting.

  3. With a config file:

    Using this config file will overwrite the settings to always enable diagnostics. Remember to disable it again in the config file after the debugging session.

    1. Download the Config.yml file.

      The config file contains the following information:

          serializer: 1
          data: 13
                  Enabled: Always
    2. Place the config file in the following directory:

      mkdir %LOCALAPPDATA%\Zivid\API
      move %HOMEPATH%\Downloads\Config.yml %LOCALAPPDATA%\Zivid\API\


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