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. Not stored — we don't store anything. Transferred. Packets relayed, encrypted, delivered, discarded. 1TB of data that moved from one person to another and left no permanent trace on our infrastructure. 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.

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. Just a file moving from here to there and then gone.

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, that files they had sent via email were sitting on mail servers indefinitely. The problem was invisible until I pointed it out. Then it was obvious.

That gap — between how people assumed file transfer worked and how it actually worked — was the whole reason to build this.

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 different from a tool people try once.

The questions people asked — the feedback emails, the occasional message via the contact form — started shaping what we built next. The QR code feature came from someone asking if there was a way to share the transfer link without typing it out. Password-protected links are on the roadmap because multiple people asked for them independently. The product roadmap is basically a list of things real users told us they needed.

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.

Some of those were probably people moving a single photo. Some were large video files from people who had hit WhatsApp's 16MB limit and needed another option. Some were almost certainly people with sensitive documents who did not want them sitting in Google Drive permanently. I do not know which — and that is by design. We see that a transfer happened. We do not see what was in it.

The 5,000 user milestone came around the same time as the 1TB number. 5,000 people who have used Zapfile at least once since October. That is a small number for a consumer app. It is a real number for a five-month-old tool built by a small team with no marketing budget. We got here on search traffic, word of mouth, and a few blog posts that people apparently found useful enough to share.

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 was the most embarrassing one. When a user's phone switched from WiFi to mobile data mid-transfer — walking out of a building, network handoff — the session would invalidate and the transfer would fail. No warning. Just a broken transfer and a confused user. We fixed it by implementing session persistence that survives network changes. It took longer to fix than it should have because we did not catch it in testing — we caught it because a user told us about it.

The large file timeout issue was the other significant one. Our relay had an aggressive timeout that worked fine for small files but caused large transfers to fail mid-way on slower connections. We missed it because our internal testing was on fast connections. The fix was adaptive timeouts that scale with file size and observed transfer speed. Obvious in retrospect.

There was also a blog seed script bug that caused 22 of our early articles to publish with nearly identical content — a template variable not being overwritten per post. We wrote about it openly in our previous product update because hiding it would have been worse than disclosing it. Hash validation now runs on every publish.

None of this is unusual for a product in its first five months. Everything breaks at some point. The question is whether you find out fast enough to fix it before it compounds.

Where We Are Going

The 1TB and 5k numbers are not endpoints. They are a baseline.

Password-protected transfer links are coming — the ability to add a password to a Zapfile link so only the intended recipient can download it. Folder transfer is in progress — currently you can transfer individual files, and we are building the ability to drop an entire folder and have it arrive intact on the other end. Delivery confirmation — knowing definitively when the recipient has downloaded — is on the roadmap.

Longer term: a mobile app, end-to-end encrypted relay mode where even Zapfile's infrastructure cannot read the packets in transit (we already use TLS 1.3 and AES-256, but E2E encrypted relay is a stronger guarantee), and expiry control so senders can set exactly how long a link stays active.

We are also launching a YouTube channel shortly — starting with a simple two-minute screen recording showing exactly how a transfer works. No voiceover, no script, just the tool being used. More honest than any written description.

The Number That Actually Matters

The 1TB is a satisfying milestone to hit. The number I actually care about is the percentage of users who come back. Return rate tells you whether the product is solving a real problem or just satisfying a one-time curiosity.

Ours is going in the right direction. The trend is what matters at this stage, and the trend is right.

If you are one of the 5,000 people who have used Zapfile — thank you. If something broke for you and you never told us, please tell us via the contact page. 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.

That is what we are building toward, at scale.