Built for developers who'd rather ship than configure storage.

PostFile is a file hosting API. You send a file, you get back a permanent public CDN URL. No S3 buckets, no IAM roles, no CloudFront distributions. One API call, one URL.

PostFile exists because the same problem kept showing up across projects: "I need to upload a file and get a URL." Every time, it meant setting up object storage, configuring permissions, wiring up a CDN, and writing upload logic. For what should be a one-liner.

How it works

Files are stored on Backblaze B2 (the same infrastructure behind many large-scale storage providers) and served through Cloudflare's CDN network. This combination gives you:

The stack

Python + FastAPI Backblaze B2 storage Cloudflare CDN Stripe billing MySQL database Hetzner infrastructure

Why PostFile exists

Most file hosting solutions are either too complex (S3 + IAM + CloudFront), too limited (free tiers with expiring links), or too expensive for what they offer. PostFile sits in the middle: simple enough for a weekend project, reliable enough for production.

The API is designed for developers and automation workflows. If you use Zapier, n8n, Pipedream, Make, or any tool that can make HTTP requests, PostFile works out of the box. PostFile is approved as a public Zapier app, has a verified n8n Cloud community node, and includes a native Pipedream component for drag-and-drop file uploads.

How we operate

PostFile is run independently. No VC funding, no growth-at-all-costs roadmap, no acquisition exit timeline that ends with the API getting deprecated.

Trust signals

Questions?

PostFile is based in Stockholm, Sweden.

Email support@@postfile.net — every message gets a reply.