CSS Houdini Resources: Worklets, Tools & Further Reading

This page is a working reference a curated jump-off point to the worklet libraries, specs, and tools worth knowing about, rather than another explainer. If you’re new to the topic, start with what CSS Houdini is, the full technical guide, or how to build your first worklet instead; this page assumes you already know the basics and want the links.

Open-Source Worklet Collections

ResourceWhat It OffersLink Type
CSSHoudini/paintletsA gallery of downloadable, tweakable paint worklets maintained under the official CSSHoudini GitHub organizationGitHub repo
liyangguang/css-houdiniA small, practical set of ready-to-use worklets (tooltips, shapes) with copy-paste usage instructionsGitHub repo
5t3ph/11ty-css-houdiniAn Eleventy starter environment for building and publishing your own worklets to npm/unpkgGitHub template
mcconville/houdini-experimentsExperimental Paint API demos, including animated effects achieved by combining a worklet with an external animation loopGitHub repo

Polyfills

ResourceWhat It Offers
GoogleChromeLabs/css-paint-polyfillBrings Paint Worklet support to Firefox and Safari, using -moz-element() and -webkit-canvas() for near-native performance where available, falling back to Canvas toDataURL()/toBlob() elsewhere

This is currently the most practical way to get a paint worklet effect working across all major browsers rather than Chromium only.

Official Specs & Documentation

Tools

  • Paint worklet generators: visual tools that let you choose a preset effect (noise, confetti, checkerboard, waves) and export the worklet JS and CSS without hand-writing the canvas drawing code — useful for prototyping before you commit to a custom implementation
  • Chrome DevTools Styles pane: lets you live-override the custom properties feeding a worklet, which is the fastest way to test a worklet’s range without editing and reloading files

Distribution Pattern: Publishing Your Own Worklet

If you build a worklet you want to reuse across projects or share publicly, the common pattern in the community is: publish it as an npm package, then load it via a CDN like unpkg. This sidesteps the HTTPS requirement for local testing and makes the worklet easy to drop into a CodePen demo or another project with a single addModule() call pointing at the CDN URL. For the registration and debugging steps themselves, see how to register and debug a worklet.

Community

  • CSSHoudini GitHub organization: hosts the paintlets gallery along with translated/localized resource repos for non-English-speaking developers
  • GitHub topic pages (css-houdini, houdini-css-paint): a live, constantly-updating feed of new experiments, portfolio demos, and starter templates tagged by the community