debuff vs PixiJS
PixiJS is a 2D renderer, and one of the fastest on the web. debuff is a small game toolkit: renderer, game loop, input, audio, assets, testing and agent tooling. They overlap on drawing sprites and differ on almost everything else. Here's how they compare as of October 2026.
Short answer
Pick PixiJS if you want a fast, mature renderer and are happy to choose the rest yourself, or if you're building something that isn't a game, such as interactive graphics or a UI-heavy app. Pick debuff if you want the game loop, input, tests and agent tooling to come together.
At a glance
| debuff 0.2 | PixiJS 8.22.0 | |
|---|---|---|
| License | MIT | MIT |
| Language | TypeScript | TypeScript |
| What it is | Game toolkit | Renderer (pixijs.com) |
| Game loop, scenes, input | Built in (fixed-step clock, seeded RNG) | Bring your own |
| Audio, UI | @debuffjp/audio, @debuffjp/ui | Separate libraries (@pixi/sound, @pixi/ui) |
| Rendering | WebGL2, Canvas 2D fallback | WebGPU and WebGL |
| Sprites at 60 fps (our benchmark) | 200,000 | 200,000 (ParticleContainer), 50,000 (Sprite) |
| Full runtime, brotli | 20 kB (every debuff package) | 185 kB (pixi.min.js) |
| Testing | Scenarios, screenshot baselines, fuzz | Up to you |
| Coding agents | MCP server for the running game, AGENTS.md | llms.txt, llms-full.txt, official skills |
| Community | Small | Large (about 48k GitHub stars) |
Each library's complete prebuilt bundle (all debuff packages, pixi.min.js), compressed with brotli and measured on 17 October 2026. Tree-shaken games ship less.
Rendering speed
We ran a bunnymark on one machine. PixiJS's ParticleContainer and debuff's ordinary draw.sprite both held 200,000 sprites at 60 fps, and ParticleContainer was faster per frame at that count (10.4 ms against 13.9 ms). PixiJS's regular Sprite held 50,000. The method, raw numbers and caveats are on the benchmarks page, and you can run it yourself.
Where PixiJS is stronger
- Rendering features. WebGPU, filters, masks, text rendering, Spine and a large plugin ecosystem.
- Maturity and reach. Years of production use in games, ads and interactive sites, and a large community.
- Agent docs. PixiJS publishes llms.txt and an official skills repository for v8, installable as a Claude Code plugin. That's current, well-kept documentation for agents.
- Flexibility. It doesn't impose a game structure, so it fits into apps and frameworks easily.
Where debuff is different
- It's a whole game toolkit. Loop, scenes, input with action bindings, audio, tilemaps, tweens and particles come together, in a much smaller runtime.
- Tests for games. Fixed steps and a seeded RNG make runs deterministic, so
npm testcan run scenarios with screenshot baselines, andnpx debuff fuzzsaves every crash as a replay. - Agents that see the game. We found no MCP server for PixiJS. debuff's lets an agent attach to your open game, read the moments you flag, reproduce them with
game_replay, and tune typed params you can undo. See the agent comparison post.
Which to choose
If you need a renderer inside a larger app, or PixiJS's rendering features, use PixiJS. If you're making a small game and want the rest of the stack included, try debuff:
npm create debuff@latest my-game