Supported platforms
This is the compatibility surface for the current release. If your project sits outside it, Loom may not render or may fall back to a slower path.
Game engine
- Unity 6 (
6000.3or newer). Earlier Unity versions are not supported. - Other engines (Unreal, Godot) are on the roadmap but do not ship today.
Operating systems
Loom runs in the Editor and in standalone player builds on:
| OS | Status |
|---|---|
| Windows (x64) | Supported |
| macOS (Apple Silicon + Intel) | Supported |
| Linux | Not supported yet |
| Mobile / consoles / WebGL | Not supported |
The native engine ships as a prebuilt binary for each supported OS inside the Unity package, there’s nothing to compile.
Render pipeline
- URP (Universal Render Pipeline) only.
- The Built-in Render Pipeline is not supported, and neither is HDRP.
Loom composites its UI surface through a render-pipeline hook that only the Scriptable Render Pipeline provides. A Built-in or HDRP project will not display the UI.
Graphics API
Loom hands its rendered UI to Unity as a shared GPU texture, so the project’s graphics API has to be one Loom can share with:
| OS | Required graphics API |
|---|---|
| Windows | Direct3D11 or Direct3D12 |
| macOS | Metal |
On Windows, set this under Player Settings -> Graphics APIs for Windows. If the project runs under Vulkan or OpenGL, the zero-copy handoff isn’t available and the UI will not appear. Switch the graphics API to Direct3D11 (the Unity default) or Direct3D12.
Tooling (development only)
- Node.js 20+ on the machine running the Editor. Loom uses it to install your UI’s dependencies and run the dev server. Node is not required in shipped player builds, the UI is pre-built and bundled.
- Firefox is optional, used only for inspecting the live UI via
Loom -> Open Browser DevTools.
Checking your setup
Run Loom -> Doctor (or open Loom -> Status Window) to verify Node, the
native plugin for your platform, the dev server, and the generated types in
one place. See the Doctor reference.