How to share an entire folder with someone

Why folder structure matters

Many workflows depend on relative paths. A web project expects CSS, JavaScript and images to live in specific directories. A design system might keep fonts and references in separate folders. If you try to send files one by one, the recipient has to manually recreate your structure, which is slow and error‑prone. Sharing the whole folder as a single package is usually much more reliable.

At the same time, you still want the benefits of private file sharing: end‑to‑end encryption, no unnecessary copies on remote servers and the ability to work with large payloads. Free Transfer's P2P model and no file size limit approach make it ideal for this scenario, as long as you prepare the folder in a way that travels well.

Option 1: compress the folder into an archive

The simplest and most universal method is to compress the folder into a single archive file before you share it. On Windows, macOS and Linux you can usually right‑click a folder and choose an option such as "Compress" or "Send to > Compressed (zipped) folder". This creates a `.zip` or similar archive that preserves all subfolders and file permissions that make sense on your platform.

Once you have the archive, you can drag and drop it into Free Transfer. Because the app does not impose a platform‑side file size limit, this works equally well for small and large projects. The recipient will download the archive, extract it and end up with an identical folder structure on their machine. This method is simple, requires no extra tools and works across operating systems.

Option 2: select multiple files and folders directly

On many modern browsers you can select multiple files at once in the file picker, and in some environments you can include folders as well. When you do this in Free Transfer, the app builds an internal representation of your selection and streams the files over the P2P connection. The recipient then reconstructs the hierarchy on their side.

This approach can be convenient when you do not want to create archives manually or when you are working from a context where zipping is not straightforward. However, support for selecting folders directly is still evolving across platforms, so the archive method remains the most predictable option if you want to be certain that the full tree structure is preserved.

Ensuring privacy while sharing folders

Regardless of whether you send a single archive or multiple files, Free Transfer keeps the same privacy and security guarantees. When you create a room or use a Nearby Devices flow, the app sets up an encrypted WebRTC channel between your browser and the recipient's browser. File data is broken into chunks, encrypted and streamed directly between peers.

No server along the way stores your files or long‑term logs of their contents. This means you can send files secure even when the folder contains sensitive information, as long as you trust the recipient and keep your own device safe. Once you close the browser tab, the session ends and there is nothing left on our infrastructure.

Tips for smoother folder sharing

A few practical tips can make folder sharing even more pleasant:

• Clean up temporary files such as build outputs or `.DS_Store` entries so you do not send unnecessary data.
• Document what you are sending in a `README` file so the recipient immediately understands the folder's purpose.
• Check total size before sending, especially on slower connections. While Free Transfer does not limit you, your bandwidth and patience still matter.
• Coordinate with the recipient so they are ready to receive; this helps avoid timeouts.

These habits apply whether you share a tiny script or a massive design project. They also make it easier to version and reuse the same folder later.