We Just Hit 1 TB Transferred. Here Is How Zapfile Got Here.
I want to be honest about what this number means — and what it doesn't.
1 terabyte of files transferred through Zapfile. Encrypted in transit and at rest, delivered, then permanently deleted. 1TB of data that moved from one person to another and left no permanent trace on our infrastructure — every file staged temporarily on Cloudflare R2 and irrevocably deleted the moment the recipient downloaded it. That is the number we crossed last week, and I have been thinking about it since.
It is a real milestone. It is also just a number. What I actually want to talk about is the five months it took to get here — because the path from where we started to where we are now is not the story most people tell about growing a product.
Also readSafe Alternative to Sharing Files Over EmailThe Zapfile Journey So Far
Five Months at a Glance
Where This Started
Zapfile launched in October 2025. The first week, we had exactly two users: me, testing transfers between my phone and laptop, and one friend I had asked to try it. The second week we had maybe five. I know this because I was watching the server logs compulsively and could count the unique sessions by hand.
The idea was straightforward to the point of being obvious: send a file, the other person gets it, nothing is kept anywhere. No account. No upload to Google's servers. No link that lives forever. No compression destroying your photos.
What surprised me was how many people, when I described this, said "wait — that's not how it already works?" They assumed file sharing tools worked this way. They did not know their photos were being compressed by WhatsApp, that their Drive links from three years ago were still live and accessible, or that sending files over email was sitting on mail servers indefinitely. The problem was invisible until I pointed it out. Then it was obvious.
Related guideHow to Send Files Without Login or Sign-Up→The First Real Users
The first users who found Zapfile without me personally telling them about it came from search. Someone in January looking for "send files without Google Drive" landed on one of our early blog posts, tried the tool, and came back the next day. I know this because the session IDs matched. One person. I remember being genuinely excited about one returning user.
By February we were seeing 50–80 unique users a week. Small numbers in any objective sense. But they were finding us on their own, using the tool, and some of them were coming back. That second part matters more than the first. A tool people return to is a different product from a tool people try once and forget.
Also readHow to Send Large Files Without Risk
What 1 TB Actually Looks Like
I tried to think about what 1 terabyte of files actually represents. At an average file size of around 50MB — a mix of photos, documents, short videos — that is roughly 20,000 individual file transfers. 20,000 times someone needed to move a file and chose to use Zapfile to do it.
| What 1 TB Equals | Approx. Count | Avg. File Size |
|---|---|---|
| Smartphone photos (12MP JPEG) | ~333,000 | ~3 MB |
| PDF documents | ~500,000 | ~2 MB |
| Short video clips (1 min, 1080p) | ~2,500 | ~400 MB |
| Mixed transfers (Zapfile average) | ~20,000 | ~50 MB |
Some of those were people moving high-res photos between devices. Some were massive video files from people who had hit limits elsewhere and needed another option. Some were almost certainly people with sensitive documents who did not want them sitting in Google Drive permanently. We do not know which — and that is by design. We see that a transfer happened. We do not see what was in it.
Related guideHow to Send Files Privately Online: What Privacy Actually Requires→What Broke Along the Way
I would rather tell you about what went wrong than pretend the last five months were a clean upward line.
- The mobile connection drop bug: When a user's phone switched from WiFi to mobile data mid-transfer, the session would silently fail. Fixed in January 2026.
- Large file timeouts: Our relay had an aggressive timeout that caused large transfers to fail on slower connections. Fixed in February 2026.
- Blog content script bug: 22 of our early articles published with nearly identical content due to a generation script error. We disclosed this openly and corrected every affected post.
Where We Are Going
The 1TB and 5k numbers are not endpoints. They are a baseline. Password-protected transfer links are coming, as is folder transfer capability. Longer term, we're looking at a mobile app and even stronger E2E encrypted relay modes.
If you are one of the 5,000 people who have used Zapfile — thank you. If something worked exactly the way it was supposed to, that is the goal. A file moved. Nobody kept a copy. Nobody knows what was in it. Done.
Tags
Tanuja Chinthati is the Content and Marketing Lead at ZapFile, based in Ontario, Canada. With a background in Electronics and Communication Engineering, she writes about privacy-first file sharing, secure data transfer, and digital privacy — making complex security concepts accessible to everyday users.
View all articles →