Usage
All five tools follow the same shape: drop an image, adjust a couple of settings, download the result.
Compression and format conversion
Path: /
Drop in one or many images, pick an output format and quality, then download. This is pure encoding — no AI involved — so it is fast and unaffected by your hardware.
Choosing a format
| Format | Best for | Notes |
|---|---|---|
| WebP | The safe default | Excellent compatibility and much better compression than JPEG. If unsure, use this. |
| AVIF | Smallest possible files | Best compression at a given quality, but slower to encode and unsupported in older browsers. |
| JPEG | Maximum compatibility | Opens everywhere. A safe choice for photographic images. |
| PNG | Transparency or lossless | Large files. If you only need transparency, prefer WebP. |
| JPEG XL | Experimental | Promising, but browser support is still limited. |
AI upscaling
Path: /upscale/
Enlarges images 4× with Real-ESRGAN. It reconstructs detail rather than interpolating pixels, which is why old photos and low-resolution assets come out noticeably sharper.
What it is and isn't good at
- Good: low-resolution but otherwise sharp images, assets that need enlarging, mild compression artefacts.
- Not good: out-of-focus or badly blurred photos. Super-resolution rebuilds detail; it does not undo blur. A blurry photo stays blurry, just bigger.
AI background removal
Path: /cutout/
Drop in an image, hit "Remove background", and get a transparent PNG. You can also switch to a white, red or blue backdrop — recolouring is an instant recomposite and does not re-run the model.
Choosing between the two models
| Tier | Download | Best for |
|---|---|---|
| MODNet (default) | ~24 MB | People and pets. Clean hair edges, a quarter the size of the HD tier. Always runs on CPU. |
| BiRefNet Lite (HD) | ~94 MB | Products, logos, and complex objects. Solid on both people and objects. |
One more thing: MODNet always runs on CPU and never touches your GPU (see the model notes). A better graphics card will not make it faster — for GPU acceleration, use the HD tier or Click to Cut.
Weights are cached by the browser afterwards, so later runs start instantly. A different browser or a cleared cache means downloading again.
Reading the result
- Compare — drag the divider to compare the original with the cutout.
- Result — the cutout alone; transparent areas show as a checkerboard.
- Original — just the source image.
- Hold space — temporarily reveal the original to check the edges.
Edges look too soft
The "Edge" setting has two modes: Sharp narrows the semi-transparent transition band for a cleaner look; Soft keeps the natural feathering, which suits hair and fur.
Nothing gets selected
The model looks for the most salient subject in the frame. That means:
- Multiple objects — only the most prominent one is kept. Use Click to Cut to pick a different one (next section).
- Pure landscapes with no clear foreground — may be judged "no subject" and reported as such, rather than handing you a nearly fully transparent image.
- A very small subject, or one that blends into the background — results degrade. A subject that fills a decent share of the frame and contrasts with the background works best.
In these cases, picking a different photo usually helps more than adjusting settings.
Click to Cut
Address: /segment/
Automatic cutout is "let the model decide who the subject is". Click to Cut flips that — you tell the model where the subject is. Reach for it when you want the second or third object in the frame, or when the automatic model keeps grabbing the wrong thing.
How to use it
- Drop an image and click the object you want to keep. The outline appears immediately.
- Not right? Keep clicking — every extra point joins the prompt and refines the result.
- To drop something that got included, hold Alt and click (or right-click) to mark it "exclude".
- Happy with it? The result appears on the right at the same time, so you can watch it change as you click — download the transparent PNG when it looks right.
Click to Cut vs. automatic cutout
- A person, one obvious subject — automatic is faster, one step.
- Several objects and you want a specific one — Click to Cut.
- Automatic picked the wrong thing or missed part of it — switch to Click to Cut and click once; no need to change models.
- A structurally complex product shot — Click to Cut plus a few extra points is usually easier than reaching for a heavier model.
Crop, rotate and slice
Address: /edit/
This one runs no model at all — plain Canvas maths, so there is nothing to download and nothing to wait for.
Crop
Drag a corner or an edge to resize the box, drag inside it to move it. The right-hand panel can lock the ratio to 1:1, 4:3, 3:4, 16:9 or 9:16; "Free" leaves it unconstrained. The output size updates live.
Rotate and auto-straighten
- Any angle — the slider covers ±180°, with ±1° buttons for fine adjustment.
- ±90° and horizontal / vertical flip — one click each, for fixing phone orientation.
- Auto-straighten — photos of documents and whiteboards are usually a degree or two off. Hit "Auto-straighten" and it infers the tilt from the straight lines in the frame, rotates, and reports the angle so you can nudge it afterwards.
Grid slicing
Set the number of columns and rows (3 × 3, say) and the gap between tiles, then hit "Download slices (ZIP)". The slicing range is the current crop box, so crop first if you like. Leftover pixels are spread across the first few tiles rather than dumped into the last one, so you never end up with one conspicuously narrow strip.
Common questions
Why is the first run so slow?
Upscaling and background removal both download a model and initialise the inference engine first. That happens once; afterwards it comes from cache. See In-browser inference.
Why is it much slower without WebGPU?
With WebGPU, inference runs on the GPU. Without it, the work falls back to the CPU, where being several times slower is expected. Desktop Chrome and Edge have the best WebGPU support; recent Safari versions work too.
How long does a hundred images take?
Compression accepts hundreds of images at once through a batch queue. Upscaling and background removal are one image at a time — they are heavy computation and you want to check each result anyway.