uploadfile.
UPLOADFILE DOCUMENTATION

Usage and limits

Four quantities make capacity and cost visible.

The four meters

MeterHow it accumulatesExcess rate
StorageTime-weighted live GB above allowance$0.25 / GB-month
DownloadsObserved successful delivery bytes$0.45 / GB
Live filesTime-weighted file count above allowance$0.25 / 1,000 file-months
Request unitsWeighted authorized operations$65 / million units

Request unit examples

  • One authorized file session: 4 units. One accepted part: 1 unit. A normal single-PUT upload totals 5 units.
  • An upload with 100 accepted parts totals 104 units.
  • One successful delivery GET, HEAD, or 304: 1 unit. Each Range request counts separately.
  • File management and list operations count per file item, with a minimum of one.
  • Deletion, cancellation, cleanup, dashboard internals, identity, and billing actions are not billable units.
  • A repeated idempotent logical operation is not charged twice. Backend retries do not add duplicate user charges.

Time-weighted excess

Storage and file excess are integrated over the actual billing period. If 10 excess GB remains for half of the period, it contributes 5 GB-months. A higher allowance starts after the paid upgrade is confirmed; previously accrued excess does not disappear.

Downloads and request units are period counters. Upgrades add only the remaining-period fraction of those allowances. Changing plans or disabling overages does not reset prior consumption.

Up nextBilling

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.