a modular synthesiser and a modular video rack, sharing one patchbay.
Drag bricks onto a canvas, run cables between them, and the sound plays the pictures or the pictures play the sound. It happens in a browser tab — no install, no account, and no server doing the work. A whole patch fits in a link.
Nothing to sign up for and nothing to download. The editor opens empty, and the first brick is one keystroke away.
the sound plays the pictures
One pink cable is the whole idea: the filter's ring leaves the sound rack, walks into the video rack, and bends a picture with it. There is no bridge to cross, because there are not two racks — there is one canvas, and the ports already know what they can carry.
what is in the box
three things at once
sounda synth you patch
Oscillators, samplers, wavetables, a voice allocator, filters, delays, a reverb built out of a delay network, a looper. Sequenced, played from a midi keyboard, or typed at.
videoa rack you patch too
Shaders, meshes, feedback, glitch, colour — on the gpu, at frame rate. Drive any of it from the sound, or point a camera at yourself and drive the sound from that.
everything elseand the room around it
A timeline that records a knob while you turn it, a terminal for patterns typed instead of patched, a stage view sized for a thumb, two players over a peer connection, and midi and dmx going back out.
five things a cable can carry
and then you keep it
- a patch is a link
- The whole thing — every brick, every cable, every knob — is text in a url. Send it and it opens.
- or a file
- Export a folder to put on a website, or a single .html that opens by being double-clicked, with the clips and the tracks carried inside it.
- or a take
- ● rec writes the picture and the mix together as one video file; ● wav writes the mix on its own.
- nothing is uploaded
- Web Audio makes the sound, WebGL2 draws the pictures, and your clips sit in the browser's own storage on your own machine. The editor has never asked who you are.
where to go from here
What you make with patchfields is yours. It runs in the tab, and the app carries its own manual: the ? button in the editor covers patching, groups, components, the terminal and the rest of it in far more detail than this page does. If you would rather be shown than told, the tutorial builds a first patch in the editor itself, a step at a time.