Creative Coding

Cables.gl 2.0: Node-Based WebGL Grows Up for Browser Installations

The browser-based visual programming tool for interactive graphics ships a major version — a faster runtime, WebGPU output, and better export — making patch-and-play GPU work viable for shipped web installations, not just prototypes.

Cables.gl released a 2.0 milestone this summer, maturing the browser-based node tool from a fast prototyping toy into something you can ship. Cables lets you build interactive GPU graphics by patching nodes together in the browser — no build step, live preview, instantly shareable by link — which made it a favorite for quick audiovisual sketches and web experiments. The 2.0 update targets the gap that kept it from production: a faster runtime, a WebGPU rendering path alongside WebGL, and improved export for embedding patches into real sites and installations.

Watch: Introduction to cables.gl (YouTube)

Node patching in the browser, no toolchain

Cables’ appeal is the same one that draws artists to TouchDesigner or Max, moved into the browser: you think in signal flow — this feeds that, this modulates the other — instead of writing and rebuilding code. The difference is zero setup and instant sharing. There’s nothing to install, a patch runs live as you build it, and you can hand someone a URL. For teaching, for rapid audiovisual ideation, and for artists who think visually rather than in text, that immediacy is the whole draw, and it’s why Cables built a following without ever leaving the browser tab.

WebGPU and export make it shippable

The 2.0 additions matter because they attack Cables’ two production weaknesses. The WebGPU path taps the same modern GPU capabilities this site has tracked across the browser-graphics wave — compute shaders, heavier particle systems, more headroom — so ambitious patches stop hitting the WebGL ceiling. And better export means a finished patch can be embedded into a client site, a gallery kiosk, or a web installation cleanly, rather than living only on Cables’ own hosting. Together they answer the question every prototyping tool eventually faces: what happens when the sketch is good enough to ship?