Free image tools
A complete set of image editing tools that run entirely in your browser. Compress photos to reduce file size, resize to exact dimensions, convert between formats, rotate or flip orientation, and crop to any shape. All processing runs locally.
Seven of the eight tools decode your image with the browser's built-in image decoder and redraw it with the Canvas API; Image to Base64 reads the file's bytes with the FileReader API instead. Your image is processed in memory, and results are downloaded or copied straight from the tab.
Read the complete image tools guide
Why use image tools that run in your browser
Photos carry more than pixels. Every JPEG from a modern phone has an EXIF metadata block embedded inside it: the GPS coordinates of where the shot was taken, the camera make and model, the time of day, sometimes the serial number of the lens. When you upload a personal photo to a free online compressor, you hand all of that to whoever runs the service.
Browser-based tools sidestep the problem. Your photo is read into the tab's memory, the pixels are transformed, and the result is offered back to you as a download. All processing runs in your browser, metadata included.
Speed is the other reason. At an upload speed of 5 Mbps, sending a 10 MB image takes about 16 seconds before a server can start on it, and the result still has to come back. With the Canvas API running locally, the job skips both transfers.
How browser-based image tools work
Most tools on this page lean on one browser API: Canvas. When you drop a file, the browser decodes it into an image element and the tool draws it onto an off-screen <canvas>. From there, JavaScript can read every pixel, scale, rotate, crop, or re-encode to a different format and quality level. Image to Base64 is the exception: it reads the file with FileReader and encodes the bytes as text.
Canvas has shipped in every major browser since 2010, so the same code runs on Chrome, Firefox, Safari, and Edge, both on desktop and on mobile. After processing, the result is wrapped into a Blob and offered as a download via a temporary object URL. When you close the tab the URL is revoked and the image is gone from memory. The tools write nothing to IndexedDB or a service worker, and the site runs no analytics.
In-browser tools compared with the alternatives
Browser-based isn't always the right answer. Here is when it makes sense and when it doesn't.
| Approach | Privacy | Cost | Best for |
|---|---|---|---|
| In-browser (this site) | All local | Free, no account | One-off edits and quick fixes on any device |
| Upload-based image services | Server-side | Free tiers or paid plans | Large batch jobs with public images |
| Desktop image editors | All local | One-time or subscription license | Daily professional work, complex edits |
For most one-off jobs (shrinking a screenshot to fit a Slack message, resizing a profile picture, converting a PNG screenshot to JPEG), in-browser is the simplest path. For batch processing thousands of images a day, a dedicated desktop tool with scripting support is usually faster.
When to use these tools
- Use image compression before uploading to a website or sending in chat. Pair with image conversion to switch between JPEG, PNG, and WebP.
- For social media posts, crop to a square or aspect ratio first to choose the framing, then resize to platform-specific dimensions.
- Need to embed an image directly in HTML or CSS? Convert it to a Base64 data URI.
- Building a website? Generate a full set of favicons from one source image in all standard sizes.
- Want to extract the exact color of something in a screenshot? Use the image color picker.
Frequently asked questions
- Are these image tools free?
- Yes. Every tool is free with no usage limits, no account required, and no watermarks on the output.
- Do my images get uploaded to a server?
- All processing runs in your browser. The tools use the browser's Canvas API to read, transform, and re-encode your image locally. Image to Base64 does not re-encode: it encodes the file's own bytes, with the metadata removed by default. Our servers are not involved at any point.
- What image formats are supported?
- Most tools accept JPEG, PNG, and WebP as input. Output format depends on the tool. JPEG and PNG are universal, WebP is roughly 25 to 35 percent smaller than JPEG at equivalent quality.
- Does the Canvas API strip EXIF metadata?
- Yes. When an image is re-encoded through Canvas, the original EXIF block is dropped. That includes GPS coordinates, camera make and model, capture time, and any other embedded metadata. The output file has none of it. Image to Base64 is the exception: it does not re-encode, so by default it removes EXIF, XMP, IPTC, comments, and C2PA without touching the pixels, keeps the orientation, and offers a Keep original metadata option.
- What is the largest image I can process?
- Each image can be up to 50 MB. Every image tool except Image to Base64 also refuses images over 50 megapixels or with a side longer than 10,000 pixels. Phones can run out of memory on smaller images, and a very large image may freeze the tab briefly while it decodes.
- Why does the compressed file sometimes look softer?
- JPEG and WebP are lossy formats by design. Higher compression discards visual information that the encoder judges to be less perceptible. Drop the quality slider less aggressively, or switch to PNG for a lossless output.
- Can I use these tools offline?
- Once a tool's page has loaded, yes, in that tab. The image tools use your browser's built-in Canvas and File APIs and download nothing else as you work, so you can disconnect and keep going until you close or reload the tab or open another page. Opening or reloading a page needs a connection, because the site installs no service worker and the browser checks each page with the server as it opens.
- Do these tools work on iPhone and iPad?
- Yes. Safari on iOS supports the Canvas API the same way desktop browsers do. Drag and drop is replaced by a tap-to-pick file flow, but the processing is identical.