Guide
On-device vs cloud file conversion
The practical difference
On-device conversion keeps the full job on your phone or computer. Server-side conversion uploads a file to infrastructure that performs the work. Server-side processing can support heavier formats and models, but the operator must have a narrowly controlled way to process the plaintext.
How OMNIvour currently works
Conversions marked On-Device run in your browser on the web: the file is not uploaded, and OMNIvour records only the formats and file size to count the conversion toward your daily limit.
For every other conversion, OMNIvour creates a per-job AES-256-GCM key in the client and encrypts the file before upload. The encrypted object and a short-lived job capability are made available to an authorized worker. The per-job key is sent over TLS to that worker so it can decrypt the input, run the requested conversion, re-encrypt the output, and clean up its short-lived working data.
This server-side design protects stored objects and limits worker authority, but it is not on-device conversion and it is not encryption that prevents the conversion worker from accessing plaintext.
At a glance
| Feature | On-device conversion | OMNIvour server-side |
|---|---|---|
| Where conversion runs | On your phone or computer | On an authorized OMNIvour worker |
| Upload required | No | Yes - encrypted before upload |
| Plaintext processing | Stays on the device | Transiently available inside the isolated job worker |
| Retention | No server-side file retention | Inputs: up to 24 hours; outputs: 24 hours to 30 days by tier |
| Heavy formats and AI | Limited by device capability | Handled by Galileo, OMNIvour's self-hosted converters and models |
Choosing the right tool
Use a genuine on-device converter when a file must never leave the device and the required format is supported locally. Use OMNIvour when client-encrypted storage, short retention, cross-format conversion, and Galileo - OMNIvour's self-hosted AI - fit your risk model.
Do not upload material whose policy or legal requirements prohibit transient processing by a service provider.
Frequently asked questions
What is on-device file conversion?
On-device conversion runs entirely on your phone or computer. No file is uploaded. Capability and performance depend on the device and converter.
Does OMNIvour currently convert files on-device?
Yes, for common formats. On the web, image (PNG, JPG, WebP, BMP, SVG), data (CSV, TSV, JSON) and text (Markdown, HTML, TXT) conversions marked On-Device run in your browser, and the file is not uploaded. Everything else is encrypted on your device and converted on our servers.
Can an OMNIvour worker read my file?
Transiently, yes. The app sends the per-job key over TLS to the authorized worker so it can decrypt, convert, and re-encrypt the file. The key is not stored in the application database.
Does OMNIvour send files to a third-party AI API?
OMNIvour's AI-assisted path uses models operated for OMNIvour rather than a third-party generative-AI API. Infrastructure providers still process data on OMNIvour's behalf.
How long does OMNIvour retain files?
Inputs expire within 24 hours. Outputs expire after 24 hours on Free, 7 days on Pro and Lifetime, and 30 days on Omni.
Try OMNIvour
Review the Privacy Policy for provider and retention details, then start a conversion if the architecture fits your needs.