Godot visionOS Plugins - Apple GitHub XR Playbook for Indies - 2026

visionOS 27 landed at WWDC26 with a surprise for Godot teams: Apple published first-party, open-source Godot plugins on GitHub instead of burying spatial tooling inside Xcode-only samples. The apple/plugins-for-godot repository ships GodotRealityKit (windows and volumes in shared space) and PHASE spatial audio, while Apple's platform docs document CompositorServices for fully immersive rendering and PSVR2 Sense controller support on visionOS.

That is not a vague "XR is the future" keynote line. It is a July 2026 shipping surface for teams already publishing Godot titles on Steam and itch who want a honest answer to: Can we evaluate Vision Pro without rewriting the whole game in SwiftUI?

This playbook gives you a beginner evening path, developer gates V1–V6, a renderer picker table, and godot_visionos_plugins_receipt_v1.json so Monday standup does not turn WWDC enthusiasm into an unowned Vision Pro promise.

Official anchors: What's New in visionOS — Game Engine updates, WWDC26 visionOS session, and apple/plugins-for-godot on GitHub.

Who this is for: indie developers, XR-curious creators, and small-studio leads deciding whether Apple spatial distribution belongs on the 2026 roadmap.

What you get: plain-language plugin map, RealityKit vs CompositorServices decision table, beginner setup steps, verification gates, and a receipt JSON.

Time: about 90–120 minutes for notes + picker + throwaway export smoke on a Mac with Xcode; add device lab time if you have Vision Pro hardware.

Why this matters now (what WWDC26 changed for Godot)

Three signals matter for indies this month:

1. First-party Godot plugins are public — Apple's plugins-for-godot repo (June 2026) documents GodotRealityKit and PHASE with MIT licensing and contributor guidelines. That is a different posture than community bridges that drift when Apple ships new spatial APIs.
2. visionOS 27 expands engine parity — Apple's Game Engine updates page names CompositorServices for Godot immersive experiences, RealityKit rendering for windows and volumes, PHASE spatial audio, and PSVR2 Sense controller spatial accessories — the same accessory story Unity PolySpatial teams already track.
3. Godot shipping volume is real — Godot 4.7 release notes cite 700+ new Godot games on Steam in 2026 before mid-year. Spatial plugins lower the evaluation cost for teams that already ship 2D/3D Godot builds and hear "what about Vision Pro?" from partners.

If you just finished GodotCon Boston Android XR playbook week, treat visionOS as a separate Apple diligence track — not a checkbox on the Quest matrix. Android XR lab time does not automatically transfer to Xcode signing, spatial personas, or App Store spatial review habits.

Pair platform risk framing with Apple Vision Pro year-one review for game developers before you model revenue. Pair export hygiene with Godot 4.7 upgrade lock so your stable Godot pin stays honest while you spike Vision Pro.

What Apple's Godot visionOS plugins actually include

Apple's repository documents two plugins today:

Apple's platform docs add a third path that is not the same plugin zip:

The GodotRealityKit README compares capabilities across RealityKit, CompositorServices, and monoscopic Metal — use that table as your renderer picker, not marketing adjectives.

Plain-language summary: most of your game (scripts, animation, simulation) still runs in Godot. What changes is who renders pixels and how the app presents (window vs volume vs immersive).

Renderer picker — Keep / Hold / Rewrite

Company diligence note: Vision Pro evaluation is lab capability until a named owner, device calendar, and receipt exist. Model support hours separately — XR support cost forecasting applies to Apple spatial work too.

Beginner path — evaluate Godot visionOS plugins in one evening

Prerequisites

• Godot project copy on a Git branch (never spike on main).
• Mac with Xcode and Apple developer account access for signing smoke.
• Clone or submodule apple/plugins-for-godot into a third_party/ or addons/ path your team documents.
• About 90–120 minutes without device; add 60+ minutes if you have Vision Pro hardware.

If export presets are rusty, skim Godot export presets lesson and Godot scene management.

Step 1 — Pick your presentation mode (15 minutes)

Answer one sentence: Are we testing shared-space volumes, or fully immersive gameplay?

• Volumes / windows → start with GodotRealityKit README Adding the Plugin.
• Fully immersive → read Apple's CompositorServices notes on visionOS what's new before you assume RealityKit covers your scene.

Write the answer in your receipt — ambiguous scope is how teams promise Vision Pro at a festival and deliver a flat iPad build.

Step 2 — Add the plugin to a throwaway scene (30 minutes)

1. Follow Apple's AddingPlugin doc for GodotRealityKit.
2. Open a single-scene test (menu + one gameplay room — not your production overworld).
3. Confirm the project still opens on desktop Godot after plugin import.
4. Note Godot version + plugin commit hash in the receipt.

Step 3 — Run PHASE audio smoke (optional, 15 minutes)

If your game already ships Mac/iOS audio:

1. Open phasegodot README.
2. Play one known SFX through PHASE on Mac build.
3. Log pass/fail — do not block Vision Pro renderer spike on audio if flat platforms are already red.

Step 4 — Export and launch smoke (30–45 minutes)

1. Configure visionOS export in Xcode per Apple docs.
2. Launch on simulator minimum; device preferred.
3. Capture one screenshot or screen recording for the receipt.
4. Stop — do not merge to main until gates pass.

Step 5 — File the receipt (10 minutes)

Complete godot_visionos_plugins_receipt_v1.json below and assign an owner for revisit date.

Developer verification gates (V1–V6)

Set "result": "pass" only when V1–V6 are honestly true — a simulator screenshot alone does not justify a store listing date.

Receipt template — godot_visionos_plugins_receipt_v1.json

{
  "receipt": "godot_visionos_plugins_receipt_v1",
  "godot_version": "4.7.1",
  "plugin_repo": "https://github.com/apple/plugins-for-godot",
  "plugin_commit": "abc1234",
  "presentation_mode": "realitykit_volume",
  "compositor_services": "hold",
  "phase_audio": "pass",
  "psvr2_sense": "out",
  "simulator_smoke": "pass",
  "device_smoke": "hold",
  "xr_matrix_note": "visionOS lab only; Quest matrix unchanged",
  "gates": {
    "V1_scope": true,
    "V2_version_pin": true,
    "V3_renderer_smoke": true,
    "V4_input_map": true,
    "V5_audio": true,
    "V6_receipt": true
  },
  "result": "pass",
  "operator": "session-owner-handle",
  "revisit_date": "2026-08-15"
}

How this differs from GodotVision and older bridges

Community project GodotVision documented a headless Godot + RealityKit frontend pattern and is moving to archive mode as native visionOS support lands in upstream Godot. Apple's 2026 plugins are first-party, versioned on GitHub, and aligned with WWDC26 platform docs.

Do not confuse this with "Godot natively owns every visionOS feature today." Apple's docs still position RealityKit and SwiftUI as the deepest integration path. The plugins are how Godot-first teams evaluate Vision Pro without rewriting the entire game loop in Swift.

Common mistakes

1. Skipping the renderer picker — RealityKit volumes and CompositorServices immersive solve different problems; mixing them mid-sprint creates orphan scenes.
2. Promising Vision Pro because WWDC slides looked easy — signing, privacy, and spatial review still cost calendar time.
3. Collapsing Quest lab work into visionOS — keep separate matrices; see GodotCon Boston XR playbook.
4. Spiking on production main — plugin import and export templates belong on throwaway branches.
5. Ignoring flat Godot export health — if desktop/macOS export is red, Vision Pro will not save you.
6. Marketing "spatial audio" without PHASE smoke — PHASE is powerful; unverified audio claims fail partner diligence.

Key takeaways

1. Apple shipped open-source Godot visionOS plugins on GitHub in June 2026 — GodotRealityKit + PHASE.
2. visionOS 27 documents CompositorServices immersive rendering and PSVR2 Sense accessories for Godot teams.
3. Pick RealityKit plugin for shared-space windows/volumes; use CompositorServices for fully immersive Godot rendering.
4. Run the one-evening beginner path on a branch — not production main.
5. Prove gates V1–V6 before external Vision Pro promises.
6. Keep Quest/Android XR and visionOS on separate diligence tracks with separate receipts.
7. File godot_visionos_plugins_receipt_v1.json with version pin, plugin commit, and revisit date.
8. Model lab cost honestly — Vision Pro evaluation is not free because the engine is MIT-licensed.

Frequently asked questions

What are the Godot visionOS plugins Apple released?

Apple's apple/plugins-for-godot repository includes GodotRealityKit (RealityKit rendering for windows, volumes, and immersive modes) and PHASE for Godot (spatial audio on Apple platforms including visionOS).

Should I use GodotRealityKit or CompositorServices?

Use GodotRealityKit when you want RealityKit to render shared-space windows or volumes while game logic stays in Godot. Use CompositorServices when you need fully immersive experiences with Godot's Metal renderer in an ImmersiveSpace. Apple's GodotRealityKit README includes a capability comparison table.

Do I need a Vision Pro to start?

No. Begin with README integration, desktop validation, and simulator smoke where possible. Device tests still matter before store claims — assign lab time explicitly.

How is this different from the GodotCon Boston XR article?

The GodotCon Boston playbook covers Android XR, headset editor, and GABE conference-week decisions. This article covers Apple's first-party Godot visionOS plugins and Vision Pro evaluation gates.

Does visionOS replace my Steam-first Godot roadmap?

Not automatically. Treat Vision Pro as an optional distribution spike until receipts, cost, and audience data justify a SKU. Many teams stay Steam-first while documenting an honest Hold on visionOS.

Where do I learn Godot export basics first?

Start with Godot export presets and the Godot guide hub before you add spatial plugins.

Related reads

• GodotCon Boston July 2026 - Android XR and Headset Editor Playbook for Indies
• Godot 4.7 Upgrade Lock - HDR AreaLight3D and Asset Store Before Ship 2026
• Apple Vision Pro Year-One Review for Game Developers
• WWDC 2026 Game Porting Toolkit Mac Indies Checklist
• XR Support Cost Forecasting for Indie Teams
• Godot export presets lesson

Conclusion

WWDC26 did not magically make Vision Pro a mandatory 2026 SKU for every Godot studio. It did make evaluation more honest: first-party plugins on GitHub, a clear renderer picker, and platform docs that name CompositorServices, PHASE, and spatial accessories. Run a bounded evening spike, pass gates V1–V6, file the receipt, and keep external promises aligned with what you actually launched on device.