The one-line version
Encrypted copies stay on the relay until all participating devices confirm delivery (or are removed), or until your plan’s retention period ends (24 hours on Free, 7 days on Pro, 30 days on Team). This frees buffer space; the working copies remain on your devices.
What the relay is — and isn’t
When you add or change a file, Foldpair (with folder encryption on) encrypts it on your device and pushes it to the relay. Your other devices pull it back down, decrypt it, and write it to disk. It is not deleted as soon as one device downloads it: the relay holds the encrypted copy while other participating devices are still offline, and drops it once they all confirm delivery or when the retention period ends. The relay never holds a key, so it cannot open the file contents it stores (it does see names and sizes).
Because it’s a pass-through buffer, it has a size limit — the amount of not-yet-delivered data it will hold for you at once. That’s the number on the RELAY card in the app.
| Plan | Relay buffer | Retention | Devices |
|---|---|---|---|
| Free | 1.5 GB in flight at a time | 24 hours | 2 |
| Pro | 10 GB in flight at a time | 7 days | 5 |
| Team | 30 GB in flight at a time | 30 days | 10 |
Under storage pressure, the relay protects the latest live version of your synced files from early eviction so offline devices are not stranded, while expired backlog can be cleared first. By default the relay keeps every non-deleted version of a file until delivery is confirmed or the retention window ends; a shorter grace window for superseded versions exists but is switched off, so it does not shorten the periods above. Delivery confirmation from every participating device, or the end of your plan’s retention window, is always the upper bound on how long the relay keeps a copy, and the relay removes its copy then; if an offline device returns after expiration, an online device can re-upload the file on demand.
Separately from the buffer, the relay’s default ceiling is 1 GiB per file, the same on every plan. For an encrypted folder the ceiling applies to the encrypted upload, so the original file has to be slightly smaller.
Why a big file can be blocked at 35% full
Each file must fit within the buffer’s currently available space. So a single very large file can be turned away even when the buffer looks mostly empty:
- Say your buffer is 1.5 GB and 525 MB is already in flight — that’s about 35% used, with about 975 MB free.
- A video of about 1 GB (just under the per-file limit) won’t fit in those 975 MB — although it would fit in an empty 1.5 GB buffer — so it waits in the queue until space frees up.
- The app will say “this file is larger than your free relay space” and list the exact file and its size. That’s not the buffer being full — it’s one file being too big for the room it needs.
“Storage limit reached” on one folder
If a folder shows this in red while your overall usage is low, check whether it contains a file larger than the available relay space. Open “not synced” on the Home screen to see exactly which file and how big it is.
How to get it moving
- Bring receiving devices online. As they download queued files, buffer space becomes available. A waiting file can then transfer if it fits within the plan’s total buffer limit.
- Exclude very large files from the folder if they don’t need to sync (VM images, disk images, big scratch files).
- Upgrade to Pro for a 10 GB buffer if you routinely move large files.
End-to-end encryption
For a synced folder with end-to-end encryption enabled, file contents are sealed on your device first — the relay stores and forwards them as ciphertext it has no way to read. The desktop app turns this on by default for folders the device owns, once every device in the folder supports it; a folder where it was never enabled, or whose devices do not all support it, syncs as plaintext. It does see metadata such as file names, sizes and timing. See how Foldpair encryption works for the full picture.