Private Upload
Multi-backend, anonymizing Cloudflare Worker proxy.
New Upload TmpFiles.org
Choose a file
or drag & drop here · max 100 MB
FileNo file selected
Anonymous filename
Sent as—
Request to/api/v1/upload
Custom endpoint URL (HTTPS)
Multipart file field
Direct to backend
Proxied: the Worker still anonymizes UA, headers and filename. Your token never reaches the custom backend.
Ready
Metadata is anonymous, the file is not. Uploaded files are public on the chosen backend until they expire. Never upload confidential data.
API Reference
Loading API document…
MethodPOST
Endpoint/api/v1/upload
Selector?backend=
Content-Typemultipart/form-data
Upstream UAAnonymous-Upload-Client
OpenAPI/api/docs
Backends/api/backends
Available Backends
Request Parameters
Response Examples 200
Status Codes
Privacy Guarantees
Your User-Agent is discarded by the Worker. Proxied examples contain no UA and no client-identifying headers. Direct-to-service examples are shown for reference only.
Gofile.io — direct to service (raw)
Terminal
Gofile.io — via Worker (anonymized)
Terminal
tfLink — direct to service (raw)
Terminal
tfLink — via Worker (anonymized)
Terminal
TmpFiles.org — default backend
Terminal
Control the published filename
Terminal
Custom endpoint (X-Upstream-Url)
Terminal
Custom endpoint + custom file field
Terminal
With access token (header only)
Terminal
JavaScript / browser (custom backend)
ES2020
Response (unified)
application/json
Download link rules
TmpFiles.org returns a landing page: insert /dl/ after the host for a raw link. tfLink and custom URLs are already direct. Gofile returns a share page only, so data.directUrl is null — open the page to download.
What the upstream sees
Only the file bytes, an expire value (tmpfiles only), a fixed anonymous User-Agent, a Cloudflare egress IP, and a sanitized filename. Nothing else leaves the Worker.
User-Agent: Anonymous-Upload-Client
Fixed, version-less, identical for every backend. Your real UA is never read or forwarded.
IP: Cloudflare egress
The subrequest is re-issued by the Worker, so your IP never reaches tmpfiles.org, tmpfile.link, gofile.io or a custom endpoint.
Headers: 3 total
Content-Type (boundary only), Accept, User-Agent. An allowlist, not a blacklist. Optional tfLink credentials and a Gofile account token come from Worker secrets, never from your request.
Never sent upstream
Cookie / Authorization / Referer / Origin
Dropped. The upload token is consumed locally and never forwarded.
X-Upstream-Url / X-File-Field
Control headers consumed by the Worker, never forwarded to the backend.
Accept-Language / Accept-Encoding / Via / X-Requested-With
Dropped. No locale, platform or client hints.
CF-Connecting-IP / X-Forwarded-For / X-Real-IP / True-Client-IP
Dropped. No inbound IP echoes.
filename="/home/alice/photo.jpg"
Directory components are rewritten in-stream. Enable ANONYMIZE_FILENAME=random for a fully random name.
Multiple backends
Same guarantees everywhere
tmpfiles, tflink, gofile and custom all pass through the identical allowlist, filename scrubber and response sanitizer.
Gofile: guestToken is dropped
An anonymous Gofile upload creates a guest account and returns a guestToken. It is an account credential, so the Worker never returns it — nor parentFolder, md5 or file id. Gofile also gives a share page instead of a raw file URL, so data.directUrl is null.
Custom endpoint SSRF guard
HTTPS only, default port, no userinfo, no IP literals, no reserved suffixes, redirects not followed. Pin CUSTOM_BACKEND_ALLOWLIST to restrict hosts.
Direct mode is opt-in and different
When enabled in the UI, the browser POSTs straight to your endpoint. Your UA and IP reach that backend, it must allow CORS, and the Worker's token does not apply. Use it for private endpoints a public Worker cannot reach.
Coming back to you
No upstream response headers
Set-Cookie, CF-Ray, Server, ETag and tracing headers are all discarded. Only our own headers are emitted.
Unified, sanitized JSON
Every backend is normalized to status / backend / data.url / data.directUrl / data.linkType. directUrl is null when only a share page exists. Unexpected fields, including Gofile guestToken, are removed and URLs are validated.
No logs, no storage
No console output, no KV/R2/Durable Objects, no analytics. Responses are no-store, private.
Per-response CSP nonce
No unsafe-inline scripts, no-referrer, COOP, CORP, Permissions-Policy, frame-ancestors none. connect-src 'self' https: exists only to allow opt-in direct mode.
Configuration
Guarantees in detail
Honest limit. Cloudflare may add its own transport-level headers to outbound subrequests; those carry the Worker's identity, not your browser's. DNS rebinding cannot be fully prevented from inside a Worker. And anonymizing metadata does not encrypt the file: the link stays public until expiry.