Delivery and access
Control who can read a file, and observe the work it creates.
Public and private files
Public files can be read by anyone who knows their delivery URL. Private files require a valid short-lived signed URL issued through an authorized server or dashboard flow.
Changing a file to private revokes future unrestricted access after propagation. Copies already downloaded by a recipient cannot be recalled. Never embed permanent server credentials in a delivery URL.
Delivery accounting
Successful GET and Range responses contribute observed delivery bytes, including response headers under the published meter contract. Successful HEAD and 304 responses consume a request unit but no download bytes. Each Range request is its own delivery request.
Delivery logs can arrive late or be incomplete. Provider costs and per-app usage records are related measurements, not guaranteed identical totals. The billing ledger reconciles accepted usage under the defined closing window.
Paused normal delivery
Relevant quota exhaustion or a billing suspension can pause normal delivery. Authenticated export and cleanup follow the application’s retention policy. A delivery pause does not by itself permanently delete retained data.
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.