Introduction
A developer workspace for file uploads, storage, and delivery.
How Uploadfile works
Your application declares an upload route and authorizes the user on your server. Uploadfile checks the file policy and available capacity, then issues short-lived upload destinations. File bytes travel directly to object storage. Processing and your completion callback finish the workflow.
The dashboard organizes files into applications. Your organization owns the people, permissions, and billing relationship; each paid application has its own subscription and invoice.
Storage-region availability depends on the deployment. The application creation screen lists the enabled regions; supported regions in the SDK are not a promise that every location is currently available.
The building blocks
| Concept | Purpose |
|---|---|
| Organization | People, roles, billing identity, and the shared Free pool |
| Application | Files, server API keys, home region, plan, and limits |
| File router | Typed upload rules and application authorization |
| Upload session | Reserved capacity, presigned parts, and completion state |
| File | Stable key, optional custom ID, visibility, and lifecycle state |
Before your first upload
- Accept your invitation and verify your email.
- Create an organization and application.
- Enable strong authentication for privileged roles.
- Create a server API key with only the scopes your integration needs.
- Follow the quickstart and configure the service endpoint for your environment.
A backend connection is required for a working workspace. Unconfigured environments show an explicit service error and do not create simulated accounts or files.
Uploadfile is an independently operated service. The framework SDK is forked from the MIT-licensed UploadThing SDK; UploadThing’s hosted backend is not included in that source.