Relayium

How to send a whole folder, not just files

Last updated: 2026-07-09

Sending a project isn't the same as sending a file — you have a folder full of subfolders, and copy-pasting each piece individually loses the structure that makes it useful. Zipping it first works, but it means a detour through a compression tool before you can even start.

Relayium lets you pick a folder directly and send it as-is. The browser walks the whole tree, keeps every relative path intact, and streams it to the other side — whether that ends up peer-to-peer with nothing stored, or as a link you can leave for later.

Pick a folder, not a pile of files

Instead of selecting files one by one, choose the folder itself. Relayium walks the directory tree in the browser and keeps every file's relative path — subfolders, nested subfolders, all of it — so what arrives on the other end has the same layout you started with.

This works today in desktop Chrome, Edge, and Firefox. It doesn't work on iOS: Safari's file picker on iPhone and iPad has no way to select a folder, only individual files, so folder sending is a desktop feature for now.

What the other person gets

How the folder arrives depends on the receiving browser. Chrome and Edge can write files straight into a directory the recipient chooses, so the folder shows up on disk exactly as it left — no extra step.

Firefox and Safari don't have that capability, so instead they receive one store-only .zip archive that unpacks to the exact same folder structure. It stays under 4 GiB (no ZIP64 support), which covers the vast majority of project folders and photo or document sets — for anything bigger, split into two sends.

Realtime, or a link for later

If you can both be online at the same time, send the folder directly — it goes peer-to-peer and nothing is stored on any server in between. This is the fastest path and needs no account if you're on the same network; sending across networks with a pairing code just needs the sender to sign in, and the receiver never needs an account at all.

If the other person isn't around right now, create a stored link instead. Your browser encrypts the folder's files before upload with a random AES-256-GCM key that only ever lives in the link itself, so the server holds ciphertext it can't read. Creating a link needs the sender to sign in; set it to expire in 1 hour, 1 day, 3 days, or 7 days, or make it burn after the first download.

Frequently asked questions

Can I send a folder from an iPhone or iPad?

Not as the sender — iOS's Safari has no folder picker, only individual files, so folder sending currently works from desktop Chrome, Edge, or Firefox. An iPhone or iPad can still receive a folder just fine, as a .zip.

Are subfolders and file structure preserved?

Yes. Relayium keeps every file's relative path, including nested subfolders, so the folder that arrives has the same layout as the one you picked.

How many files can a folder send hold?

Up to 1,000 files in a single batch, each individually verified with a SHA-256 hash on arrival.

Does the recipient get an actual folder or a .zip?

It depends on their browser. Chrome and Edge write the files straight into a directory they choose. Firefox and Safari receive one store-only .zip (under 4 GiB) that unpacks into the same folder structure.

Do I need an account to send a folder?

Not on the same network. Sending across networks with a pairing code needs the sender to sign in, but the receiver never needs an account either way.

Pick a folder and send it exactly as it is — structure intact, every file verified.

Try Relayium now

Keep reading