Image Tools
Twelve image tools that run entirely in your browser: compression, resizing, format conversion, cropping, rotation, watermarking, and metadata inspection or removal. Your files are read by JavaScript on your own device and never uploaded, so there is no queue, no upload limit, and no copy sitting on a server afterwards.
Image Resizer
Resize images to exact dimensions or by percentage, with optional aspect-ratio lock. Runs entirely in your browser — images never leave your device.
Private · in-browserImage Compressor
Shrink JPG, PNG and WebP file sizes in your browser without uploading. Adjust quality and download instantly.
Private · in-browserBulk Image Compressor
Compress many images at once, entirely on your device. Pick a quality and download them all.
Private · in-browserImage Converter (PNG / JPG / WebP / AVIF)
Convert images between PNG, JPG, WebP and AVIF locally — no upload, no quality sent to a server.
Private · in-browserImage Cropper
Crop images to a custom selection or aspect ratio in your browser. Download the cropped result.
Private · in-browserImage Rotator & Flipper
Rotate or flip images by 90° increments locally and download the result instantly.
Private · in-browserImage to Base64
Convert an image to a Base64 data URL in your browser — handy for embedding in CSS or HTML.
Private · in-browserEXIF Viewer
Inspect the EXIF metadata (camera, date, GPS) stored in a photo — read entirely on your device.
Private · in-browserEXIF Remover
Strip EXIF and location metadata from photos for privacy, locally in your browser.
Private · in-browserImage Color Extractor
Extract the dominant colors and palette from an image in your browser.
Private · in-browserImage Watermark
Add a text watermark to images locally and download the result. Nothing is uploaded.
Private · in-browserImage to PDF
Combine one or more images into a single PDF in your browser. Files never leave your device.
Private · in-browserWhich image tool do I need?
Work backwards from the problem rather than from the file extension.
- Too big to attach or upload — the image compressor re-encodes one file at a quality you choose, and the bulk image compressor does the same to a whole batch in one pass.
- Wrong dimensions — the image resizer scales the whole picture down; the image cropper cuts a region out of it. Resizing keeps everything and makes it smaller, cropping throws part of the frame away.
- Wrong format — the image converter exports PNG, JPG or WebP.
- Sideways or mirrored — the image rotator turns and flips in 90° steps.
- Posting something you want credited — the image watermark stamps text across the picture.
- Unsure what a photo reveals about you — the EXIF viewer shows the camera, timestamp and GPS coordinates a file carries, and the EXIF remover strips them out.
- Building something — image to Base64 inlines a small graphic as a data URL, color extractor pulls a palette from a photo, and image to PDF binds scans or receipts into one document.
JPG, PNG or WebP?
Photographs belong in JPG or WebP. Both are lossy, and lossy compression is what makes continuous-tone detail cheap to store. Screenshots, logos, diagrams and anything with flat color or transparency belong in PNG, which is lossless and carries an alpha channel. WebP is usually the smallest of the three at comparable visual quality and is safe in every current browser.
Two traps. JPG has no transparency, so converting a transparent PNG to JPG fills those pixels with white. And lossy re-encoding compounds — a JPG saved from a JPG loses a little more each time, while converting a JPG to PNG freezes the damage rather than undoing it. Always start from the original file. The guide to compressing images without visible loss works through the quality settings in detail.
Everything happens on your device
These tools read your file with the browser File API and process it on a canvas, so there is no upload endpoint, no processing queue and no server-side copy to expire later. The only practical ceiling is your device memory. That matters most for the metadata tools: you can see exactly what a photo would have told the internet about you before you post it, which is the whole subject of the photo metadata privacy guide.
Frequently asked questions
- Are my images uploaded to a server?
- No. Every image tool here decodes and re-encodes the file in your own browser using the File and canvas APIs. There is no upload request, so nothing to intercept in transit and nothing stored for us to delete. The trade-off is that very large files are limited by your device memory rather than by a server.
- Why did my PNG barely shrink when I compressed it?
- Because PNG is a lossless format, so a quality setting has almost nothing to act on. If the PNG is really a photograph, saving it as JPG or WebP with the image converter will cut far more than any PNG recompression can. Keep PNG for screenshots, line art and images that need transparency.
- Should I resize or crop?
- Resize when the whole picture is right but the pixel dimensions are too large — everything stays in frame, just smaller. Crop when part of the frame is unwanted or you need a specific aspect ratio, such as a square avatar. Cropping is destructive to the discarded area, so keep the original.
- Does converting an image also strip its metadata?
- Yes, as a side effect. The converter redraws your image onto a blank canvas and encodes a brand-new file, so camera model, capture time and GPS coordinates are not carried over. Orientation survives because browsers apply the EXIF rotation flag while decoding, baking it into the pixels.
- Is there a limit on file size or how many images I can process?
- There is no imposed limit. The bulk compressor handles as many files as you select, and the practical ceiling for a single image is how much memory your browser can allocate to decode it. Very large panoramas on a phone are the usual failure point; the same file typically works on a laptop.