Practical overview
When it fits
Use it for browser-based Cadence learning, teaching or early contract prototyping, especially when an emulator workflow without a locally installed node is useful.
Who it is for
- Developers learning Cadence or prototyping Flow contracts.
- Educators preparing browser-based Cadence examples.
- Contributors working on the Playground itself.
Documented uses
- Draft Cadence contracts, transactions and scripts.
- Compile and iterate on code against an embedded Flow emulator.
- Start examples from templates and share projects by URL.
Requirements & limits
The hosted Playground is described as usable in a browser without local tooling. The repository lists an Apache-2.0 license.
- The editor supports Cadence contracts, transactions and scripts.
- Code can be run against an embedded Flow emulator using in-browser accounts.
- The project combines a static React and TypeScript frontend with a Playground API wrapping the Flow Emulator.
- Local contributor setup requires npm and Docker.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Create and share a Cadence project
Use a template to deploy a contract in the browser emulator, try a transaction or script, and share the project.
Before you start
- A browser and access to https://play.flow.com.
Steps
Open the hosted Playground and create a new project.
Choose a contract, transaction or script template.
Deploy the contract to one of the in-browser accounts.
Run a transaction or script against the deployed contract, then share the project URL.
Expected outcome
A Cadence project with an emulator-based contract workflow and a URL that can be shared with teammates or learners.
Guide limitations
- The documented workflow uses the embedded Flow emulator and in-browser accounts.
Set up the Playground locally for contribution
Prepare the frontend and API for local development of Flow Playground.
Before you start
- Git, npm and Docker.
Steps
Clone the repository and change into its directory.
Run the command below.
npm installRename
.env.localto.env.Start the Playground API with the documented Docker command, then run the command below.
npm run start
Expected outcome
The README describes the local Playground as available at http://localhost:3000.
Guide limitations
- This is contributor setup; the hosted version is the documented route for using the Playground without local tooling.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 9 October 2026
- Original website title
- onflow/flow-playground · Official homepage title · retained in its source language

