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. Page assets, optional libraries, and consent-dependent services can still generate requests; inspect whether any request contains image data. 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. Processing can continue without a connection once all required code and assets have loaded; test the particular format before relying on offline use. Speed depends on your device and browser. The image pipeline does not create a server-side copy, but the source and downloaded results remain on your device. Closing the tab releases its working state; it is not a secure-erasure procedure for local files.

A converter decodes an image and encodes the resulting pixels into another format. The WebP to PNG converter can retain transparency and avoid another lossy encoding step, but that is not a byte-for-byte archive of the source. Canvas color handling, bit depth, animation, and metadata can change what survives. The color-profile guide explains why appearance can change even when the destination uses lossless encoding.

JPEG and quality-controlled WebP exports trade information for smaller files. PNG preserves the samples supplied to its encoder; GIF palette conversion can discard colors before lossless storage. The browser WebP exporters do not expose a dedicated lossless switch, and quality 100 is not such a switch. Use the lossless versus lossy guide to separate format capabilities from the controls a particular tool actually offers.

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 starts with the actual layout. Follow the responsive image workflow to create appropriate widths, then test format and quality with the image compressor. Compare bytes and appearance instead of assuming a fixed saving. For a CMS, the WordPress WebP guide covers upload support, thumbnail generation, and safe migration of existing media.

Sharing iPhone photos with non-Apple users: HEIC to JPG provides a widely accepted delivery format. The HEIC conversion guide explains the process. If the recipient still rejects the result, check actual format, dimensions, and bytes with the upload troubleshooting guide; changing format alone cannot fix an expired session or a service outage.

Print and editing prep: the JPG-to-PNG guide explains when a PNG intermediate avoids repeated lossy saves. Keep the untouched source separately. For screen delivery, the retina sizing guide distinguishes display density from print DPI so you export enough pixels without needlessly enlarging every asset.

Developer assets need both visual and semantic checks. Use the favicon guide for site icons and the dark-mode image guide to test logo contrast and transparent edges. The alt-text guide explains meaningful, decorative, and functional images: an optimized file does not supply its own accessible description.

Social and quick edits: choose the framing with the crop-versus-resize guide before changing dimensions. For photographs, identify whether the problem is exposure, noise, or edge softness. The guides to brightening dark photos, reducing noise, and controlled sharpening explain separate corrections and their limits. Applying all three at full strength is not a reliable enhancement workflow.

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.

When this suite does not fit the job, the image converter comparison helps evaluate other workflows by format support, privacy, and batch requirements. Read the no-upload guide before handling sensitive material: local processing reduces one type of exposure but does not remove the need to trust the application and device.