ClearPix workflow guide
What Browser-Based AI Processing Actually Uploads?
ClearPix does not upload your image or video content to a processing server. Models, static assets and anonymous product telemetry travel over the network, but the media you edit stays on your device. “No upload” describes the media-processing architecture, not the absence of every network request.
What does and does not leave your device
| Network activity | What it contains |
|---|---|
| AI model and runtime downloads | ONNX models, WebAssembly and processing code—not your media. |
| Static images and demos | Public comparison assets and sample files. |
| Anonymous product events | Coarse actions such as process start, completion, cancellation and export. |
| Your source image or video | Not sent to ClearPix for processing. |
| File name or media contents | Not included in the anonymous event properties. |
Model downloads happen once and are cached. After the required models and application shell are cached, supported tools can continue working offline. First-run time and size depend on the tool and backend.
Steps
- Open your browser’s developer tools and switch to the Network panel.
- Load a file in a ClearPix tool and start processing. Confirm that requests are for models, code or public assets—not your source media.
- After the required models are cached, disconnect from the network and process another file.
- For implementation details and the privacy policy, read Local First and the Trust Center.
Why this distinction matters
A browser tool can be private by architecture without being network-free. Model and static downloads are expected; anonymous product analytics help reliability and are listed publicly. The important distinction is that your actual image or video is read and processed locally instead of being uploaded for a remote AI job.
For acceptance data and output examples, see Quality Dashboard.