What continuous two-way folder sync means
There are two different jobs hiding behind the phrase “move files between Windows and Mac”. One is a transfer: you pick a file, send it once, and you are done. The other is continuous sync: you pick a folder, and from then on it stays the same on both computers. This page is about the second job. If you are still deciding which kind of tool you need, the overview Sync files between Windows and Mac compares six approaches. This guide assumes you have chosen folder sync and want to know exactly how it behaves.
In practice, continuous sync has three properties. It is automatic: a change on either computer is noticed and sent without you doing anything. It is two-way: the Windows PC and the Mac are equals, so there is no fixed “source” and “backup” side. And it is persistent: the folder is a standing arrangement, not a one-off copy, so the same rules apply on Monday as on Friday.
Foldpair implements this for selected folders between participating devices. The two computers do not have to be on the same Wi-Fi network, and the sync works alongside an existing VPN. Because it is a sync product rather than a nearby-transfer tool, it also keeps working when the other computer is asleep for a while: changes wait on the relay in encrypted form and arrive when that computer comes back online.
How a change travels from one computer to the other
When you save a file in a synced folder, the desktop app on that computer notices the change and encrypts the file content on the device with AES-256-GCM before anything leaves the machine. The encrypted data goes to a temporary, authenticated relay over a TLS connection. The relay stores and forwards ciphertext; the encryption keys stay on your participating devices. The other computer then pulls the data, decrypts it locally and writes the file into its own copy of the folder.
When an earlier version of a changed file is already known, the desktop app can send a binary delta instead of the whole file. For a large file with a small edit, that is the difference between sending a few changes and sending everything again. The relay is not a cloud drive: it carries encrypted data between your devices and has no file browser or storage plan of its own. The relay can see file names and sizes, but not file contents.
| What you do on one computer | What happens on the other |
|---|---|
| Create a new file | The file appears in the same place in the synced folder after the device pulls it. |
| Edit an existing file | The new version replaces the old one; when a previous version is known, only a delta may travel. |
| Rename or move a file | The change is normally applied as a rename, so the file keeps its place in the folder instead of being duplicated. If the other computer cannot safely tell that a file was renamed, for example because it holds unsaved edits under the old name, it keeps both copies rather than deleting anything. Renaming a file only by letter case is handled the same way. |
| Delete a file | The deletion is applied on the other computer; a copy that sync removes or replaces can be kept in that folder's local recovery bin. |
| Edit the same file on both computers before they sync | The first version to reach the relay keeps the original name; the other edit is preserved beside it as a conflict copy. |
| Switch the other computer off | Your changes wait on the relay and are delivered when it returns, within your plan's retention period. |
Set it up in six steps
- Download the current build for each computer from the download page. Windows and macOS (Apple Silicon and Intel) are both supported.
- Create or sign in to your account on the first computer.
- On the second computer, use Add another device on the first one. It shows a QR code, a link and a six-digit code; paste the link or code on the second computer's welcome screen to sign it in to the same account. Treat that link like a password.
- On the first computer, add the folder you want to keep in sync. Start with a new test folder holding a few harmless files, not your only copy of real work.
- Open the folder's Devices panel and switch the folder on for the other computer. Selective sync is per folder, and nothing is shared until you switch a second device on.
- Wait for the first sync to finish, then run the verification below before moving real files in.
If the second computer belongs to someone else, such as a colleague or a client, use a folder invitation instead of a device link. A device link signs another device in to your whole account, while an invitation shares one folder. The folder sharing help explains that case.
Where Windows and macOS differ
A folder that is fine on one operating system is not always fine on the other. Windows rejects some file names that macOS accepts. When a change arrives on a computer, the receiving app checks the path before writing it, and it refuses a change whose path contains characters such as < > : " | ? or *, a trailing space or period, or a reserved device name such as CON, PRN, AUX, NUL, COM1 or LPT1. In practice, avoid those names on the Mac side so that a file does not stall on its way to the Windows PC.
The default exclude list also keeps platform noise out of the relay. It skips operating-system leftovers such as .DS_Store, Thumbs.db and Desktop.ini, temporary and log files such as *.tmp and *.log, development folders such as .git and node_modules, and packaged installers and bundles such as *.dmg, *.pkg, *.msi and *.app. If a folder you expect to sync contains one of these, check the folder's exclude rules before concluding that sync is broken.
| Item | Windows and macOS behavior in Foldpair |
|---|---|
| File content | Encrypted on the device with AES-256-GCM before it reaches the relay. |
| Path validity | Paths that Windows cannot store are refused when a change is applied. |
| System and temp files | .DS_Store, Thumbs.db, Desktop.ini, *.tmp and *.log are excluded by default. |
| Conflict copies | Named <name>.conflict-<stamp><ext> and excluded from sync, so they stay on the device that preserved them. |
| App bundles and installers | *.app, *.dmg, *.pkg and *.msi are excluded by default. |
Verify the folder in both directions
- Create a small text file on the Windows PC and confirm the same file and contents on the Mac.
- Create a different small file on the Mac and confirm it on the Windows PC.
- Edit one test file on one computer, rename another, and delete a third. Confirm each result on the other computer.
- Open Settings and press Check now. The app compares, for each folder, the tracked list of paths, sizes and content hashes on every device, and reports whether the devices match, which devices were offline and which could not be checked.
- Only then move the real working files into the folder.
Conflicts, deletions and recovery
A conflict happens when both computers change the same file before either has synced with the other. Foldpair does not guess which version is right. The version that reached the relay first keeps the original name; on the computer with the later edit, the local version is preserved beside it as <name>.conflict-<stamp><ext> and the published version is applied. Open Review sync conflicts to find the copies, compare their contents, then keep one or both under separate names. The timestamp in the name does not prove which computer produced the copy.
Deletions also sync, so recovery matters. Files that sync removes or replaces can be kept in the folder's local recovery bin on that device, and the dialog restores a file to its original path when that path is free. A file you delete by hand is not guaranteed to appear there. Recovery copies stay on the device; no extra copy is uploaded. None of this replaces a backup. Keep a separate backup of anything that cannot be recreated.
Offline computers and plan limits
Sync is not required to have both computers online at the same moment. A change waits on the relay as ciphertext until every participating device has confirmed delivery or the plan's retention period ends. If the other computer returns after that period, an online device can send the file again on demand. The relay holds only data that has not yet been delivered, up to a per-plan buffer, and a single file larger than the available buffer waits in the queue.
| Plan | Devices | Relay buffer | Offline wait |
|---|---|---|---|
| Free | 2 | 1.5 GB in flight | 24 hours |
| Pro | 5 | 10 GB in flight | 7 days |
| Team | 10 | 30 GB in flight | 30 days |
The Free plan covers one Windows PC and one Mac. The buffer is the amount of undelivered data the relay holds at once, not a cap on how large the folder on your disk can be.
When folder sync is the wrong tool
If you only need to hand one file to a computer on the same Wi-Fi, a nearby-transfer tool such as LocalSend is simpler; see Foldpair vs LocalSend for the trade-off. If you need a browsable copy of every file in a web interface, folder sync is not that either, because the working copies live on your devices. The Android app handles one-off file transfers rather than full folder sync. Choose continuous folder sync when the same folder must be current on two computers that are not always side by side.
Frequently asked questions
Do the Windows PC and the Mac need to be on the same network?
No. Foldpair is designed to work across different networks through an authenticated temporary relay, and it is compatible with an existing VPN. Both computers need access to the Foldpair service.
Is sync really two-way?
Yes. Every device that has the folder switched on can send and receive changes. The label showing where the folder was created is only history, not a permanent one-way source.
What happens if I edit the same file on both computers?
The version that reached the relay first keeps the original name. The later local edit is preserved beside it as a conflict copy, and you compare the two files and decide what to keep.
Does the relay keep a permanent copy of my folder?
No. The relay is a temporary buffer, not storage: it holds encrypted data until all participating devices confirm delivery, and no longer than the plan's retention period (24 hours on Free, 7 days on Pro, 30 days on Team). Under storage pressure it keeps the latest version of a file longest and clears older versions first. Your working copies stay on your devices.
Can the relay read my files?
File contents are encrypted on the device with AES-256-GCM before they reach the relay, and the keys stay on your devices. The relay does see file names and sizes.
Is it safe to use for work I cannot lose?
Foldpair is in beta. Test with harmless files first, and keep a separate backup of irreplaceable data, because sync is not a backup.
Related guides and comparisons
Sources and related reading
- How Foldpair works — first-party description of the encrypted folder-sync and relay model; checked November 17, 2026.
- Sync conflicts help — first-party conflict-copy behavior; checked November 17, 2026.
- Recover a deleted file — first-party local recovery bin behavior; checked November 17, 2026.
- The relay buffer — first-party buffer sizes and retention by plan (Free 1.5 GB and 24 hours, Pro 10 GB and 7 days, Team 30 GB and 30 days, per the plan table on that page); checked November 17, 2026.
- Selective sync — first-party per-folder device switches; checked November 17, 2026.
- Check sync status — first-party verification check; checked November 17, 2026.
- LocalSend official site — official description of nearby local-network transfer; checked October 21, 2026.