How does local processing work?

The page loads code into your browser, then file reading, processing, and export happen locally on your device.

Can PrivateTools see my files?

No. The files are not uploaded to PrivateTools servers, so we do not receive their contents.

Is this safer than cloud-based converters?

For file privacy, usually yes. Cloud converters need uploads, while local processing keeps the working file on your device.

Does it work offline?

Often yes after the code and required runtimes have been cached, though first load may still need network access.

What happens to my files after conversion?

The source and output stay in your browser session and on your device. Closing the tab clears in-memory working data.

Does PrivateTools use analytics?

If analytics is enabled for a deployment, PrivateTools may send anonymous usage events such as page views or tool actions. File contents and filenames are not sent.

How Local Processing Works

Updated May 12, 2026 by PrivateTools

This page shows what stays on your device, what code the page loads, and what happens to your files.

What happens to your file

1

The browser opens the file from your device

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

Your Files

Browser memory

2

The browser does the work

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

Browser processing

WebAssembly + Canvas

3

You save the export

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

Saved locally

What happens, and what does not

What we do not do

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

What to expect

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

What runs in the browser

Main pieces

The tools use browser features and media libraries that run on your device instead of a backend server.

Browser APIs

• WebAssembly (WASM) for heavier 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 where supported
• OffscreenCanvas for rendering outside the main page

FAQ

Try the tools

Open a tool, load a local file, and see how it behaves.

Open Image Sequence Player Open trimy