How to Get 67,000 Free 3D Assets Into Your Godot XR Project, and Where the Pipeline Still Breaks

Blendkit is a 3D asset library with a Blender add-on bolted to the front, and for most of its life that was the whole description. Roughly 22,000 free models. Another 36,000 free materials, 4,000 free HDRIs and 1,000 free brushes, all cleared for commercial work. At the end of July the company, formerly BlenderKit and renamed this year, published plugins for Maya, Rhino and Godot. The Godot one is why anyone building for headsets should look.

Godot stopped being the promising XR option this year and became a real one. Version 4.7 shipped production-ready support for Valve's Steam Frame and Android XR, which we covered in July, and the OpenXR vendors plugin had already sorted out the per-headset extensions before that. So the engine side is close to handled. The content side is not, and if you have ever started a solo Godot XR project you know exactly what that feels like: working OpenXR rig, hand tracking, comfortable locomotion, and a gray box room, because modelling a single convincing coffee cup eats an afternoon you did not budget.

That gap is what this plugin is aimed at.

Getting it into your project

The plugin is free and open source under GPLv2, and it lives at BlenderKit/bk_godot on GitHub. On Godot 4.7 or newer, open the built-in Asset Store tab, search Blendkit, press Download. On older 4.x builds, pull the zip from the Godot Asset Store listing or from GitHub Releases and unzip it into your project folder. Note that second word. The plugin installs per project rather than once per machine, so every new prototype means doing this again.

Next, Project, then Project Settings, then the Plugins tab, then tick Enabled next to Blendkit. A Blendkit tab shows up in the right dock beside the Inspector, though you may have to walk the little arrow buttons in the top right to reach it. Green checkmark and the word Connected means the editor is talking to the local Blendkit Client and you are finished setting up.

Actually using it takes one click. Browse the gallery in your web browser, open any asset page, hit Get this model, and a Send to Godot button turns up shortly after. The file drops into a bk_assets/ folder in your project root, sorted by type. From there it is yours to reorganize, and the README explicitly invites you to build your own pipeline on top of that drop point rather than treating it as the finished workflow.

Where it breaks

Blendkit's own documentation calls the Send to Godot button "fickle and elusive," which is unusually honest for a vendor describing its own feature. The browser or the OS can block the plugin's connection to the local client for security reasons. In Chromium-based browsers you need to grant Apps on Device permission, sometimes after reloading the page a few times before the prompt even appears. Their guidance is that Firefox has worked on every OS they have tried.

The deeper problem sits downstream of the plugin. Godot imports .blend files by handing them to a Blender installation on your machine, which means an asset library full of .blend files inherits every rough edge of that handoff. The repo's README says plainly that many .blend files import incorrectly or not at all, with a generous run of warnings in the Output panel. It also names a specific version trap: as of Godot 4.5.1 the importer wants Blender 3, and Blender 5 has been shipping for some time now. Version 0.4.0 of the plugin added an option to prefer GLTF (.glb and .gltf) over the original .blend file, which skips Blender entirely when a GLTF export exists. The README rates those auto-exports as "by no means perfect" and says they "might occassionally work," their spelling.

Mac users are shut out for now. The plugin covers Linux and Windows on x86_64 and arm64, and the team lists macOS as not working yet because of code signing, with a fix planned.

So is it worth your afternoon?

Calibrate against the version number. The current release is v0.6.1, published on 1 July, and its whole changelog is one fix for a harmless invalid UID warning at startup. The project labels itself alpha and experimental in its own README. The plugins were announced on Blendkit's news blog on 31 July and the trade coverage that surfaced in mid-August was catching up to that post, not reporting anything newer.

Early does not mean pointless, though. A solo developer blocking out an XR scene needs placeholder geometry that looks like a chair instead of a cube, and 67,000 free assets reachable from a dock panel is a materially better starting position than a browser tab and a downloads folder. Prefer the GLTF option where it exists, keep Blender 3 around if you are going to lean on .blend imports, and expect to file an issue or two. The repo is small and the maintainers are asking for exactly that. Open source tooling gets good because early users write down what broke, and this one is early enough that your bug report will actually change it.