Is Your PDF Converter Uploading Your Files? How to Check in Your Browser
A PDF converter either converts your file inside your browser or uploads it to a server, and your browser's DevTools Network tab shows you which. The interface rarely says. Both kinds can produce the same Markdown file, but only a converter that never uploads keeps your document private.
You don't have to trust marketing copy to find out which kind you are using. The check takes about five minutes and works on any converter. Run it on the one you use now, and on MarkPrep too.
Client-side vs. server-side, in plain terms
Server-side processing means the work happens on someone else's computer. Your file travels over the network to a server, which runs the conversion and sends the result back.
Microsoft's MarkItDown, for example, is a Python library you install and run on your own machine. A website built on it can work differently. For example, markitdown.tech converts files with MarkItDown on its own server. It also offers to convert some files inside your browser. EPUB and notebook files always go to its server.
Client-side processing means the conversion runs inside your browser tab, using your own device. The file is read from disk into the page's memory and converted there. No network request carries the document anywhere. When you close the tab, it is gone, because it was never anywhere else.
Unlike most privacy questions, this one is something you can verify. You can't see whether a server deletes your file after processing. You can see whether your file was sent to a server at all.
Why "we delete after processing" doesn't settle it
Reputable server-side tools often promise to delete your files right after conversion. That promise may be true, but you have no way to confirm it. It describes servers you can't inspect and logs you will never see. There is no receipt and no button that confirms the deletion. You can't tell a company that deletes on schedule from one whose backups keep a copy for ninety days. Nor can you tell whether it was breached last week.
A deletion promise only covers what happens after an upload. A client-side converter never uploads the file, so no deletion promise is needed. That guarantee is stronger, because the company never received the file.
The audit: DevTools Network tab, step by step
Desktop browsers, including Chrome, Edge and Firefox, have a Network tab in their developer tools that logs every request the page makes. If your file is being uploaded, it shows up there as an outbound request about the size of your file.
- Open your converter in a normal browser tab, but don't convert anything yet.
- Open DevTools. Press
F12orCtrl+Shift+I(Cmd+Option+Ion macOS). You can also right-click anywhere and pick Inspect. - Switch to the Network tab. You will see a table with columns for Name, Status, Type and Size.
- Clear the log with the circle-with-a-slash icon, so you start clean. Tick Preserve log if you want to keep records across page changes.
- Convert your file. Pick a document you will recognise by size. A 5 MB PDF is ideal, because a 5 MB upload is hard to miss.
- Read the log. Sort by the Size column and look at the largest outbound requests. Click any suspicious row and check the request type (
XHRandFetchare the usual ones for uploads) and the payload.
You are looking for a request that goes out carrying your file's worth of data. Uploading a 5 MB PDF produces a request body of several megabytes, sent to the converter's domain or a cloud storage address. A request like that means the converter uploaded your file.
For a sharper test, set Network throttling to a slow preset, such as "Slow 3G", before converting. If the tool uploads, a big file on a throttled connection will crawl. You will watch a progress bar or a pending request sit there for seconds. If conversion takes the same time however slow you set the connection, nothing is being sent.
Reading the results honestly
Signs of a server-side upload:
- A large
XHR,FetchorPOSTrequest with a body roughly the size of your file. - The request goes to an upload address, an API route or a cloud storage bucket.
- Conversion slows down when you throttle the connection.
Signs of client-side processing:
- No outbound request carries your file. You may still see small requests for scripts, fonts or a WebAssembly module. Those are the app's own files loading.
- Conversion works while the Network tab shows no relevant outbound traffic.
- It still works with your network disconnected (more on that below).
The disconnection test is the blunt instrument. Load the converter and convert one file while online, so the browser has the code it needs. Then disconnect from the network and convert another file of the same type. If it works offline, the conversion runs on your device, because there was no server to reach.
Now audit MarkPrep the same way
Run the same procedure on MarkPrep rather than taking our word for it. Open the Network tab, convert a large PDF, and look for an outbound request carrying the file. You won't find one. The conversion runs in JavaScript inside your tab, and OCR for scanned pages runs on a local Tesseract engine built as WebAssembly. Then try the harder test. After one conversion online, disconnect and convert again. It works, because MarkPrep's service worker keeps the app's code in the browser after the first visit.
Two features do send data, and the interface says so where you use them. First, converting a public URL sends a request. MarkPrep's server fetches the web page you named, because browsers block most direct requests to other sites. That page is already public. Second, the optional AI enhance feature passes the converted text to Anthropic, using your own API key, straight from your browser. You will know, because you turned it on.
No other feature sends anything. The PDFs, Word documents, spreadsheets and slide decks you convert stay in the tab, and the Network tab lets you confirm it.
When this matters
For a blog draft or a public research paper, the stakes are low. They change when the document isn't yours to leak:
- Legal contracts under NDA, where sending the text to a third-party server may itself breach the agreement you are trying to read.
- Patient notes and anything with health information, where sending data to a vendor can trigger legal duties.
- Financial records such as statements, deal models and unpublished results, where the document's value is that few people have seen it.
- Locked-down work laptops, where IT policy forbids uploading company files to unapproved services.
In each case, you can show a compliance review the Network log as proof that the file never left the browser.
To test MarkPrep, open DevTools, convert a PDF to Markdown, and watch the Network tab stay quiet. The privacy page lists everything that can leave your device and when.
Try it on your own file
Convert a document and watch the token counter. It's free, needs no account and uploads nothing.