Best file.io Alternative in 2026: 5 Services Compared
file.io is a popular service for one-time transfers, and it is now LimeWire-branded. 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. The old file.io upload API was retired in 2025. This reference covers its current limits, the historical API, and alternatives for permanent file URLs.
FilePost files have no automatic expiry by default. The first upload on a free account before email verification is provisional and expires after 24 hours unless the account verifies; any requested expiry also applies.
If the URL goes to another system
For an automation, the important test is not whether the upload succeeds once. It is whether the next node can fetch the URL later.
Upload → capture the URL → save or send it downstream → fetch it again.
Use file.io for intentional expiry. Use FilePost when the URL is an application record, a hosted asset, or a durable automation output.
file.io at a Glance: Defaults and Limits
| Setting | Default / Limit |
|---|---|
| Default expiration | 3 days (free), even if never downloaded |
| Download limit (free) | Up to 10 downloads per file per day (20 with a free LimeWire account) |
| Max file size (free) | 4 GB per upload (no account) |
| Max file size (paid) | 250 GB LimeWire Pro; 500 GB Pro+ |
| Upload endpoint | POST https://file.io/ (retired in 2025; file.io points to the LimeWire MCP server) |
| Body format | multipart/form-data with file field |
| Authentication | Anonymous uploads; free LimeWire account optional |
| Paid plans start at | $9.99/month (LimeWire Pro) |
file.io Default Expiration: 3 Days on the Free Sharing Path
On file.io's free sharing path (now LimeWire-branded), links expire after 3 days, even if nobody downloads the file, and the file is removed from storage within about a week. Each file can be downloaded up to 10 times a day without an account. Treat the expiry as part of the link's contract, not as storage you can assume will remain available. See file.io and LimeWire pricing.
In practice, a free file.io link has two limits:
- 3-day expiry: the link stops working after 3 days, whether or not anyone downloaded the file.
- Daily download cap: up to 10 downloads per file per day without an account (20 with a free LimeWire account).
The expires, maxDownloads, and autoDelete parameters belonged to the old file.io API, which was retired in 2025. On the current service, keeping files longer means a paid LimeWire plan.
Paid LimeWire plans use a different model: Pro is $9.99/month (250 GB uploads, 2 TB storage, files never expire) and Pro+ is $19.99/month (500 GB uploads, 4 TB storage). That is separate from the free sharing path. If you need a simple account-owned API with durable public URLs and predictable upload-count plans, FilePost is the narrower alternative.
file.io File Size Limits by Plan
file.io allows large individual files, which is one of its main selling points. The per-file maximum depends on your plan:
- Free (no account): 4 GB per upload; links expire after 3 days
- Free LimeWire account: 4 GB per upload, 40 GB storage, 20 downloads per file per day
- 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
Note that the per-file size is only one constraint. Free links also expire after 3 days and have a daily download cap. If you are doing automated uploads at scale, the expiry and download limits tend to bite before the file size limit does.
file.io Upload API: Endpoint and curl Example
The old file.io upload endpoint was a single POST. file.io retired this API in 2025 and now points developers to the LimeWire MCP server, so treat the examples below as historical:
# Historical: old file.io API (retired in 2025)
curl -F "file=@report.pdf" https://file.io
# Historical: custom expiration and download limit
curl -F "file=@report.pdf" "https://file.io?expires=7d&autoDelete=false&maxDownloads=10"
A response from the old API looked like this (historical):
{
"success": true,
"status": 200,
"id": "abc123",
"key": "abc123",
"name": "report.pdf",
"link": "https://file.io/abc123",
"expires": "2026-09-16T10:32:14.123Z",
"expiry": "3 days",
"downloads": 0,
"maxDownloads": 1,
"autoDelete": true,
"size": 204800,
"mimeType": "application/pdf",
"created": "2026-09-13T10:32:14.123Z",
"modified": "2026-09-13T10:32:14.123Z"
}
The old API's upload parameters were:
expires: how long until the file expired. Accepted values like1dor1w, or an ISO 8601 duration.maxDownloads: number of downloads allowed before the file was deleted.autoDelete: whentrue, the file was deleted after reachingmaxDownloads.
When file.io's Ephemeral Model Is a Problem
file.io's short-lived links are a feature for one-time file transfers. It becomes a liability the moment you need the URL to be stable. Common situations where developers run into the limit:
- Storing file URLs in a database. User avatars, uploaded documents, form submissions — anything the app will re-read later. The URL breaks after 3 days.
- CMS or blog asset hosting. Images referenced in published content need to load every time a reader visits, not just once.
- Automation webhooks. Zapier/Make/n8n workflows that upload a file and pass the URL to another step break once the 3-day link expires.
- Sharing links with unknown download counts. Link-unfurlers, preview bots, and scrapers count toward the daily download cap before the human opens the link.
If any of those are your use case, you need a file upload API with durable public URLs. That is exactly what FilePost provides — the same simple curl -F upload pattern as file.io, but URLs have no automatic expiry by default.
FilePost vs file.io: Ephemeral vs Permanent
This is the single most important distinction between the two services, and it should drive your decision:
- file.io: Free links expire after 3 days, even if never downloaded, and the URL stops working once the file is gone. Paid LimeWire plans list files that never expire.
- FilePost: Files are stored on Backblaze B2 and served through Cloudflare CDN. URLs have no automatic expiry by default and stay available until you delete the file, configure expiry, or the account is terminated.
If you are building a one-time file transfer tool, a "send this to someone" feature, or a temporary paste service, file.io is a great fit. If you are building anything where the file URL needs to persist: user avatars, document storage, hosted assets, form submissions, you need FilePost.
Quick Comparison Table
| Feature | FilePost | file.io |
|---|---|---|
| File permanence | Permanent (until you delete) | Free: 3-day links; paid LimeWire plans: files never expire |
| CDN delivery | Yes (Cloudflare) | No CDN delivery |
| Authentication | API key required | Anonymous (optional account) |
| File management API | Yes (list, delete, metadata) | Old upload API retired in 2025 |
| Dashboard | Yes | Limited |
| Intake links (shareable upload pages) | Yes | No |
| Max file size (free) | 50 MB | 4 GB |
| Free tier uploads | 1 provisional / 15 verified | 3-day links, up to 10 downloads/day |
| Swagger / OpenAPI docs | Yes | No |
| Paid plan starting price | $4/mo | $9.99/mo (LimeWire Pro) |
Uploading a File: curl Examples
Both upload flows are simple. Here is how they compare side by side (the file.io API shown is the old one, retired in 2025).
Upload with file.io (historical API)
curl -F "file=@report.pdf" https://file.io
Response:
{
"success": true,
"key": "abc123",
"link": "https://file.io/abc123",
"expiry": "3 days"
}
On the current service, a free file.io link expires after 3 days even if nobody downloads it, with up to 10 downloads per day. Check the current plan before relying on a link.
Upload with FilePost
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": 204800
}
That URL is served from Cloudflare's CDN. You can share it, embed it, and store it in your database.
Upload with Python
import requests
# file.io (historical API, retired in 2025): temporary link
resp = requests.post("https://file.io", files={"file": open("report.pdf", "rb")})
print(resp.json()["link"]) # expires after 3 days
# FilePost : permanent CDN URL
resp = requests.post(
"https://upload.filepost.dev/v1/upload",
headers={"X-API-Key": "your_api_key"},
files={"file": open("report.pdf", "rb")}
)
print(resp.json()["url"]) # permanent
When file.io Is the Right Choice
file.io solves a different problem. Use it when:
- You need short-lived links. Sending a file to someone and you want the link to die after a few days? That is file.io's core feature.
- You want anonymous uploads. file.io does not require an API key or account for basic usage. If you need zero-friction, no-auth file sharing, it works.
- You are transferring files between machines. Quick one-time transfers from a server to your laptop, from CI to a staging environment, or between two scripts that do not need persistent storage.
If any of those describe your use case, file.io is a solid pick. But if you answered "no" to all three, keep reading.
When FilePost Is the Right Choice
FilePost is built for developers who need file URLs that last. Use FilePost when:
- Your app stores file URLs in a database. User profile photos, uploaded documents, form attachments. FilePost URLs do not expire by default; they remain available until you delete the file, configure expiry, or the account is closed.
- You need a file upload and management API. file.io retired its old upload API in 2025; FilePost keeps the product centered on an upload API, upload-count plans, and durable CDN URLs.
- You want CDN performance. FilePost serves files through Cloudflare's global CDN. For apps that embed uploaded content (images, PDFs, downloads), this matters.
- You need an intake page for someone else to upload through. FilePost's intake links provide a shareable upload page and associate the files with your account. Use this when you want a managed handoff rather than anonymous file sharing.
- You want a dashboard. FilePost gives you a web dashboard to browse, search, and manage your uploaded files. Useful when you need to find a file without writing code.
- You need authentication. FilePost requires an API key, which means only your workflow can upload to your account. file.io's anonymous model is a feature for some use cases, but a liability for others.
- Automation output. FilePost gives the next node a durable
urlvalue that can be stored, delivered, or fetched again after the workflow finishes.
Pricing Comparison
Both services offer free tiers, but the paid plans differ in what you get.
FilePost Pricing
- Free: one provisional upload before verification, 15/month after email verification, 50 MB max file size
- Lite ($4/mo): 300 uploads/month, 100 MB max file size
- Starter ($9/mo): 1,500 uploads/month, 200 MB max file size
- Pro ($29/mo): 7,500 uploads/month, 500 MB max file size
All plans include CDN URLs with no automatic expiry by default, the file management API, dashboard access, and intake links.
file.io (LimeWire) Pricing
- Free: 4 GB uploads, links expire after 3 days, up to 10 downloads per file per day (a free LimeWire account adds 40 GB storage and 20 downloads per file per day)
- LimeWire Pro ($9.99/mo): 250 GB uploads, 2 TB storage, files never expire
- LimeWire Pro+ ($19.99/mo): 500 GB uploads, 4 TB storage, files never expire
Prices from LimeWire pricing, checked November 15, 2026. The free sharing path remains ephemeral, while paid plans list files that never expire.
Migrating from file.io to FilePost
If you are currently using file.io and want URLs that do not expire by default, the migration is a few lines of code. The upload pattern is nearly identical.
Step 1: Get Your API Key
Sign up at filepost.dev and grab your API key from the dashboard. The free tier starts with one provisional upload before verification and unlocks 15/month after email verification for testing.
Step 2: Swap the Endpoint
# Before: file.io
curl -F "file=@photo.jpg" https://file.io
# After: FilePost
curl -X POST https://upload.filepost.dev/v1/upload \
-H "X-API-Key: your_api_key" \
-F "file=@photo.jpg"
The main differences: you add the X-API-Key header, and the response gives you a CDN URL with no automatic expiry by default instead of a 3-day link.
Step 3: Use the File Management API
Unlike file.io, FilePost lets you list and manage your files after upload:
# List your files
curl -H "X-API-Key: your_api_key" https://filepost.dev/v1/files
# Delete a file
curl -X DELETE -H "X-API-Key: your_api_key" \
https://filepost.dev/v1/files/a1b2c3d4e5f6
FAQ
What is file.io's default expiration time?
file.io is now LimeWire-branded. Free links expire after 3 days, even if the file is never downloaded, and each file can be downloaded up to 10 times a day without an account (20 with a free LimeWire account). Check file.io before relying on a link.
What is file.io's maximum file size limit?
4 GB per upload without an account. LimeWire Pro lists 250 GB uploads and Pro+ lists 500 GB.
What is the file.io upload API endpoint?
The old endpoint was POST https://file.io/ with a multipart/form-data body containing a file field. That API was retired in 2025, and file.io now points developers to the LimeWire MCP server. Treat older curl -F ... https://file.io examples as historical.
Can I use file.io for permanent file hosting?
Not on the free path: free links expire after 3 days. LimeWire Pro ($9.99/mo) and Pro+ ($19.99/mo) list files that never expire, but they use a different storage and billing model. For a focused upload-count API with durable public URLs, FilePost is a direct alternative.
What is the best file.io alternative for developers?
FilePost is the closest alternative to file.io for developers who want a simple upload API with URLs that do not expire by default. Both services use a single POST request to upload. FilePost adds CDN delivery, a file management dashboard, intake links, and API key authentication.
How much does FilePost cost compared to file.io?
FilePost's free tier starts with one provisional upload before verification and unlocks 15 per month after email verification, with 50 MB max file size. Paid plans start at $4/mo (Lite: 300 uploads, 100 MB max), then $9/mo (Starter: 1,500 uploads, 200 MB max) and $29/mo (Pro: 7,500 uploads, 500 MB max). file.io (now LimeWire) paid plans start at $9.99/mo for LimeWire Pro and use a different storage and transfer model. Compare the workflow and usage meter, not only the headline price.
Test a small upload
Test the request with a small file from your own workflow. If the URL resolves in the next step, the basic integration is working.
Test a small upload