Best Free Image Tools That Don't Upload Your Photos (2026)

brevio and Squoosh are the two main image tools that process entirely in-browser — no upload, no account required. brevio covers compression, HEIC conversion, cropping, resizing, watermarking, and EXIF removal; Squoosh specialises in codec-level compression with AVIF, MozJPEG, and OxiPNG.

Image processing is a common task — compress before emailing, convert a WebP download to JPG, resize for a form upload. The problem: most popular tools (TinyPNG, Canva, Adobe Express) upload your photos to their servers. For personal photos, ID documents, or internal company images, this is worth avoiding. Several high-quality tools handle images entirely in the browser.

How to verify an image tool isn't uploading your file

Before trusting any image tool with a sensitive photo, run a 30-second verification in your browser's developer tools. This works on any tool, regardless of what the privacy policy says.

1. Step 1: Open DevTools. Press F12 on Windows/Linux, or ⌘⌥I on Mac.
2. Step 2: Go to the Network tab. Filter to Fetch/XHR and check Disable cache to ensure all requests are visible.
3. Step 3: Drop your image into the tool.
4. Step 4: Watch the Network tab. On brevio you see zero POST requests with image data — the only network activity is loading static JS and CSS assets. On TinyPNG, iLoveIMG, or Canva, you will see POST requests to their servers carrying your image file as a multipart upload.

This test is the definitive check. Privacy policy claims are unverifiable from the outside; network activity is not.

Comparison: Image tools by privacy, cost, and capability

The table below covers the leading tools. "Upload?" is verifiable via the Network tab. Pricing is as listed publicly as of 2026.

Key finding: brevio is the only no-upload tool that covers the full suite of common image operations — compression, conversion, resize, crop, EXIF removal, watermark, and flip/rotate — at no cost, with no file size limit.

When privacy matters for image processing

For most images — a product photo, a banner, a resized screenshot — uploading to TinyPNG or iLoveIMG carries negligible risk. But there are specific cases where keeping the file on-device matters:

• Personal photos containing EXIF GPS data. Your camera or phone embeds your precise location in every photo by default. Uploading to TinyPNG or iLoveIMG means sharing this location data with a third-party server. A photo of your home, workplace, or children's school carries your GPS coordinates in the file header until EXIF is stripped.
• Company product images. Internal unreleased product photos, document screenshots, or HR headshots should not be processed on third-party infrastructure before review. NDAs and internal data policies often prohibit this.
• ID documents and passports. Image cropping and resizing tools are sometimes used to prepare ID photos for submission. These should never leave the device — no third-party should hold a copy of a passport or national ID scan.
• Client work. Designers handling client brand assets may be bound by NDAs that prohibit uploading to third-party services. Processing locally avoids any contractual ambiguity.
• Medical images. Health photos — wound photos, prescription labels, medical scan exports — should stay local under GDPR Article 9 (special category data) and are not appropriate for third-party cloud processing without explicit consent.

How EXIF data is handled

Images processed via the Canvas API — which brevio uses for compression, resizing, cropping, and format conversion — lose EXIF data by default. This happens because canvas.toBlob() and canvas.toDataURL() do not carry EXIF metadata through the re-encoding step. The Canvas API outputs a clean image with only pixel data. As a result, compressing, resizing, or converting an image on brevio also strips GPS coordinates, camera model, and timestamp — as a side effect, not by explicit intervention.

For deliberate, confirmed EXIF removal where you want to verify the strip occurred, brevio has a dedicated EXIF Remover tool that performs the Canvas pass explicitly and allows you to confirm the output is metadata-free before downloading.

Complete list of brevio image tools

brevio includes 8 image tools, all running client-side with no upload:

• Compress Image — reduce JPEG, PNG, WebP file size without uploading
• Resize Image — resize by pixel dimensions, aspect ratio preserved
• Convert Image — JPG ↔ PNG ↔ WebP conversion
• Crop Image — free-form and aspect-ratio cropping
• Image to PDF — combine images into a single PDF
• Add Watermark — text or image watermark overlay
• Flip / Rotate — 90°/180°/270° rotation and horizontal/vertical flip
• Remove EXIF — strip GPS, camera model, timestamp metadata

All tools use the HTML Canvas API and run locally. No account, no file size cap, no watermark on output.

When to use Squoosh instead

Squoosh by Google offers more advanced compression codecs (AVIF, MozJPEG, OxiPNG, WebP 2) and is fully open-source with code published at github.com/GoogleChromeLabs/squoosh. Squoosh is the right choice when you need AVIF format — which delivers roughly 50% smaller files than JPEG and better compression than WebP — access to per-codec fine-tuning (effort levels, chroma subsampling, Z-depth), or want to compare codecs side-by-side before choosing an output format. For routine compression and format conversion without advanced tuning, brevio is faster: select the file, set quality, download. No codec configuration required.

Frequently asked questions

Does TinyPNG upload images to a server?

Yes. TinyPNG sends your image to their servers (tinypng.com backend) for compression using their pngquant/mozjpeg pipeline. You can verify this in the DevTools Network tab — you will see a POST request with your image file as the payload. The free tier allows 500 images per month; paid starts at $25/month. For images without sensitive content this is a reasonable trade-off for the compression quality; for personal photos with GPS data or business-sensitive images, use a client-side tool instead.

Is Squoosh by Google safe?

Yes. Squoosh is an open-source Progressive Web App built by the Chrome team that runs entirely in your browser using WebAssembly codecs. It does not upload images — the compression and encoding happens locally in your browser tab. The source code is public at github.com/GoogleChromeLabs/squoosh and has been independently reviewed. It is one of the most trustworthy image compression tools available.

What is the difference between lossy and lossless compression?

Lossy compression (JPEG, WebP at <100 quality) permanently removes some image data to achieve smaller files. The changes are typically invisible at 80–85% quality for most photos, and the file size reduction is significant — often 50–80% smaller than the original. Lossless compression (PNG, WebP at 100 quality) finds redundancy in the file without losing any data: files are larger than lossy equivalents but bit-for-bit identical to the original. Use lossless for graphics, logos, screenshots, and anything with text or sharp edges; use lossy for photographs where the quality trade-off is acceptable.

Other ways to do this

You don’t need a web tool for this at all — these options also keep your files on your own machine:

• macOS Preview / Photos and the Windows Photos app resize, crop, and convert without any upload.
• ImageMagick covers nearly every image task from the terminal (e.g. magick in.png out.jpg -resize 50%).
• ImageOptim (macOS) and Squoosh (Google — also runs in-browser) compress offline.

The browser tool is just the no-install, cross-platform option for when you would rather not set any of these up.