SwissTransfer
swisstransfer.com · Storage · 1 record · JSON
SwissTransfer (Infomaniak) Storage
caveatinstitutionno cardRper-object-cap
| Free tier | 50 GB per transfer, all files combined, no account required. Hosted in Infomaniak's own Swiss datacentres. One notable global property: the source is open (Infomaniak android/iOS/multiplatform clients on GitHub) and there is a working CLI. unit GB; metered on unstated |
|---|---|
| Price | none stated |
| Per-object cap | per-object-cap: 50 GB (50000000000 bytes) |
| Retention | Retention: 15 days by default; 30 only if the SENDER accepts an extension email on day 12 (offer open 3 days) (15 days) |
| Egress | unmetered, no egress pricing published; direct download links plus a 'Download All' ZIP (ZIP is capped — above 10 GB you must fetch files one by one). |
| Identity | institution derived from the record's prose, not from an identity field, and no signup was executed: s a working CLI. The write path requires human verification at the API: POST /api/containers without a recaptcha field returns 400 'The recaptcha field is required. (and 1 more error)'. swis |
| Limits |
per-object-cap: 50 GB per transfer (combined, not per file). Retention: 15 days by default; 30 only if the SENDER accepts an extension email on day 12 (offer open 3 days). After expiry Infomaniak states a link cannot be reactivated or extended. pull-count: download cap selectable at 1/20/100/250 — 'unlimited' requires a paid plan. Request-rate: the container-create endpoint enforces a reCAPTCHA field (see reliability note). |
| Binding | per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota |
| Interface | rest, cli rest |
| Tooling | swissfer (github.com/Blutsh/swissfer, 44 stars, pushed 2026-10-21) — Rust CLI, upload AND download, email-confirmed sender. First upload requires a 6-character code emailed to you, then cached. Upstream send-style clients do not work. |
| Composes with | Per-transfer 50 GB x unlimited transfers. With swissfer this is scriptable, so capacity is bounded by how many 50 GB transfers you are willing to mint, each living 15-30 days. |
| Reliability | The write path requires human verification at the API: POST /api/containers without a recaptcha field returns 400 'The recaptcha field is required. (and 1 more error)'. swissfer routes around this with an emailed 6-char confirmation, not with a token. The 30-day option is a trap — it silently deletes at 15 days unless the sender acts on day 12. |
| Notes | 50 GB per transfer, all files combined, no account required. Hosted in Infomaniak's own Swiss datacentres. One notable global property: the source is open (Infomaniak android/iOS/multiplatform clients on GitHub) and there is a working CLI. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
| Parsed numbers |
|
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | www.infomaniak.com/en/support/faq/2929/understanding-swisstr | '50 GB', retention table, download caps, 'cannot be reactivated or extended' |
| 2026-10-21 | www.swisstransfer.com/api/containers | probe: POST -> 400 {'message':'The recaptcha field is required. (and 1 more error)'} |
| 2026-10-21 | linkinseconds.com/blog/swisstransfer-limits | (Oct 2026) — independent confirmation of the day-12 extension mechanics |
Unknown or withheld values (3)
$.free_tier.notesprocess$.per_object_cap.notesnot-extracted$.retention.notesnot-extracted