Answer first: Before you drop a contract, payslip, or ID scan into any "free online PDF tool," open DevTools → Network, clear the log, then run the tool. If you see a multipart upload or a request to api.*.com carrying your file bytes, that document already left your machine — privacy policy wording does not undo that. Prefer tools that process files in the tab (Canvas / pdf-lib / WASM). Below is a repeatable audit plus a private compress → merge workflow you can finish in under five minutes.
Why this is hot right now
Over the past week, DEV and GitHub have been full of the same pattern: privacy-first PDF/image suites that refuse to upload (browser-only WASM/JS tools, CSP connect-src 'self' experiments, “verify with Network tab” posts). The shared pitch is simple — cloud converters are convenient until the file is regulated or embarrassing. The useful takeaway for working developers is not “another SaaS exists,” but a habit: treat every online converter as untrusted until the Network panel says otherwise.
The 5-minute Network-tab audit
- Open Chrome/Firefox/Edge DevTools (
F12orCmd+Opt+I). - Go to the Network tab. Check Preserve log. Click the clear (🚫) button.
- Optionally filter by Fetch/XHR (or disable cache and leave “All” on).
- Pick a non-sensitive test PDF or JPG (a blank page is fine).
- Run the online tool’s compress / merge / convert action.
- Watch for:
-
POST/PUTwith a large payload right after file pick - Hosts like
api*,upload*, CDN buckets, analytics SDKs firing on drop - A progress bar that only moves while a request is in flight
-
Pass criteria: while the file is being processed, you should see no request that carries the document body. Asset loads for the app itself (JS, WASM, workers) are normal. File bytes going to a third-party origin are not.
Extra check: after the page has loaded once, flip to airplane mode and try again. If the tool still works offline, upload-to-server architecture is off the table for that action.
A private compress → merge workflow (local browser)
Here is a practical path when you need to ship a smaller, single PDF of scans or screenshots without handing them to a random host.
Step 1 — Shrink heavy photos first
Phone photos and scans are often 3–8 MB each. Compress them locally before they become PDF pages.
Use a browser-local image compressor (e.g. Lizely Image Compressor) in your browser:
- Drop JPG/PNG/WebP files onto the page.
- Drag the quality slider (start around 60–80% for photos).
- Use the split preview to confirm text and edges still look sharp.
- Download the compressed copies.
Tip: WebP often wins 20–30% over JPEG at similar visual quality when the destination is the web. Stick with JPEG when the next system only accepts .jpg.
Step 2 — Combine documents without an upload
When you have several PDFs (or several exports) that should be one attachment:
Open Merge PDF:
- Browse or drag two or more PDFs.
- Reorder with the up/down controls so the page sequence matches what the recipient expects.
- Download the merged file.
Merging happens with client-side page copy (lossless concatenation of page objects) — text stays selectable and vectors stay crisp. Password-protected inputs need unlocking first; the tool will skip locked files rather than guess.
Step 3 — Optional: shrink an image-heavy PDF
If the result is still too large for email or a portal cap, try a bounded local pass with a browser-local PDF compressor. It re-encodes eligible embedded JPGs in-browser (with honest limits). Keep the original and spot-check pages before you send anything.
What “local” actually buys you
| Concern | Cloud converter | In-browser tool |
|---|---|---|
| File leaves device | Yes (by design) | No (bytes stay in tab memory) |
| Queue / file-size gate | Common | Bound by your RAM, not a free tier |
| Offline after first load | Rare | Often yes |
| Auditability | Privacy policy prose | Network tab + airplane mode |
None of this replaces good judgment (malware-laden PDFs are still PDFs). It does remove an unnecessary third party from everyday compress/merge chores.
Soft wrap-up
Make the Network-tab check a reflex. Once you trust a tool’s architecture, a local compress → merge loop covers most “please send one smaller PDF” requests without uploading sensitive material.
Lizely’s browser tools (image compress, merge PDF, and friends) run on-device with no signup — useful when you want the workflow above without installing desktop software.
Top comments (0)