Read the processing badge
The interface labels a route as Instant, Local WASM or Server before processing.
ImgIng / Local image processing
PRIVACY · PROCESSING LOCATIONLocal image processing: what stays on-device and what gets downloaded
“Local processing” does not mean “nothing is downloaded.” ImgIng may deliver a codec or AI model to your browser, while common-format and local-AI workflows keep the user’s source-image pixels on the device.
Source pixels stay on-deviceProcessing paths disclosedWASM and models cached on demandServer boundaries labelled
Capability quick facts
These facts describe the current product, not unshipped roadmap work.
- Common formats
- Source-image pixels stay on-device
- WASM / AI
- Programs and models download to the browser
- Language switch
- Chinese and English share root assets and caches
- Server
- Only for clearly labelled specialist formats
Reviewed by the DataDance product and engineering team · Published · Updated
Finish in three steps
Confirm important settings before export; the processing location is always disclosed.
Separate download from upload
A codec or AI model travels to your browser; that is different from a source image travelling to a server.
Check the task boundary
Only clearly labelled specialist formats such as HEIC writing, TIFF and JPEG 2000 use the server path.
How do the four processing paths differ?
| Path | What crosses the network | Do source-image pixels upload? | Typical capabilities |
|---|---|---|---|
| Browser-native / ImgIng engine | Page and program assets | No | JPG, PNG, WebP, GIF, APNG and Online Design |
| Device-side WASM | A codec module downloads on demand | No | HEIC reading and AVIF writing |
| Local AI | An ONNX model downloads on demand | No | ISNet, BEN2 and BiRefNet HR-Matting cutout |
| Specialist server | The selected file is transmitted only after a clearly labelled server route is chosen | Yes | HEIC writing, TIFF, JPEG 2000 and PDF |
Why do downloaded modules normally survive a refresh?
AI models use browser Cache Storage. AVIF and HEIC modules use same-origin HTTP caching plus a localStorage load record. The Chinese and English pages share the same origin, root asset URLs and browser caches, so changing language should not download them again. Clearing site data, using a private window or browser cache eviction may require another fetch.
How can I verify the claim myself?
While processing JPG, PNG, WebP, animation or a local-AI cutout, open the browser developer tools and inspect the Network panel. On first use you may see a codec or model download, but there should be no request uploading the source image. If you deliberately choose a format labelled Server, rely on the disclosure shown before processing.
This page describes product architecture and data-flow boundaries; it is not a substitute for a legal privacy policy. The current processing badge and real network requests are the authoritative evidence for a particular task.
Updated 2026-08-20 · Live capability detection inside the tool is authoritative
Frequently asked questions
These visible answers match the current product behaviour and structured data.
Does downloading an AI model mean my image is being uploaded?
No. The model travels from ImgIng to the browser, while image pixels stay on the device; the two transfers move in opposite directions.
Will switching between Chinese and English download a model or AVIF module again?
It should not. Both languages share the same origin, root asset URLs and browser caches.
Which features really need a server?
Today the main examples are HEIC writing, TIFF, JPEG 2000, PDF and other specialist or legacy formats. The interface labels the route before processing.
Explore ImgIng
Each task page documents real settings, limits and format advice—not keyword-swapped duplicates.