Loom renders the @rbxts/react or vide UI you ship to Roblox in a browser. Layout follows
Roblox’s rules, not CSS’s: UIListLayout, UIPadding, AutomaticSize, UISizeConstraint and text
measurement run in a Rust layout engine compiled to WASM. Clicks, typing and hover reach your code
through UserInputService and instance signals, so a preview is interactive.
Run it on a roblox-ts project with no setup:
pnpm exec loom preview .Or add one plugin to your own Vite config:
import { loomPreview } from "@loom-dev/preview/vite";import { defineConfig } from "vite";
export default defineConfig({ plugins: [loomPreview()] });The plugin generates the page, installs the Roblox globals (UDim2, Color3, Enum, game) and
the Luau standard library, and points @rbxts/* imports at browser versions. There is no
rbxtsc step: esbuild transpiles your TSX, and HMR works.
Start with Installation.
import { loomPreview } from "@loom-dev/preview/vite";import { defineConfig } from "vite";
// Aliases @rbxts/react, @rbxts/react-roblox and @rbxts/services onto the// loom adapters, installs the Roblox globals, and sets the automatic JSX// runtime — a roblox-ts source tree then runs unmodified in the browser.export default defineConfig({ plugins: [loomPreview()],});Guides
Wire it into a project.
Reference
Every flag, alias, and export.
A preview tool, not a runtime.
Nothing loom produces ships to Roblox. It renders your UI tree in a browser so you can iterate without a Studio round-trip, and its fidelity is deliberately partial — UIScale, UIPageLayout and UITableLayout are not implemented. Read the scope before you trust a preview as ground truth.