FFileTools
↑

Resize your image

Upload an image and choose its format and dimensions.

FILETOOLS BENCHMARK

How output formats change a resized image

We resized the same 1,280 × 854 JPEG to 640 × 427 and encoded the result in several formats. This shows why choosing an output format can matter almost as much as choosing the dimensions. Your TGApage uses the same browser-based resize engine.

JPEG
218.9 KB
PNG
917.6 KB
WebP
715.4 KB
GIF
267.8 KB
AVIF
162.2 KB
OutputFile sizeChange vs sourceTime
JPEG218.9 KB−78.9%39.23 ms
PNG917.6 KB−11.4%31.40 ms
WebP715.4 KB−30.9%29.60 ms
GIF267.8 KB−74.1%223.17 ms
TIFF1.04 MB+3.1%28.01 ms
BMP1.04 MB+3.1%29.50 ms
AVIF162.2 KB−84.3%1,334.84 ms

Method: a generated 1,280 × 854 RGB test image was encoded as JPEG, then resized to 640 × 427 with Lanczos3. Release-mode benchmark on the FileTools Rust engine. Source JPEG: 1,060,701 bytes. Each result was measured once in this format comparison. ICO was tested separately at 128 × 85 because the ICO encoder limits image width to 256 pixels: 27,520 bytes in 36.39 ms. TGA, PNM and QOI at 128 × 85 produced 43,370, 43,248 and 40,793 bytes respectively.

Why dimensions matter

Resizing changes the number of pixels in an image, so it can reduce file size far more than changing a filename or metadata. A smaller image is useful for websites, email attachments and social posts, while keeping the original file makes sense when you may need its full resolution later. FileTools performs the resize in your browser, so the image does not need to be uploaded to a server.