Weave Code
Filament Multi Source Upload Laravel Package
happenv-com/filament-multi-source-upload
Filament file upload field that accepts a local file or a URL, always materializing the file onto the target disk.
Frequently asked questions about Filament Multi Source Upload
- What is happenv-com/filament-multi-source-upload?
- It is a Filament field package that replaces the standard FileUpload component. The main difference is that users can add a file either from their local disk or from a URL. It is intended for Laravel applications that use Filament forms.
- How do I install filament-multi-source-upload in a Laravel app?
- Install it with Composer using composer require happenv-com/filament-multi-source-upload. Then use the package field in your Filament form schema instead of the normal FileUpload field. Check the repository README for any asset publishing or configuration steps.
- Does filament-multi-source-upload work with Filament v3?
- The package is designed as a FileUpload replacement for Filament forms, so it targets Filament-based admin panels. Filament v3 is the current major line, but you should confirm the exact supported version in the package composer.json and README before installing. Test compatibility first if you are on a different Filament major version.
- Can users add a file from a URL instead of their disk?
- Yes. The core feature is letting users choose between a local disk file and a remote URL. Both sources feed into the same field so your form and storage flow stay consistent. Review the README for accepted URL schemes and any host restrictions.
- Is filament-multi-source-upload a drop-in replacement for FileUpload?
- It is designed to be used in place of Filament FileUpload in your form schemas. That means you can swap the component without rebuilding the whole form around it. Verify any FileUpload methods you rely on against the package README, since URL sourcing can add extra behavior.
- How does URL file upload work and is it safe?
- The field accepts a URL as a source and then adds the remote file through the same upload flow as a disk file. You should validate URL schemes, file size, MIME type, and trusted hosts before enabling it broadly. For production, consider server-side allowlists and timeouts to reduce SSRF risk.
- Can I validate file types and sizes with this field?
- Because it replaces Filament FileUpload, you can generally use the same Filament validation methods such as acceptedFileTypes and maxSize. Confirm each method in the README because URL-sourced files may need extra checks. Server-side validation is still required regardless of the UI field.
- Does it support multiple files or image-only uploads?
- The package focus is multi-source uploads, meaning disk or URL, rather than necessarily multiple-file selection. You can likely combine it with Filament modifiers like multiple() and image(), but verify support in the docs. Test multi-file and image-only behavior in a staging form before relying on it.
- Is filament-multi-source-upload maintained and production ready?
- Review the GitHub repository for recent commits, tagged releases, issue activity, and Laravel and Filament version constraints. Any package that fetches remote URLs should be security-reviewed for SSRF, file size, and MIME validation before production. Pin a tested version in composer.json and cover the field with your own tests.
- What are alternatives to filament-multi-source-upload?
- Filament built-in FileUpload covers local disk uploads but not URL sources by default. Alternatives include adding a separate URL input with custom handling or using a media library package alongside FileUpload. This package is best when you want both disk and URL sources in one familiar field.
Weaver
How can I help you explore Laravel packages today?