How we handle your files

Exactly what happens to your files, tool by tool. No vague promises.

Tools that run on your device (52)

These tools load their processing code into your browser – PDF.js, pdf-lib, QPDF and Tesseract (the last two compiled to WebAssembly) – and process the file in memory on your computer or phone. The file is not uploaded to PDF Converter. Results are created as temporary download links that are released when you leave the page.

A few things are fetched from the network while you use them: the processing code itself (from our site), and for OCR in languages other than English, the language model (from the jsDelivr CDN). Neither request contains your document.

Tools that use our server

• File to Images
• Word to PDF
• Excel to PDF
• PowerPoint to PDF
• File to PDF

When you choose the server engine (Word, Excel) or use PowerPoint to PDF, the file is sent over HTTPS to our conversion server, converted with LibreOffice in an isolated temporary folder, returned in the same response, and deleted immediately. A sweeper deletes any leftover temporary files after 15 minutes. Files are not used for anything else.

What we do store

• If you create an account: your email, a salted password hash (scrypt), plan and hashed API keys.
• Payment details are handled by Stripe; we store only the Stripe customer and subscription IDs.
• Operational logs: request path, status, timing and approximate size, kept for up to 30 days for abuse prevention.

Validation and safety

• Files are checked for their real type (file signature), not just the extension, before processing.
• Scripts inside PDFs and HTML are never executed. HTML conversion runs in a sandbox.
• Server conversions run with time and size limits, without a shell, and with a fresh LibreOffice profile per job.

Found a security issue? Email support@dpdfconverter.com.