Filament Chunk Upload Laravel Package

Product Decisions This Supports

• Unblocking large-file features without infrastructure work. If the roadmap includes video uploads, course media, product assets, legal documents, or dataset ingestion, this package removes the "raise upload_max_filesize and hope" workaround that usually stalls those features. It lets a chunked-upload capability ship inside an existing Filament admin panel rather than as a separate service.
• Build vs. buy for upload plumbing. The alternative is either (a) hand-rolling chunk assembly, temp-file lifecycle, and validation workarounds inside your Filament resources, or (b) commissioning S3 presigned/multipart direct-to-bucket uploads. This package is the cheap option: a thin, purpose-built Filament field wrapping rahulhaque/laravel-filepond. Choose it when upload volume is modest and the admin panel is the primary ingestion surface.
• Scope decisions on where uploads live. Because it targets Filament forms specifically, adopting it is also a decision that file ingestion happens in the admin panel rather than through a public API or end-user app. That constrains which personas can upload and should be confirmed against the customer-facing roadmap.
• Storage and access-control decisions. The ->visibility('private') + streamDownload guidance signals a private-disk posture, which is the right default for regulated or customer-confidential content. This supports roadmap items that require authenticated file delivery rather than public URLs.
• Deferring media-pipeline work. The package covers transport, not post-processing. Virus scanning, transcoding, thumbnailing, and retention policies remain your responsibility — budget those explicitly rather than assuming the upload feature is "done" at merge.
• Use cases that fit well: internal CMS/media libraries, LMS video and audio, HR/legal document intake, product image sets beyond a few MB, customer onboarding requiring large attachments.

When to Consider This Package

Adopt when most of these are true:

• The application is Filament-based and the upload UX belongs in a form (create/edit resource), not a bespoke front end.
• Real user files are exceeding your PHP limits today, or you expect them to within the planning horizon.
• You want a single, configurable field (->chunkSize(), ->directory(), ->visibility()) with a familiar Filament API rather than a custom component.
• Your infra is conventional PHP hosting or a single app server — i.e., direct-to-object-storage multipart uploads are overkill or blocked.
• You can accept private-disk storage plus authenticated streaming as the delivery model.

Look elsewhere when:

• You are not on Filament, or uploads originate from an API, mobile client, or public-facing form.
• You need very high volume or very large files (multi-GB, many concurrent uploads) — S3/GCS multipart with presigned URLs is cheaper and more scalable than proxying chunks through PHP.
• You require built-in scanning, transcoding, or resumable-across-sessions behavior; this package does not provide a media pipeline.
• Supply-chain risk tolerance is low. This is a v1.0.0 with a single maintainer and a hard dependency on rahulhaque/laravel-filepond. That is acceptable for internal tooling, harder to justify for a revenue-critical, externally facing path.
• Your team cannot absorb maintenance of a young dependency — pin versions and expect to read the source when Filament or FilePond upgrades land.

How to Pitch It (Stakeholders)

For executives: We can ship large-file upload — video, document, and asset ingestion — inside the admin panel without new infrastructure or a dedicated upload service. It's a small, focused component layered on an existing, established FilePond backend, so the cost is a Composer dependency and a config publish, not a build. The caveat is maturity: version 1.0.0, one maintainer, and no media processing — so treat it as transport only and fund scanning/transcoding separately if the roadmap needs it.

For engineering: iperamuna/filament-chunk-upload provides a ChunkedFileUpload Filament field that splits files into configurable chunks (default 10MB), delegating to rahulhaque/laravel-filepond for the server side. It works around Filament's array-based validation in BaseFileUpload to accept single-string FilePond IDs, and provides secure dehydration that moves temp files to final storage on submit while preserving original filenames. Configurable via filepond.server.url for non-default deployments. Two things to verify before adoption: temp-file cleanup and orphan handling, and the security of the dehydration path — that's where chunked uploaders usually break. Pin the version and review the source; it's a young package.