uploadthing: a framework agnostic core, two wrapper packages, and twenty example apps
File uploads for modern web devs
At a glance
- What is it?
- uploadthing is a TypeScript SDK for file uploads, published as a monorepo of packages, examples and a docs site rather than as a library with a tutorial. The repository tells you a great deal about how the packages are built and released, and nothing at all about pricing or storage.
- Who is it for?
- uploadthing is worth evaluating as an SDK if you want TypeScript upload primitives with a framework agnostic core, official React and Solid wrappers, and twenty example apps to read. It tells you nothing about pricing, storage, or where files end up, so check uploadthing.com before committing a production upload path.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 49 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 18, 2026, and from our analysis. They are not legal advice.
Star history
- pingdotgg/uploadthing5,387 ★ · +58
| Repository | 2026-09-23 | 2026-11-18 |
|---|---|---|
| pingdotgg/uploadthing | 5.3k | 5.4k |
58 Stars in the last 56 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The README is three words long and the packages are the actual product
The landing page says one thing about itself: A thing for uploading files. The repository description is File uploads for modern web devs, the language is TypeScript, and the license is MIT. What follows that tagline is not a tutorial but an inventory, because the README opens by saying this repository contains the packages, docs and examples for uploadthing, and the table of contents links each entry to a directory instead of to a page of prose.
That shape matters for what you are actually looking at. Nobody is shipping a framework here. Three package directories carry the SDK, a docs directory holds the source for docs.uploadthing.com, and the example directories are the only place a claim about how to use it gets proved. If you are evaluating the SDKs, the examples are the fastest read in the repository. If you are evaluating the hosted service, none of this answers it.
The one navigational aid the README gives you is the link row at the top: Home, Docs, and a Roadmap pointing at a T3 tools notion page. The road map lives outside the repository on a Notion page, while the source for docs.uploadthing.com is in docs/.
One framework agnostic core with React and Solid sitting on top
Three package directories carry the SDK. packages/uploadthing is described as server/client stuff (framework agnostic), which makes it the piece that does not care what renders your form. packages/react is @uploadthing/react, the components and hooks for React projects, and packages/solid is @uploadthing/solid, the components and hooks for Solid projects.
The split tells you where your code has to live. Anything framework neutral belongs to the core package, and anything that touches a component or a hook belongs to a wrapper.
Worth noticing: the table of contents names three packages, while the root devDependencies also carry turbo 2.5.3-canary.1, typescript 5.8.3, and a workspace reference to uploadthing itself. And the recent release tags include @uploadthing/vue and @uploadthing/svelte, so more than two wrappers exist in the published set even though only the React and Solid ones are linked from the README. Treat the table of contents as an entry point, not as an inventory of what ships.
Node 22 and pnpm 10 are pinned, and every script is a turbo invocation
The workspace root package.json is named uploadthing-turbo, is marked private, and fixes its toolchain in the engines field plus a single exact package manager build:
"engines": {
"node": ">=22.x",
"pnpm": "10.x"
},
"packageManager": "[email protected]",The build, test and check commands then all route through turbo with a filter, which is how a monorepo of this shape keeps one command from running in the wrong place:
"build:all": "turbo run build",
"build:vanilla": "turbo run build --filter uploadthing...",
"build:react": "turbo run build --filter @uploadthing/react...",
"clean": "turbo run clean && git clean -xdf node_modules",
"test": "turbo run test --filter @uploadthing/* --filter uploadthing",
"test:all": "turbo test",
"test:watch": "turbo watch test --filter @uploadthing/* --filter uploadthing",
"typecheck": "turbo run typecheck"The clean script is the one to note. It runs git clean -xdf node_modules, which removes untracked and ignored files under that directory, so it is not a command to try on a machine where node_modules holds something you care about. Lint is also two things at once, combining turbo run lint with manypkg check, which is how the workspace dependency graph gets validated.
Examples cover twenty frameworks, but the table of contents links three
The examples/ directory holds twenty directories, and only three are linked from the README's table of contents: examples/minimal-appdir for the Next.js app directory, examples/minimal-pagedir for the Next.js pages directory, and examples/minimal-solidstart for SSR with SolidStart. The rest are reachable only by browsing the tree.
The directory names are more informative than the prose. There is a minimal-astro-react, a minimal-expo, a minimal-nuxt, a minimal-sveltekit, and a minimal-tanstack-start. Then there are integration examples rather than framework examples: with-clerk-appdir, with-clerk-pagesdir, with-clerk-react-router, with-clerk-remix, with-drizzle-appdir, with-drizzle-pagesdir, with-novel, with-react-image-crop, with-serveractions, with-tailwindcss, profile-picture, and backend-adapters.
Two different things are being demonstrated there. The minimal-* directories test the upload path on a framework, and the with-* directories test it next to somebody else's product. The presence of backend-adapters suggests the boundary between your server and theirs is where the interesting differences live, and that boundary is also the part the README says nothing about.
Every change needs a changeset before the pull request opens
Contributing here has a fixed order, and step five is the one that gets missed. Fork and clone the repository. Ensure you have the LTS version of Node.js installed, as well as the latest version of pnpm. Install the project dependencies. Implement your changes, as well as any documentation or tests that are required. Create a changeset for your changes. Open a pull request with your changes and changeset. The two commands that matter are short:
pnpm install
pnpm changesetThe changeset step is not bookkeeping for its own sake. The root tree carries a .changeset/ directory, and the root devDependencies include both @changesets/cli and @changesets/changelog-github, so the release note for a change is generated from the changeset instead of written by hand. A pull request that skips it carries no version bump.
There is one more condition worth flagging. The project asks that if your change also requires infrastructure changes, you reach out first so the necessary changes can be worked out on their end. Code that needs a server change is not something you can land as a lone pull request, and the README says so in a callout rather than burying it.
The three newest tags are one day and one project cutting three versions
Recent release tags do not look like one project cutting one version. [email protected] was published on 2025-08-17, @uploadthing/[email protected] on 2025-08-17, and @uploadthing/[email protected] on 2025-08-17. Three packages, two version numbers, one day.
That tells you the release unit is the package rather than the repository, and that the wrappers were not all on the same minor. The core sat at 7.7.4 while the Vue and Svelte wrappers named in the tag list sat at 7.3.3, so a project on a wrapper and a project on the framework agnostic core are not automatically on a matching version. Nothing in the README tells you how the wrapper versions are kept in step.
Set that against the source. The default branch is main, the last push landed on 2026-09-30, and the repository is not archived. The last push came more than a year after those tags, so the tag list may be a poor guide to what is in the tree. If you are picking a version, read the changelog the maintainers generate from changesets rather than assuming the newest tag is the newest code.
MIT covers the SDKs, and the tree holds four files nobody explains
The license is MIT, and the contributing section says all UploadThing SDKs are open source and welcomes contributions from the community. That sentence is precise in a way worth preserving: it says SDKs. The hosted service, the dashboard, and the upload pipeline itself sit somewhere this repository does not describe, and the homepage at uploadthing.com is where you would go looking for them.
The root tree is .changeset/, .envrc, .github/, .gitignore, .nvmrc, .prettierignore, .thing/, .vscode/, CODE_OF_CONDUCT.md, LICENSE, README.md, assets/, docs/, examples/, flake.lock, flake.nix, package.json, packages/, playground-v6/, playground/, pnpm-lock.yaml, pnpm-workspace.yaml, prettier.config.js, tooling/, and turbo.json. That is a source tree for libraries and a documentation site, not an operations repository, and nothing in it describes where uploaded files are stored or how they are served.
Four entries sit outside the JavaScript toolchain and are not explained anywhere in the README: .envrc, flake.nix, flake.lock, and .nvmrc. A contributor reproducing somebody else's setup has to work out what those do by reading them, which is a small but real gap for anyone who would rather follow written instructions.
Editorial conclusion
uploadthing is worth evaluating as an SDK if you want TypeScript upload primitives with a framework agnostic core, official React and Solid wrappers, and twenty example apps to read. It tells you nothing about pricing, storage, or where files end up, so check uploadthing.com before committing a production upload path. If you are contributing, install with pnpm on Node 22 and open the pull request with a changeset.
Frequently asked questions
what is uploadthing
uploadthing is a TypeScript toolkit for file uploads, described as File uploads for modern web devs and shipped as several packages from one repository. The tree holds packages/, docs/, and examples/, and the MIT license covers the SDKs.
what does uploadthing do
It provides the upload primitives for a web app. The core package is described as server/client stuff (framework agnostic), while @uploadthing/react and @uploadthing/solid add the components and hooks for React and Solid projects.
is uploadthing open source
The SDKs are. The repository is MIT licensed and the contributing section states that all UploadThing SDKs are open source and welcome contributions from the community. The hosted service behind it is a separate question the repository does not cover.
how to use uploadthing
Start from the example apps. The README links examples/minimal-appdir for the Next.js app directory, examples/minimal-pagedir for the pages directory, and examples/minimal-solidstart for SolidStart with SSR, and the source for docs.uploadthing.com lives in the docs/ directory.
is uploadthing a cdn
The repository does not say where uploaded files are stored or served from. It describes the packages as upload primitives for developers, names uploadthing.com as the homepage, and keeps the source for docs.uploadthing.com in the docs/ directory.
is uploadthing free
The repository states no pricing. What it does state is the MIT license on the SDK packages and the toolchain they need, namely Node.js 22 or newer with pnpm 10, enforced through the engines field in the root package.json.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pingdotgg-uploadthing)Star history chart for your README
[](https://hysenlabs.com/projects/pingdotgg-uploadthing)Was this useful?