Compatibility
System requirements
Minimum hardware and software for optimal performance.
Minimum requirements
| Requirement | Minimum |
|---|---|
| Browser | Chrome 94, Edge 94, Firefox 90, Safari 16.4 |
| RAM | 4 GB (8 GB recommended for large images) |
| Storage | 500 MB free (for model cache) |
| Internet | Required on first use for model download |
| GPU | Not required (WASM fallback available) |
Recommended for best performance
| Requirement | Recommended |
|---|---|
| Browser | Chrome 94+ or Edge 94+ |
| RAM | 16 GB |
| GPU | Any modern GPU with WebGPU support (2019+) |
| Internet | Required on first use only |
GPU / WebGPU support
WebGPU is supported by most modern dedicated and integrated GPUs from 2019 onwards. If your GPU is too old to support WebGPU, the tool falls back to WASM automatically — the output quality is the same, but inference takes longer.
GPUs with known WebGPU support in Chrome/Edge:
- NVIDIA GTX 1000 series and newer
- AMD RX 5000 series and newer
- Intel Arc and Intel Iris Xe (11th gen+)
- Apple M1 and newer (Mac)
- Most Android GPUs from 2020+
Memory usage
| Scenario | Approximate RAM |
|---|---|
| App + RMBG-1.4 model | ~300 MB |
| App + RMBG-2.0 model | ~500 MB |
| Processing one 4K image | +100–300 MB |
| Queue of 10 processed images | +200–500 MB (varies) |
If your device runs low on memory, close other tabs and applications before processing large images or long queues.
Storage
The AI model weights are cached in your browser:
| Model | Download size | Cached size |
|---|---|---|
| Fast (RMBG-1.4) | ~80 MB | ~80 MB |
| Best Quality (RMBG-2.0) | ~180 MB | ~180 MB |
Model files are stored in the browser's Cache API storage. You can clear them from your browser settings (Site Data for this domain) if you need the space back.
Mobile devices
| Platform | Support |
|---|---|
| iPhone (iOS 16+, Safari) | Supported — slower inference |
| iPhone (iOS < 16) | Limited — no service worker, basic processing |
| Android (Chrome) | Full support |
| iPad (Safari) | Supported — varies by model |
On mobile devices, processing is slower (typically 30–120 seconds per image) due to memory and thermal constraints. For batch work, a desktop is recommended.