Heyo, users!
I have completed several updates. One for the Monero patch and another for a 'secret' update. I haven't published them yet, nor will I until we get a bit more foot traffic.
I have tested both features locally and they seem to be working fine. I also have not been updating our canary keys.
After my computer crapped the bed, I lost my source code for the client and all the key signing stuff. It's rather easy to do it manually but I've been more focused on these new content updates.
Within the next month, I intend to get our canary files up to date.
Thank you for your patience, and thank you for using FileFade!
p.s. Please share the site with your friends! As we scale our user base, limits will scale as well!
Heyo!
I'm running behind on the update due to some computer problems. Hopefully this will be resolved soon.
But I am thinking of postponing this major update until we get a more active user base.
For now, the Monero update is delayed indefinitely. Share this site with your friends to get it published quicker!
On average we only have about 2 uploads a week. I'd like to get it to 1 a day. We have free public image hosting! No ads, direct link for forums or sites.
Spread the word! Can't wait to share what I've been working on.
Thanks!
-swig
Welcome back! Glad you're here.
Originally, I intended to not push any updates requiring people to pay for this service, because to be honest... I'm not doing it for the money.
BUT, I have decided that one of the first features I would like to implement is users being able to monetize their downloads. And because of that, I will be implementing paid features a little sooner than anticipated.
My goal is to publish this update by Saturday, June 27th (so about 1.5 weeks from now).
This future update will include:
- New paid account tier
- Monetization for downloads utilizing Monero
- Optional licensing for your (the user) downloads
- (View only) setup for Monero wallets
- Automatic delivery of files once transaction is confirmed
... and more!
Comment and let me know if you think this is the right direction!
Talk soon!
swig
Hotfix update:
php max_file_size and max_post_size as well as some other settings were set too low and would not allow uploads of more than 2mb. This setting has been adjusted and uploads larger than 2mb should be working now.
Date: June 15th, 2026
Content:
Completed a major backend storage upgrade. Going forward, uploaded files are now being stored through a dedicated VPS-based storage system instead of the previous local shared-hosting storage workflow.
You can continue uploading and sharing files as before, but the backend storage layer has changed. New uploads are now routed through the new VPS storage backend, giving FileFade more flexibility, better separation between the main website and stored files, and a stronger foundation for future scaling.
Encrypted uploads remain encrypted before they ever leave your browser. FileFade still does not receive, store, or have access to the private decryption key for encrypted uploads. This storage upgrade changes where encrypted file blobs are stored, but it does not change the client-side encryption model.
As part of this migration, files uploaded before the upgrade have been purged. If you had files hosted before this update, they will need to be uploaded again.
This update also begins FileFade’s move toward offshore storage infrastructure. Iceland-based hosting is often viewed as stronger from a privacy perspective because Iceland operates under strict European-style data protection rules through the EEA and its national data protection law. In practice, this means hosting providers are subject to stronger expectations around lawful processing, data security, and privacy protections than many lower-standard jurisdictions. Iceland is also outside of the "Five Eyes" surveillance network.
There may still be minor issues discovered as the new workflow is tested under normal use. Any problems found during this rollout will be reviewed and fixed as quickly as possible. If you encounter any problems, please email support@filefade.com. Also, since the email accounts are new, please comment on this changelog as well. Assuming your email on file is accurate, I can email you to discuss further.
Also in this update: I have launched filefade.com/transparency.html
I am in the process of creating a "FileFade Client" that will verify the integrity of site files against an offline private key. I have also added several "warrant canaries" that serve as a means for FileFade to attest that those statements are true. More information about "canaries" and why this matters can be found on that page. I am still formatting the page properly, but the contents should not vary much from now until it is completed how I would like.
Thank you for your patience while this upgrade was completed, and thank you for using FileFade!
swig
Greetings, fellow... FileFade-r's? A-hem.
Anyways!
Two things I'd like to share with you today, incase you missed it on the roadmap, or you are just perusing and happened to end up here.
Email accounts are now live, as of this post! admin@, no-reply@, support@, and reports@ are now up and accepting mail.
If something is broken or you need help, please email support@.
If you have a question, concern, or would like clarification on anything, please email admin@.
If you have already reported a file and are sending evidence for your claims, please email reports@.
Also... off-shore hosting is confirmed! I am in the process of setting up a new server that will handle the storage of user uploads. It is located in Iceland. Why Iceland, you may ask? It's a long story, and since I can't add hyperlinks in this text (yay security features), feel free to Google the benefits of servers located in Iceland. Compared to US data/privacy laws, you'll see why I made that choice.
Feel free to post on these changelogs as well! Shout-out to our first commenter, Midnight_Apostate! I saw as soon as you commented, but I don't have a reply function implemented so I just left it be.
This marks the 3rd update I was able to push this week. I'll more than likely take a break this weekend. But if I get bored, I'll probably piddle anyways.
Next up is a new UI. I am not a front-end guy. I absolutely hate design and yes, I got ChatGPT to make this front-end. I'm talking to a few freelancer's right now, one of which I will be hiring to update the front-end to be more appealing and less confusing. I hate this design with a passion, but it got all my backend stuff to work, so I live with it for now.
After that, I'll be implementing email verification. If you registered with a throw-away email that's fine. I'm still on the fence about password recovery. I'll have to really think about it. There are more security related things that I plan on changing and other routes I'm considering taking, so for now, if you lose your password you're just kinda screwed.
That pretty much covers it! Keep following along.
Thanks!
swig
Date: June 10th, 2026
Content:
This update changes several security related concerns to more adhere to FileFade's future Content Security Policy (CSP).
Notice
- If something does not work, PLEASE comment and let me know! I check this page frequently! Once email accounts are up and running, you can email me anytime with questions / concerns.
Added
- Stronger browser safety rules for FileFade pages.
- Unique script approval codes to help the browser identify trusted FileFade scripts.
- Stronger security headers for both filefade.com and secure.filefade.com.
Improved
- Protection against injected or unexpected JavaScript.
- Referrer privacy so browsers share less page information.
- Browser permission restrictions for features FileFade does not use, like camera, microphone, geolocation, payment, and USB access.
Fixed
- Removed an inline secure upload form handler.
- Moved secure upload form protection into the main app.js file.
Security
- Blocks unexpected scripts from running.
- Blocks FileFade pages from being loaded inside frames or iframes.
- Blocks older risky embedded content types.
- Adds stronger HTTPS behavior with HSTS.
- Helps prevent browsers from guessing file types incorrectly.
Date: June 9th, 2026
Content:
This update adds a new changelog section so users can follow FileFade development more easily.
Added
- Added a changelog page for site updates.
- Added commenting for logged-in users.
Improved
- Improved transparency around ongoing FileFade changes.
Fixed
- Minor internal code cleanup.
Security
- No updates.
Notice
- No updates.
Midnight_Apostate ·