The Complete Guide to Collabs Tool's 91 Free Image Tools

The image category is the site's largest: 91 tools that convert, compress, resize and transform pictures without sending a file anywhere. They group into six families.

• Format converters — every direction you are likely to need: WebP to PNG, PNG to WebP, JPG to PNG, PNG to JPG, HEIC to JPG and PNG for iPhone photos, AVIF to PNG, JPG and WebP, plus BMP, GIF, APNG and JFIF conversions, SVG to PNG and back, and image-to-GIF and video-to-GIF (MP4, WebM, MOV).
• Optimisation — an image compressor that holds visual quality while cutting file size, and an image resizer for exact pixel dimensions.
• Effects — 46 one-click looks: grayscale, sepia, blur, sharpen, and the creative end (glitch, pixelate, oil-painting, neon-glow, vintage, tilt-shift, kaleidoscope), plus rotate, flip, circle-crop and rounded-corners for layout work.
• Utilities — an EXIF viewer for the metadata hiding inside a photo, a colour palette extractor, a favicon generator, a placeholder image generator, and image-to-Base64 / Base64-to-image for developers.
• Clean-up — a background remover and an image upscaler for the two edits people reach for most.
• Every tool runs standalone. No account joins them into a workflow, no queue orders them, and no watermark signs the output.

Every image tool on the site follows the same pipeline. A file input reads bytes from your disk into memory. A decoder turns them into pixels — the browser's own image decoder for common formats, a WebAssembly decoder for HEIC. A Canvas element applies the conversion, effect or scaling. An encoder writes the result back out as a file you download. Every step is a JavaScript API that already exists in the browser; the server that delivered the page takes no part in the processing.

You can watch it happen. Open the Network tab in developer tools and run any conversion: there is no request carrying your file — no POST, no PUT, no websocket frame. The only traffic is the page itself loading. That is a property of the code rather than a promise in a privacy policy, and unlike a promise, it can be checked.

The consequences are practical. A conversion keeps working after your connection drops, because nothing was travelling over it. Speed is bounded by your own CPU rather than an upload link plus a server queue. And there is nothing to delete afterwards — no retention window, no deletion request, no account to close — because the file was never written anywhere except the tab's own memory, which the browser releases when you close it.

Conversion itself is pixel-exact in every direction. The decoder produces a fixed set of pixels; the converter encodes exactly those pixels into the new format. A WebP-to-PNG output holds precisely what the WebP contained, transparency included. No sharpening, no resampling, no silent colour shifts.

The only quality decision is the one you make about the output format. A lossy output (JPG, or WebP in lossy mode) discards data to shrink the file; a lossless output (PNG, GIF, WebP in lossless mode) keeps every pixel. The compressor tools surface that decision explicitly with a quality setting and a side-by-side preview, rather than hiding it behind a default.

The same honesty applies in reverse: a converter cannot recover data that the source format already threw away. A small JPEG converted to PNG looks identical to the JPEG — the artefacts are preserved faithfully, because that is all there is to preserve.

Batch conversion accepts up to 20 files in a single run. One quality setting applies to the whole batch, each file is processed in turn, and results are downloadable individually. For most real jobs — a folder of product shots, a set of downloaded WebPs — one pass is enough.

The per-file ceiling is 25 MB, and it is set by practical browser memory rather than by a quota: the bound is what a tab can decode and re-encode comfortably, not what the site wants to charge you for. A very large image on a low-powered phone can still exhaust the tab; if a conversion fails on a huge file, resizing it first or splitting the job usually succeeds.

The boundaries are worth stating plainly, because a tool that admits them is more useful than one that promises everything. Processing speed is your device's speed, so a mid-range phone decodes a 24 MB photo slower than a server farm would. The formats that convert are the formats browsers (plus the bundled WebAssembly decoders) can read. And because there is no server, there is no cross-device job queue: work lives in the tab that started it.

Preparing images for a website: drop the originals on the compressor, keep visual quality and watch bytes fall; then convert the survivors to WebP for delivery. A 3 MB PNG hero image typically lands under 500 KB without a visible difference, which is the single biggest Core Web Vitals win most pages can buy.

Sharing iPhone photos with non-Apple users: HEIC to JPG removes every compatibility complaint — email, Windows, web uploads — without opening a desktop app. The full walkthrough lives in the HEIC guide.

Print and editing prep: JPG to PNG gives a lossless canvas for work that will be edited and re-saved, with the walkthrough in the JPG-to-PNG guide.

Developer assets: image-to-Base64 for embedding, favicon-generator for site icons, placeholder-image-generator for mockups, colour-palette-extractor for pulling a theme out of a reference image.

Social and quick edits: resize to platform dimensions, background remover for clean cutouts, then whichever of the effects suits the post.

The site is free because the expensive part of a converter — the server doing the work — does not exist here. There is no processing bill to cover, no queue to monetise, no storage to meter, and therefore no reason to hold a feature hostage behind a premium tier. Advertising keeps the lights on, which is why there is no watermark on your files: the deal is attention from readers, not branding on their outputs.

The data economics are the same shape. The site stores at most three values in your own browser (theme, recent tools, cookie choice), and Google Analytics loads only after you accept the consent banner — decline it and no analytics cookie is set. Nothing about you or your files is sold, shipped or trained on, because nothing about your files ever arrives.

There is no onboarding, which suits a library this size better than a tour would. Pick the job rather than the tool family: converting a downloaded image? Start at WebP to PNG or HEIC to JPG. Making a page faster? The image compressor. Fixing a photo for a post? Resize, then the effect you want. Every tool page carries its own step-by-step instructions and its set of FAQs, and the guides in this section cover the decisions the tools cannot make for you.