transloadit/uppy

Choose this fork only if you specifically need its old, customized state. For most adopters, current upstream Uppy is the better choice because this fork is materially stale and likely missing many years of fixes and features.

Choose this fork only if you need its specific legacy behavior or the large-batch preview change and are comfortable owning long-term maintenance. For new adopters, upstream Uppy is the safer default because this fork is materially stale and significantly diverged.

Prefer this fork only if you need the SharePoint/OneDrive customization and can accept a stale, heavily diverged codebase. For most adopters, upstream Uppy is the safer choice because it is active and far more current.

Choose this fork only if you need its specific legacy AWS/React Native-oriented behavior and can own long-term maintenance. For most adopters, upstream Uppy is the safer choice because this fork is stale and materially behind current development.

Prefer upstream unless you specifically need this fork’s customizations or legacy behavior. This fork is significantly behind and appears best suited for adopters who want a frozen, customized Uppy variant and are prepared to maintain it themselves.

Prefer upstream unless you specifically need Speechify’s custom legacy behavior. This fork is too stale and too divergent to adopt as a general-purpose uploader without accepting significant maintenance and upgrade risk.

Prefer upstream unless you specifically need this fork’s preserved 2021 behavior or customizations. This fork is suitable as a legacy, project-specific snapshot, not as a foundation for new work.

Prefer upstream unless you specifically need this old fork’s frozen state, branding, or bundled example/website setup. For active product work, this fork is too stale and too far from upstream to be a low-risk base.

Prefer upstream unless you specifically need this older snapshot. This fork is most defensible as a legacy-maintenance or archival codebase, not as a current production uploader.