fshy

Home / Storage

Axfc Uploader (あぷろだ / axfc.net)

www.axfc.netAnonymous dumpstorage/axfc-uploaderJSONcomparereport an errorprovider JSON

Free allowance
No account, no total quota — per-object only.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
anonymous?placeholder, not evidence; card unknown, phone unknown
Binding limit
per-object-cap128 GiB per file
Evidence
documented5 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21
Free tierNo account, no total quota — per-object only. '1ファイル最大128 GiB。複数ファイルも順番にアップロードできます' (max 128 GiB per file, multiple files uploaded in sequence). Upload form constant data-max="137438953472" = 128 GiB, confirming the number in the markup.
unit GiB; metered on unstated
Pricenone stated
Limits
  • per-object-cap (binding) 128 GiB per file source
per-object-cap 128 GiB. Retention is client-chosen (published-until field showed 'No limit' on a live file) and additionally bounded by a download-count cap the uploader may set.
Identityanonymous (inferred, not read) not published
EgressNo egress meter or paid bandwidth product; the whole service is stated free ('本サービスは、別途明示する場合を除き無料です').
Per-object cap128 GiB per file (137438953472 bytes)
Retentionper-object-cap 128 GiB. Retention is client-chosen (published-until field showed 'No limit' on a live file) and additionally bounded by a download-count cap the uploader may set
Interfacerest, rclone rest
ToolingNo public API and no rclone backend — form-POST only, behind a Laravel CSRF token (_token) plus a session cookie, with delpass (delete key, >=8 chars) and optional expiry_datetime/maxcount. The legacy numbered URLs (/u/4144979) still resolve; new uploads get random /u/f_<22-char> URLs.
Composes withAccount-less: unlimited objects per IP x 128 GiB each, with 'No limit' available as the expiry. Chain is a re-upload loop only if you set an expiry; with expiry unset the object has no scheduled deletion.
ReliabilityThis is the legendary Japanese uploader and it is emphatically alive: the public file list was showing uploads from minutes earlier on the day of this run. But it has already had at least one near-death outage that lost voicebanks (UTAU Wiki recorded the site going dark and coming back with a broken certificate), and its own terms say no-expiry is 'not a promise of permanent storage'. Treat it as a live service with a history of vanishing.
Evidence notedocumented The page states the number in the record; the claim is documented, not measured.
Parsed numbers
  • has-free-tier 1
  • per-object-cap 128 GiB
Evidence 5
datesourcewhat it proved
2026-10-22www.axfc.net/128 GiB per file, no registration. Re-read https://www.axfc.net/: HTTP 200, 1911 bytes, sha256 313b5538c03c1b34. Quoted: 登録不要。小さな資料から大きなファイルまで。リンクひとつで、いつものように。 [ファイルを共有する ↗](https://www.axfc.net/upload)[ファイルを探す →](https://www.axfc.net/files) ✓ 会員登録なし✓ リンクで限定共有 ファイルをドラッグ&ドロップまたはファイルを選ぶ1ファイル最大128 GiB。複数ファイルも順番にアップロードできます。 広告 ## 最近の公開ファイル [一覧を見る →](https://www.axfc.net/files) アップロードした人が公開一覧への掲載を選んだファイルです。 [ZIPMedaBotsMugen.zipe17.7 MBOct 21, 2026, 23:07 UTC ↗](https://www.axfc.net/u/f_WH2-GZn7xyM_yFqIUbsiAw) ZIP261021-6.zip261021-6237.1 M
2026-10-21www.axfc.net/upload'1ファイル最大128 GiB', form constant data-max="137438953472"
2026-10-21www.axfc.net/u/4144979live share page reads 'Available until: No limit'; 'Published Oct 21, 2026'
2026-10-21www.axfc.net/filespublic listing shows uploads timestamped the same day (Oct 21 2026, 14:55 UTC), so the service is actively receiving files
2026-10-21source not publishedprobe: GET /download?tg=4144979 -> HTTP 405, Allow: POST; POST with a valid _token -> 302 back to /u/4144979 (needs a JS-driven second step)
More fields 1
verified[{"url": "https://www.axfc.net/","date": "2026-10-22","via": null,"http_status": 200,"bytes": 1911,"sha256": "313b5538c03c1b34fec046f4e8f898aaa7ff9f108bf963a2210a1895a939e415","pattern_found": true,"what_changed": "no change: the page still states the claim","capture": null}]
Unknown values 2
  • per object cap notes: 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