Wouter Dijkstra

FileFish lets you transfer files between devices - usually from one you own to one you don’t.

I built it for event work, where you constantly need to move documents to laptops owned by rental companies, venues, or technicians. And logging into your Google account on their machine has always felt like a bad idea.

“Just log in for a second” is how mistakes happen

The classic workflow is familiar:

• log into email or cloud storage
• download or upload one file
• log out (hopefully)

But...

In reality:

• you forget to log out
• browsers remember sessions
• suddenly way more than that one file is accessible

All that risk, just to transfer a PDF or a pixel map.

What file.fish does (and doesn’t)

FileFish is intentionally limited:

• no accounts
• no personal libraries
• no long-term storage

You upload a file on one device.
You download it on another.

After one hour, it’s gone.

Not hidden. Not archived. Deleted.

The 1-hour limit is the feature

FileFish is not trying to be WeTransfer, Dropbox, or Google Drive.

Those are storage products.
file.fish is a transfer tool.

Files exist just long enough to move from A to B. That’s it.

This removes:

• cleanup later
• forgotten files
• accidental oversharing

Which is exactly what I want when I’m standing in a venue with people waiting.

Why this fits event work

I mostly use file.fish for:

• pixel maps (from HappyMaps)
• plots and PDFs
• small config files
• quick “can you send me that?” moments

Especially when the receiving machine isn’t mine and won’t be tomorrow either.

Closing thought

file.fish exists because convenience kept pushing me into unsafe habits.

It doesn’t try to be smart.
It doesn’t try to keep your files.
It just moves them — briefly.

Get Hooked today, visit file.fish!