Fewer pixels, and nothing stretches

Processed on your own hardware · never transmitted, never stored

What happens when you drop a file in

1. The file stays put. Your browser opens it the same way an image viewer would. There is no transfer, which is why there is no upload bar to watch.

2. An encoder arrives once. The first job on this site pulls down a compiled build of FFmpeg, roughly 30 MB. It is kept afterwards, so every job after the first starts immediately.

3. Your own hardware does the job. The work happens in this tab, on your processor. A laptop from the last few years handles short clips in well under real time.

4. The result lands in Downloads. Assembled in memory and handed straight to your browser. Close the tab and every trace of it is gone.

Nearly every image is bigger than its job requires

A current phone produces photographs four thousand pixels wide. A web page shows them at eight hundred. The remaining three quarters are downloaded, decoded and then thrown away by the browser — paid for in time and bandwidth, seen by nobody.

Resizing eliminates that waste at source. Compression trades quality for size; this trades resolution that was never being displayed, which is why it costs nothing visible when the image was oversized in the first place.

Proportions are maintained automatically. Give it a width and the height is derived, so nothing distorts.

Enlarging is deliberately absent

Ask for a width beyond the original and the image is returned unchanged rather than stretched. Nothing can manufacture detail that was never recorded — tools claiming otherwise are either interpolating, which yields a soft waxy surface, or running models far heavier than a browser tab can host.

Common questions

Related tools