file.io cURL Upload API: Endpoint, Expiry Rules, and Permanent URL Fix
file.io is a tiny upload API with a very developer-friendly shape: send one multipart/form-data request, get JSON back, copy the link field. For a debug log, a one-off build artifact, or a quick file handoff, that was exactly the right amount of API.
Current status (checked November 15, 2026): file.io is now LimeWire-branded, and the old upload API described below was retired in 2025; file.io now points developers to the LimeWire MCP server. Free links expire after 3 days, even if never downloaded, with up to 10 downloads per file per day. The cURL examples below are historical.
The catch is durability. On the free tier, file.io links expire after 3 days. This guide covers the old upload endpoint, the cURL command, the file form field, maxDownloads, expiry rules, size limits, and the practical fix when your app needs a URL that stays online.
Developer summary
- Old upload endpoint (retired in 2025):
POST https://file.io - cURL command:
curl -F "file=@report.pdf" https://file.io - Request body:
multipart/form-datawith the file attached asfile - Response: JSON with a
link,key, expiry fields, download count, and size metadata - Current free default: links expire after 3 days, with up to 10 downloads per file per day
- Use FilePost instead when: the returned URL needs to be a permanent CDN URL, listed later, deleted by API, or used inside production automation
file.io API Endpoint
The old file.io API used a single endpoint for uploads (retired in 2025):
POST https://file.io
The body is a multipart/form-data request with the file attached under the file field. There is no API key required for the free tier, and no separate "auth" call; the upload IS the whole flow.
Upload a File with cURL
The historical one-line cURL upload:
curl -F "file=@report.pdf" https://file.io
Historical response (JSON):
{
"success": true,
"status": 200,
"id": "abc123xyz",
"key": "abc123xyz",
"link": "https://file.io/abc123xyz",
"expiry": "3 days",
"expires": "2026-04-22T14:30:00.000Z",
"downloads": 0,
"maxDownloads": 1,
"autoDelete": true,
"size": 245810,
"mimeType": "application/pdf",
"created": "2026-04-19T14:30:00.000Z",
"modified": "2026-04-19T14:30:00.000Z"
}
The link field is the shareable URL. Send that to whoever needs the file, and they can download it from a browser or another cURL.
Upload with a Custom Expiration
The old API accepted an expires form field:
curl -F "file=@report.pdf" -F "expires=1d" https://file.io
Accepted values:
1y,2y,3y(years, paid plan required for longer periods)1w,2w(weeks)1d,7d(days)1h,6h,24h(hours, paid plan)
On the current service, free links expire after 3 days; longer retention means a paid LimeWire plan.
Upload with autoDelete Disabled (Paid)
On the old API's paid plans, you could keep the file available after the first download:
curl -F "file=@report.pdf" \
-F "autoDelete=false" \
-H "Authorization: Bearer YOUR_API_KEY" \
https://file.io
On the old API's free tier, autoDelete was always true.
Default Expiration Rules
This is where most confusion lives. The old API had a one-download default; the current service uses a simpler 3-day rule:
1. Old API: auto-delete after first download
On the old API, free-tier uploads defaulted to maxDownloads: 1 and autoDelete: true. The moment someone downloaded the file, it was gone. This is the behavior most developers remember, but it is not the current default.
2. Current service: 3-day expiry
On the current LimeWire-branded service, free links expire after 3 days even if nobody downloads the file, and each file can be downloaded up to 10 times a day without an account (20 with a free LimeWire account).
Plan for the expiry. Whatever you share through the free path, the link is gone after 3 days.
File Size Limits
| Plan | Max File Size | Storage / Retention |
|---|---|---|
| Free (no account) | 4 GB per upload | Links expire after 3 days |
| LimeWire Pro ($9.99/mo) | 250 GB per upload | 2 TB storage, files never expire |
| LimeWire Pro+ ($19.99/mo) | 500 GB per upload | 4 TB storage, files never expire |
Limits and prices from LimeWire pricing, checked November 15, 2026. If your real need is a link that stays online, see the alternatives section below.
Rate Limits
The old file.io API rate-limited anonymous IPs. If you hit 429 responses from a server running automated uploads, you are past the free-tier ceiling. Options:
- Upgrade to a paid plan, which raises the limit per authenticated key.
- Spread uploads across multiple IPs (not recommended).
- Switch to a service with predictable plan-based rate limits, like FilePost (10 req/second on free, 30 on Lite, 50 on Starter, 200 on Pro).
Downloading and Inspecting Files
Every upload response includes a link. Anyone with that URL can download the file:
curl -OJ https://file.io/abc123xyz
-O tells cURL to save the file; -J uses the server-provided filename if present.
The old file.io API did not provide a list-my-files or metadata-lookup endpoint on the free tier. Once you upload, you only know about the file through the response you captured. If you lose the response, you lose the file. Paid plans add account-level file management.
When file.io Is the Right Choice
file.io is a great fit when:
- You need a one-time share link (think: sending a debug log to a colleague).
- The file is under 4 GB.
- You want the link to disappear after a few days.
- You do not need a file management UI or API.
- You do not need the URL to stay stable in production systems.
When file.io Is the Wrong Choice
file.io does not fit when:
- You need a URL that remains available in production apps, emails, or automation workflows.
- You want to list, inspect, or selectively delete files later.
- You need file-upload ingress at scale with predictable rate limits.
- You want a paid plan but prefer flat pricing over tier-gated feature locks.
- You need the link to work for more than 3 days without a paid plan.
For those cases, a persistent upload API is the better shape. FilePost keeps the same developer flow, POST a file and get a URL, but the returned URL is a permanent CDN URL that stays up until you delete it.
FilePost cURL Upload Example
curl -X POST https://upload.filepost.dev/v1/upload \
-H "X-API-Key: your_api_key" \
-F "file=@report.pdf"
Response:
{
"url": "https://cdn.filepost.dev/file/filepost/uploads/a1/a1b2c3.pdf",
"file_id": "a1b2c3d4e5f6",
"size": 245810
}
The response url is a permanent CDN-backed URL. No expiration, no auto-delete, and no "this worked yesterday" debugging session when a workflow tries to reuse the link.
Try FilePost Free
One provisional 10 MB upload before verification, then 15 uploads/month and 50 MB files on Free. Full REST API.
Get Your Free API KeyQuick Comparison: file.io vs FilePost
| Feature | file.io | FilePost |
|---|---|---|
| cURL one-liner upload | Old API only (retired in 2025) | Yes |
| Permanent URLs | No (free links expire after 3 days) | Yes |
| File management API (list/delete) | Old API retired in 2025 | Yes (free) |
| Max file size (free) | 4 GB | 50 MB |
| Max file size (entry paid plan) | 250 GB (LimeWire Pro) | 500 MB |
| Free tier uploads | 3-day links, up to 10 downloads/day | 1 provisional / 15 verified |
| Starting paid price | $9.99/mo (LimeWire Pro) | 4 USD/mo (300 uploads, Lite) |
| Best fit | One-time transfers | Production file hosting |
Common file.io Error Codes (Old API)
- 400 Bad Request: Missing the
fileform field, or the file body is empty. - 413 Payload Too Large: File exceeds the free or paid size cap. Check the size caps in the table above.
- 429 Too Many Requests: Rate limit hit. Wait, slow down, or upgrade.
- 500 Internal Server Error: Transient server issue; retry with backoff.
Summary
file.io (now LimeWire) does one thing well: ephemeral file transfers. Free links expire after 3 days, which is fine for one-time sharing and the wrong choice for anything that needs a stable URL. Its old cURL API was retired in 2025.
If you need the cURL ergonomics of file.io plus permanent URLs, a management API, and predictable pricing, FilePost is the closest adjacent tool. Same muscle memory, different durability.