Isaac Sim 7 libraries#

Isaac Sim 7 is the next generation of Isaac Sim, with simulation capabilities delivered as independently installable C, C++, and Python libraries for building simulation tools and robotics workflows.

Applications, services, and agents can install and compose only the capabilities required for a task. To start exploring the features and capabilities in the current release, see the overview.

The libraries organize simulation capabilities into focused distributions that you can install, combine, and deploy independently. Start with a Kit-independent physics program, add rendering and sensors as needed, distribute services across processes or machines, or compose the complete Isaac Sim application.

The library inventory lists the available capabilities. The roadmap describes planned capability areas; package names and APIs can change during the alpha period.

Key terms#

The library documentation uses the following terms:

  • Isaac Sim libraries are the focused, independently installable packages that provide Isaac Sim capabilities.

  • Omniverse libraries, sometimes shortened to OV libraries, are low-level, standalone runtime components used by the Isaac Sim libraries. For example, OVStage provides scene access, the physics engine libraries provide implementations such as PhysX.

  • OV SIM is a common client API for scene authoring, simulation control, and data access. It lets the same orchestration code use an in-process implementation or connect to a remote simulation service. See Direct library APIs and the OV SIM API.

Why the architecture is changing#

Kit-based Isaac Sim releases provide complete workflows for scene authoring and robot rigging, synthetic data generation (SDG), and software-in-the-loop (SIL) testing. Delivering these workflows through a full application provides an integrated experience, but makes it difficult to embed one simulation capability or build a smaller, purpose-specific runtime.

Isaac Sim 7 disaggregates these capabilities into libraries so applications, services, and agents can use them outside the full application and combine them into deployments of different sizes. The architecture changes how Isaac Sim is packaged and deployed, not the scope of the complete product. All capabilities of prior Kit-based Isaac Sim releases will be possible in the complete Isaac Sim 7 experience.

Each alpha adds capabilities to the libraries and the application. A workflow that is absent from an early alpha is scheduled for a later milestone rather than removed from the final product experience.

The architectural shift#

Kit-based Isaac Sim releases deliver capabilities through an application and its extensions. Isaac Sim 7 moves reusable runtime capabilities into independently packaged libraries with public C, C++, and Python APIs.

This shift provides the following benefits:

  • Lightweight workflows: Install only the distributions required by your workflow. A smaller runtime can start faster, use fewer resources, and shorten iteration cycles.

  • Scalable deployment: Start with an in-process library, then use the same capabilities across processes or machines as the workload grows.

  • Greater control: Select dependencies and providers explicitly. This makes behavior easier to inspect and reduces side effects from unrelated extensions.

  • Backend integration: Embed simulation capabilities into an existing application or service without starting a Kit application.

  • Agent-native composition: Give software agents typed APIs, focused packages, and runnable examples that they can discover, call, and combine. An agent can compose a minimal runtime for a simulation task instead of operating a full user interface.

  • Backend-neutral APIs: Write simulation logic against common APIs while implementations provide engines such as PhysX and Newton.

  • Complete product composition: Build the full Isaac Sim experience from the same libraries used by embedded, headless, and distributed deployments.

The libraries do not replace Isaac Lab. Isaac Lab remains the framework for robot learning workflows and can consume Isaac Sim capabilities as the platform develops.

Compatibility and migration#

The move from Kit extensions to standalone libraries requires API changes, so existing Kit-based integrations will not always be source-compatible with Isaac Sim 7. Migration guides and agentic skills will be provided as workflows become available. These resources will map established workflows to the new libraries and give coding agents task-focused instructions for automating common migration tasks.

You do not need to move an established workflow to an incomplete alpha release. Continue to use the supported Isaac Sim release when you need the complete production feature set, and evaluate the alpha milestones as the capabilities relevant to you become available. Package boundaries and APIs can also change between alpha milestones.

Choose a starting point#

  • Start with Overview to explore the current alpha release and its available capabilities.

  • Follow Install and run to build the libraries, install a package, or run an example.

  • Use Tutorials for guided workflows.

  • Browse Libraries for API documentation or the Example catalog for runnable reference implementations.