p5.js, the creative-coding library that has introduced more people to programming through visuals than almost any other tool, is in the middle of testing its 2.4 release — and the headline feature is a WebGPU renderer that sits alongside, not instead of, the WebGL mode generative artists already know. As of early November the library is still cycling through release candidates (six and counting as of November 5), with the Processing Foundation explicitly asking the community to load up familiar sketches and try to break them before the version goes live in the official p5.js Editor.
WebGPU mode is opt-in, and that’s the point
WebGPU mode ships as a separate add-on script rather than a silent swap under the hood. A sketch opts in by loading p5.webgpu.js alongside the core library and passing WEBGPU to createCanvas — with one catch that trips up anyone copying an existing WebGL sketch: WebGPU’s initialization is asynchronous, so setup() has to become an async function and the canvas call needs an await in front of it. p5.js contributor Dave Pagurek, who has led much of the WebGPU work, has been clear that this isn’t a deprecation push — WebGL isn’t going anywhere soon, and WebGPU mode exists because that’s where the browser ecosystem’s new rendering work is actually happening.
p5.strands carries over
The more immediately useful payoff for working artists is that p5.strands, the JavaScript-native shader syntax p5.js introduced to avoid hand-writing GLSL, is designed to work across both renderers. A shader written for WebGL mode should run under WebGPU mode without a rewrite — including, as of this release cycle, instancing support, so a single strands shader can drive many repeated geometry instances rather than requiring a separate draw call per copy. The 2.4 line also adds SVG loading and multi-material 3D model support, both aimed at bringing more “normal” asset workflows into a library that has historically leaned toward code-generated geometry.
Why a release candidate matters to actual sketchers
A release candidate isn’t live on the public editor, so this is squarely a call for the community that maintains and extends p5.js in public — the same open, teachable ethos the library has run on since it replaced the original Processing applet model. Testing instructions point people toward specific pull requests and feature areas rather than asking for blanket feedback, with the explicit suggestion to “pick something you’re familiar with in p5, and dig into it, especially looking for strange behavior in edge cases.” For a library whose whole reason for existing is making code-based art approachable, that’s a fitting way to ship a rendering-engine change: in public, with the people who’ll actually use it holding the keyboard.