How Local Processing Works

This page explains what stays in the browser, what code gets downloaded, and what happens to your files during local processing.

What happens to your file

1

The file is opened locally

When you select a file, the browser reads it directly from your device. There is no upload step to a PrivateTools server.

Your Files

Local Browser Memory

2

Processing runs in the browser

The tool uses browser APIs such as WebAssembly, Canvas, Workers, and media codecs to do the work on your device.

Processing Engine

WebAssembly + Canvas

3

The export downloads back to your device

The output file is generated in the browser session and then saved back to your device. There is no cloud storage step in between.

Your Device

Direct Download

What we do and do not do

What we do not do

  • ✗Upload your files to our servers
  • ✗Store your images in the cloud
  • ✗Track your file contents or names
  • ✗Share data with third parties
  • ✗Require account creation or login

What to expect

  • ✓Processing runs inside the browser
  • ✓Files never leave your device
  • ✓Exports download directly to your device
  • ✓No account required for basic use
  • ✓Some tools can keep working after assets are cached

What runs in the browser

Core browser-side pieces

Local processing relies on standard browser capabilities and media runtimes that can execute on your device instead of on a backend server.

Browser APIs

  • • WebAssembly (WASM) for heavy local processing
  • • Canvas API for pixel work and rendering
  • • File API for local file access without uploads
  • • Web Workers for background processing

Media runtimes

  • • FFmpeg.wasm for video encoding and conversion
  • • ImageData API for raw pixel manipulation
  • • WebCodecs API for hardware-accelerated media work
  • • OffscreenCanvas for high-performance rendering

FAQ

Try the tools

Open a tool, load a local file, and see the workflow in practice.

Open Image Sequence PlayerOpen trimy