Why uploading a PDF is risky by default
The convenient ‘PDF to Word’ or ‘view online’ sites usually require you to upload the file. Once it's on their server you depend on their security, their retention policy, and their honesty about what they keep. For anything that isn't already public — invoices, IDs, medical notes, internal reports, draft manuscripts — that's a real trade-off.
How local-only reading works
Modern browsers can open and render a PDF on their own. PDFcove picks up the file you choose, hands it to the in-browser PDF engine, and draws the pages on a canvas. There is no upload endpoint to call — the bytes simply stay in the browser tab. Disconnect your network after the app loads and reading still works.
No account, nothing to forget
No email, no password, no signup screen. There's nothing to recover, nothing to leak, and nothing to delete from a database later. Your library and highlights live in this browser's storage on this device; back them up to a file when you want a copy, restore them whenever you like.
What about the read-aloud voice?
Read-aloud uses your operating system's built-in speech engine. The text is spoken on your device, with your installed voices. The PDF isn't sent to a cloud TTS service — there is no ‘upload to narrate’ step.
When privacy matters most
- Legal & medical documents. Contracts, scans, lab results — content you would never want indexed.
- Licensed material. Textbooks and ebooks that come with watermarks or DRM-adjacent obligations.
- Work documents at home. Internal reports you'd rather not push through an unknown third-party service.
- Anything personal. If you wouldn't email it to a stranger, don't upload it to one either.