Temporary File Sharing Tool • Zero-Knowledge
Free client-side temporary file sharing tool. Encrypt files with AES-256-GCM, generate zero-knowledge URL hash share links.
1. Select File or Text Secret
Click to choose a file or drag and drop here
Ideal for documents, credentials, and keys (< 64 KB)
2. Generated Share Link
Data is stored strictly inside the URL hash fragment (#d=...). Fragment data is never sent to any web server in HTTP requests.
Zero-Knowledge Guarantee
- AES-256-GCM authenticated encryption
- 100,000 PBKDF2 iterations with random salt
- Hash fragment never leaves client browser
- No server logging, database, or analytics tracking
Self-Decrypting Standalone Package
Package any file into a single encrypted HTML file. Recipient can double-click and open it in Chrome, Safari, Firefox, or Edge to decrypt and extract the original file offline.
Click to choose any file for packaging
Works with images, PDFs, archives, and documents
How Standalone Packages Work
| Feature | Standalone Bundle | Standard Cloud Share |
|---|---|---|
| Server Dependency | Zero (Runs 100% offline) | Requires corporate cloud server |
| Third-Party Tracking | None | IP & download telemetry logged |
| Software Needed | Any modern browser | Proprietary client or account |
| Tamper Proofing | GCM authentication tag | Provider-dependent |
In-Browser Decrypter & Unpacker
Paste a received share link or ciphertext payload and enter the passphrase to inspect metadata and extract the original file.
Cryptographic Architecture & Security Specs
Cryptographic Primitives
- Symmetric Cipher: AES-256-GCM (Galois/Counter Mode).
- Key Derivation: PBKDF2 with HMAC-SHA-256 and 100,000 iterations.
- Salt: 128-bit cryptographically secure random value generated via crypto.getRandomValues.
- IV / Nonce: 96-bit unique random initialization vector per encryption pass.
- Integrity: 128-bit GCM authentication tag guarantees tamper detection.
Privacy & Threat Model
- Zero Cloud Footprint: Files exist solely in device RAM and client storage.
- URL Hash Privacy: Browser standards mandate that hash fragments are stripped before transmission to HTTP servers.
- No Third-Party Intermediary: Neither Google, AWS, nor any CDN ever holds your plaintext or decryption key.
- Tamper Proof: Any modification to ciphertext causes GCM authentication to fail automatically.
About this tool
How to use it
- Select an ephemeral sharing mode: 'Encrypted Share Link' for small files and text secrets (under 64 KB), 'Self-Decrypting HTML Bundle' for larger files, or 'Decrypt / Inspect' to unlock a received file.
- Choose or drag-and-drop your file, or type/paste sensitive text, credentials, or code snippets.
- Set a custom decryption passphrase or click 'Generate Secure Key' for a random 256-bit cryptographic token.
- Click 'Encrypt & Generate Share Link' or 'Export Self-Decrypting Package'. All AES-256-GCM encryption occurs entirely inside your browser's Web Crypto engine before anything leaves your RAM.
- Copy the generated secure link or send the offline HTML package to your recipient. The recipient opens it in any browser to verify SHA-256 checksums and restore the exact original file.
Why it matters
Centralized file hosting and cloud sharing services store your unencrypted files, track download IP addresses, and retain data indefinitely on corporate servers. Our Temporary File Sharing Tool uses zero-knowledge client-side AES-256-GCM encryption and URL fragment architecture. The encryption key never touches a network wire, and no file data is ever uploaded to any external server.
When to use it
Use this tool whenever you need to send sensitive documents, private SSH keys, password backups, contract drafts, API tokens, or personal photos without leaving traces on external cloud providers or messaging servers.
Common questions
Are my files uploaded to any third-party server or cloud storage?
No. The entire process runs 100% client-side in your web browser using the native Web Crypto API. No files, passwords, or encryption keys are ever transmitted across the internet.
How does the URL hash share link work?
Data stored after the '#' symbol in a URL (the fragment identifier) is never sent to web servers by browsers in HTTP requests. The encrypted ciphertext and initialization vector (IV) are encoded directly into the hash, ensuring pure peer-side decryption.
What encryption standard is used?
We use AES-256-GCM (Galois/Counter Mode) with an authenticating tag and a cryptographically random 96-bit initialization vector (IV), paired with PBKDF2 key derivation using SHA-256 and 100,000 iterations.
What is a Self-Decrypting HTML Package?
It is a standalone single-file HTML document containing your encrypted payload and an embedded offline decryption script. Your recipient can open it offline in Chrome, Safari, Firefox, or Edge, enter the password, and instantly extract the file.
What is the maximum file size for URL hash sharing?
Modern browsers handle URL fragments comfortably up to approximately 64 KB, making them ideal for text files, scripts, SSH keys, configuration files, and small images. For larger files (up to hundreds of megabytes), use the Self-Decrypting HTML Bundle option.