Drop files here
Upload cancelled: this file is blocked
files selected
Total:
Preparing...
0%
Ready to share
Anyone with this link can download the file.
SHA-256
The file stays encrypted on our servers, but we would be able to read it. With a password, only you and the recipient can.
file.txt · 0 KB
Information for copyright holders
tmp0.cc respects the intellectual property rights of others. We are committed to responding to valid DMCA takedown notices in accordance with the Digital Millennium Copyright Act.
While we cannot prevent all users from uploading copyrighted content, we take copyright infringement seriously and will promptly remove files when we receive a valid takedown request.
tmp0.cc operates as a neutral hosting provider under DMCA Section 512. We do not monitor, review, or control the content uploaded by users. We have no knowledge of potentially infringing content until notified. Upon receiving valid takedown notices, we act expeditiously to remove or disable access to the material.
Your notice must include:
Email: legal@tmp0.cc
Subject: DMCA Takedown Request
Upon receipt of a valid notice, we will review and remove infringing content, typically within 24-48 hours.
If you believe your content was removed in error, you may submit a counter-notification to legal@tmp0.cc
The short answers.
Drop a file, pick how long it should live, and share the link. When the timer runs out — or the download limit is reached — the file is deleted.
No. Everything works without registration. Signing in with Discord is optional and only adds a dashboard that lists what you have shared.
2 GB per upload, and storage from one hour up to 30 days. Multiple files are bundled into a single ZIP automatically.
Set a password and your file is encrypted in your browser before it leaves your device — we never see the password or the contents. Without one, files are still encrypted at rest on our servers.
Yes. Every upload comes with a private delete link. Keep it — anyone who has it can remove your file.
Use tmp0.cc/paste for a proper editor with syntax highlighting, or just press Ctrl + V anywhere on the home page.
Direct transfer sends files browser to browser while both tabs stay open. Nothing is stored on our servers.
Yes — see the for endpoints, ShareX setup and the CLI.
Privacy-first: Minimal data, maximum protection
E2EE files (with password — default recommendation): Encrypted in your browser before upload using Argon2id + AES-256-GCM. A built-in password generator and entropy meter enforce minimum password strength (50+ bits). The server stores only ciphertext.
True Zero-Knowledge mode: E2EE with the additional guarantee that the server performs zero plaintext processing — no metadata stripping, and the contents cannot be scanned. The server only handles the encrypted blob as received: its SHA-256 is recorded and compared with the blocklist, and it passes through the virus scanner to catch files that are merely labelled as encrypted. Neither reveals anything about real ciphertext.
Server-encrypted files (no password): A warning is displayed when uploading without encryption. The server processes your file (hash computation, metadata removal, virus scan), then encrypts at rest. The server has temporary access to plaintext during processing.
About IP hashing: We use HMAC-SHA256 with a server-side secret key to hash IPs. Unlike plain SHA-256, HMAC prevents reverse-engineering via lookup tables — even with full access to the hashed values, the original IPs cannot be recovered without the secret key. The key is configurable via environment variable or auto-generated per instance.
Pastes (created at tmp0.cc/paste) are stored in an in-memory database that is cleared on server restart. Paste content is not encrypted server-side (unlike files) but can be password-protected with client-side encryption.
Pastes auto-delete after their chosen expiration time (1 hour to 30 days) or when view limits are reached.
You can optionally log in with Discord to link your content to a personal dashboard. This is entirely voluntary and does not affect how the service works without login.
What we store when you log in with Discord:
What we do NOT access or store:
Account Deletion: You can delete your Discord connection at any time from your dashboard. This permanently removes your Discord data from our system. Your uploaded content (files and pastes) will remain accessible but will no longer be linked to your account. Re-registering will not reconnect previous content.
Each upload generates a secret delete link containing a unique 32-character token. This link allows you to delete your file at any time before expiration.
Important: Keep your delete link private. Anyone with this link can delete your file. We cannot recover deleted files.
Zero server storage — strongest privacy mode. P2P transfers use WebRTC DataChannel (DTLS-encrypted) to send files directly between browsers. No file data, metadata, or transfer history is ever stored, logged, or cached.
Privacy-relevant details:
ICE candidates and IP exposure: During signaling, IP addresses of both peers are relayed through our server for NAT traversal. Held in memory only, never written to disk. Room data is garbage-collected after 10 minutes.
Third-party STUN/TURN: Google and Cloudflare STUN servers used for NAT discovery (binding requests only). Optional TURN relay for firewalled users — relays encrypted traffic it cannot decrypt.
QR codes are generated entirely in your browser using client-side JavaScript. No data is sent to external services.
Brute Force Protection: We temporarily store HMAC-SHA256 hashed IP addresses in memory (not on disk) to prevent abuse. These keyed hashes cannot be reversed without the server's secret key and are automatically cleared after 1 hour.
Rate Limiting: Request counts are tracked temporarily in memory using HMAC-hashed IP addresses. No persistent storage, no raw IPs stored.
Abuse Detection: A scoring system tracks suspicious patterns (failed auth, rapid uploads, scanning behavior). IPs exceeding the abuse threshold are temporarily blocked for 15 minutes. Scores decay automatically after 5 minutes of inactivity. To recognise automated abuse, such as the same file uploaded over and over, the keyed hash of your IP is linked in memory, for at most 24 hours, to your recent uploads (their ID, size and content hash) and to failed or refused requests. Our team sees this only under a pseudonym and can block that hash or remove what was uploaded; your IP address itself is never stored or shown. None of it is written to disk, and all of it, blocks included, is gone after a restart.
Self-Hosted Resources:
Scripts, styles, icons and fonts all come from our own server. Loading a page sends no request to a CDN or font service, and our Content Security Policy makes browsers refuse scripts, styles and fonts from anywhere else.
The one exception is your profile picture if you log in with Discord, which is loaded from cdn.discordapp.com.
Security Trust Model:
E2EE in the browser depends on the JavaScript our server delivers. If our server were compromised, malicious code could theoretically intercept passwords before encryption. This is a fundamental limitation of browser-based E2EE.
Mitigations: All of that code comes from our own server, so no CDN can alter it, and the browser refuses scripts from other origins. For maximum security, advanced users can use our CLI tool, which encrypts locally and does not depend on code from the website.
Virus Scanning: All uploads are scanned with ClamAV antivirus. A file can only be downloaded once its scan has finished, and infected files are removed.
Hash Blocklist: Known malicious or illegal content is automatically blocked based on SHA-256 hash.
Scanning Exceptions:
No Guarantee: Security scanning is provided on a best-effort basis. No antivirus can detect 100% of threats. Files marked as "clean" may still contain malware. Download at your own risk.
See the encryption modes described above, or the summary in:
For server-encrypted files, we automatically strip metadata from supported file types:
Supported formats:
Limitations:
For maximum privacy with sensitive files, use E2EE and consider stripping metadata yourself before upload.
We maintain a Merkle tree-based audit log of file operations. This is different from traditional access logs:
Privacy note: If someone knows a file's SHA-256 hash, they can check the transparency log to see when it was uploaded/downloaded. This enables auditing but also means file hashes are semi-public information. For maximum privacy, use E2EE (the hash of encrypted ciphertext reveals nothing about the original file).
A command-line interface (tmp0) is available with full E2EE support for automated workflows and power users.
All features are accessible via public API endpoints documented in the API section.
Files auto-delete after their chosen expiration time (1 hour to 30 days).
Limitation: On modern SSDs with wear-leveling, "secure deletion" cannot be guaranteed at the hardware level. The SSD controller may retain old data in spare blocks. For highly sensitive data, use E2EE - even if old ciphertext is recovered, it cannot be decrypted without your password.
Operating Jurisdiction: Iceland
tmp0.cc operates under Icelandic law. Iceland is a member of the European Economic Area (EEA), ensuring strong privacy protections equivalent to EU standards while benefiting from Iceland's robust legal framework for digital privacy and freedom of expression.
All legal matters, disputes, and data protection inquiries are governed exclusively by Icelandic law and subject to the jurisdiction of Icelandic courts.
As an EEA member state, Iceland has incorporated the General Data Protection Regulation (GDPR) into national law through the Icelandic Data Protection Act (Lög um persónuvernd og vinnslu persónuupplýsinga).
Data Processing Principles:
Your GDPR Rights:
Our Commitment to User Privacy
We are committed to protecting user privacy to the fullest extent permitted by law. Any government or law enforcement request for user data will be subject to rigorous legal scrutiny.
Request Handling Procedure:
Technical Limitation: For E2EE files, we cannot provide plaintext content even under legal compulsion—we do not possess decryption keys. Any disclosed data would be limited to encrypted ciphertext and minimal metadata.
In the interest of transparency, we publish annual statistics on legal and takedown requests received. This report is updated annually.
| Year | DMCA Requests | Government/Legal Requests | Data Disclosed |
|---|---|---|---|
| 2025 | 0 | 0 | 0 |
| 2026 | 0 | 0 | 0 |
Last updated: February 2026 • Next update: January 2027
Zero Backup Architecture
tmp0.cc intentionally operates without any backup systems. This is a deliberate architectural decision to maximize privacy—not a limitation.
Infrastructure Design:
User Responsibility: If you need to retain a file beyond its expiration, download a copy. We cannot recover deleted or expired files under any circumstances—this is a feature, not a bug.
Verifiability: Our zero-backup policy is verifiable through our infrastructure: single-server deployment, no replication endpoints, no backup agent processes. This architecture ensures that when data is deleted, it is truly gone—with no hidden copies to potentially surface later.
E2EE files: Server-side key management is irrelevant — your password-derived key never touches our servers.
Please read these terms carefully
By using tmp0.cc, you agree to these Terms. If you don't agree, don't use the service.
Privacy-focused temporary file sharing with multiple encryption modes:
All files auto-delete after expiration. No accounts, minimal metadata, HMAC-hashed IPs only.
Paste (Code & Text Share): Dedicated editor at tmp0.cc/paste. Share text and code with syntax highlighting. Pastes are stored in ephemeral memory (cleared on restart), support password protection and burn-after-reading, and auto-delete after expiration.
P2P Transfer: Direct browser-to-browser file transfer via WebRTC. The server acts only as a signaling relay - no file data is stored, transmitted through, or logged by the server.
We reserve the right to block, flag, or remove any content that violates our policies.
Direct browser-to-browser file transfer via WebRTC. The server acts exclusively as a signaling relay and never processes, stores, or logs file data.
No server-side protections: Because the server never sees P2P-transferred files, ClamAV virus scanning, metadata stripping, hash blocklist checking, and content moderation do not apply. All prohibited content rules still apply, but enforcement is technically limited to signaling-level controls (rate limiting, room limits). Receivers accept files at their own risk.
To prevent abuse, we implement multi-layered protection:
You must be at least 13 years old to use this service. If you are under 18, you should have parental consent.
We do not guarantee uninterrupted service. The service may be modified or discontinued at any time without notice.
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED.
We make no warranties regarding reliability, accuracy, availability, security, or fitness for any particular purpose. We do not warrant that files are virus-free, safe, legal, or free from harmful content.
YOU USE THIS SERVICE AND DOWNLOAD FILES ENTIRELY AT YOUR OWN RISK.
In no event shall we be liable for any claims, damages, or losses exceeding the amount you paid to use the service (which is zero).
We are a neutral hosting platform. We do not control, endorse, or take responsibility for any content uploaded by users. Users are solely responsible for their uploads.
Our only commitment is to review and remove content upon receiving valid abuse reports or legal requests (DMCA, law enforcement, etc.).
You agree to indemnify, defend, and hold harmless the service operator from any claims, damages, losses, or expenses (including legal fees) arising from your use of the service, your uploaded content, or your violation of these terms.
As a hosting provider, we operate under applicable safe harbor provisions (such as DMCA Section 512). We respond to valid takedown requests but bear no liability for user-uploaded content.
We may update these terms at any time. Continued use of the service constitutes acceptance of any changes.
Icelandic Law
These Terms of Service are governed exclusively by the laws of Iceland. Any disputes arising from or relating to these terms, the service, or your use thereof shall be subject to the exclusive jurisdiction of the courts of Iceland.
Iceland is a member of the European Economic Area (EEA), providing strong legal protections for privacy and data protection under GDPR-equivalent standards.
Operator information according to applicable law
Service: tmp0.cc - Temporary File Sharing
Type: Privacy-focused hosting service (non-commercial)
Jurisdiction: Iceland (EEA member state)
Service Model
tmp0.cc operates as a privacy-focused file hosting service. All uploads are temporary and auto-delete based on the configured retention period (1 hour to 30 days).
Applicable Law
EU General Data Protection Regulation (GDPR), ePrivacy Directive, Digital Services Act (DSA), DMCA Safe Harbor (Section 512). All disputes subject to Icelandic jurisdiction.
Content Responsibility
As a hosting provider, we are not responsible for user-uploaded content under applicable safe harbor provisions. We respond to valid takedown requests within 24 hours.
For all contact channels (support, legal, abuse, privacy, security), see:
Choose the right channel for your inquiry
support@tmp0.cc
abuse@tmp0.cc
legal@tmp0.cc
privacy@tmp0.cc
We respond within 24-48 hours. Abuse reports prioritized within 24 hours.
We respond in English and German.
Upload and share programmatically. No key required.
$ curl -F "file=@report.pdf" -F "expires=7d" \
https://tmp0.cc/api/v1/upload
{
"fileId": "a1b2c3d4e5f6",
"fullUrl": "https://tmp0.cc/d/a1b2c3d4e5f6",
"deleteUrl": "https://tmp0.cc/delete/a1b2c3d4e5f6",
"expiresAt": "2026-08-14T12:00:00"
}
Optional fields: expires (1h, 6h, 12h, 1d, 3d, 7d, 14d, 30d — default 7d), maxDownloads, password, note.
Pipe text straight into the body. The language is detected from the content unless you name one.
$ cat main.py | curl -X POST --data-binary @- \
-H "Content-Type: text/plain" \
"https://tmp0.cc/api/snippet/create?expires=7d"
{
"success": true,
"snippetId": "b2c3d4e5f6a1",
"language": "python",
"fullUrl": "https://tmp0.cc/paste/b2c3d4e5f6a1",
"rawUrl": "https://tmp0.cc/api/snippet/b2c3d4e5f6a1/raw",
"deleteToken": "…",
"deleteUrl": "https://tmp0.cc/paste/b2c3d4e5f6a1/delete?token=…"
}
Query parameters: language, title, expires, password, maxDownloads, burnAfterReading, autoDetect (default true).
The same endpoint accepts JSON, with every option in the body:
$ curl -X POST https://tmp0.cc/api/snippet/create \
-H "Content-Type: application/json" \
-d '{"content":"print(1)","language":"python","expires":"1d"}'
Read it back as plain text — ideal for curl | sh style use:
$ curl https://tmp0.cc/api/snippet/b2c3d4e5f6a1/raw
Password-protected pastes take ?password=… on /raw and /content. Limits: 10,000 lines or 500 KB per paste.
| POST /v1/upload | Upload a file |
| GET /file/{id}/info | Metadata, expiry and download count |
| POST /file/{id}/download | Download (password in body if set) |
| DELETE /file/{id} | Delete using the delete token |
| POST /snippet/create | Create a paste from text or JSON |
| GET /snippet/{id}/info | Title, language, line count and expiry |
| GET /snippet/{id}/raw | Plain-text contents of a paste |
| POST /snippet/{id}/content | Contents as JSON, with metadata |
| DELETE /snippet/{id} | Delete a paste using its delete token |
| POST /upload/init | Start a chunked upload for large files |
| POST /v2/presign | Request a pre-signed direct upload URL |
Requests are rate limited per IP address — 10 file uploads, 5 pastes and 30 metadata requests per minute. Responses use standard HTTP status codes; 429 includes Retry-After and X-RateLimit-Remaining. Errors return { "success": false, "error": "…" }.
Import a custom uploader for screenshots, files and text.
A single-file Node script for uploads from your terminal.
curl -O https://tmp0.cc/api/v1/cli/tmp0.js
How your files are protected.
When you set a password, the file is encrypted in your browser before upload using AES-256-GCM with an Argon2id-derived key. The password is never transmitted, so we cannot read the file or recover it if you lose the password. Files uploaded without a password are still encrypted at rest with AES-256-GCM.
Only what the service needs: the encrypted file, its size and type, the expiry date and a counter. No IP addresses are kept in plain form — they are hashed with a keyed HMAC for rate limiting and expire within hours.
Expired files are removed automatically every few minutes and overwritten on disk. Burn-after-reading destroys a file the moment it has been downloaded once. You can delete anything early with the delete link you receive on upload.
Uploads that the server can read are scanned for malware and checked against a hash blocklist. Rate limits apply per IP address. Files you encrypt yourself are opaque to us, so their contents cannot be scanned.
Send findings to security@tmp0.cc. Please give us reasonable time to fix an issue before disclosing it. Our policy is also published at /.well-known/security.txt.