Playground
Compile and share snippets without installing anything.
Playground
The playground is a runnable companion to these docs. Write a snippet in roblox-ts or in Luau, press Run, and the output appears in the pane beside it.
Choosing a language
Two options sit above the editor, and they are genuinely different entry points rather than a cosmetic toggle:
| roblox-ts | Luau | |
|---|---|---|
| What you write | TypeScript | Luau |
| Compilation | the real roblox-ts compiler, in your browser | none |
| What the sandbox runs | the Luau it produced | exactly what you wrote |
Switching languages keeps both buffers, so you can flip between the two versions of an idea without losing either.
How a run works
- Compile, in your tab. In roblox-ts mode the real
roblox-tscompiler turns your TypeScript into Luau through its in-memory project — the same code path the CLI uses. If it does not compile, nothing runs, and the diagnostics appear in the output pane instead. - Execute, on MicroStudio. The Luau is sent to the sandbox and run by the
actual MicroStudio runtime, not a simulation of it.
Instance.new,game,workspace,task, the service layer and the datatypes are all real, and they behave as they do on the server.
What comes back is stdout, stderr, the exit code and how long it took — the same information the CLI gives you locally. The Luau tab beside the output shows the exact source the sandbox received.
What the sandbox does not give you
- No network access. A snippet cannot reach the internet, so
HttpServicerequests to real hosts will not work here. - No persistence between runs. Each run gets its own DataModel and its own scratch directory.
- A time limit. Anything still running when the limit expires is killed,
which mostly matters for a snippet that never returns, such as a bare
while true do end.
The runtime does not flush buffered output when it is killed, so a snippet that is stopped mid-flight may show nothing even though it printed earlier. Prefer snippets that finish on their own.
Sharing a snippet
Share produces a link carrying both the source and the language, so the other person sees exactly what you saw — no install, no sign-up. That makes the playground a convenient way to put a runnable MicroStudio example in a bug report or a chat message.
Playground or microstudio?
| Playground | microstudio | |
|---|---|---|
| Needs an install | no | yes |
| Compiles roblox-ts to Luau | yes, in the browser | yes, via the project's own rbxtsc |
| Runs Luau | yes, in a sandbox | yes, locally |
| Live DataModel and simulated services | yes | yes |
| Network access from a script | no | yes |
Project runtime (dev) | no | yes |
| Tests and REPL | no | yes |
| Your files on disk | no | yes |
Use the playground to try an idea in seconds. Use
microstudio for real work — see
Installation to set it up and
Quickstart to run your first script.