Runs in the browser · Vision
Run CLIP ViT-B/32 in your browser
CLIP ViT-B/32 downloads 240.0 MB over WebGPU (q4f16), or 291.3 MB over WebAssembly (uint8), to classify images against your own text labels entirely in the tab with Transformers.js. No install, no server.
Vision · Xenova/clip-vit-base-patch32
- Parameters
- 151.3M
- Pipeline task
- zero-shot-image-classification
Reading
The second-largest vision download in the catalog (240.0 MB).
The quant ladder spans 4.8x: 240.0 MB (q4f16) to 1.13 GB (fp32).
Will it run in your browser?
Checking for WebGPU support…
All measured variants
| Variant | Size |
|---|---|
| q4f16 WebGPU pick | 240.0 MB |
| uint8 WASM pick | 291.3 MB |
| bnb4 | 346.5 MB |
| q4 | 361.2 MB |
| q8 | 438.7 MB |
| fp16 | 578.8 MB |
| fp32 | 1.13 GB |
Sizes measured from the HuggingFace API file tree for Xenova/clip-vit-base-patch32, not estimated.
Use it with Transformers.js
import { pipeline } from "@huggingface/transformers";
const pipe = await pipeline("zero-shot-image-classification", "Xenova/clip-vit-base-patch32", {
device: "webgpu", // usually falls back to "wasm"; wrap in try/catch for production
dtype: "q4f16", // use "uint8" for the WASM build
});
const result = await pipe(/* your input */);
Requires npm install @huggingface/transformers (or the CDN build).
Sources
Same job, different size
FAQ
WebGPU or WASM for CLIP ViT-B/32, in practice?
Chrome, Edge, and Safari 26+ run the WebGPU build (q4f16) on the GPU. Firefox has WebGPU on Windows and Apple Silicon Macs but not everywhere yet. Any browser without a WebGPU adapter falls back automatically to the WebAssembly build (uint8) on CPU: same model, slower to load, slower to run.
What does q4f16 mean for CLIP ViT-B/32?
The WebGPU build here uses q4f16: 4-bit weights with some layers kept at 16-bit for stability: WebGPU's usual smallest clean build. The WASM fallback uses uint8: 8-bit integers: about a quarter the size of fp32, with a smaller quality trade than 4-bit.
Sizes measured 2026-08-01 from the HuggingFace API. Last validated 2026-08-03. See all browser models or the methodology.