# Introducing glTF 2.1 with Complex Scenes

DevFeed: [Introducing glTF 2.1 with Complex Scenes](<https://devfeed.tech/articles/introducing-gltf-2-1-with-complex-scenes-15110.md>)

Original publisher: [Read original article](<https://www.khronos.org/blog/introducing-gltf-2.1-with-complex-scenes>)

Author: jphilips (jeff@khronosgroup.org)

Published: 2026-06-11T13:00:00Z

Content type: release

Language: en

Sources: [Blogs Khronos Blog](<https://devfeed.tech/sources/blogs-khronos-blog.md>)

Topics: [3D](<https://devfeed.tech/topics/3d.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Simulation](<https://devfeed.tech/topics/simulation.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [announce](<https://devfeed.tech/tags/announce.md>), [api](<https://devfeed.tech/tags/api.md>), [blog-glt](<https://devfeed.tech/tags/blog-glt.md>), [gltf](<https://devfeed.tech/tags/gltf.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [release](<https://devfeed.tech/tags/release.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

The Khronos 3D Formats Working Group announces plans for glTF 2.1, a focused and backward-compatible revision designed to support large, composed scenes. Proposed capabilities include multi-file scene graphs, spatial primitives, stable object IDs, progressive 3D streaming support, larger GLB files, and a formally deprecated multiple-scenes pattern.

## Source excerpt

Since the release of glTF™ 2.0 in 2017, the format has matured into a rich ecosystem spanning mesh compression, texture optimization, 3D Gaussian splats, and more. Today, the Khronos® 3D Formats Working Group is excited to announce plans for glTF 2.1: a focused, backward-compatible revision of the core specification, built around a single motivation -- making glTF work as well for large, composed scenes as it already does for single assets. Every feature in this release addresses a real gap that today forces teams toward proprietary conventions, custom tooling, or workarounds that break interoperability.