LilyPond in the browser

The published wspringer/lilypond-wasi WebAssembly engine, driven through a WASI host written in JavaScript. Nothing is engraved on a server.

Score

Idle — press Load engine, or just Render.

No output yet.

Tip: the MIDI box is ticked, so a score with a \midi { } block gives you a piano you can play right here. The first run downloads ~34 MB of release artifacts (17 MB engine + three .tar.gz asset trees) and caches them, so later renders only pay for engraving. The artifacts must sit in public/lilypond/ and be served from this same origin — GitHub release assets send no CORS headers, so a browser cannot fetch them from github.com directly.