What browser-only image compression protects

Photos used for identity checks, applications, signatures, and personal profiles can be sensitive. An upload-based compressor sends the source file to a remote server, waits for processing, then downloads a result. A browser-only compressor can perform the same basic operations without that transfer.

On ImageCompressor.pics, image decoding, cropping, resizing, encoding, previews, and ZIP creation run in the page on your device. The site does not provide an endpoint that receives image files.

What happens when you choose a file

The browser gives the page a temporary File object for the item you selected. The tool creates a local object URL for the preview and decodes the pixels with browser APIs. That object URL is not a public web address. It only points to data held by the current browser session.

The result is created as another local Blob. When you download it, the browser writes that Blob to the location you choose. The same applies to a ZIP archive made from a batch.

The network and the image pipeline are separate

A website still needs network requests to load its HTML, JavaScript, fonts, and optional services. Browser-only processing means the image bytes are not included in those requests. It does not mean the page can load without any network activity on the first visit.

HEIC conversion uses a JavaScript decoder that is delivered with the site. Once loaded, the decoder receives the file inside the browser. It does not forward the file to a remote conversion API.

Re-encoding removes metadata

A camera file can include EXIF metadata such as capture time, camera model, orientation, and GPS coordinates. The compressor draws decoded pixels to a canvas and exports a new image. The original metadata block is not copied into that export.

This protects against accidentally sharing stored location or camera data. It also removes useful metadata such as copyright fields, editing notes, and capture dates. Keep the original file if you need that information later.

Optional analytics does not receive image data

Google Analytics 4 is loaded only after a visitor chooses "Allow analytics." If permission is not given, the Google tag is not loaded and no analytics event is sent.

When allowed, the site records page views and aggregate tool events such as target size, output format, and completed file count. It does not send file names, image contents, image previews, or local file paths.

Google explains that a standard Analytics setup may collect session statistics, approximate location, and browser or device information. See Google's current GA4 data collection documentation. The site's privacy policy describes the choice and how to clear it.

How to verify the claim yourself

A technical user can open the browser developer tools, switch to the Network panel, clear existing requests, then add and compress a test image. The compression work should not produce a request carrying the image file or a multipart upload.

You can also work offline after the page and its code are loaded. Disconnecting the network before selecting a file should not stop JPEG, PNG, WebP, or AVIF processing. HEIC needs its decoder chunk to have loaded before the connection is removed.

What local processing cannot protect

• Malware, browser extensions, or other software already running on the device may access local data.
• A compromised browser or operating system is outside the protection of a web page.
• Saving a result to cloud-synced storage can upload it through the operating system after download.
• Submitting the final image to another website is a separate upload governed by that site's privacy policy.

Practical privacy checks

1. Confirm the address bar shows imagecompressor.pics over HTTPS.
2. Do not select files on a shared device if other users can access its downloads.
3. Review the compressed preview before downloading and submitting it.
4. Keep sensitive originals in a secure location and remove temporary results when they are no longer needed.
5. Use the analytics choice that matches your preference.

Browser-only processing removes one major privacy exposure: sending the source image to a compression provider. It should be one part of a wider, sensible file-handling workflow.