◀ VibeCruiser

webgl engine bench

A free playcanvas demo — play it in your browser, no install. How many sprites and 3D cubes can a web engine draw at 60 fps on your machine? LittleJS, PixiJS, Three.js, PlayCanvas, Phaser and Babylon.js, on WebGL and WebGPU. Run it and share your results.

by @KilledByAPixel · KilledByAPixel/webgl-engine-bench on GitHubLANG JavaScript★ 2HOSTED ON KILLEDBYAPIXEL.GITHUB.IOUPDATED 2 Oct 2026

Vote and save it — free account with email or sign in with GitHub

Made this, @KilledByAPixel? See how many people played it → or use email

▶ Play full screen ▲ Vote: free account with email ▲ Or sign in with GitHub

GitHub may ask you to sign in, then to let VibeCruiser “Verify your GitHub identity” and “Act on your behalf”. We only read your profile and email, and never post anything.

Open the live demo Source on GitHub

From the README

How many moving sprites and 3D cubes can a web engine draw while holding 60 fps, on your machine?

The two scenes, shown here with 2,000 objects each. Every engine draws exactly the same picture; the benchmark keeps adding objects until the engine can no longer hold 60 fps.

Engines compared: LittleJS, PixiJS, Three.js and PlayCanvas, plus an extended set with Phaser, Babylon.js and the WebGPU renderers of Pixi and Three.

This benchmark was started by the author of LittleJS, so read it with that in mind.

Read the full README on GitHub →

Built something like this? Submit your vibe — free account, takes a minute. How listing works.

More like this

Made this?

Claim it: create a free account, then press CLAIM THIS in the cruiser. Put the badge below in your README or on your demo page first; that link is how we know it's yours.

Your project is on the cruise, loaded live from your own site. Put the badge in your README or on the demo page: it shows your live play count, it links back to this page, and everyone who lands here is one click from running the real thing.

On VibeCruiser

How listing, the badge and claiming work →