Which situation are you in?
| Situation | What decides whether it works | What to do |
|---|---|---|
| Home computer and a laptop at the office | Both can reach the service. Neither needs to see the other's network. | Set up the folder once, then send a small test file. |
| Laptop on hotel, cafe or airport Wi-Fi | Outbound access to the service from that network. | Test on that network before you depend on it. |
| Guest Wi-Fi with client isolation | Isolation stops devices from seeing each other, which does not matter for relay sync. | A relay-based tool is not affected by isolation itself; confirm outbound access. |
| Existing VPN switched on | Whether the VPN profile lets traffic reach the service. | Keep the VPN; no extra Foldpair setup. See the VPN guide. |
| Mobile carrier or strict corporate firewall | Carrier NAT and firewall rules differ, and behaviour behind a specific one is not documented. | Test with a small file. See CGNAT and firewalls. |
| One device is switched off most of the day | Changes wait on the relay and arrive when it returns, within the retention window. | Check the retention for your plan before relying on long gaps. |
In every row the important requirement is not a shared Wi-Fi name. It is that each participating device can reach the Foldpair service and has been set up for the selected folder.
Why the relay is part of the design
Tools that find each other by announcing themselves on the local network cannot reach a device behind a different router. LocalSend, for example, says on its official site that it does not work over the internet. Direct peer-to-peer tools can bridge networks, but the result depends on NAT and firewall behaviour between the two machines.
Foldpair takes a different route. Each device makes an outbound connection to an authenticated temporary relay. For a folder with end-to-end encryption enabled, the sending device encrypts the folder contents first, so the relay carries ciphertext between your devices; a folder where it was never enabled is carried as plaintext over TLS. The relay holds undelivered data only until it is delivered or the plan's retention window ends. The working copies remain on the devices, and the relay is not a cloud-storage product with its own file browser. The full path of a change is described in how Foldpair works.
Set it up, and test each network
- Install the app on both computers from the download page and put them in the same account or add one as a device of the other (device pairing). Treat any pairing link like a password.
- Add the folder and switch on the second computer in the folder's devices list (choosing devices per folder). The click-by-click setup is in the setup section of the cloud-drive-free sync guide, so it is not repeated here.
- Run the first test on each real network you will use, with a small file in both directions, before you move the real working files in.
The screens are covered in the help articles on device pairing and choosing devices per folder. Both computers use the same folder key, which is sent to each device sealed to that device's key, so you do not copy any key by hand.

What to check after the first sync
- Both devices show the folder as up to date. Then run Check now in settings, which compares a digest of each folder's file list across your devices.
- The test file matches. Open it on both computers rather than trusting the status label alone.
- Large files. A single file larger than the currently free relay buffer space waits in the queue until room is available, but a file larger than the whole buffer of your plan never fits. The free plan allows 1.5 GB of undelivered data at a time and Pro allows 10 GB, so see the relay help article before syncing a disk image.
- Both versions on a clash. If you edit the same file on both computers before they sync, the later local edit is kept beside it as a conflict copy instead of being overwritten.
Adding a person on another network
The same setup works when the other computer belongs to a colleague or a client. Instead of signing in to your account, they receive an invitation to the folder, see who it is from and what it is for, and accept it before they get anything. You choose a role for them: Reader to view and download, or Editor to upload changes as well. The server rejects a Reader's uploads and edits. Each person decides which of their own devices keep a copy, independently of everyone else.
A folder invitation link is single-use and expires after seven days by default, so send it when the recipient is ready. The folder sharing help page walks through the screens, and member roles lists what each role can do.
Working with an existing VPN
You can keep an existing VPN active while using Foldpair, provided the VPN allows access to the service. No separate VPN setup is required. If the VPN is controlled by your employer, do not change its routing, proxy or DNS settings on your own; ask for the exact allowance needed. Verify the first transfer with the VPN profile and network you actually intend to use.
Comparing tools is a separate question
This page covers what the two networks need, not which tool to pick. In short: a local-network tool such as LocalSend needs both computers on the same network and, by its own site, does not work over the internet, while relay-based folder sync needs outbound access to the service from each computer. To choose between folder-sync tools on features, price and where the master copy lives, read sync files without Dropbox, OneDrive or Google Drive. For the local-network side, see the Foldpair vs LocalSend comparison.
Best for, and not the best fit
| Best for | Not the best fit |
|---|---|
| Selected folders that must stay current on computers that are not always near each other. | A quick offline transfer between two devices on one local network. |
| A Windows, Mac or Linux workflow where verifying the first transfer is acceptable. | A sole backup strategy for irreplaceable work. |
| Devices that are online at different times, within the plan's retention window. | Reading files in a browser while every computer is switched off. |
| People who do not want to run their own server. | A phone that must sync whole folders; the Android beta handles one-off file transfers only. |
Frequently asked questions
Can I sync files between two computers on different networks?
Yes. Foldpair is designed for it: each computer connects out to an authenticated temporary relay, so they do not need a shared Wi-Fi network. Both must be able to reach the service.
Do I need to open ports or set up a VPN?
No separate VPN setup is part of the normal workflow, and each computer connects out to the relay instead of waiting for incoming connections. You can keep an existing VPN as long as it allows access to the service.
What if one computer is switched off?
Changes wait on the relay in encrypted form and are delivered when the computer returns, within the plan's retention window: 24 hours on Free, 7 days on Pro and 30 days on Team.
Will it work on hotel, guest or corporate Wi-Fi?
Often, because it only needs outbound access to the service, but behaviour on a specific restricted network is not documented. Test with a small file on that network first.
Is my data encrypted while it travels between networks?
For folders with end-to-end encryption enabled, yes: contents are encrypted on the device with AES-256-GCM before upload, and TLS protects the connection. A folder where it was never enabled is uploaded as plaintext over TLS. The relay can still see metadata such as file names and sizes. See the security page.
Does the relay keep a permanent copy of my files?
Not permanently. It is a temporary buffer: it holds encrypted data until delivery or the end of the retention window, although under storage pressure it protects the latest live version of each file from early eviction. The working copies stay on your computers.
Which computers are supported?
Windows, macOS (Apple Silicon and Intel) and Linux (x64 and arm64). An Android beta handles one-off file transfers, and iOS is not publicly installable yet.
How is this different from syncing without a cloud drive?
This page is about reaching a computer on another network. The guide to syncing without a cloud drive compares tools such as Syncthing, Resilio Sync, a NAS and Nextcloud on features and where the master copy lives.
Related guides and comparisons
Sources and related reading
- How Foldpair works — first-party explanation of different-network behaviour and relay scope; checked November 17, 2026.
- Foldpair security — first-party explanation of protected payloads, keys and the beta boundary; checked November 17, 2026.
- The relay buffer — first-party help page for buffer size and retention; checked November 17, 2026.
- LocalSend official site — official statement that transfers stay on the local network and do not work over the internet; checked October 14, 2026.
- Syncthing: Relaying — official relay fallback behaviour and performance trade-off; checked October 14, 2026.
- Tailscale: Can I use Tailscale alongside other VPNs? — official coexistence limits and workarounds; checked October 14, 2026.