Measure
Real WebGPU compute kernels move 512 MiB through your GPU's memory and multiply dense matrices, timed by the GPU's own clock.
A 45-second benchmark, right in your browser. Get a verified score, your rank against identical hardware, and the AI models your machine can run.
No install. No account. Nothing personal leaves your browser.
Live from the network. Every figure on this site is a real run; nothing is simulated.
Spec sheets say what hardware should do. This says what yours does, from the browser you already have open.
Real WebGPU compute kernels move 512 MiB through your GPU's memory and multiply dense matrices, timed by the GPU's own clock.
A signed, single-use ticket opens every run. The server recomputes the score and checks it against what the hardware can physically do.
Your result lands in its device class, never against different hardware. It becomes a die on the public wafer and earns points.
Each phase isolates one thing an AI workload asks of your hardware. Together they make the X-Score.
Generating one token reads every active weight once. Read throughput is the hard ceiling on tokens per second.
Pick a machine and see which open models fit in its memory, and the fastest they can possibly decode.
Most popular, about 4.85 bits per weight.
The ceiling is memory bandwidth divided by the bytes of weights read per token. It is an upper bound from the memory side; real runtimes land below it. Memory need is the weights plus an estimate for the KV cache and runtime.
A laptop never competes with a workstation card. Every board is one device class, so a rank says something about your machine, not your budget.
Runs appear here the moment they are verified.
$XCOMP is wired into the product: it multiplies what a run earns, unlocks the pro tools, and pays for certificates and compute as the network grows.
Link a wallet that holds $XCOMP and every verified run earns up to 2× the points. The balance is read on-chain when the run is submitted.
Deep reports with per-sample traces and export, API keys with raised limits, and fleet mode to track every machine you own.
Each weekly season has a fixed pool, split by the points earned that week. Boosted points mean a larger share of the same pool.
Spend $XCOMP to anchor a verified result on-chain as a certificate: proof of what a machine does, for resale listings and rental marketplaces.
Machines that prove their performance can serve inference jobs. Buyers pay in $XCOMP, and a verified score is the entry ticket.
Holders vote on season themes, point rules and the reference machine behind the score.
Real. It compiles compute shaders, allocates 512 MiB on your GPU and times hundreds of passes with the GPU's own clock. The 3D wafer only draws between timed passes, so it never touches a measurement.
A recent Chrome, Edge or other browser with WebGPU. Browsers without it fall back to a CPU measurement: you still get a score, but it is not ranked.
Browser numbers cannot be proven honest. They can be made hard to fake by accident and awkward to fake on purpose: signed single-use tickets, a minimum run time, a score recomputed on the server, and a ceiling set by the hardware's own memory bus.
The scores, the GPU model your browser reports, and your browser and OS family. No account, no cookies, no IP address stored, no fingerprint. Your identity is a random key that lives in your browser.
It multiplies the points a verified run earns, unlocks the pro tools, and is the unit for season pools, certificates and compute as they ship. Each function is labelled with its real status on the $XCOMP page.
No. Points are a ledger of verified work. They decide how a funded reward pool is split, and a pool pays only once it has been funded on-chain. Nothing here is a promise of return.
Find out what your machine is worth to an AI model.