Weave Code
Laravel Filex Laravel Package
devwizardhq/laravel-filex
Laravel Filex is a Dropzone.js-powered Blade component for Laravel with drag-and-drop uploads, chunked large-file transfers, real-time progress, multi-layer validation, quarantine security, temp storage, and auto cleanup.
laravel-filex is a powerful and reusable Blade component that brings modern, asynchronous file uploads to Laravel applications. It supports features like drag-and-drop uploads, real-time progress indicators, preview rendering, chunked upload for large files, and temporary file handling with finalization on form submission.
Frequently asked questions about Laravel Filex
- How do I install devwizardhq/laravel-filex in a Laravel app?
- Install it with Composer by running composer require devwizardhq/laravel-filex, then publish the package assets and configuration so the Blade component and Dropzone.js assets are available to your app. The component is designed as a drop-in, so you can render it inside an existing form and point it at your upload endpoint. Check the README for the exact publish tags and any config or migration steps for your version.
- Which Laravel and PHP versions does laravel-filex support?
- Laravel Filex targets Laravel 9 or newer on PHP 8.1 or higher, matching the framework baselines described in its technical assessment. The frontend relies on Dropzone.js, so your build setup (Vite or Webpack) or the package's published assets need to make that available. If you are on older Laravel or PHP versions you would need to upgrade before adopting it.
- Does laravel-filex support chunked uploads for large files?
- Yes. Laravel Filex automatically splits large files into chunks and uploads them in sequence, which is critical for video, high-resolution images, and other big payloads. Chunked transfers also make retries more reliable because a failed chunk can be resent without re-uploading the whole file. You should still plan concurrency safeguards and orphaned chunk cleanup for high-traffic environments.
- How do temporary files and cleanup work in laravel-filex?
- Uploads land in temporary storage first and are only moved to permanent storage when your form is submitted and validated. The package includes automatic expiration plus a scheduled cleanup for orphaned temporary files and quarantined content. Use a dedicated disk such as uploads_temp and monitor disk usage so abandoned uploads do not accumulate.
- Is laravel-filex secure against malicious file uploads?
- Laravel Filex layers client-side and server-side validation with file signature checks, threat detection, and a quarantine system for suspicious content. Always pair this with your own Laravel validation rules for size, MIME type, and authorization, since no package can cover every threat model. For public-facing endpoints, add rate limiting per user or IP and log rejected uploads.
- How do I use the laravel-filex Blade component in a form?
- Render the component inside your existing form and configure its upload endpoint, accepted file types, and validation rules. Files are uploaded asynchronously to temporary storage, then finalized when the form is submitted, which decouples the upload from permanent storage and keeps the operation closer to atomic. You can customize previews, metadata, and styling through the component's exposed options.
- Can I customize Dropzone.js configuration and styling in laravel-filex?
- Yes. The Blade component is highly configurable, with options for theming, styling, validation rules, and preview rendering. Dropzone.js settings such as max file size and chunk size are exposed through configuration, so you can tune behavior per form. Publish the config and views if you need to override defaults or add custom metadata handling.
- Does laravel-filex work with S3 or other cloud storage drivers?
- It works through Laravel's Storage facade and Filesystem contracts, so local, S3, and other standard drivers are supported, including streaming uploads. Custom or non-standard drivers should be tested for edge cases like partial uploads and temporary file permissions. For S3, make sure the bucket policy and multipart behavior fit your chunking configuration.
- How do I test file uploads with laravel-filex in my Laravel test suite?
- Use Storage::fake and UploadedFile::fake to isolate uploads in your test suite, then assert against the disk and any database records your finalization step creates. Test the chunk endpoint and the finalize-on-submit flow via HTTP tests, including validation failures and quarantine cases. Running the package's own test suite and CI workflow locally is also a good sanity check before upgrading.
- What are alternatives to laravel-filex and is it actively maintained?
- Alternatives include Livewire's native file uploads, Spatie Media Library for media management, and FilePond or other Dropzone wrappers. Laravel Filex differentiates itself with chunking, quarantine, and temp-file finalization built in as a Blade component. It is MIT licensed, ships with GitHub Actions test and code style workflows, and you should check recent releases and Packagist download activity to confirm maintenance cadence.
Weaver
How can I help you explore Laravel packages today?