Book a consultation

Cognex In-Sight Smart Cameras: Families, Selection and Failure Modes

In-Sight Vision Suite vs In-Sight Explorer: Which Software Runs Which Camera

In-Sight Vision Suite vs Explorer: which software runs the 2800, 3800, 3900, 8900 and the older 7000, 8000 and 9000, and what we can and cannot say.

Vladimir Romanov


Which Cognex software runs which In-Sight camera, and did In-Sight Vision Suite replace In-Sight Explorer? The cameras launched from 2022 onward are documented for In-Sight Vision Suite (the 2800, 3800 and 8900 manuals), and Cognex describes the 3900 and 6900 as using it too. The older 7000 second generation, 8000 and 9000 are documented for In-Sight Explorer. Cognex has not, in anything we could read, said that Vision Suite “replaced” Explorer, so that part is our inference from the support lists and the release history. This page sets out the evidence, the release timeline and what a plant running both toolchains should plan for. It sits under the In-Sight overview and the Cognex hub.

Which software runs which camera

Which Cognex software connects to which In-Sight camera family Three software boxes on the left and camera families on the right. In-Sight Vision Suite, releases 22.1.0 to 26.2.0, connects to the In-Sight 2800, 3800, 3900, 8900 and the 6900 controller. In-Sight Explorer, last found as version 6.5.1 from October 2024, connects to the In-Sight 9000, 8000 and 7000 second generation, and older lines. A web browser connects to the In-Sight SnAPP vision sensor with no installed software. A dashed line shows that Explorer does not list the newer cameras and that no Cognex statement of replacement was found. Software on the left, the cameras it is documented for on the right In-Sight Vision Suite Releases 22.1.0 to 26.2.0 EasyBuilder and Spreadsheet, emulator, utilities In-Sight Explorer Versions 5.x and 6.x Last found: 6.5.1, October 2024 A web browser No installed software 2800 · 3800 · 3900 · 8900 and the 6900 controller (SDKs within Vision Suite) 3800 from release 23.1.0, 8900 from 24.4.0 Edge AI tools on the newest cameras 9000 · 8000 · 7000 second generation and older lines in the firmware list Rule-based tools, spreadsheet only Covered by the 2025 CISA advisory In-Sight SnAPP Set up in the browser, per Cognex not listed Explorer 6.5.1 lists none of the 2800, 3800 or 3900. "Replaced" is our inference, not a Cognex statement.
Two toolchains cover the In-Sight range, split roughly by generation. A plant with cameras from both groups needs both installed, supported and secured.
Camera familySoftwareThe evidence
In-Sight 3800, 3800 Line ScanVision SuiteThe 3800 manual tells you to download Vision Suite and click Connect. The 3800 first appears in release 23.1.0; Line Scan in 24.4.0
In-Sight 2800Vision SuiteThe 2800 reference manual belongs to the Vision Suite 25.3 documentation set, and the 23.1.0 notes refer to the 2800
In-Sight 8900Vision SuiteThe 8900 manual states full Vision Suite support; release 24.4.0 added 8900 support
In-Sight 3900, 6900Vision SuiteA Cognex product leader told Vision Systems Design that 3900 users work with the In-Sight Vision Suite tools they know; the 6900 SDKs and APIs are described as within Vision Suite, and the 26.2.0 notes add GPU acceleration for the 6900
In-Sight SnAPPA browserCognex states it is the first of its products that does not require software for installation
In-Sight 9000, 8000, 7000 second generationExplorerExplorer 6.5.1 (October 2024) lists their firmware
In-Sight 5000, Micro, Advantage EngineExplorerAlso in the 6.5.1 firmware list
In-Sight 2000ExplorerNamed with Explorer 5.x to 6.5.1 in the CISA advisory; not in the 6.5.1 firmware list we read

What moved between the two

The first release in the history is 22.1.0, which the release history calls the initial release of the product. Cognex says in its 3800 launch release that Vision Suite is a platform shared across In-Sight products, yet Explorer’s own support list shows older products it still covers, so the two statements describe different generations. The release history shows a steady cadence of about three to four releases a year in 2024 to 2026. These are the changes most likely to affect a plant.

ReleaseWhat it added or changed
22.1.0Initial release of the product
23.1.03800 support, the In-Sight Emulator, Spreadsheet Editor on Spreadsheet-licensed cameras
24.2.0Windows 11 supported and preferred, passive FTP as the default
24.3.0Edge AI on the 3800 without an external graphics accelerator, audit logging
24.4.08900 and 3800 Line Scan support, single sign-on, CIP Sync
25.1.0System Validation, HTTPS for the browser operator screen, an Elevated access level
25.3.0MQTT connectivity, FTP and SFTP server setup from Vision Suite
26.1.0“Renamed ViDi EL tools to Edge AI tools”, EtherCAT support, OPC UA up to five simultaneous clients
26.2.0Multi-Light Hub, minimum password strength option; the one release with a dated build, 17 August 2026

One rename deserves a note. In 26.1.0 the ViDi EL tools became Edge AI tools, so older documentation, forum posts and job files use the earlier name for the same tool family. A technician searching for a feature may need to try both names.

Laptop showing a dashboard of charts on a desk beside a sunny window
Configuration software lives on a laptop, so the version on that laptop decides which cameras a technician can reach and how securely.

What a plant should plan for

These are our views, based on the support lists and the release history.

Plan for two toolchains. A plant with a 7000 on one line and a 3800 on another needs In-Sight Explorer for the first and Vision Suite for the second, and each toolchain has its own PC requirements, licensing and security position. Cognex’s 2025 advisory covers Explorer 5.x to 6.5.1 and the older families, so the Explorer PC deserves the more cautious network treatment, as described on the 2025 advisory page.

Treat a migration as a rebuild. We found no Cognex statement on converting an Explorer job to Vision Suite. The 3800 ships with converter brackets for the 7000 mounting footprints, which solves the bolt pattern and not the job. Rebuild the job, compare its results with the old camera on known good and bad parts, and revalidate. The replacing older In-Sight cameras page walks through the sequence.

Mind the firmware compatibility. According to the release history, a job re-saved on Vision Suite 24.4.0 firmware cannot be loaded on earlier firmware. A spare camera on older firmware may therefore not accept a job saved from a newer setup. Keep a record of the software and firmware version with every job backup.

Mind the PC. Windows 11 became the preferred operating system in release 24.2.0. Edge AI work in the emulator needs a Cognex security dongle, and the installer bundles the CodeMeter licence software. Check the current system requirements for your release, because the requirements page we found was written for an older release.

A migration sequence we would follow

If a plant moves a line from an Explorer-era camera to a Vision Suite camera, the order below keeps the process controlled. It is our sequence, not a Cognex procedure.

  1. Record the old job. Export the job and note the Explorer and firmware versions, the camera network settings, the trigger source, the output format the PLC reads and the light settings.
  2. Capture reference images. Collect known good and known bad parts under the existing light, so the same set can test the new job.
  3. Choose the new camera by resolution, space and plant interface, using the camera selection page, and confirm Vision Suite support in writing.
  4. Build the new job in Vision Suite, using the emulator where possible, and match the old result and handshake layout so the PLC logic changes as little as possible.
  5. Run both in parallel if the line allows, comparing pass and fail decisions and timing.
  6. Revalidate, then document the new job, its software and firmware versions, and the backup location.

Where it gets hard

  • No Cognex statement of replacement. Everything in this page about Vision Suite replacing Explorer is inference, and the plan should not rest on it without a written answer from Cognex.
  • Release dates are mostly unknown. Only 26.2.0 has a dated build in the sources we read, so we cannot say how old a given release is.
  • Camera support by release is incomplete. We could not read a full compatibility matrix, so confirm that a given camera and firmware work with the Vision Suite release you intend to install.
  • Licensing is not public. Tool packs, Edge AI per model and the Spreadsheet licence on some cameras are priced and defined by Cognex or its channel.
  • Explorer’s future is unknown. We found no 7.x release and no end-of-support notice. Ask Cognex how long it will maintain Explorer.

Related: In-Sight overview · Choosing an In-Sight camera · EasyBuilder versus Spreadsheet · Cognex hub

Frequently asked questions

What is In-Sight Vision Suite?

In-Sight Vision Suite is the Cognex PC software used to connect to, configure and back up current In-Sight cameras. It contains the two programming environments, EasyBuilder and Spreadsheet, plus utilities for network, users, time, backup and an emulator. The In-Sight 3800 reference manual tells you to download Vision Suite, connect the camera and click Connect.

Does In-Sight Vision Suite replace In-Sight Explorer?

Cognex does not say so in any text we could read, so treat it as an inference. The evidence is that the 2800, 3800 and 8900 manuals are Vision Suite documents and the 3900 is described by Cognex as using the same tools, and that In-Sight Explorer's last release we found, 6.5.1 from October 2024, lists older firmware families and none of those cameras. Ask Cognex for a written statement if your plan depends on it.

Can I program an In-Sight 3800 with In-Sight Explorer?

No, not according to the documentation. The In-Sight Explorer 6.5.1 release notes list firmware for the 7000 second generation, 8000, 9000 and older lines, and do not include the 2800, 3800 or 3900. The 3800 first appears in Vision Suite release 23.1.0, and the 3800 manual directs you to Vision Suite for connecting and programming.

Which software runs the older In-Sight 7000, 8000 and 9000?

In-Sight Explorer. Release 6.5.1 from October 2024 still lists firmware for the 7000 second generation, 8000 and 9000 families, so those cameras were still supported by Explorer in late 2024. Cognex's 2025 advisory on these lines and Explorer 5.x to 6.5.1 is a reason to keep their engineering PCs off shared networks.

Can I move an Explorer job to Vision Suite?

We could not find a Cognex statement on converting jobs between the two. Both use the spreadsheet idea, and Vision Suite builds on it, but camera families, tools and firmware differ. Treat a migration as a rebuild and revalidation of each job on the new camera until Cognex confirms otherwise, and compare results on known good and bad parts.

References and further reading

  1. In-Sight Vision Suite EasyBuilder release history · Cognex documentationEvery Vision Suite release from 22.1.0 to 26.2.0 and what each added.
  2. In-Sight Explorer 6.5.1 release notes · Cognex documentationThe supported-firmware list that defines what Explorer still covers.
  3. In-Sight 3800 Reference Manual (Vision Suite 25.3) · Cognex documentationThe connect procedure and the converter brackets for 7000 footprints.
  4. In-Sight Vision Suite 26.2.0 about page · Cognex documentationThe one release with a dated build.
  5. Cognex launches the In-Sight 3800 vision system for fast, accurate AI-based inspections · Cognex release, 10 April 2023Describes Vision Suite as a platform shared across In-Sight products.
  6. CISA advisory ICSA-25-261-06 · CISA
  7. Scalable, PC-Free AI Inspection with Cognex In-Sight 3900 · Vision Systems Design
  8. Cognex's Brian Benoit answers our questions about the In-Sight 6900 vision controller · Vision Systems DesignSDKs and APIs within In-Sight Vision Suite.

← In-Sight

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.