Browser-local image tools: how to check the upload boundary
This guide comes from the ImgIng project. It explains how to evaluate an image tool's processing path; it is not an independent security audit or a comparison of compression performance.
A browser interface does not tell you where a file is processed. A web app might run a codec on your device, send the source to a service, or combine both paths. The useful question is more specific than “is this website private?”: what does this selected operation send, receive, and save?
Separate the operation from the product name
ImgIng's published documentation describes common image-processing routes as local to the browser. It also documents specialist-server exceptions. Reading an existing HEIC photo is a different operation from exporting a new HEIC file, for example. A local compression workflow does not establish that every conversion offered by the same site is local.
| Selected task | Published processing boundary | What to check before using it |
|---|---|---|
| Common-format image compression and supported local exports | Described by ImgIng as browser-local | The actual input, chosen output, and notice in that workflow |
| HEIC writing, TIFF, JPEG 2000, or exporting images to PDF | May use a labelled specialist server | Whether this operation uploads material and whether that fits your requirements |
| Compressing an existing PDF | Described as local; different from creating a PDF from images | The PDF's supported features and the saved result |
| HTML to PDF | Has a server-side rendering path | The conversion notice rather than a general local-processing claim |
These are documented boundaries, not measurements performed for this post. Check the current tool notice because file type, output choice, and product changes can affect the route.
A download is not the same event as an upload
A local application still needs its page, scripts, and other assets. Some workflows also download a codec or a machine-learning model before processing can start. Network activity alone therefore does not prove that the source image left the device. Conversely, finding one local worker does not prove that another part of the workflow never sends data.
Squoosh provides another useful distinction: its official README describes local compression, while separately disclosing analytics. Local image processing and the absence of all telemetry are different claims. Evaluate each requirement separately.
Inspect a small, permission-cleared example
- Choose a non-sensitive image you own or are allowed to use. Keep an unchanged original.
- Open the browser's Network panel before loading the workflow. Record the browser version, page, date, and selected task.
- Run that one operation. Distinguish document, script, codec, and model downloads from requests carrying file or image content. Inspect payloads where the browser makes them available.
- Repeat after assets are cached, recording the difference. Do not turn one apparently quiet run into a claim covering every format or feature.
- Save and reopen the output. Confirm dimensions, format, transparency, text legibility, and the details that matter to the intended use.
Browser inspection can provide observations for a particular run; it is not a complete security audit. If your organization restricts uploads, follow those handling rules and verify the selected route before using confidential material.
Record output quality separately
For compression comparisons, retain the input and output files, actual byte sizes, dimensions, format, exposed quality settings, errors, and unsupported cases. Compare equivalent tasks: PNG-to-PNG optimization and converting PNG to WebP answer different questions. Smaller files can still lose detail or behave differently in the destination workflow.
The aim is a reproducible decision about a concrete job, with the data path and output quality evaluated independently. You can explore ImgIng using a permission-cleared example and the current operation notices.
Sources
- ImgIng: local image processing and privacy architecture
- ImgIng English product summary
- Squoosh official repository and README
Sources checked on November 6, 2026. Product statements are attributed to their publishers. No new compression benchmark, file-handling test, or security-audit result is presented here.
