Privacy by design

How your files are processed

We choose the safest practical execution path for each operation. Page arrangement can run locally; conversions and specialist document processing need the server.

Local processing

The PDF is read and rebuilt inside your browser. Its contents are not uploaded to PDF Converter. Processing runs in a background Web Worker so the interface remains responsive.

  • No document upload
  • No server copy to delete
  • Works after the required scripts have loaded

Server processing

The file is securely uploaded for operations that need specialist software, reliable high-memory processing or formats browsers cannot safely reproduce.

Processing mode by tool

Scan to PDFServerImages to PDFServerWord to PDFServerPDF to ImageServerPDF to TextServerMerge PDFLocalOrganize PDFLocalSplit PDFServerRotate PDFLocalPowerPoint to PDFServerExcel to PDFServerHTML to PDFServerDelete PDF PagesLocalCompress PDFServerResize PDFServerWatermark PDFServerSign PDFServerProtect PDFServerAdd Page Numbers to PDFLocalCrop PDFServerUnlock PDFServerRepair PDFServerOCR PDFServerPDF to WordServerRedact PDFServerPDF to PDF/AServer

Why not run everything locally?

Browser memory varies widely, especially on phones. OCR, compression, Office conversion, encryption, repair, PDF/A, redaction and image rendering depend on specialist engines or stronger resource controls. Moving them into the browser would reduce reliability or output fidelity, so they remain accurately labelled as server processing.