Local processing
File pixels are decoded, edited and exported by browser APIs and client-side libraries after you choose a file.
Privacy you can verify
How ImageME keeps image work in your browser.
ImageME tools are designed to read selected files in the browser, transform them with client-side code and let you download the result without uploading the file to an ImageME server.
- POST /upload
- 0
- File API
- local
- Analytics
- page events
Privacy you can verify
The practical promise
No ImageME file storage
Selected files and generated results are not sent to an ImageME backend for editing, storage or model training.
Honest network boundary
The site still loads pages, app assets and Google Analytics. Those requests are separate from the files you select for editing.
File lifecycle
What happens to a file
The exact operation differs by tool, but the file lifecycle follows the same browser-local pattern.
1. You select a file
The browser grants this tab temporary access to the file you picked. ImageME does not receive a path to browse your device.
2. The tool reads it in memory
The selected file is decoded in the tab using APIs such as File, Blob, Canvas, workers and format libraries.
3. The result is created locally
Compression, resizing, conversion, metadata removal and related edits produce a new Blob or downloadable file in the browser.
4. You download or clear it
The result remains available to the page until you save it, remove it, navigate away or the browser frees the session memory.
Network
What network requests may still appear
A private editor still needs to load the application. These requests are expected and should not contain your selected image file.
Page and app assets
HTML, JavaScript, CSS, icons and generated Open Graph images can load from ImageME or the hosting platform.
Analytics
Google Analytics may receive page views and interaction events, but ImageME does not intentionally include selected file content or generated image content in those events.
External pages you open
Links such as Google privacy documentation or ecosystem pages leave ImageME and follow the destination site rules.
DevTools
Verify it yourself in DevTools
Use any modern desktop browser. The Network panel lets you distinguish app delivery from file upload behavior.
Open a tool before selecting a file
For example, open Compress Image, Resize Image or Strip Metadata in a fresh tab.
Open DevTools and clear Network
Open the Network tab, enable Preserve log if you want, then clear existing requests so the next actions are easy to inspect.
Select a test image and run the tool
Drop or choose a local image, adjust settings and export. Keep the Network tab visible while the tool processes.
Filter requests by Fetch/XHR and payload
You may see app assets or analytics requests. You should not see a request uploading the selected image to ImageME for processing.
Check names, sizes and request bodies
Look for your file name, a multipart upload, binary request body or large image-sized transfer. Those should not appear for normal tool processing.
Checklist
Verification checklist
Use these boxes while testing a tool. They are local browser controls and do not send data.
Boundaries
Limits and plain-language caveats
- Local processing does not mean zero network traffic. Loading the site and analytics still require network requests unless blocked or already cached.
- Browser extensions, operating system services, sync folders or security software may observe files independently of ImageME.
- Very large files depend on your device memory and browser limits because processing happens on your device.
- This page is a technical explanation, not a security certification or legal compliance guarantee.
Try a privacy-sensitive workflow
Strip metadata before posting a photo, compress a private image or convert a file while watching the Network panel.