UPLOADFILE DOCUMENTATION
Framework adapters
Use the same upload model across your application stack.
Server and client packages
| Platform | Package or entry point |
|---|---|
| Next.js App Router | uploadfile/next |
| Next.js Pages Router | uploadfile/next-legacy |
| Express | uploadfile/express |
| Fastify | uploadfile/fastify |
| Remix | uploadfile/remix |
| H3 / Nitro | uploadfile/h3 |
| React | @uploadfile/react |
| Vue | @uploadfile/vue |
| Nuxt | @uploadfile/nuxt |
| Solid | @uploadfile/solid |
| Svelte | @uploadfile/svelte |
| Expo | @uploadfile/expo |
Shared configuration
Set UPLOADFILE_TOKEN and UPLOADFILE_API_URL in the trusted server environment. Each framework handler must preserve the raw request needed for signature validation and expose the configured route to your application.
Use types exported by your server file router to configure client components. Keep server tokens out of frontend configuration. Test progress, cancellation, multiple files, and errors in the target runtime before shipping.
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.