Design constraints
Cross-network file synchronization requires a rendezvous point reachable from both sides. Foldpair centers that path on a temporary authenticated relay, shaped around three engineering requirements: keeping folder and clipboard payloads unreadable at the relay, delivering edits saved while a peer was powered down, and avoiding full-file uploads after tiny edits whenever feasible.
Every end-to-end encrypted directory satisfies the first two requirements. Only non-encrypted directories get byte-level delta uploads, reflecting an explicit architectural choice explained below.
The data path in five hops
| Hop | What happens | Form of the data |
|---|---|---|
| 1. Device | The agent notices a change in a selected folder and prepares an upload | Plain file on your disk |
| 2. Encrypt | For an end-to-end folder, contents are sealed with AES-256-GCM on the device | Ciphertext |
| 3. Upload | Sent to the relay over TLS by an authenticated device | Ciphertext inside TLS |
| 4. Relay | Held until every participating device confirms delivery or retention ends | Ciphertext, plus names, sizes and timing |
| 5. Receive | Other devices download, verify, decrypt and apply the file locally | Plain file on their disk |
Unlike a cloud drive, the relay offers neither web-based file browsing nor hosted storage tiers; authoritative working trees stay on your enrolled computers. For a walkthrough of device enrollment and relay routing, read how Foldpair pairs folders.
Content encryption on the device
When end-to-end encryption is active on a synced folder, the local agent seals file payloads using AES-256-GCM prior to upload while keys stay strictly on participating endpoints. Clipboard transfers follow that identical encryption path. Desktop builds enable folder encryption automatically on newly owned folders once all member devices advertise support; directories where encryption was never switched on, or that include a legacy endpoint, transmit plaintext.
Transport TLS wraps the network socket as an outer layer, though relay confidentiality does not rest on TLS: payloads are already AES-256-GCM ciphertext before touching the wire. Key distribution, frame nonces, and observable metadata are detailed in our threat model write-up.
Delta transfer: exactly where it applies
Binary delta transfers rely on FastRsync and run strictly on plaintext relay sessions, meaning folders where end-to-end encryption is off. Because the desktop client activates end-to-end encryption by default on folders it owns, any modified file inside an encrypted folder is freshly encrypted and uploaded whole as a single ciphertext blob, and receivers never offer a delta basis on potentially encrypted folders.
| Case | Upload behavior |
|---|---|
| Folder with end-to-end encryption | Changed file re-encrypted and uploaded in full |
| Folder without it, earlier version unknown | Whole file uploaded |
| Folder without it, earlier version known, file under 256 KiB | Whole file uploaded |
| Folder without it, earlier version known, file of 256 KiB or more | FastRsync delta, used only when it is under 50% of the file |
That boundary is by design. Because the relay holds only opaque ciphertext, it cannot diff versions server-side, and fresh per-frame nonces ensure re-encrypted edits share zero matching ciphertext blocks with prior uploads. On encrypted folders, Foldpair prioritizes payload secrecy ahead of upload volume, meaning edits to big files transmit the entire encrypted object again. Prioritizing delta bandwidth over relay opacity is an explicit per-folder encryption choice rather than a quirk to bypass.
First-party delta benchmark, with its limits
Every measurement below applies strictly to folders without end-to-end encryption. Numbers were captured in a reproducible first-party harness running the exact FastRsync primitives and tuning used by the sync agent (XxHash3 alongside Adler32RollingV3) on a 6-vCPU Linux arm64 virtual machine.
| Scenario | Delta size | Share of file |
|---|---|---|
| Same-length in-place 4 KiB edit in a 1 GiB file | 4,332 bytes | about 0.0004% |
| Same-length in-place 5 MiB edit in a 500 MiB incompressible file | 5,243,111 bytes | about 1.0% |
Notice that the second test case adds just 231 bytes of framing overhead beyond the modified 5 MiB slice, illustrating typical framing cost on incompressible payloads. Rolling-hash signatures stay cached locally on disk rather than uploading to the relay.
What the relay holds and for how long
Encrypted file payloads remain unreadable to the relay, though it observes file names and byte sizes, plus payload type, origin device, and timestamp on clipboard items. Delivery tracking state also lives there temporarily, whereas permanent folder copies reside strictly on your machines.
Relay blobs are purged as soon as all enrolled folder endpoints acknowledge receipt or the tier's retention ceiling expires, whichever occurs earlier, setting a hard lifetime cap. Updates pushed while a machine is powered off wait in the relay buffer and download once it reconnects inside that retention window. By default, the superseded-version grace window stays disabled so active historical versions are shielded from quota eviction; turning it on permits quota pressure to evict only older superseded revisions.
| Plan | Undelivered data in flight | Retention | Linked devices |
|---|---|---|---|
| Free | 1.5 GiB | 24 hours | 2 |
| Pro | 10 GiB | 7 days (168 hours) | 5 |
| Team | 30 GiB | 30 days (720 hours) | 10 |
Any individual file exceeding currently open buffer capacity pauses locally in the upload queue. Independently, a server-configured limit caps each upload at 1 GiB by default; because desktop sync counts both ciphertext framing and a thin request wrapper toward that 1 GiB ceiling, plaintext files inside an encrypted folder need to stay marginally below 1 GiB. Operational guidance on stalled large uploads is covered in the relay help.
Failure modes worth designing around
- Mixed-version folders. One device without encryption support leaves the whole folder as plaintext, so the delta rules for folders without end-to-end encryption apply.
- Device offline past retention. The relay copy is gone; an online device can upload the file again on demand.
- Oversized files. A file over the per-file ceiling is refused by the relay, and a file larger than your plan's whole buffer can never fit.
- Metadata sensitivity. File names and sizes are visible to the relay even when contents are not.
Synchronization never substitutes for independent backups. Whenever you pair a new directory, confirm end-to-end delivery using a small disposable file first and maintain separate offline or versioned backups for critical work.
How to use this page
Keep the benchmark context attached to any cited figure: those delta measurements cover synthetic workloads in folders without end-to-end encryption. When assessing Foldpair for heavy binary assets, run trials with representative files under your target encryption mode, and review the security model prior to placing confidential data inside a non-encrypted folder.
Frequently asked questions
Does Foldpair use delta sync for encrypted folders?
No. Delta transfer applies only to folders without end-to-end encryption. An encrypted folder re-encrypts each changed file and uploads it in full.
Which delta algorithm does it use?
FastRsync binary deltas, used for files of at least 256 KiB and only when the delta is under 50% of the file.
What did the benchmark measure?
In folders without end-to-end encryption, a 4 KiB in-place edit of a 1 GiB file produced a 4,332-byte delta, and a 5 MiB edit of a 500 MiB incompressible file produced 5,243,111 bytes. It was synthetic, without inserted bytes, and not a comparison with other products.
What can the relay see?
File names and sizes, and for clipboard items the item type, source device and time. It cannot open encrypted contents.
How long does the relay keep data?
Until all devices confirm delivery or retention ends: 24 hours on Free, 7 days on Pro, 30 days on Team.
How much can wait on the relay?
1.5 GiB in flight on Free, 10 GiB on Pro and 30 GiB on Team.
Is the relay a cloud drive?
No. It carries encrypted sync data between participating devices and has no file browser or storage plans.
Related guides and comparisons
Sources and related reading
- Product overview: pairing, relay, offline delivery — first-party walk through the sync path that this page examines at engineering depth; checked November 18, 2026.
- Encryption page: formats and key flow — first-party description of content encryption, key wrapping and what stays visible to the relay; checked November 18, 2026.
- Relay help: buffer and retention — first-party help for undelivered data, plan buffers and large waiting files; checked November 18, 2026.