Trust Center

Limitations of browser-native processing

Browser-native processing is useful for many privacy-sensitive utility workflows, but it is not a replacement for every converter, a device sandbox, or a guarantee that every file type will work.

Short answer

Use ConvertUnlimited when the workflow is supported by your browser and device. Use desktop or server-side workflows when files are too large, formats are unsupported, or automation is required.

Build boundary

The public site may load ads and analytics. The privacy build at privacy.convertunlimited.com is the no-ads, no-analytics review target.

Verification path

Use the verification page, browser DevTools, and repository privacy tests to inspect the behavior instead of relying on marketing language.

Technical limitations

Browser support: Format decoding and encoding depends on the browser.
Device memory: Large images, PDFs, or batches can exhaust tab memory.
Processing speed: Mobile devices may be slower or more constrained than desktop browsers.
Output verification: Sensitive outputs should be inspected before sharing.

Privacy limitations

Compromised device: A compromised browser, operating system, or malicious extension can observe page data.
Host-level injection: Privacy deployment depends on the host not injecting runtime scripts.
Downloaded files: Once a file is downloaded or shared elsewhere, it leaves the page's control.
Visible content: Metadata removal does not remove faces, addresses, text, or other visible pixels.

Trust topics

FAQ

When should I avoid browser-native tools?

Avoid them when files are too large for your device, formats are unsupported, or you need automation/API workflows.

Does metadata removal remove visible private information?

No. It removes metadata by re-encoding supported images, but visible pixels remain.

Does the privacy build protect against extensions?

No. Browser extensions operate outside the app's control.

Review note

Trust documentation reviewed: May 2026. These pages describe the current public and privacy-build architecture and should be updated when deployment, telemetry, or runtime dependencies change.