Guides
Why Server-Side Paste Tools Leak Secrets — Zero-Upload Architecture
Learn why pasting .env files, JWTs, customer CSVs, or contracts into cloud converters leaks data—and how to verify 0 bytes uploaded locally.
Quick Answer: Unlike traditional online paste utilities that transmit `.env` files, JWTs, customer CSVs, or contracts to remote servers, TxtTo runs every parser, PDF.js worker, spreadsheet converter, and PII redactor strictly inside your browser's RAM. Verify zero outbound traffic in DevTools Network tab—even in Airplane Mode.
How TxtTo guarantees zero-upload execution
Every single parser, converter, PDF.js worker, spreadsheet engine, and ZIP archiver inside TxtTo executes deterministically inside your own browser's JavaScript runtime. No conversion endpoints exist on the server.
DevTools -> Network tab -> Filter: Fetch/XHR
Action: Paste JWT / Drop .env / Convert 500-row CSV
Expected uploaded bytes: 0 B (works with Wi-Fi turned off)Test .env to JSON with Network tab open
| Evaluation Criterion | Traditional Server Paste Sites | TxtTo Browser-Local Architecture |
|---|---|---|
| Network payload during run | POST/XHR body logged by remote API | 0 bytes sent (verifiable in DevTools) |
| Offline / Airplane Mode | Fails immediately without backend | Runs 100% offline once SW cached |
| .env, JWT & PII handling | Exposed to server access logs & CDNs | Masked in browser RAM + .redactkey vault |
| Binary PDF / XLSX / DOCX | Uploaded for remote extraction queues | Self-hosted PDF.js & OOXML workers in RAM |
Inspecting JWTs and comparing configs completely offline
Once cached by the browser Service Worker, TxtTo's converters even work with your internet connection disabled. Decode URL-safe JWT claims or diff production vs. staging JSON configs cleanly inside local RAM.
Smart mis-drop routing without telemetry
File magic-byte probing reads only the first 64 KB slice via `File.slice()` in memory to detect BOM, encoding, and delimiters—never sending file hashes or metadata outward.
References
Frequently asked questions
How can my security team verify TxtTo never uploads pasted text?
Open browser DevTools -> Network tab (or switch on Offline throttling / Airplane Mode), load any tool, paste data or drop a file, and run conversion—zero XHR/Fetch/Beacon requests occur.
What happens to text if I switch languages mid-edit?
Your workspace snapshot stays strictly inside local browser memory across locale switches and clears permanently when you close the tab.
Does TxtTo load external CDN scripts for PDF or spreadsheet parsing?
Never. All assets, fonts, and the PDF.js worker are self-hosted directly from txtto.app.
Related formats
Related Comparisons
Related Guides
- Offline JWT Decoding, Base64URL & Semantic JSON DiffingInspect JWT headers and claims, encode Base64URL without padding, run key-order-agnostic semantic JSON diffs, and scrub Bearer tokens offline.
- How to Anonymize Text, Contracts & Logs for ChatGPT LocallyReplace names, IBANs, contracts, and secrets with reversible [[TYPE-NN]] tokens locally in browser RAM before pasting prompts into ChatGPT or Claude.
- How to Mask CSV & JSON Customer Data Before AI AnalysisAnonymize sensitive CSV columns, scale financial revenue proportionally (×k), and mask nested JSON keys locally in browser RAM without breaking file syntax.