Image & PDF Tools
Image and document work usually means handing your file to someone else's server. These tools use the browser's own canvas and file APIs instead, so the file never leaves the machine. Each tool states its size limits and supported formats up front, and tells you where processing happens before you choose a file.
All image & pdf tools
How these are grouped
- Image
- Compression, resizing and format conversion.
- Document
- PDF and document handling.
Choosing the right tool
Use the Image Compressor when the file size itself is the problem — the image is the right dimensions but too heavy to load quickly or fit an upload limit. Use the Image Resizer when the dimensions are wrong — too large for where it will be displayed, or not matching a platform's required size. The two are often needed together: resize first to the dimensions you actually need, then compress, since compressing an oversized image wastes quality on detail that will just be scaled down anyway.
Common mistakes
- Compressing before resizing — an image compressed at full resolution and then scaled down keeps file-size overhead spent on detail that never gets displayed. Resize to the target dimensions first.
- Using PNG for photographs — PNG's lossless compression has very little repetitive pixel data to work with in a photo, producing a file several times larger than an equivalent JPEG or WebP for no visible quality gain.
- Repeatedly re-compressing an already-compressed JPEG — each lossy pass encodes the artifacts of the previous pass, compounding quality loss. Always work from the original.
- Choosing JPEG for an image that needs transparency — JPEG has no alpha channel, and transparent areas get filled with a solid colour instead.
A short example
A 4.2 MB, 4032×3024 phone photo needs to go on a web page at a sensible display size.
Resizing to the actual display width first, then compressing the result as JPEG or WebP at quality 80, produces a far smaller final file than compressing the full-resolution original — the detail being discarded by resizing would otherwise be preserved by compression and then thrown away by the browser's own scaling anyway.