Skip to content
Run BunYour friendly Bun playground

Use cases

Find what you want to do, and start from the recommendation beside it. Each row has a section below with more.

You want to Start from Good to know
Try Bun or one of its APIs The Blank starter, or an example Nothing to install, no account
Build a small server or API The HTTP API starter, Elysia or Hono The preview sends any request
Build a page or a frontend The React starter, or Vite The fast path skips the install
Prototype with a database The SQLite starter SQLite and Postgres run in the tab
Share a bug reproduction Your project’s Share link The link is the whole project
Put runnable examples in your docs The embed configurator One script tag, or an Astro integration
Teach a class or run a workshop A share link or a ?repo= link Everyone runs the same project
Check a package or a framework The frameworks list Native bindings are what usually fails
Use an API a browser doesn’t have Local Bun The same editor, real Bun underneath

The starters and examples are in the project gallery: the project button in the playground’s header.

Open runbun.dev, pick the Blank starter and press Run. For one API, the examples each have a short program you can run and edit on the page: Bun.serve, bun:sqlite, Bun.file, Bun.password and Bun.$.

Recommended:

  • Check the API in Bun APIs or Node built-ins first. Each one is marked Works, Partial, Stub or Missing.
  • Use the console for bun test, bun add and shell lines. See Console.

Bun.serve runs in the page and the preview shows what it answers. Start from the HTTP API starter for plain Bun.serve, or from Elysia or Hono for a framework. For WebSockets, the WebSocket chat starter has a server and a page that talk to each other.

Recommended:

  • Use the preview’s request bar to send a method, headers and a body, without leaving the tab.
  • Turn on Watch, so a save restarts the server. See Running code.
  • Keep the requests a reader should try in runbun.json, so they open with the project.

Servers answer the preview, not the network: nobody else can reach them.

Start from the React starter. A project with an index.html and no Bun or Node APIs can use the fast path, which shows the page without bun install. For a dev server with HMR, start from Vite or Astro + Solid.

Recommended:

  • Try the fast path first for a page that only needs a few npm packages. It is experimental, and loads them from esm.sh.
  • Use Vite when you need its plugins or its config.

bun:sqlite needs no package and runs in the tab: start from the SQLite starter or the bun:sqlite example. Bun.sql runs Postgres in the tab too, on PGlite, kept in the project’s browser storage.

Recommended:

  • Use SQLite for a quick schema or query. Use Bun.sql when the code must be Postgres.
  • For a database over the network (a hosted Postgres, Redis), use Local Bun: a browser can’t open those connections.

The Share menu copies a link that carries the whole project in its URL. Nothing is uploaded, and whoever opens it runs the same files. Paste it in an issue.

Recommended:

  • Let a coding agent write the reproduction and hand you the link. Reproduce a bug with an agent has a prompt to paste.
  • Keep it small: one file and the fewest packages that still show the bug.
  • If the bug is in Bun itself, confirm it with real Bun as well. The playground runs your code in the browser’s engine, so a difference may be the playground’s.

The <bun-playground> element turns a code block into one that runs in the reader’s browser. In an Astro site, @runbun/astro does it from a Markdown fence. The configurator builds the snippet for you.

Recommended modes:

The example is Mode
A snippet that prints something code
A server or a page preview
A test file, or something run with a command console
A finished demo, where the code is secondary result
A whole project to explore full
  • Prefer the lighter modes. full loads the most and waits for Run.
  • Readers on Safari and iOS can read and edit but not run. See Browsers.

Everyone opens one link and has the same project, with no install and no account. Use a share link for a small exercise, or runbun.dev/?repo=owner/repo for a repository on GitHub. Each person’s edits stay in their own browser.

Recommended:

  • Ask for Chrome, Edge or Firefox. See Browsers for the versions.
  • Have people open the link once before the session: after the first visit the playground works offline, except for installing packages.
  • Collect answers as share links.

bun install fetches packages from npm, so the quick test is to add the package and run it. Frameworks lists what is known to run, each with a link that opens it.

Recommended:

  • Read what usually blocks a framework before a long attempt: native bindings without a wasm fallback, install scripts, and tools that spawn other programs.
  • If a framework’s CLI doesn’t start, start its dev server from a file instead.

Some things a browser can’t do: start other programs, open raw sockets, load native addons. Benchmarks mean nothing here either.

Recommended:

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.