Google, along with guest contributors, has published a demo site at houdini.how showing what Houdini can do, accompanied by a write-up from Una on web.dev. All of the demos currently focus on the Paint API, though Houdini is technically a collection of seven separate specifications, and the paint work is only one of them.
What makes the Paint API compelling is how much effect fits into such a small amount of code. Una's confetti demo serves as the clearest example: you import it, you use it, and you control it through CSS custom properties. The whole thing weighs in at under 1 kB.
The early framing of Houdini positioned these as low-level APIs that platform engineers would use to prototype new browser features more safely. The current framing is closer to: confetti!!!! Both are reasonable.
Browser support and the Firefox question
Firefox remains the major unknown. Mozilla describes Houdini as "worth prototyping," but that characterization looks like more of a stretch following the company's platform team layoffs. The Paint API can be polyfilled, at least:
(async function() {
if (CSS['paintWorklet'] === undefined)
await import('https://unpkg.com/css-paint-polyfill')
CSS.paintWorklet.addModule('https://unpkg.com/houdini-tesla/dist/worklet.js');
})()
Given that the polyfill is roughly 5 kB, cross-browser support may not be a serious obstacle.
Where to look and what to learn
Vincent De Oliveira's collection at css-houdini.rocks has long been a favorite set of demos. Though they lean artistic, several resemble practical UI patterns that are genuinely useful on the web but have historically been difficult to implement well.
For a written walkthrough, Estelle Weyl, Ruth John, and Chris Mills have put together a tutorial in the mdn/houdini-examples repository. It covers the Paint API alongside the Typed OM, which is less flashy but highly practical.



