SoftwareJune 10, 2026

Apple Just Put Its visionOS Engine Tools on GitHub. Yes, Including Godot.

By Nina Castillo
Staff Writer, VR.org
Share

Apple does not open-source things. That is the reputation, anyway: a company that builds the whole stack, ships it sealed, and asks you to develop the Apple way or not at all. So the most surprising part of the entire visionOS 27 developer story was not a feature. It was a GitHub link. Apple is shipping its new spatial engine plugins as open source, and the list of supported engines includes Godot, the scrappy community-built engine Apple has no commercial reason to care about.

Advertisement

I wrote earlier about how visionOS 27 quietly opened Safari to the spatial web. That was the browser half of the story. This is the native half, and it is just as out of character for Apple.

Apple Vision Pro on a display stand inside an Apple Store
Image: Wikimedia Commons

What Apple Actually Shipped

visionOS 27 adds new spatial plugins across the three engines most developers actually use, and Apple is distributing them on GitHub instead of burying them inside its own toolchain. Unity PolySpatial, Unreal Engine, and Godot all pick up the same set: a spatial controller plugin for the new tracked-accessory input model, an ARKit plugin so engine-side code can reach Apple's world and object tracking, and a PHASE plugin for spatial audio. There is also support for custom rendering engines through CompositorServices, which means a studio running its own in-house engine is no longer locked out of Vision Pro.

For Godot specifically, the support runs deeper than a token gesture. It gets CompositorServices for fully immersive rendering, a RealityKit plugin for windows and volumes in the shared space, the PHASE audio plugin, and even support for PlayStation VR2 Sense controllers. That is a real spatial pipeline, not a checkbox.

The Godot Part Is the Real Tell

The Godot inclusion is what made me read the slide twice. Godot is the fully open-source, community-governed engine that has become home to indie developers who do not want to pay Unity's runtime fees or live inside Unreal's ecosystem. Apple officially supporting it, with first-party plugins on a public repository, is the kind of olive branch to the open-source world that Apple almost never extends. It says Apple cares more about getting spatial content built than about funneling every developer through RealityKit and Swift.

Godot game engine logo
Image: Godot Engine / Wikimedia Commons

This is not the first sign of Apple inching toward Godot. The engine has been quietly turning into the best open-source XR engine going, and the platform holders have noticed. What changed at WWDC is that the support is now official, shipped, and public.

Why Open Plugins Matter

Here is the thing about engine plugins on GitHub: they are forkable. When Apple ships a Godot spatial plugin to a public repo, the community can read it, extend it, file issues against it, and adapt it for cases Apple never imagined. That is a fundamentally different relationship than a closed SDK you can only consume exactly as delivered. It invites the same community iteration that has pushed the open spatial web forward faster than any single company could manage alone.

Colorful syntax-highlighted source code on a dark screen, representing the open plugins Apple published on GitHub
Image: Wikimedia Commons

It also lowers the barrier for exactly the developers Vision Pro needs most. The platform does not have a content gap because the hardware is bad. It has a content gap because building for it has been expensive and tied to Apple's native stack. Meeting Unity, Unreal, and Godot developers where they already work, with open plugins they can drop into an existing project, is how you get more apps from people who were never going to rewrite their pipeline from scratch.

The Quiet Pattern

Step back and a pattern shows up across the whole industry this year. Meta has been putting agentic developer tools and open web SDKs on GitHub, and Google built its vibe-coding XR experiments on an open framework. Now Apple, the most famously closed of the three, is publishing spatial engine plugins and officially backing a community engine. The platform holders have all worked out the same thing: the real constraint on spatial computing is not hardware, and it is not even users. It is the number of developers who can realistically ship something good, and the fastest way to grow that number is to stop making them fight your tools.

visionOS 27 is in developer beta now and ships this fall. The plugins are on GitHub today. If you have been curious about building for Vision Pro from Unity, Unreal, or Godot, this is the most open that door has ever been.

Share
Advertisement