Transfer.it
transfer.it · 2 records in Storage · JSON
Records 2
- caveatTransfer.it (MEGA)
Storagefree tieridentity institution?card?limit retention-clampedevidence reportedstale on 2026-11-05disagrees
- fails: quotatransfer.it (mega) as a paid capacity route
Storageidentity email?card?evidence reportedstale on 2026-11-05disagrees
Transfer.it (MEGA)
StorageSibling records disagree:
- identity_kind:
storage/transfer-itsays institution, storage/transfer-it-as-a-paid-capacity-route says email - verdict:
storage/transfer-itsays qualifies-with-caveat, storage/transfer-it-as-a-paid-capacity-route says fails-quota
- Free allowance
- No per-transfer size limit (MEGA blog: 'Send 100 GB, 1 TB, or even more, all for free').
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- retention-clampedRetention: SERVER CLAMPS EXPIRY TO 90 DAYS
- Evidence
- reported5 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | No per-transfer size limit (MEGA blog: 'Send 100 GB, 1 TB, or even more, all for free'). Backing store is a fresh ANONYMOUS ephemeral MEGA account per uploader with mstrg = 21474836480 (20 GiB), read live from the API. unit TB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
per-object-cap: none advertised per transfer, but the real ceiling is the 20 GiB ephemeral-account storage (mstrg) — a transfer larger than the account's remaining space cannot complete. Retention: SERVER CLAMPS EXPIRY TO 90 DAYS. Verified with a:xl on transfers requested at 1d/90d/1y/10y/no-expiry: all returned e = now+90.00 days. The 10-year ceiling in transferit-py's docs (MAX_EXPIRY_SECONDS) is a CLIENT clamp the server silently overrides. Request-rate: not hit in ~10 uploads. |
| Identity | institution (inferred, not read) not published |
| Egress | unmetered; direct host-issued CDN URL (gfsXXX.userstorage.mega.co.nz) supports Range and returns 206. Link/bandwidth not metered per-download on the free tier. |
| Per-object cap | not stated |
| Retention | Retention: SERVER CLAMPS EXPIRY TO 90 DAYS (90 days) |
| Interface | rest, git, cli rest |
| Tooling | transferit-py (PyPI, github.com/viperadnan-git/transferit-py, 20 stars, pushed 2026-04-22) — CLI + library, pip install worked and roundtrip verified. Also NTFSvolume/mega.py has a read-only transfer.it client. |
| Composes with | Each Transferit() upload creates a NEW anonymous MEGA account (a:up + a:us, no email/phone) => 20 GiB x unlimited free accounts. Shard a file into 20 GiB (or 4 GiB) objects, one ephemeral account per shard, one URL per shard. Cost per identity: two unauthenticated API calls. |
| Reliability | Expiry IS re-settable in place: a:xm with a new 'e' on an existing xh works and returns 0 (verified 1d -> 30d -> 90d). This is the 'transfer as store' trick — an unexpired transfer can be pushed back to the 90-day wall indefinitely without re-uploading, so the object only dies if you stop touching it for 90 days. Parallel ranged GETs scale (0.29 MB/s @1 conn -> 2.73 MB/s @32 conn on a 32 MiB object, 206s throughout); occasional 403 on a range suggests per-connection shaping, not a hard pull cap. |
| Parsed numbers |
|
Evidence 5
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | transfer.it/t/JzZzzDxj2JCS | probe: transferit upload 1 MiB -> , download + sha256 match 66a5b62e...d1637 |
| 2026-10-21 | source not published | probe: a:uq on ephemeral session -> mstrg 21474836480 (20 GiB), identical across two independent sessions |
| 2026-10-21 | source not published | probe: a:xl after xm e=365d -> e=now+90.00 days (clamped); xm re-set to 30d then 90d both returned 0 |
| 2026-10-21 | transfer.it/t/<xh> | probe: GET -> 200 text/html 900 bytes (JS SPA; the URL is NOT a plain-GET byte link) |
| 2026-10-21 | blog.mega.io/introducing-transfer-it | (archived 2025-07-21) — 'No file size limits. Send 100 GB, 1 TB, or even more, all for free' |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
Sibling records disagree:
- identity_kind:
storage/transfer-itsays institution, storage/transfer-it-as-a-paid-capacity-route says email - verdict:
storage/transfer-itsays qualifies-with-caveat, storage/transfer-it-as-a-paid-capacity-route says fails-quota
- Free allowance
- Transfer.it has no paid tier of its own — it is a sharing front end that requires MEGA storage: 'You can only share files that you have uploaded to MEGA.' Its expiry selector offers up to 1
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Transfer.it has no paid tier of its own — it is a sharing front end that requires MEGA storage: 'You can only share files that you have uploaded to MEGA.' Its expiry selector offers up to 1 unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | transfer.it/ | the text of Free tier, above |
More fields 1
| dead end | {"failure_class": "quota","why": "Transfer.it has no paid tier of its own — it is a sharing front end that requires MEGA storage: 'You can only share files that you have uploaded to MEGA.' Its expiry selector offers up to 1","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field