Skip to main content
DocuShrink
Back to Tools
Technical Transparency & Verifiability

Don't Trust Words.
Verify the Network Yourself.

Most cloud converters upload your private documents to third-party servers. DocuShrink is engineered differently: 100% of document processing, PDF manipulation, image resizing, and OCR runs strictly inside your web browser using WebAssembly and Web Workers.

Live Outbound Document Bytes
Real-time browser activity monitor
0 B Zero Uploads

Interactive Privacy Sandbox

Upload a sample document and run an on-device test to inspect live network isolation.

Active Harness
Choose or drop any test file
Encrypted locally in memory only
Live Network Inspection Stream Waiting for test...
// Ready. No outbound document data detected.
Step-by-step tutorial

How to verify in 3 steps (Chrome, Firefox, Safari, Edge)

1

Open DevTools

Press F12 (or Ctrl+Shift+I / Cmd+Opt+I on Mac), or right-click anywhere and choose Inspect.

2

Select "Network" Tab

Click on the Network tab in the inspector. Filter by Fetch/XHR or watch all outbound entries. Check the "Request Payload / Body" column.

3

Convert Any File

Compress a 50MB PDF or resize an image. Notice that zero outbound file requests are sent. All conversion activity happens purely on your CPU.

What You Will (and Will Not) See in the Network Tab

To keep DocuShrink free without subscriptions, general tool pages load standard Google AdSense display scripts and anonymous static assets. When inspecting DevTools, you will see HTTP entries for font files, UI bundles, and ad impressions.

The critical proof to check: Inspect every request's Payload / Request Body. It will always be 0 bytes for your documents. Your files, filenames, text, and images are never transmitted over the wire. Sensitive tools (Redact, Protect, Sign, Metadata Stripper) run 100% ad-script free with browser-enforced CSP (connect-src 'self' blob: data:).

The Offline Challenge

Try The Airplane Mode Test

Once this website finishes loading, you can completely disconnect your Wi-Fi, Ethernet, or mobile data. Turn on Airplane Mode, drag your files into DocuShrink, and process them. Everything still completes and downloads instantly, proving without doubt that no server is involved.

Privacy by Architecture: Reduced Compliance Exposure

Sending confidential records to third-party cloud servers can trigger complex data processor obligations under privacy frameworks such as GDPR and HIPAA.

Architecture & Compliance Advantage: Processing files locally inside your browser can significantly reduce compliance exposure. Because documents never leave your device and are never transmitted to DocuShrink or external cloud servers, no third-party data processor relationship is created, no server-side retention copies exist, and unauthorized cloud data exposure is prevented by design.

Enforced Content Security Policy: Our sensitive security tools (Redact, Protect, Sign, Metadata Stripper) enforce a strict browser Content Security Policy (connect-src 'self' blob: data:) that mathematically prevents any outbound network socket from opening.