No upload, no waiting
Unlike the video tools, image work happens entirely in this tab. There is no queue, no job to poll and no copy of your photo on a server.
Reshape a picture and get it under an upload limit, without sending it anywhere.
Crop when the shape is wrong: a rectangle heading into a square avatar slot, a landscape photo destined for a 9:16 cover. Compress when the shape is already right and only the file size stands between you and the upload button. Both pages run the same engine, so either one can do both in a single pass.
Unlike the video tools, image work happens entirely in this tab. There is no queue, no job to poll and no copy of your photo on a server.
The targets are the ones that actually block people: 500 KB for a Reddit avatar, 250 KB for a forum attachment, 100 KB for anything that has to load instantly.
Choosing a ratio and a size ceiling in the same screen means you do not crop somewhere, compress somewhere else, and discover the result is still too heavy.
Video is decoded and re-encoded with FFmpeg on a server, because a browser cannot do it at a usable speed. That is why a video job uploads a file, gets queued and expires after 30 minutes.
Images are small enough that the browser can do the whole job itself. Nothing is uploaded, nothing is stored, and the result appears as soon as the encoder finishes.
No. Cropping and encoding run on a canvas in the page, so the image never leaves your device — which is also why they work with no account and no limit on how many you process.
WebP, always. It holds more detail than JPEG at the same file size, which is what makes tight limits like 100 KB workable.
Yes. The processing uses the browser on the device, so a recent mobile browser handles it — very large photos are the only thing likely to run out of memory.