Skip to content
Run BunYour friendly Bun playground

runbun.dev vs installing Bun locally

runbun.dev isn’t a replacement for Bun. Installed Bun is the real runtime: JavaScriptCore, every API, native speed. runbun.dev is the quickest way to run Bun code when installing it isn’t worth it, or isn’t possible.

runbun.dev Bun installed
Setup Open a tab Install Bun on macOS, Linux or Windows
Engine The browser’s JavaScript engine JavaScriptCore
APIs Most of Bun.*, bun:* and node:* (compatibility) All of them
Processes, sockets, bun:ffi, native addons No Yes
Your files A project saved in the browser, or a folder you open Your disk
Sharing A link carries the whole project A repository or an archive
Runs on locked-down machines, Chromebooks Yes, in Chrome Where you can install software
  • Trying Bun, or a Bun API, before installing anything.
  • Bug reproductions: a share link is a whole project in one URL, which anyone can run.
  • Teaching and docs: examples that run where the reader is, embedded in a page.
  • Real projects: anything that spawns processes, talks to a database over TCP, or needs every API.
  • Performance: benchmarks and heavy workloads mean nothing in a browser shim.

From the playground, Download as zip saves the project; unzip it, then bun install and bun index.ts (or bun run dev). The other way, open a folder from disk in the playground, or a GitHub repository with runbun.dev/?repo=owner/repo.

With Bun installed, the playground can run projects with it: bunx @runbun/connect --open adds a Local Bun button, and runs go to the real runtime on your machine, sandboxed, while you keep the playground’s editor and preview. See Run with local Bun.

Was this page helpful?

Sends the rating and this page's address; nothing else unless you write it. Privacy

runbun is an independent project, not affiliated with or endorsed by Oven or Bun.