Image Tools
Process, compress, and convert images. Optimize images for web performance and convert between different formats.
Image work in a browser, with no uploads. These tools compress images, convert formats, and handle Base64-encoded images - useful for test assets, documentation, and quick web chores.
2 tools availablePick the format before you compress
Compression hides two different contracts, and the file format decides which one you got. WebP, standardised as RFC 9649, is "an image file format based on the Resource Interchange File Format (RIFF) that supports lossless and lossy compression as well as alpha (transparency) and animation", and it covers use cases similar to JPEG, PNG and GIF. PNG's own specification describes it as "an extensible file format for the lossless, portable, well-compressed storage of static and animated raster images" and a patent-free replacement for GIF.
| Format | Compression | Right job | Watch out for |
|---|---|---|---|
| PNG | lossless (W3C PNG specification, third edition) | UI screenshots, text, diagrams, before-and-after evidence | large files once the content is photographic |
| JPEG | lossy | photographs and avatars | artifacts cluster around text and sharp edges |
| WebP | lossless and lossy, with alpha and animation (RFC 9649) | web delivery where the client supports it | re-encode once; a lossy pass per test run compounds |
| AVIF | lossy family; MDN calls it a "Good choice for both images and animated images" | modern image delivery | support varies, so keep a fallback |
| Base64 in HTML or JSON | none - this is encoding, not compression | small inline assets and fixtures | about a third larger, with line-length limits of its own (RFC 4648) |
Treat the compressor as a suspect in any defect about appearance. If the bug is colour banding, blocking or blown-out edges, the evidence artefact has to be the untouched capture; the compressed copy is a convenience for the ticket, never the thing that defines what the bug looks like. Re-encoding the same image twice makes the comparison meaningless, because the second pass is lossy on top of the first.
Base64 is the other common trap. RFC 4648 notes that MIME caps base64 lines at 76 characters and that PEM used 64, both inherited from SMTP limits - which is why an inlined image belongs in a small icon or a test fixture, not in a payload you paste into a database column or a JSON body. The Image Compressor and the Base64 Image Converter both run entirely in the browser, so a screenshot that shows a customer's data never leaves the machine, and the Image Format Converter handles the format swap itself when you need the same pixels in a different container.
Sources: RFC 9649 (WebP), PNG Specification, third edition (W3C), RFC 4648 (base64 line limits), MDN image file type and format guide.