Weave Code
Laravel Filemanager Laravel Package
unisharp/laravel-filemanager
A responsive file manager for Laravel with a clean, mobile-friendly UI. Browse, upload, crop, resize, and organize files and folders, then integrate it with any WYSIWYG editor via CKEditor, TinyMCE, or Summernote adapters, with configurable storage and access control.
UniSharp Laravel FileManager is a ready-to-use file and media manager for Laravel applications, providing a responsive interface for browsing, uploading, and organizing files. It integrates seamlessly with CKEditor and TinyMCE, letting users pick and insert images directly into rich-text editors.
Features:
- Drag-and-drop uploads with thumbnail previews
- Built-in image cropping, resizing, and optimization
- Out-of-the-box CKEditor and TinyMCE integration
- Per-user folders with access control and private storage
- Configurable storage paths and multi-language support
Frequently asked questions about Laravel Filemanager
- How do I install UniSharp Laravel FileManager in a Laravel app?
- Install it with Composer using unisharp/laravel-filemanager, then publish the package config and frontend assets. Configure your storage disks and folder paths, apply authentication and authorization middleware to the file manager routes, and wire your editor adapter. A basic spike is usually one to two engineer-days, while a production rollout with access control and storage hardening is closer to five to ten.
- Does UniSharp Laravel FileManager integrate with CKEditor and TinyMCE?
- Yes. It ships adapters for CKEditor and TinyMCE, and the package also supports Summernote and a standalone upload button or iframe route. Users can browse, upload, and insert images directly into rich-text editors. This covers common CMS, blog, help-center, and knowledge-base authoring without building a media library.
- Which Laravel versions does this file manager support?
- It is a Laravel package with a service provider, publishable config, routes, middleware hooks, Blade views, and assets, so it installs like a normal Composer package. The exact Laravel and PHP compatibility ranges depend on the version you pin, so check the Packagist metadata and composer constraints for that release. Run the install and route wiring in a spike before committing to a version.
- How do I set up per-user folders and private file access?
- Multi-user mode is opt-in, and the default shared-folder behavior is easy to ship by accident. Configure per-user folders and private storage when you need isolation, and apply your own auth middleware to the file manager routes. The package supplies the folder model, but tenant boundaries, ACL semantics, and quota policy remain your application's responsibility.
- Can I store uploaded files on Amazon S3 instead of local disk?
- Storage is deferred to Laravel's filesystem abstraction, so you can start on the local disk and move to S3 or another cloud disk later without changing the upload UX. Version 2.14.0 added support for S3 bucket-owner-enforced, ACL-disabled buckets, which matters if your organization uses modern S3 defaults. Pin at least that version if you rely on those buckets, and test downloads, visibility, and path handling in your environment.
- How do I secure file uploads and prevent executable files or XSS?
- Do not rely on package defaults for upload safety. Treat executable and script content as a high risk, use an allowlist-only posture, validate MIME types, store files on a private disk or outside the web root, and keep the file manager behind authentication and authorization middleware. Pin at or above 2.6.3 for the image preview XSS fix, at or above 2.6.4 for the path traversal fix, and at or above 2.15.1 for the empty-extension upload fix.
- Does it support image cropping, resizing, and optimization?
- It delegates image manipulation to intervention/image and supports cropping, resizing, and rotating, with optimization and format conversion added in version 2.15.0. Pin intervention/image explicitly because the package has moved across major versions, including v3 support and later v4 support. Treat intervention/image upgrades as coordinated changes rather than transitive bumps.
- Are there events I can use for audit logging or virus scanning?
- Events, expanded in version 2.4.0, give you a hook for audit logging, virus scanning, and CDN invalidation without forking the package. Verify during your spike that the event surface covers upload, rename, move, and delete for the version you pin, not just upload. Wire your listeners around your own policy and storage rules.
- Does UniSharp Laravel FileManager require database migrations?
- In the modern line the package has no database migrations of its own; files are managed through Laravel storage. That keeps rollback and environment promotion simpler because there is no package schema to migrate. Confirm this against the exact version you pin during the spike rather than assuming it.
- Is it a good fit for an API-first app, and what are the alternatives?
- It fits a Blade, Livewire, or Inertia admin surface well, but it fits an API-first product with a fully custom React or Vue media library poorly because its main seam is an iframe or popup route rather than a documented JSON contract. For editor-driven authoring, it is a credible buy-versus-build choice; alternatives include building on Laravel's filesystem and intervention/image or using a headless media service. Evaluate based on whether you need editor adapters or a first-class API.
Weaver
How can I help you explore Laravel packages today?