Privacy & Security
Why Free File Converter Websites That Upload Your Files Are a Privacy Risk
Every time you drag a document into a free online converter, you're handing your data to a third-party server. Here's what actually happens — and why 637 cookies on one popular tool should concern you.
What Actually Happens When You Upload a File to a Converter
When you upload a file to an online converter, it is transmitted via HTTP POST to a remote server, processed by server-side software (typically FFmpeg, LibreOffice, or ImageMagick running in a containerized environment), and the converted result is returned to your browser as a download. This entire process takes between 2 and 30 seconds depending on file size and server load.
The critical question is what happens to your file after conversion. Most services claim to "delete files after 1-2 hours" — but during that window, your document exists on infrastructure you don't control. It may be written to disk, cached in memory, replicated across availability zones, logged in error-tracking systems, or included in automated backups. Services like CloudConvert, Zamzar, and Convertio process millions of files daily; the operational reality of immediate and provable deletion at that scale is technically challenging.
Beyond the file itself, metadata about your conversion is almost certainly retained: your IP address, browser fingerprint, timestamps, file types, file sizes, and conversion patterns. This metadata builds behavioral profiles that are increasingly valuable to advertising networks and data brokers.
Data exposed in a typical server-side conversion:
- Full file contents (documents, images, audio, video)
- Embedded metadata (EXIF data, author names, revision history)
- IP address and approximate geolocation
- Browser fingerprint and device information
- Conversion patterns (what formats you use, how often)
- Referring page (what you were doing before converting)
- Third-party cookies from ad networks and analytics providers
The iLovePDF Cookie Scandal: A Real-World Example
The privacy problem with free file converters isn't theoretical — it was dramatically illustrated when a viral Reddit thread on r/YouShouldKnow revealed that iLovePDF, one of the most popular PDF conversion tools with over 30 million monthly visits, was setting 637 cookies on users' browsers.
The post, titled "YSK: ilovepdf.com loads 637 cookies when you visit it," gained tens of thousands of upvotes and sparked widespread community investigation. Users opened their browser developer tools and confirmed the count. Some reported even higher numbers — over 700 cookies when accounting for third-party scripts that loaded asynchronously.
To understand what 637 cookies means: a typical privacy-respecting website sets between 3 and 10 cookies (session ID, preferences, maybe one analytics cookie). A cookie count of 637 indicates an extraordinarily aggressive tracking infrastructure. These cookies come from dozens of different domains including Google Ads, Facebook Pixel, Criteo, Taboola, Outbrain, and numerous lesser-known ad-tech vendors. Each cookie represents a separate entity that can track your browsing behavior, build a profile of your interests, and target you with personalized advertising.
The community reaction was swift. Commenters pointed out the irony: a service trusted with sensitive legal documents, financial statements, and personal records was simultaneously running one of the most invasive tracking operations on the web. One commenter noted: "If they're this aggressive about tracking how I use their website, what are they doing with the actual files I upload?"
The incident revealed a structural problem: free file conversion services need revenue, and when the product is free, the user's attention and behavioral data become the product. The 637 cookies weren't a bug — they were the business model.
The Hidden Costs of "Free" File Converters
Free file converters aren't actually free. They monetize your usage through multiple channels, and understanding these revenue streams reveals why your files and data are valuable to them.
Your Files as Training Data
Several major tech companies have acknowledged using user-uploaded content for AI and machine learning model training. While most file converter services don't explicitly state this in their primary privacy policy, terms of service often include broad language granting the operator rights to "use, reproduce, modify, and create derivative works" from uploaded content. When services process millions of documents, images, and spreadsheets daily, that data is extraordinarily valuable for training document understanding models, OCR systems, and format conversion algorithms.
Metadata Harvesting
Every file you convert carries metadata. PDFs contain author names, creation dates, software versions, and sometimes embedded comments or tracked changes. Images contain EXIF data including GPS coordinates, camera models, and timestamps. Documents contain revision histories and collaborator lists. Even after conversion, this metadata may be retained by the service for analytics purposes. If you're converting photos from a family vacation, the GPS data reveals your home address. If you're converting business documents, the metadata reveals your software stack and organizational structure.
Terms of Service You Didn't Read
Many popular converter services include clauses that grant them broad rights over uploaded content. Common language includes: "By uploading content, you grant us a worldwide, non-exclusive, royalty-free license to use, reproduce, and distribute your content for the purpose of providing and improving our services." This language, while seemingly limited to "providing the service," can be interpreted broadly. Some services additionally reserve the right to retain anonymized or aggregated data indefinitely, and "anonymized" file content from documents can still reveal patterns about your work and life.
Ads and Redirect Loops
The user experience on free converter sites tells its own story. Ad overlays, countdown timers, fake download buttons, pop-under windows, and push notification requests are industry-standard. Some services require you to navigate through multiple pages of advertisements before reaching your converted file. This "attention arbitrage" — forcing you to view ads in exchange for a service that costs pennies of compute to provide — generates revenue that funds the 637-cookie tracking infrastructure. Your attention, measured in seconds of ad exposure, is being sold to the highest bidder while your file sits on their server.
Convert files without ever uploading them.
Prescosoft Local File Converter processes everything in your browser. Images, video, audio, documents, spreadsheets, archives — all local, all private.
Try Local File ConverterServer-Side vs Client-Side Conversion: The Technical Difference
The fundamental distinction is where the conversion computation executes. Server-side converters process files on remote infrastructure; client-side converters process files in your browser using WebAssembly, Canvas APIs, and native JavaScript libraries. This single architectural choice determines whether your data leaves your device.
Here's a direct comparison of the two approaches:
| Factor | Server-Based | Browser-Based |
|---|---|---|
| Data leaves device? | Yes — uploaded to external server | No — processed in browser memory |
| Conversion engine | Server-side FFmpeg/LibreOffice | WebAssembly (ffmpeg.wasm, WASM codecs) |
| Works offline? | No — requires internet upload | Yes — after initial page load |
| Third-party tracking | Extensive (ads, analytics, beacons) | None required |
| Breach risk to your files | Files on server are breachable | No server copy exists to breach |
| File size limits | Server bandwidth costs limit free tier | Limited only by device RAM |
What "Runs in Your Browser" Actually Means
Modern browsers are powerful computing platforms. WebAssembly (WASM) allows compiled C/C++/Rust code to run at near-native speed inside the browser. The Prescosoft Local File Converter uses ffmpeg.wasm — a WebAssembly port of the industry-standard FFmpeg library — to perform video and audio conversion directly in your browser tab. For images, the Canvas API and OffscreenCanvas provide pixel-level manipulation. For documents, libraries like PDF-lib handle PDF operations, SheetJS handles spreadsheets, and JSZip handles archive manipulation.
These are the same algorithms used by server-side services — FFmpeg is literally the same software that iLovePDF, CloudConvert, and Zamzar run on their servers. The only difference is where the CPU cycles happen: on their hardware or yours. Since 2020, WebAssembly has been supported by all major browsers (Chrome, Firefox, Safari, Edge) with multi-threading support via SharedArrayBuffer, making client-side conversion viable for files up to several hundred megabytes.
Local processing eliminates the privacy risk entirely because there is no moment at which your file exists outside your device's memory. There's no upload, no transit, no server storage, no third-party access — not even theoretically.
How to Verify a Converter Doesn't Upload Your Files
Don't trust marketing claims — verify behavior. These three methods let you independently confirm whether a file converter transmits your data to external servers.
Check the Network Tab
Open DevTools (press F12 or Ctrl+Shift+I), navigate to the Network tab, and filter by "All." Load the converter page, clear the network log (⊘ icon), then perform a file conversion. If you see HTTP POST or PUT requests to external domains during the conversion process — especially requests containing your file in the request body or as multipart form data — the tool is server-side. A truly client-side converter will show zero outbound file-transmission requests during processing. You may see the initial WASM module download (typically a one-time ~25MB load), but no subsequent file uploads.
Test with Canary Data
Create a test file containing a unique, identifiable string — for instance, a text document with the phrase "CANARY_TEST_7f3a9b2e_UNIQUE" embedded in it. Upload this file to the converter. After conversion, search the Network tab for that specific string. If it appears in any outbound request payload, query parameter, or cookie value, your data is being transmitted. This technique is used by security researchers to detect data exfiltration that might be disguised or obfuscated in standard network traffic.
Read the Privacy Policy
Search the service's privacy policy for specific language. Trustworthy client-side tools will state explicitly: "Files are processed entirely in your browser and never transmitted to our servers." Be wary of ambiguous language like "we do not permanently store your files" (which implies temporary storage does occur) or "files are processed securely" (which doesn't specify where processing happens). If the privacy policy mentions "third-party service providers who assist in processing," your files may be routed through additional infrastructure beyond the primary service's servers. For more on protecting metadata in personal files, see our guide on organizing photos by date taken — a workflow that's especially risky with server-side tools.
When Server-Side Converters Are Acceptable
Server-side converters aren't inherently malicious — they solve a legitimate need for format conversion, and there are scenarios where the convenience tradeoff is reasonable.
Non-sensitive files: Converting a public domain image to WebP, resizing a Creative Commons photo, or converting a sample dataset for testing are all low-risk operations. If the content is already publicly available or contains no personal or proprietary information, the privacy risk of uploading to a server is minimal. Public domain images, stock photos with appropriate licensing, and test data are all reasonable candidates for server-side conversion.
Enterprise contracts with DPAs: Large organizations may negotiate Data Processing Agreements (DPAs) with converter services that contractually bind the provider to specific data handling requirements. Services like CloudConvert Business and Adobe's online tools offer enterprise tiers with contractual guarantees about data deletion, non-retention, and compliance with GDPR, HIPAA, or SOC 2 requirements. These come at a cost — typically $20-100/month per seat — because without tracking revenue, the service needs direct payment.
Acknowledging convenience tradeoffs: Client-side conversion using WebAssembly is powerful but not yet universal. Some obscure proprietary formats (like certain CAD files or legacy Microsoft formats) may lack browser-compatible conversion libraries. Very large files (multiple gigabytes) may strain browser memory limits. In these edge cases, a trustworthy server-side service with a clear privacy policy and verifiable deletion practices is a reasonable fallback — just never for documents containing personal data, financial information, or business secrets.
For a detailed technical walkthrough of browser-based conversion, see our companion article on how to convert files in the browser.
Frequently Asked Questions
Are file converters safe?
It depends entirely on how they process your files. Server-side file converters upload your documents to remote infrastructure where they are processed, temporarily stored, and potentially logged. Client-side file converters that use WebAssembly or Canvas APIs process everything locally in your browser and never transmit your files over the network. The safety of a converter is directly proportional to how much of your data leaves your device. If you need to convert sensitive files, always use a verified client-side tool like Prescosoft Local File Converter.
Do online converters upload my files?
Most popular free file converters — including iLovePDF, SmallPDF, CloudConvert, and Zamzar — upload your files to their servers for processing. This is visible in their network activity: you can observe HTTP POST requests containing your file data in the browser DevTools Network tab. Some services claim to delete files after 1-2 hours, but this deletion window still means your data exists on third-party infrastructure where it could be breached, subpoenaed, or retained despite policy claims.
How can I convert files privately?
Use a client-side file converter that processes files entirely in your browser using WebAssembly (like ffmpeg.wasm for media), Canvas API for images, or libraries like PDF-lib and SheetJS for documents. These tools never send your files to any server. You can verify this by opening DevTools Network tab (F12) and confirming no outbound requests occur during conversion. Prescosoft Local File Converter is one such tool — 100% browser-based with zero uploads.
What is a client-side file converter?
A client-side file converter is a web application that performs file format conversion entirely within your browser using technologies like WebAssembly (WASM), the Canvas API, Web Codecs API, and JavaScript libraries. Unlike server-side converters, no file data leaves your device. The conversion happens in your browser's memory using the same algorithms that server-based tools use, but executed locally. Examples include ffmpeg.wasm for video/audio, Sharp (via WASM) for images, and PDF-lib for PDF manipulation.
Is iLovePDF safe?
iLovePDF uploads your files to their servers for processing and was exposed setting 637 cookies on users' browsers in a viral Reddit investigation on r/YouShouldKnow. While they claim to delete files after 2 hours and use HTTPS in transit, your documents still reside on their infrastructure during processing. The 637-cookie count indicates extensive third-party tracking including ad networks, analytics providers, and data brokers. For sensitive documents (contracts, financial records, personal data), iLovePDF and similar server-side services present a measurable privacy risk.
Can converters steal my data?
Server-side file converters have technical access to every file you upload. While most legitimate companies don't intentionally steal data, they do retain it temporarily (typically 1-24 hours), may use aggregated data for analytics or AI training, and can be compelled to hand over stored files via legal requests or experience data breaches. The 2017 iLovePDF security breach exposed 44 million user email addresses and encrypted passwords. Any file on their servers during a breach is potentially compromised regardless of their privacy policy.
Convert files without ever uploading them.
Prescosoft Local File Converter processes everything in your browser. Images, video, audio, documents, spreadsheets, archives — all local, all private.
Try Local File ConverterRelated Guides
How to Convert Files Directly in Your Browser
A step-by-step technical guide to browser-based file conversion using WebAssembly and modern web APIs.
How to Organize Photos by Date Taken (Without Risking Privacy)
Why EXIF metadata in your photos is sensitive, and how to organize them locally without uploading to cloud services.
Prescosoft Local File Converter
The privacy-first file converter that processes images, video, audio, documents, and archives entirely in your browser.