Self-Hosted File Sharing Without a Server — Is It Actually Possible?

The Server Assumption Problem

Search for self-hosted file sharing and most results assume you have a server: a Windows Server machine, a Linux box running Nextcloud, a NAS they tell you to buy. The advice is technically correct but misses an important reality: most small offices do not have a dedicated server and are not planning to acquire one.

This article answers a different question: can you share files effectively across a small office network without any machine acting as a dedicated server? And if so, how?

What "Serverless" Actually Means Here

In this context, serverless means no machine is permanently dedicated to serving files. Every machine is both a client (accessing files) and a peer (making files available). No machine needs to be on for the others to work — each machine shares and accesses files independently.

This is the peer-to-peer model, and it is how most small office file sharing actually works in practice, regardless of what the IT guides say.

Option 1 — Windows SMB Peer-to-Peer Sharing

The simplest server-free approach is the built-in Windows file sharing system, used in peer-to-peer mode.

Each machine shares specific folders. Other machines access those shared folders directly. There is no central server — each machine hosts its own shares, and other machines connect to them on demand.

This works without any server hardware. The machine whose folder you are accessing needs to be on, but no permanent "server" machine is required.

The limitation is reliability: Windows SMB peer-to-peer sharing is subject to all the configuration and maintenance issues described throughout this site — service dependencies, credential management, firewall rules, and network location settings that can break after updates.

Option 2 — Dedicated LAN Transfer Applications

LAN transfer applications operate on the same peer-to-peer principle — each machine is equal, no machine is a server — but handle the discovery and transfer layers themselves rather than relying on Windows networking.

This is the most practical server-free option for small offices:

• Both machines are peers. Neither is a "server."
• No machine needs to be permanently on for others to function.
• Discovery is automatic — no IP addresses to manage.
• Transfers initiate on demand — you decide when to send a file, not when to sync.

Oxolan operates on this model. Install it on each machine. Each machine is visible to the others when it is running. Files are sent between machines directly.

Get Oxolan for Windows

LocalSend also uses this approach and is free and cross-platform.

Option 3 — Windows Public Folder

Every Windows machine has a Public folder (C:\Users\Public) that is shared automatically when file sharing is enabled. Any machine on the network can access it without credential configuration.

This is genuinely server-free and requires no setup beyond enabling sharing. The obvious limitations: no access control, no organisation beyond a flat folder, and everything is world-readable on the LAN.

For very small teams (2–3 people) with non-sensitive files and a trusted network, the Public folder approach works. For anything larger or more complex, it quickly becomes unmanageable.

Option 4 — Resilio Sync (Folder Synchronisation)

Resilio Sync uses a BitTorrent-derived protocol to keep folders synchronised between machines without a central server. Share a folder on machine A, add it on machine B, and the contents stay in sync automatically.

This is genuinely peer-to-peer and requires no server. It works across the local network and can also sync when machines are on different networks (via relay, or direct connection if ports are open).

The model is different from transfer: rather than sending a file on demand, Resilio keeps selected folders automatically mirrored. This suits some workflows well (shared project folders that everyone needs a copy of) and less well for others.

When You Actually Need a Server

Server-free approaches work well up to a certain scale and complexity. A dedicated machine acting as a file server is the right answer when:

• More than 8–10 people need to access a shared file location simultaneously
• Files must be accessible from remote locations without complex networks
• Access controls need to be granular (specific users can access specific projects)
• Version history is required for compliance or operational reasons
• Files need to be available 24/7 regardless of whether any particular user's machine is on

If your needs include any of these, a NAS device is the most practical entry point. Synology DS223+ with drives costs around $400–$500 and provides a proper file server without requiring IT expertise to maintain.

The Realistic Small Office Picture

Most small offices operate effectively with a hybrid approach:

• Peer-to-peer LAN transfer for moving files between colleagues
• Cloud storage (Dropbox, Google Drive) for remote access and client delivery
• No dedicated on-site server until the team grows large enough to justify one

This is not a compromise — it is the appropriate architecture for a team of 3–8 people. The server route adds complexity that only becomes worthwhile when peer-to-peer approaches start showing their limits.

Frequently Asked Questions

Can peer-to-peer file sharing work if machines are on different WiFi networks in the same building? Only if both networks are on the same subnet. Many offices have separate WiFi SSIDs for staff and guests that are on isolated subnets — devices on these cannot discover each other. Connect both machines to the same network (SSID) to enable peer discovery.

What happens if the machine with the file I need is turned off? In peer-to-peer mode, you cannot access files from a machine that is off. This is the fundamental limitation that a dedicated file server solves. For most office workflows, machines are on during working hours and this is not a practical problem.

Is peer-to-peer sharing less secure than a server? Not inherently. Security depends on the specific implementation: whether transfers are encrypted, whether access requires authentication, and whether the network itself is trusted. Both LAN transfer tools and Windows SMB have configurable authentication. The peer-to-peer topology itself is not a security weakness.

Can I run both peer-to-peer LAN sharing and a NAS simultaneously? Yes. Many offices use a NAS for the central file store and a LAN transfer tool for quick exchanges between individuals. They coexist without conflict.