Skip to content

Orbbec SDK v2

  • Software
  • Perception
  • Driver or SDK

An open-source cross-platform C/C++ SDK for interfacing with Orbbec RGB-D cameras, with wrappers for other languages and frameworks. It is the successor to Orbbec SDK v1.

Made by Orbbec, United States (checked on github.com/orbbec (opens in a new tab)).

Source on GitHub: github.com/orbbec/OrbbecSDK_v2 (opens in a new tab). Facts read at commit 85e94c4 (opens in a new tab).

Licenses

Code
LGPL-2.1-only (opens in a new tab)

Read by Robotheca from LICENSE.txt (opens in a new tab) (LGPL-2.1-only) at commit 85e94c4 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

Copyleft: Modified source must be published.

What it does

  • Provides C/C++ APIs for Orbbec RGB-D cameras and LiDAR devices, plus wrappers for other languages and frameworks.
  • Includes the Orbbec Viewer GUI for stream preview, camera configuration, post-processing and firmware updates.
  • Supports Windows 10 or later, Linux x64 and ARM64, Android 13 and macOS.
  • Offers a LingBot Enhanced Depth Filter that uses color and depth to reduce noise and fill holes, on NVIDIA Jetson with JetPack 6.2.
  • Provides a DepthQualityTool to evaluate depth accuracy, spatial and temporal precision, and fill rate.
  • Includes a QuickStart example that starts a pipeline and shows frames in a window.

Written by Robotheca from the project's README (opens in a new tab) at commit 85e94c4.

Getting started

Difficulty
Intermediate
Hardware it needs, as the project states it
Supported platforms: Windows 10 or later (x86 and x64); Linux x64 tested on Ubuntu 20.04, 22.04 and 24.04; Linux ARM64 tested on NVIDIA Jetson AGX Orin, Orin NX, Orin Nano, AGX Xavier, Xavier NX and Jetson Thor; Android tested on Android 13; macOS tested on M2 chip, OS version 13.2.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
8 Oct 2026 on main
Latest release
Release v2.10.6 (30 Sept 2026)

Checked on GitHub on 16 Oct 2026.

Robots on Robotheca that use it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.