How Local Processing Works

Q: Can ConvertUnlimited see my files?

For supported local-processing flows, ConvertUnlimited does not provide a server-side upload endpoint for selected file contents. The public site may still load ads and analytics.

Q: Which version should I use for sensitive documents?

Use the privacy build for privacy-sensitive workflows. It is designed without ads, analytics, remote fonts, or third-party runtime scripts.

ConvertUnlimited is built around browser-native processing. Supported file tools process selected file contents locally in your browser using your own device's hardware.

Translation status

This guide is currently shown in English for this locale. Tool links still point to localized routes where available.

What this guide explains

ConvertUnlimited is built around browser-native processing. Supported file tools process selected file contents locally in your browser using your own device's hardware.

Technical scope

This guide describes browser-based file workflows, format tradeoffs, and ConvertUnlimited processing boundaries for supported tools.

What is Local Processing?

Many online converters are upload services: files are sent to a remote server, processed there, and sent back. Local processing avoids that round trip for supported flows. Selected file contents are handled in browser memory by client-side scripts.

Browser APIs used

ConvertUnlimited uses browser standards for supported local workflows: - HTML5 Canvas API: redraws and re-encodes images to change formats. - File & Blob APIs: handle selected files as local data streams. - Object URLs: create downloadable outputs in the browser tab. - Vendored client-side libraries: support selected PDF, archive, and image operations where browser APIs need help.

Comparison: Local vs. Upload

Feature	Upload-Based Sites	ConvertUnlimited
Privacy	Higher exposure risk because files are uploaded	File contents are processed locally in your browser
Security	Server breach risk	No server-side upload endpoint for supported local flows
Wait Time	Upload + Download time	Local in-browser processing
Data Usage	Upload + download	Static page load, then local processing for supported flows
Internet	Required for processing	Not required after load

Operational advantages and limits

For supported workflows, avoiding a server-side upload step reduces transfer time and file-exposure surface. Processing speed still depends on device CPU, available memory, browser support, and source file size.