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.

3 min read

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.

The hidden risk inside routine developer paste boxes

Every day, developers paste `.env` database credentials, production JWT tokens, internal API responses, and customer CSV exports into random 'free online formatter' tabs.

Many legacy web converters post inputs to backend APIs for formatting, logging raw request bodies in access logs, analytics replays, or third-party caches.

  • JWT payloads contain user IDs, roles, emails, and tenant claims.
  • `.env` files carry live database connection strings and API keys.
  • Customer CSVs and PDF contracts trigger compliance violations on upload.

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.

text
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 CriterionTraditional Server Paste SitesTxtTo Browser-Local Architecture
Network payload during runPOST/XHR body logged by remote API0 bytes sent (verifiable in DevTools)
Offline / Airplane ModeFails immediately without backendRuns 100% offline once SW cached
.env, JWT & PII handlingExposed to server access logs & CDNsMasked in browser RAM + .redactkey vault
Binary PDF / XLSX / DOCXUploaded for remote extraction queuesSelf-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.

Decode JWT & Base64 offline

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.

Compare sensitive diffs in browser memory

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