Pomf.lain.la
- Free allowance
- Max upload size is 1 GiB, wow!
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- per-object-cap1 GiB per file
- Evidence
- measured3 sources; a live request was made and its output kept
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | Max upload size is 1 GiB, wow! unit GiB; metered on none; No account, no email, no cap on the number of files stated. |
|---|---|
| Price | USD 0 |
| Limits |
|
| Binding | per-object-cap At 1 TiB a month this is 1 024 objects of 1 GiB; the cap is what forces splitting, and no rate or byte counter was observed to bind first. |
| Identity | anonymous Multipart POST with no account, no email and no cookie; a link came back. |
| Egress | Downloads are served from pomf2.lain.la; no byte allowance and no download counter are published. free allowance: none published |
| Per-object cap | Max upload size is 1 GiB (1073741824 bytes) |
| Retention | unverified: the homepage publishes no expiry and the FAQ was not readable as text (served gzip without a decoded body to the reader) |
| Interface | rest, cli POST https://pomf.lain.la/upload.php multipart field 'files[]'. JSON reply with success, files[0].url, .hash (SHA-1), .size. The stored object is served from the pomf2 host. endpoint: https://pomf.lain.la/upload.php |
| Tooling | curl -F 'files[]=@file' https://pomf.lain.la/upload.php; an optional 'speedkey' field exists for a queue priority the site calls Speedkeys |
| Composes with | 1 GiB per object with no account is the right shape for a single large media file or a dataset shard: two files cover a 2 GiB upload that most relays refuse, and the JSON reply carries SHA-1 so the store can be verified without a second download. |
| Reliability | Uploads were switched off during a PHP CVE and switched back on, per a comment left in the homepage HTML; treat availability as hobby-grade. |
| Notes | The caveat is retention, which nobody states: a 1 GiB cap is worth nothing if the file is gone in a week, and that is the one number still missing. |
| Evidence note | measured Upload, read-back and SHA-256 match, at 1 MiB. The 1 GiB claim is the vendor's and was not pushed to. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe: https://pomf.lain.la/upload.php | POST of 1 048 576 bytes -> HTTP 200, {'success':true,'files':[{'url':'https://pomf2.lain.la/f/nck8aluy.bin','size':1048576,'hash':'c96b568c...'}]} |
| 2026-10-23 | probe: https://pomf2.lain.la/f/nck8aluy.bin | read-back 1 048 576 bytes, sha256 da0099c231f1182a5d411c8ac5149dfb7a2e3578a3970928490cb78ba92aecc9, full-body hash matched |
| 2026-10-23 | pomf.lain.la/ | 'Max upload size is 1 GiB, wow!' and the comment that uploads had been disabled for a PHP CVE and are back |
More fields 2
| cap stated bytes | 1073741824 |
|---|---|
| sha1 echoed | c96b568c8726029947ffc0e752a2bb7463030153 |