---
title: "Vision"
slug: "vision"
status: "new"
updated: 2025-06-10T16:52:24Z
published: 2025-06-10T16:52:24Z
canonical: "support.tulip.co/vision"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Vision

*Learn how to incorporate computer vision functionalities in your Tulip apps.*

          Who can use this feature

          

Users on Professional plans and above.

**In this article you will learn...**

- **Vision functionalities and use cases**
- **How to setup a Camera Configuration**
- **How to remotely view the video stream of a camera**
- **How to use multiple camera configurations at a station**

With Vision, you can integrate computer visual functionality with your Tulip apps. Vision is integrated into Tulip Player, and requires no additional software installation.

Vision is available to all Tulip accounts and integrates with the newest release of the Tulip Player.

[Embedded content](https://www.youtube.com/embed/qGO1_K0ng_8)

## Features

- **Video Stream** - view video stream of cameras on your shop floor.
- **[Change Detector](/r230/docs/using-the-change-detector)** - detect changes in pre-defined Regions.
- **[Jig Detector](/r230/docs/using-the-jig-detector)** - detect Jigs, objects to which you've attached printed markers.
- **[Snapshots](/r230/docs/using-visions-snapshot-feature)** - set up Snapshots to send images along to different models of your choice.
- **[Color detector](/r230/docs/using-the-color-detector)** - detect different colors
- **[Barcode and datamatrix detectors](/r230/docs/using-the-datamatrix-and-barcode-detectors)** - read in barcodes or 2D Datamatrix barcodes as vision events
- **Custom models** - create and train your own custom model for classification and object detection on your shop floor
- **[IP Cameras](/r230/docs/using-ip-cameras-with-vision)** - connect and use IP cameras on your shop floor
- **Camera Resolution** - set camera resolution
- **Tulip tables as a dataset** - turn valuable data from tables into your a dataset

## What can vision do for your operation?

- Remotely **assist operators** by having a real-time view into what's happening at a station
- Implement an **advanced Pick To Light** system by combining the Change Detector with the [Light Kit](/r230/docs/tulip-light-kit-initial-setup)
- Extend your **time studies** with additional events detected through Vision
- Track **material arrival & departure** at a station by knowing when a *jig* appears or disappears or by capturing barcode, qrcode, or datamatrix readings in **real time**.
- Improve **tracking of** **quality problems** or create your own **quality inspections** by capturing snapshots.
- Quickly create **custom models** by sending data from a Tulip connector or table to an external platform.
- Improve processes by reviewing video of specific instances for audit or process logs.

These example use cases show that, much in contrast to traditional visual inspection systems, vision is focused on augmenting your operators.

Watch the video below for a demo:

[Embedded content](https://www.youtube.com/embed/ms1EUQfCcFo)

## Requirements

Before starting with the setup, there are some prerequisites to note:

- Tulip Player must be running on **Windows** (minimum version is **1.3.2**).
- Your user must have a **Station Supervisor** role, or higher.
- Use a supported camera, see [Hardware Recommendations for Vision](/r230/docs/hardware-recommendations-for-vision)

**NOTE**: When connecting USB cameras to Tulip, please make sure to only use **USB 3.0 cables** to the clearly marked USB 3.0 ports on the computer

## Set up Vision

To setup vision, you'll need to first setup a Camera Configuration.

1. Click **Shop Floor** tab, and select **Vision**.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_335073814.png)

1. Click **Create** to create a new Camera Configuration. Name the configuration then click **Next**.
2. **Assign** the new Camera Configuration to a camera on your shop floor.

This shows a list of **all cameras connected to any Tulip Player** authenticated to your Tulip Account. If the list is empty, please plug in a USB camera now.

You can also duplicate/edit camera configurations by clicking the **three-dot-menu** pertaining to a specific camera configuration.

To **identify a specific camera** you may want to un-plug it, and then plug it back in. The most recently connected camera will be shown at the top of the list.

1. Click **Assign** and then **Done**. A new page for your Camera Configuration will open.

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_335073707.png)

By default, once your camera configuration is completed, the operator at the assigned station will be prompted with the following modal in the Player:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_269125790.png)

Note: For more information on camera stream permissions, please [Vision and Privacy](https://support.tulip.co/docs/vision-and-privacy)

Once permission has been granted in Tulip Player, the video stream of the camera you selected will appear:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_269125919.png)

Congratulations - you are now ready to create Regions, and start using Detectors.

See our collection of [Vision setup](/r230/docs/vision-setup) articles to learn how to setup features such as a change detector or jig detector.

## Advanced assignment of camera configurations

An overview of all assignments you previously made on Camera Configuration page can also be found on the **Shop Floor** page. This overview can be convenient, especially if you want to simultaneously use multiple cameras at a Station:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_269126139.png)

1. In the bottom right of the **Shop Floor** page, you'll see the **Display Device** (Interface) section:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_269126287.png)

This [list](/r230/docs/hardware-recommendations-for-vision) shows all connected cameras.

1. Click on the **View** button to view the camera's live stream directly.
2. To edit your assigned cameras, or adjust their Camera Configuration, click the **Change** button:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Getting%20Started%20with%20Vision_269126507.png)

## Further reading

- [Using the Change Detector](https://support.tulip.co/docs/using-the-change-detector) (Requires: Intel RealSense D415)
- [Using the Jig Detector](https://support.tulip.co/docs/using-the-jig-detector)
- [Using the Color Detector](https://support.tulip.co/docs/using-the-color-detector)
- [Using the Vision Camera Widget in Apps](https://support.tulip.co/docs/using-the-vision-camera-widget-in-apps)
- [Using the Snapshot Feature in Apps](https://support.tulip.co/docs/using-visions-snapshot-feature)
- [Using the Snapshot Feature with an External Vision Service](https://support.tulip.co/docs/using-visions-snapshot-feature-with-an-external-ocr-service)
- [Using the Datamatrix and Barcode Detectors](https://support.tulip.co/docs/using-the-datamatrix-and-barcode-detectors)
- [Vision and Privacy](https://support.tulip.co/docs/vision-and-privacy)
- [Hardware Recommendations for Vision](https://support.tulip.co/docs/hardware-recommendations-for-vision)

**Camera Configuration**

**Camera** **Configurations** are statically set detectors and their associated settings that can be applied to one or many cameras.

**Tulip Vision**

**Vision** is a simple no-code tool to use cameras for visual inspection, process adherence, equipment, personnel, and material tracking on the shop floor.

**Tulip Player**

**Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser and allows increased IT controls.

**Region**

**Regions** are user-established parts of a camera view within **Tulip Vision.** **Detectors** can be added to individual regions, and when that detector is triggered, app logic can be executed. Multiple regions can be established in a single camera view.

**Jig**

**Jigs** are 2D fiducial marks that **Tulip Vision** can identify. A Jig entering a **Vision Region** can trigger app logic.

**Snapshot**

**Snapshots** are the capture of a single frame of a camera running **Tulip Vision.** These image captures can be stored to tables, passed to external APIs, and more.

**Pick to Light**

**Pick-To-Light** is a very common use case for Tulip in discrete assembly use cases. Users are walked through an assembly process, and a **Light kit** lights the bins each user needs to pick components from.

**Tulip Player**

**Tulip Player** is the Windows/Mac executable program where users can run Tulip apps. Tulip player allows you to create a more seamless user experience by removing the need for a web browser, and allows increased IT controls.

**Shop Floor**

The area of the platform responsible for moving applications into production. Under the shop floor, you can manage **Stations**, **Edge Devices,** and the app publication details such as which **Version** is accessible to users, which **Devices** are connected to the app, and which **Interface (display device)** the app is run on.

**Station**

**Stations** are a digital representation of a physical place or device in your facility. Stations are 1:1 with **Interfaces (display devices)** running Tulip Player, but Stations can also be assigned **Edge Devices,** Tulip Vision Camera Configurations, Machines, and more.

**Interface (Display Device)**

**Note:** From r283 onwards, display devices are renamed interfaces.

Users interact with Tulip applications through physical devices like touchscreens, PC monitors, mobile devices, and LCD screens. We refer to these as **display devices**. Display devices are always paired with a **station** during the application publication process.