Documentation menu

upup vs FilePond

FilePond (by PQINA) is a polished, highly accessible JavaScript uploader known for its silky image-optimization UX and a broad catalog of plugins, with first-party adapters for React, Vue, Angular, Svelte, and jQuery. It renders its own UI component and focuses on uploading local files and URLs to your own server endpoint. It does not include cloud-drive browsing, camera, or screen capture out of the box, and its full-featured image editing is a separate product (Pintura). upup is a headless core plus native UI that adds cloud drives, camera and screen capture, and an S3-compatible server with an HMAC-signed trust model.

At a glance

FeatureFilePondupup
Native first-party UIVanilla JS core + adapters: React, Vue, Angular, Svelte, jQueryReact, Vue, Svelte, Angular, Vanilla JS, Preact
Headless coreNo — renders its own UI componentYes (@upupjs/core)
License / pricingMIT, free & open source (the Pintura image editor is a separate commercial product)MIT, free & open source
Self-host incl. S3-compatibleYes — uploads to your own server endpoint (process / revert / restore), with chunk uploads; no built-in S3 signingYes — @upupjs/server presigns and proxies to any S3-compatible storage
Cloud-drive sourcesNo (local files, directories, blobs, local/remote URLs, Data URIs, paste)Google Drive, OneDrive, Dropbox, Box
Camera / screen captureNoYes (both)
Image editorVia plugins (crop / resize / transform); a full editor is Pintura (separate/commercial)Yes — React/Preact only
Resumable uploadsChunked uploads (server-driven)Yes — optional (tus or S3 multipart)
i18nConfigurable label strings (no locale bundles)Yes (ICU locale bundles)

Choose FilePond if

  • You want best-in-class image preview and optimization UX, smooth animations, and strong accessibility for a local-file upload flow.
  • You need a jQuery adapter, or you're happy uploading to your own server endpoint.
  • You want a mature, plugin-rich, single-purpose uploader and will add any cloud sources yourself.

Choose upup if

  • You need cloud-drive sources (Google Drive, OneDrive, Dropbox, Box), camera, or screen capture built in.
  • You want a headless core you can drive from your own UI, plus native UI across six frameworks with a shared DOM contract.
  • You want an included server that presigns and proxies to any S3-compatible storage behind an HMAC-signed trust model.