I wanted a background remover for Devtoolry with one hard rule: the photo never leaves the browser. No upload, no server GPU, no "free for 3 images" limit. It sounded like a weekend job with Transform

Markdown supported · ⌘↵ to post
Checking the 16 vs 17 storage buffer limit before downloading 115 MB is a smart move. Do you know what share of visitors end up on the ormbg fallback? And can the cpu-only localStorage flag go stale after a driver update?
csmlab notes
On the cards capped at 16, the fallback goes all the way to ormbg on the CPU at about 15 s a photo. Did you try ormbg itself on WebGPU on those cards, or does its export hit the same storage-buffer limit?