obrobka

In-browser image processing

Runs in your browser

Upscale an image

A plain stretch only smears the pixels you already have. The network invents detail that is not in the file — measured, that is worth 1.5 to 2.9 dB over bilinear at 2×. At 4× the result is uneven: +2.7 dB on smooth surfaces, almost nothing on foliage.

drop it here or paste with Ctrl+V · the file never leaves your device

How to fit

Fits and returns the smaller size — no padding

Aspect ratio
Framing
Upscaling
Brush
Layers

Put an image on top — a logo, a sticker, a watermark.

How to do it

  1. Pick an image, drag it in, or paste with Ctrl+V
  2. Under “Upscaling” choose 2× or 4× — the model downloads once
  3. Wait for the tiles: the preview shows how many are left and how long it should take

Frequently asked questions

How long does it take?
About 2.6 s per tile on an ordinary CPU. For a large shot that is minutes. If the browser has WebGPU it is roughly ten times faster — the interface says which one is doing the work.
Why tiles?
So that memory does not depend on image size. Measured: a 256×256 tile at 2× peaks at 561 MB; double the tile and it reaches about 1.8 GB, past what a tab can hold. The seams are blended linearly — without that they would stay visible.
Can it recover lost detail?
No. The network invents something plausible, not something true. For text and faces check with your eyes: the result can be convincing and wrong at the same time.
How large is the model?
7.7 MB for 2×, 18.1 MB for 4×. It downloads once and is then served from your browser cache.