Direct-to-S3 / Azure tus 1.0 resume IndexedDB Golden Retriever 30 locales Webcam & screen capture

CoreUpload vs FilePond

FilePond is a polished, animation-rich uploader with a strong plugin ecosystem and first-party framework adapters. Its companion image editor, Pintura, is a commercial product in its own right.

The honest summary

FilePond is hard to beat on presentation and on breadth of framework adapters. If your priority is a refined drop-in UI for React/Vue/Svelte/Angular, it is a strong choice — and Pintura is a genuinely good image editor.

CoreUpload's centre of gravity is different: the transport layer and the ASP.NET Core server half. Image editing is included rather than licensed separately, but the UI is Razor-first rather than framework-adapter-first.

Side by side

Dimension FilePond CoreUpload
Scope Client library plus plugins; you supply the server. Client runtime plus ASP.NET Core endpoints.
Framework adapters First-party React, Vue, Svelte, Angular, jQuery. Razor Tag Helper plus first-party React/Vue hooks, Svelte action and Angular service in the package.
Image editing Via plugins; the full editor (Pintura) is licensed separately. Included: crop, annotate/redact, watermark, EXIF auto-orient, HEIC decode, AVIF/WebP output.
Architecture Small core with an official plugin ecosystem you compose. Batteries included; capabilities toggled by attributes/options.
Transports Chunked uploads supported; cloud/resumable via your endpoint or plugins. Seven strategies incl. tus 1.0, S3 multipart, Azure Blob, GCS resumable.
Instant upload (dedupe) Not built in. Opt-in SHA-256 dedupe (instantUpload): content the server already stores completes instantly with zero bytes transferred; the server hashes stored uploads itself.
Blazor JavaScript library - no Blazor component. Ships a native <CoreUploader /> Blazor component (Server + WebAssembly) with typed C# events, in the same NuGet package.
Licensing Core is open source; some add-ons are commercial. Commercial licence; free on localhost for evaluation.

If image handling is the deciding factor

CoreUpload's image pipeline runs in the browser before upload, so you send the processed asset rather than the original:

  • Content-aware crop with edge-energy suggestion. Demo
  • Annotate & redact before the file leaves the browser — useful when the redaction is the point.
  • EXIF auto-orient & HEIC decode, so iPhone photos are not sideways or unreadable.
  • AVIF / WebP output to cut bytes at the source.
  • Off-main-thread processing via Web Workers so large batches do not jank the page.