# Khronos glTF-Blender-IO for Blender 5.x

> KhronosGroup/glTF-Blender-IO is the official Blender add-on for importing and exporting glTF 2.0 scenes. It is already included with Blender 2.80 and later, while this repository is most relevant to development, debugging, or testing against a selected Blender release branch.

**KhronosGroup/glTF-Blender-IO** — Blender glTF 2.0 importer and exporter

- Repository: https://github.com/KhronosGroup/glTF-Blender-IO
- Website: https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.html
- Stars: 1,666 · Forks: 360
- Language: Python
- License: Apache-2.0
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/khronosgroup-gltf-blender-io

## The glTF 2.0 bridge inside Blender

KhronosGroup/glTF-Blender-IO solves a format boundary problem: Blender stores scene information in its own internal representation, while glTF 2.0 uses a portable JSON scene format and associated binary or texture resources. The project is for Blender users who need to bring glTF assets into Blender, send Blender scenes to systems that consume glTF, or repeat those operations in asset-production workflows. It is also aimed at developers who extend the Blender add-on or reuse its Python implementation in other packages.

The repository identifies itself as the official Khronos Group importer and exporter. Its README also states that it contains the features of the previous exporter and makes this repository the location for future development. The intended scope is broader than a one-way Blender plug-in. Common code is shared by the importer and exporter specifically to support round-trip work, where a scene may pass from Blender to glTF and back into Blender.

## Why the Python scene representation sits in the middle

The central architectural choice is a Blender-independent Python representation of a glTF scene. For export, Blender scene data is extracted and converted into this representation. The resulting glTF scene description is then written as JSON, while mesh, animation, and texture compression occurs at this stage.

Import reverses the flow. The add-on parses glTF data, writes it into the same Python scene representation, performs decompression where needed, and then generates Blender's internal scene tree from that information. This separation keeps format-specific operations away from direct manipulation of Blender scene objects. It also creates a package boundary that can be reused by third-party Python packages.

That design is useful when an asset must make several conversions without treating glTF as a thin wrapper over Blender data. It does not mean that every Blender export can be reproduced without loss, however. The README describes the conversion path but does not claim lossless parity for every Blender feature.

## Choosing the correct release line in the repository

The default `main` branch is not presented as the branch a Blender user should install indiscriminately. The README says that `main` is mirrored in Blender's main source tree and will become Blender 5.2. For stable work, it directs users to release branches: `blender-v5.0-release` for the current stable release, `blender-v5.1-release` for the next stable release, and `blender-v4.5-release` for the current LTS line.

That distinction matters because this repository tracks Blender's built-in add-on across changing releases. Selecting `main` while running Blender 5.0 could place code from another compatibility target into the installation. The repository is therefore most useful to contributors who understand the mapping between Blender versions, branches, and bundled add-on directories.

For ordinary users, using the add-on already shipped with the installed Blender version is the lower-risk path. The repository is the development home for that component, not necessarily an extension to install over every Blender installation.

## Enabling the importer and exporter in Blender

For Blender 2.80 and higher, no third-party installation is required because the add-on is bundled in Blender's main installation package. If someone needs to reinstall a development or testing copy, the README gives a manual procedure. Copy the `addons/io_scene_gltf2` folder into the Blender installation's `scripts/addons_core/` directory, then enable it under the *Add-ons* tab.

The folder copy is an operation on a local Blender installation, so its path depends on where Blender was installed. The README does not provide a platform-specific command or package-manager installation, so there is no safe shell command to reproduce here. It also does not document the exact import and export menu locations for a first scene operation.

A practical first check is therefore limited to what is documented: confirm that the add-on is enabled in Blender, locate the existing glTF import and export interface in that Blender release, and use a representative project containing the materials or animations that the pipeline must preserve. Exact menu names should be checked in the Blender manual for the installed version.

## Running the repository's validation and round-trip tests

The repository gives a concrete local verification path for contributors. A `blender` executable for the desired Blender version must be available in the path, and the latest Yarn must be installed. From the `tests` directory, dependency installation and test execution use the following documented commands:

```bash
yarn install
yarn run test
```

The first command installs the test dependencies in the tests environment. The second runs the test suite through the repository's configured Yarn workflow. The README does not describe the console output for a successful run, so a successful result should be identified from the command's exit status and any suite output produced by that checkout.

This is a development test rather than a tutorial for exporting a particular Blender scene. It becomes most useful when paired with the documented CI checks: exported output is validated with Khronos' glTF Validator, and a round-trip import and export is compared using validator results.

## What CI validates and what remains scene-specific

Continuous integration runs after each commit or pull request. According to the README, one test exports a Blender scene and validates it with the glTF Validator. A second performs a round trip through import and export, then compares glTF Validator results. These checks target file validity and the effect of a complete scene conversion, rather than merely checking that Python can be imported.

This approach gives contributors a defined quality gate, but it does not replace inspection of a production asset. The repository documentation does not list every supported Blender feature, enumerate unsupported combinations, or promise that visual appearance survives every conversion. It also does not provide a compatibility matrix for drivers, render settings, constraints, or proprietary Blender extensions.

For that reason, validator success should not be confused with complete preservation of intent. A pipeline owner still needs a scene that contains the relevant mesh data, materials, animations, and textures, then must compare the generated result with the expected deliverable. The CI process can catch malformed glTF output, but the source does not claim that it proves visual equivalence for every asset.

## Repository scope, maintenance record, and licensing

The repository is not archived, and its last push was on 2026-10-15. That status records recent repository activity, but users should still choose a branch aligned with their Blender release. The only listed release is version 2.79, identified as the last version compatible with Blender 2.79 and dated 2020-02-20. Its dedicated release page provides the legacy add-on; current users are directed to the versioned branches instead.

Maintenance cost differs by role. A normal Blender user receives a bundled add-on and normally avoids Python package installation. A contributor may need to switch branches as Blender releases change, keep the add-on directory aligned with the target Blender source, run Yarn-based tests, and diagnose differences with the selected Blender version. The repository also points contributors to `DEBUGGING.md`, `Technical.md`, and the versioned Blender documentation.

The project uses the Apache-2.0 license. That identifier permits reuse under the license's terms, including reuse of its shared Python code in other packages, but this review does not interpret the license text or provide legal advice. Review `LICENSE.txt` and preserve its notices when redistributing code.

## Conclusion

Artists and pipeline engineers should use the copy bundled with their Blender release because it requires no separate installation and follows that release's compatibility line. Contributors should adopt this repository only when they need its development branches, tests, or debugging files. Before changing a production pipeline, first verify that the selected branch matches the installed Blender version, run the documented test command, and inspect the glTF Validator results for the actual scene.

## FAQ

### Does Blender already include KhronosGroup/glTF-Blender-IO?

Yes. Blender 2.80 and higher bundle the glTF importer and exporter in the main installation package, so a separate third-party installation is not required.

### Which KhronosGroup/glTF-Blender-IO branch should I use?

The README identifies `blender-v5.0-release` for the current stable release, `blender-v5.1-release` for the next stable release, and `blender-v4.5-release` for the current LTS line. The default `main` branch is mirrored toward Blender 5.2.

### How do I test KhronosGroup/glTF-Blender-IO locally?

Put the desired `blender` executable in the path, install the latest Yarn, and run `yarn install` followed by `yarn run test` from the `tests` directory. The associated CI validates exports and checks import-export round trips with the glTF Validator.

## Sources

- [KhronosGroup/glTF-Blender-IO on GitHub](https://github.com/KhronosGroup/glTF-Blender-IO)
- [License: Apache-2.0](https://github.com/KhronosGroup/glTF-Blender-IO/blob/main/LICENSE)
- [Project website](https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.html)
- [README](https://github.com/KhronosGroup/glTF-Blender-IO/blob/main/README.md)
- [Releases](https://github.com/KhronosGroup/glTF-Blender-IO/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/khronosgroup-gltf-blender-io