Nested paths stay intact
Browser folder selection keeps relative paths, subfolders and predictable duplicate-name handling.
A client should see the same project you packed—not a pile of loose filenames.
Move a complete project without flattening filenames or asking the recipient to rebuild the hierarchy.
Campaign launch
24 files · structure preserved
The flow
Choose Add a folder
Review the preserved paths
Share one link or send by email
What changes
Browser folder selection keeps relative paths, subfolders and predictable duplicate-name handling.
A folder and its files share one access policy, expiry and recipient link.
Recipients can move through the hierarchy and download an individual file or the complete bundle.
The same structure remains useful in the sender workspace after delivery.
Trust detail
Paths are normalized before storage. Traversal sequences and blocked executable types are rejected.
Structure survives
Nobody should rename forty files to rebuild a hierarchy that already existed. Drop in a folder tree and it stays one transfer, with its shape intact on the other side.
Quick answers
Yes. A folder upload stays one transfer and keeps its hierarchy instead of arriving as a flat list.
No. Folder hierarchy lives inside one transfer. A Collection is your own private way of grouping complete transfers.
No. Compressing it yourself only hides the structure the recipient is meant to see.
Yes. Recipients can download the whole transfer or select the files they need.
Keep going
Send a file, share the link, and see for yourself what changes.