About CamPlay

CamPlay is a collection of free browser games you control with your body. A webcam watches how you move — jog in place, jump, duck, lean, squat — and those movements drive the game directly. There is no controller, no console, no wearable and nothing to install: a laptop with a camera and a little standing room is the whole setup.

Why CamPlay exists

CamPlay is built and run by Faridul Reza Sagor, a software engineer, as an independent project with a simple premise: most people don’t skip exercise because it’s hard — they skip it because it’s boring. Games solve the boredom problem better than any gadget: nobody has to be convinced to play one more round. So instead of building another workout app that counts reps, CamPlay makes games that happen to be workouts. If you play to beat your high score and only later notice you’re out of breath, the design is working.

The second premise is accessibility. Fitness games traditionally demanded hardware — a Kinect, a Switch, a VR headset, a sensor mat. Modern browsers can now run real-time machine learning on an ordinary laptop, which means the hardware barrier is gone. Everyone with a webcam already owns a motion controller; CamPlay is the software that turns it on.

How the technology works

Every CamPlay game is driven by pose estimation — a computer-vision model that looks at a camera frame and returns the positions of 33 body landmarks (nose, shoulders, elbows, wrists, hips, and so on). CamPlay uses Google’s BlazePose model running through MediaPipe, compiled to WebAssembly and WebGL so it executes inside your browser tab at real-time frame rates.

On top of the raw landmarks sits CamPlay’s own input engine. It converts landmark motion into game signals: arm-pump cadence and head bob become a continuous running speed, a synchronized rise of head and hips becomes a jump, a drop becomes a duck, shoulder-line roll becomes a lean. All distances are normalized by your shoulder width, so the controls behave the same whether you stand one metre or three metres from the camera, and an adaptive reference tracks your posture over time, so there is no calibration step. Only your head-to-waist needs to be in frame — the games are deliberately playable in a small room, close to the screen.

The games themselves never see the camera. They receive only abstract signals — “speed 0.7”, “jump”, “lean left” — through a strict internal boundary: game code never imports pose internals, and pose code knows nothing about games. That separation is what lets one input engine power an endless runner, a ski race, a dodge game and a party game at once.

Why no video ever leaves your browser

This is the part of CamPlay we care most about, so it’s worth being precise: your camera feed is processed entirely on your device, and no video, image or frame is ever uploaded, recorded or stored. This isn’t a policy promise that a server politely deletes your footage — it’s architecture. The pose model is downloaded to your browser and inference runs locally; there is no code path that sends frames anywhere. The only things that ever leave your device are gameplay results: a score, an estimated calorie count, your progress in a multiplayer race. You can read exactly what is stored and why in the privacy policy.

Why the browser, and not an app

Browser delivery is a deliberate choice. It means zero installs and zero updates for players, one link starts a game on any modern laptop or desktop, and a multiplayer round with friends is just a shared room code — the same seeded course is generated independently on every player’s machine, so only tiny progress updates cross the network. It also keeps the privacy model honest: everything the game does is visible to your browser’s own developer tools.

Design principles

A few rules shape every CamPlay game. Sessions are short by design — three to ten minutes — because bursts you actually finish beat marathons you skip. The interface is readable from several feet away, since you play standing back from the screen. Calories are estimated honestly and labelled as estimates — the methodology is documented on the how calorie tracking works page. And gameplay is never interrupted by advertising: ads appear only on content pages like this one, never on a game screen.

Get in touch

CamPlay is actively developed, and player feedback directly shapes what gets built next — several games started as suggestions. Found a bug, have an idea, or want to say hi? Use the feedback page.