Live-code Audio Playground

Writing and iterating on Tone.js live-coding music sketches entirely in your browser. No account, no server round-trip — your code runs as real JavaScript against the real Tone.js library loaded in the page, driving the Web Audio API.

Browsers block audio from playing before a user gesture (a click or keypress) on the page. The Run button's click satisfies that requirement, which is why the playground calls Tone.start() inside the Run handler rather than automatically on page load.

There is no visible browser console in this playground, so log(message) is the only way your code can print text feedback — it appends a line to the Output panel on the right. It plays the same role print does in the Blockly playground.

Every run swaps in a fresh Tone.js audio context and disposes the previous one, which tears down its clock and every synth/sequence/loop built on it — so switching examples or re-running never leaves a previous loop playing underneath the new one.

Yes — every documented Tone.js class and the global Transport are available on the Tone parameter, including Synth/PolySynth/MembraneSynth/MetalSynth, Sequence/Loop/Pattern, and the full Transport scheduling API (Tone.Transport.bpm, .start(), .scheduleRepeat(), etc.).

Errors (invalid note names, scheduling mistakes, thrown exceptions) are caught and shown in an inline error banner instead of silently failing or leaving stuck audio playing.

Yes. Click Share to copy a URL that encodes your current code, so anyone who opens the link sees (and hears) the same sketch.