Browser capability report · WebGPU + WASM
What can your browser actually run?
54 of 54 models in this catalog publish a measured WebAssembly build, so even a browser with no WebGPU support, the smallest common denominator, can still download and run every one of them, memory allowing. The lightest download in the whole catalog is 1.5 MB (pyannote Speaker Segmentation 3.0, uint8 over WebAssembly). Run the live check below to see what this browser can do right now.
WebGPU adapter · shader-f16 · device limits · WASM SIMD/threads · memory · storage quota, measured in-tab.
Live browser capability check
Probing this browser’s capabilities…
What WebGPU support means in practice
WebGPU is the API that lets a browser tab run AI inference on your GPU instead of your CPU. It ships by default in current Chrome, Edge, and Safari (26+); Firefox has it on Windows and Apple Silicon Macs, with Linux support still catching up. Whether it is actually available to a given visitor depends on the browser version, the OS, and sometimes the GPU driver, not just "which browser": an old point release of an otherwise-supported browser can still lack it, and a locked-down enterprise build can disable it outright.
When WebGPU is not available, every model in this catalog falls back to a WebAssembly build that runs on the CPU. It is a real fallback, not a dead end: the model still downloads and still runs, just slower to load and slower to infer, and often (median 3% across this catalog) as a larger download too, since the WASM-friendly int8 quant usually compresses less than the WebGPU q4f16 build. 27 of 54 models buck that trend and download smaller over WASM.
Per-buffer limits are the trap worth knowing about even when WebGPU is available: maxBufferSize caps a single buffer, not your total download or your GPU's total VRAM. A model's total weight file can still exceed it even on a GPU with memory to spare, because the runtime has to fit each individual weight tensor's buffer under that ceiling. The live check above reads your browser's actual reported value, not a guess.
FAQ
Does WebGPU support depend on my operating system, or just my browser?
Both. WebGPU now ships by default in current Chrome, Edge, and Safari (26+); Firefox has it on Windows and Apple Silicon Macs but not everywhere yet. An older browser version, or Firefox on Linux, can lack it even when the browser family generally supports it. The live check on this page tells you which side of that line you're actually on, right now.
What does the WebAssembly fallback actually cost me?
Across this catalog, the WebAssembly build is a median 3% larger than the WebGPU build for the same model (27 of 54 models download bigger over WASM; 27 do not). It also runs on the CPU instead of the GPU, so it loads slower and infers slower, but it never blocks you outright: every model in this catalog ships a measured WASM build.
Catalog sizes measured 2026-08-01 from the HuggingFace API. Last validated 2026-09-14. Every browser signal above is measured live in your own tab via localfit and the Web APIs it wraps (WebGPU, WebAssembly, Storage), never estimated. See all 54 browser models or try the main hardware detector for the native GGUF catalog.