Frequently asked questions
Files are kept indefinitely as long as storage allows. There is exactly one rule: a file only becomes eligible for deletion once it has gone 45 days without a single access.
We only actually delete when we're running low on disk space, which is rare — we maintain large storage capacity and actively monitor usage. So in practice, untouched files often survive well past 45 days; how long depends on how full we are. But the bar never moves: any file accessed within the last 45 days is untouchable.
No. We don't run scheduled deletion jobs. Files are only removed during space reclaims, and only files with zero accesses in the last 45 days are candidates. If your file is being downloaded even occasionally, it will never be removed.
If you are hosting something important and long-term, we recommend keeping your own copy as with any third-party hosting service.
Yes — the upload history page lists the files you've uploaded from this browser (the last 1000). History is stored entirely in your own browser (localStorage); nothing is sent to or kept on our servers, so it stays as anonymous as the uploads themselves.
It's per-browser and per-device — clear your browser data and it's gone, switch devices and it won't follow you. You can also wipe it any time with the clear button on the history page.
150 GB per file. There is no limit on the number of files you can upload.
No. FileDitch is fully anonymous. No registration, no login. Drop a file, get a link.
Very little. There are no accounts, so a file is never tied to an identity. For each upload we record the time, the uploader's IP address, the filename and the file size. Our web server keeps standard access logs (IP, time, request) for a limited period. The site uses Plausible for cookie-free, aggregate page statistics.
If law enforcement requests that information, we provide it and cooperate fully. To be candid, it is rarely of much practical use — uploads are almost always made through VPNs or proxies — but we hand it over when asked.
Most common file types are accepted. We block anything that could be dangerous or executed server-side, including:
Executables and installers: exe, msi, apk, ipa, dmg, deb, rpm, app
Scripts: php, py, sh, bash, pl, rb, bat, cmd, ps1, vbs and similar
Web files: html, htm, js, svg, xml
Macro-enabled Office files: docm, xlsm, pptm and similar
Java archives: jar, war, ear
Videos, audio, images, plain documents, archives, disk images (iso, img, vhd — not dmg), databases and most other formats are all fine. Renaming a blocked file type does not help: the content is checked too.
Then the file itself is the problem, not the upload: browsers only play a narrow set of codecs (H.264 video + AAC audio in an MP4, with the index at the front). HEVC from iPhones, 10-bit exports, MOV/MKV containers or Dolby audio all fail in the same way on every host, not just here.
The encoding guide explains how to check what's inside your file and fix it in one command on macOS, Windows or Linux, usually without any quality loss.
No. Hotlinking and embedding are not supported. Files must be downloaded and hosted elsewhere if you want to embed them. Direct linking to files on FileDitch from external sites will not work as intended.
Yes, two of them, no keys required. Uploading is a simple HTTP POST or PUT that returns a JSON link. There is also a read-only status endpoint on fileditchfiles.st: insert /api after the domain of any file link and it tells you whether the file still exists and how big it is, with CORS open so it works from a web page. See the API page for documentation and examples.
Use the abuse page. Include the file URL and as much detail as possible. We act fast.
Files are accessible to anyone with the link. Links use random 20-character folder names which makes them unguessable by brute force, but we do not guarantee privacy — treat anything uploaded here as potentially public.
The download endpoint is protected by rate limiting and automated abuse prevention to stop bulk scraping and spam. We do not publicly index uploaded files.