# Transfer.it

> transfer.it | Storage; 2 records: free tier, limits, identity cost and evidence.

HTML https://fshy.ajam.dev/p/transfer/ | JSON https://fshy.ajam.dev/api/v1/entity/transfer.json | how to read a record: https://fshy.ajam.dev/llms-full.txt

## Transfer.it (MEGA)

- `storage/transfer-it` | qualifies-with-caveat | evidence reported | binding retention-clamped | category cloud-drive
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://transfer.it
- disagrees on identity_kind: `storage/transfer-it` says institution, `storage/transfer-it-as-a-paid-capacity-route` says email
- disagrees on verdict: `storage/transfer-it` says qualifies-with-caveat, `storage/transfer-it-as-a-paid-capacity-route` says fails-quota
- 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 | read on: 2026-10-21 | source: [1]
- per-object cap: not stated | source: [1] | note: not stated
- retention: Retention: SERVER CLAMPS EXPIRY TO 90 DAYS | days: 90 | source: [1] | note: not stated
- 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. | metered: no
- identity: institution
- interface: rest, git, cli
- limits:
  - per-ip-shaping: 0.29 MB/s [1]
  - per-ip-shaping: 2.73 MB/s [1]
  - retention-clamped (binding): Retention: SERVER CLAMPS EXPIRY TO 90 DAYS [1]
- limits note: 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.
- interface detail: 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.
- notes: the same as the free tier
- evidence:
  - [2] 2026-10-21: probe: transferit upload 1 MiB -> , download + sha256 match 66a5b62e...d1637
  - withheld 2026-10-21: probe: a:uq on ephemeral session -> mstrg 21474836480 (20 GiB), identical across two independent sessions
  - withheld 2026-10-21: probe: a:xl after xm e=365d -> e=now+90.00 days (clamped); xm re-set to 30d then 90d both returned 0
  - [3] 2026-10-21: probe: GET -> 200 text/html 900 bytes (JS SPA; the URL is NOT a plain-GET byte link)
  - [4] 2026-10-21: (archived 2025-07-21) — 'No file size limits. Send 100 GB, 1 TB, or even more, all for free'
- sources:
  - [1] https://transfer.it/
  - [2] https://transfer.it/t/JzZzzDxj2JCS
  - [3] https://transfer.it/t/<xh>
  - [4] https://blog.mega.io/introducing-transfer-it

## transfer.it (mega) as a paid capacity route

- `storage/transfer-it-as-a-paid-capacity-route` | fails-quota | evidence reported | binding none | category rejected-provider
- identity a placeholder: card and phone unknown | verified 2026-10-21 (inherited) | stale on 2026-11-05
- url https://transfer.it/
- disagrees on identity_kind: `storage/transfer-it` says institution, `storage/transfer-it-as-a-paid-capacity-route` says email
- disagrees on verdict: `storage/transfer-it` says qualifies-with-caveat, `storage/transfer-it-as-a-paid-capacity-route` says fails-quota
- 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 | read on: 2026-10-21 | source: [1]
- per-object cap: not recorded | source: [1] | note: not recorded
- retention: not recorded | source: [1]
- egress: not recorded | metered: no
- identity: email
- interface: unknown
- tooling: not recorded
- composes with: the same as tooling
- reliability: the same as the free tier
- notes: the same as the free tier
- extras:
  - dead_end.failure_class: quota
  - dead_end.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
  - dead_end.first_recorded: 2026-10-21
- evidence:
  - [1] 2026-10-21: 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
- sources:
  - [1] https://transfer.it/