Skip to content
    PDFWix logo — free browser-based PDF toolsPDFWix
    PDFWix processes 34 of 35+ tools entirely in your browser via WebAssembly — your files never leave your device. No server upload occurs for compress, merge, split, sign, rotate, watermark, organize, extract, remove pages, crop, compare, fill forms, edit, redact, and all conversion tools. Protect PDF and Unlock PDF use in-memory server processing — never written to disk, freed immediately after download.

    Security & Privacy at PDFWix

    Most PDF tools want you to upload a contract, a tax return, or a passport scan to a server you've never heard of. We built PDFWix to do the opposite: process your file in your browser whenever the operation allows, and keep server processing in-memory and short-lived when it doesn't.

    Quick answer

    PDFWix processes 34 of its 35+ tools entirely in your browser using WebAssembly (WASM) — your PDF file is never uploaded to any server. The two server-side tools (Protect PDF and Unlock PDF) process files in-memory only over TLS 1.3, and the in-memory buffer is freed immediately after the response is returned. No files are written to disk. No files are retained.

    Where your file is processed

    Most PDFWix tools — including Merge, Split, Compress, Rotate, Edit, Sign, JPG to PDF and PDF to JPG — run entirely in your browser using pdf-lib, PDF.js and the browser's built-in crypto APIs. Your file is never sent to our servers. We literally cannot see it.

    A small number of tools — currently Protect PDF and Unlock PDF — use a server-side function (qpdf compiled to WebAssembly) because the password handling is too fragile to do reliably in the browser. For these, your file is sent over HTTPS, processed in memory only, and the response is returned immediately. We do not write the file to disk and we do not keep a copy.

    Encryption in transit

    Every connection to pdfwix.com uses HTTPS. TLS configuration is managed by our hosting provider.

    Encryption and transport security

    All connections to pdfwix.com use TLS 1.3 — the current cryptographic standard for web transport security. TLS 1.3 removes support for legacy cipher suites and significantly reduces connection latency versus TLS 1.2.

    For server-side tools (Protect PDF, Unlock PDF): the two tools that use server processing encrypt file data in transit using TLS 1.3. Files are processed using AES-256 (NIST FIPS 197) encryption for the output (for Protect PDF) — the same standard required by US FIPS 140-2 and most enterprise document security policies. AES-256 with a strong password provides computational security that current technology cannot break in a practical timeframe.

    For browser-side tools: no file data is transmitted at all. TLS applies only to page and script loading.

    What we log

    • For browser-side tools: the tool slug, success/failure, input and output size in bytes, and how long the operation took. No file contents, no file names.
    • For server-side tools: the same fields. We do not store the file or the password you provide.
    • If you sign in: we keep a list of your tool runs (filename and tool only — never the file itself) so you can re-find them on the History page. Delete any entry from there at any time.

    What we never log or share

    • The contents of your PDFs or images.
    • The passwords you use with Protect PDF or Unlock PDF. They are used to perform the operation in memory and discarded with the response.
    • Your data sold to third parties. There is no marketing data resale.

    Open-source foundation

    The PDF parsing primitives we rely on are open source and audited by the wider community: pdf-lib, Mozilla's PDF.js, and qpdf compiled to WebAssembly.

    Compliance posture

    • GDPR: we minimise personal data collection. Browser-side tools generate no personal data tied to your file.
    • HIPAA: not certified. If you handle PHI, we recommend using only browser-side tools.

    Client-Side PDF Manipulation — How PDFWix Processes Your Files

    PDFWix uses client-side PDF manipulation for the majority of its tools — meaning all PDF processing happens inside your browser using WebAssembly, with zero data transmitted to any server.

    WebAssembly (WASM) is a low-level bytecode format that runs at near-native speed inside modern browsers. PDFWix compiles PDF processing libraries — including Ghostscript for compression and PDF manipulation — to WebAssembly, so they execute directly on your device. This is WebAssembly PDF processing in practice.

    WebAssembly (WASM) is a binary instruction format that runs inside the browser sandbox at near-native speed. PDFWix compiles Ghostscript — the professional-grade PDF engine — to WebAssembly, then loads and executes it entirely within your browser tab. Your PDF bytes are passed to the WASM module in your browser's memory and never transmitted over the network. You can verify this: open your browser's DevTools Network tab, upload a PDF, and observe that no file upload request is made to any external endpoint. The only network requests are to load the WASM module itself (once, on first use) and to return the processed file to your device. For technical documentation on WebAssembly, see: MDN WebAssembly documentation

    The result: your PDF file is loaded into browser memory, processed entirely on your CPU, and the output is written back to your device. At no point does the file data cross a network boundary. Data residency — your device only.

    This architecture is fundamentally different from cloud-based PDF tools that upload your file to a remote server for processing:

    Cloud-based processing (most PDF tools): Your file → uploaded over internet → processed on remote server → result downloaded back → file stored on server until deletion.

    Client-side processing (PDFWix — 34 tools): Your file → loaded into browser memory → processed by WebAssembly on your device → output saved to your device → zero server involvement. This is our zero server storage architecture.

    For the two tools that require server processing (Protect PDF and Unlock PDF):

    • File transmitted over TLS 1.3 (HTTPS)
    • Processed in volatile server memory only
    • Never written to disk at any point
    • Memory buffer freed immediately after response is returned
    • No file retention, no logging of content

    This no-disk-write processing server architecture means even server-processed files leave zero persistent traces after your download is complete.

    Frequently asked questions

    Can PDFWix see my files?

    For 34 of 35+ tools: no. Processing happens in your browser via WebAssembly — the file never leaves your device and PDFWix servers never receive it. For Protect PDF and Unlock PDF: the file is processed in server memory only (never written to disk) and the in-memory buffer is freed immediately after your download begins. No PDFWix employee can access your file at any point.

    Is PDFWix GDPR compliant?

    Yes. PDFWix does not collect or process personal data from uploaded documents. The browser-based architecture for 34 tools means no personal data in documents is transmitted to PDFWix. For the two server-side tools, in-memory processing with immediate buffer clearing means no personal data is retained after your session. PDFWix does not use uploaded document content for any purpose other than performing the requested operation.

    What encryption does PDFWix use for Protect PDF?

    PDFWix Protect PDF uses AES-256 encryption — the strongest standard encryption supported by the PDF specification and the same standard used by US government agencies under FIPS 140-2. The password you set is never stored or transmitted to PDFWix. Only you know the password — PDFWix cannot recover it if forgotten.

    MCP server & Claude connector security

    PDFWix publishes a remote MCP (Model Context Protocol) server so assistants such as Claude can run PDF operations on your behalf. It exposes 14 headless tools: inspect a PDF, extract text, merge, split, remove pages, reorder pages, rotate, add page numbers, add watermark, compress, repair, images to PDF, unlock, and open a file in PDFWix.

    Transport and authentication

    • Streamable HTTP over TLS 1.3 — no plaintext transport is accepted.
    • OAuth 2.1 with Dynamic Client Registration. No anonymous or lazy access: every tool call is bound to an authenticated PDFWix account.
    • Access tokens are scoped per user; a token can never read or write another account's files.
    • Creating an account is free and never asks for a credit card. Sign in with Google or email.

    File handling and 24-hour lifecycle

    • Inputs are accepted as an HTTPS URL or base64 data, capped at 100MB per file.
    • Processing runs in an isolated server function; nothing is shared between accounts or between requests.
    • Output files are written to a private, per-user storage area that is unreadable without a signed link.
    • Download links are cryptographically signed and expire after 24 hours. Expired objects are pruned automatically.

    No training, no content logging

    • Document contents and extracted text are never used to train AI models and are never stored in our database.
    • We log only operational metrics for each run: tool name, byte counts, duration, and success or failure.
    • No conversation data from the assistant is collected beyond the parameters needed to perform the requested operation.
    • Tool descriptions contain plain functional text only — no hidden instructions, no encoded content, no references to external instruction sources.

    Scope limits

    The MCP server performs document manipulation only. It transfers no money, holds no payment credentials, generates no images, video, or audio with AI models, and surfaces no sponsored or promoted content. Operations that need a visual canvas — signing, redaction, form filling, cropping, and visual editing — are not performed server-side; the connector returns a PDFWix browser link instead.

    To report an issue with the MCP server, email support@pdfwix.com.

    Reporting a security issue

    If you believe you've found a vulnerability, please email support@pdfwix.com. We respond within 72 hours.

    Verifiable claims

    You don't have to take our word for any of this. Open the browser DevTools Network tab, run a tool like Merge PDF, and confirm that no request carrying your file content is sent. The merge happens entirely in JavaScript on your device.

    For a practical overview of how browser-based processing protects your files, see the fastest, most private way to get PDF work done.