- What is 3x1io/filament-browser and what does it do?
- Filament Browser is a Filament panel plugin that adds a file, folder, and media browser to your admin UI, along with a code editor. From the panel you can browse directories, upload and preview files, and manage media without building custom controllers. It sits on top of Laravel's Filesystem abstraction, so it inherits your app's configured disks rather than introducing its own storage layer. It is a presentation-layer plugin, so it fits any Filament v3 panel and can be embedded in a resource or page.
- How do I install filament-browser in a Laravel application?
- Install it with Composer using composer require 3x1io/filament-browser, then register the plugin in your Filament panel provider. No database migrations are implied by the release notes, so the install is additive and does not touch your schema. After registering, confirm which disk the browser points at and test upload, preview, and delete in a non-production panel first. Check the repository README for the exact plugin registration snippet for your Filament version.
- Which Laravel and Filament versions does Filament Browser support?
- Filament Browser is built as a Filament v3 panel plugin, so a Filament v3 admin is the baseline requirement. The exact Laravel and Filament version ranges are defined in the package's composer.json constraints, which you should read before installing rather than assuming broad compatibility. Because v1.0.2 refactored to extend Laravel's base controller, teams on older Laravel releases should verify the Illuminate\Routing\Controller dependency resolves cleanly. If you are not already running Filament, the package is effectively a non-starter without adopting that stack.
- Does Filament Browser work with S3 and other cloud disks?
- Yes. The package uses Laravel's Filesystem abstraction, so it works with local disks and cloud disks such as S3, provided the disk is configured in your config/filesystems.php. That also means credentials, visibility, and URL generation follow your existing disk configuration rather than package-specific settings. Test previews and uploads on the target disk, since temporary URL behavior and thumbnail support can differ between drivers.
- How is authorization enforced in Filament Browser?
- Access is gated primarily by the Filament panel itself, so only users who can reach the panel can reach the browser. The package does not document a per-directory policy layer, and the technical review flags authorization boundaries as something you must validate yourself. If different roles should see different directories or disks, confirm whether that is achievable through panel access, disk scoping, or custom plugin configuration before relying on it. Treat the browser as a privileged surface and test with a low-privilege account.
- Is Filament Browser safe against path traversal and disk-scope escape?
- A file browser reads and may write or delete arbitrary paths on a configured disk, so path traversal and escape from the configured root are the primary risks to review. The documentation does not publish a formal security model, so you should verify traversal handling explicitly in a sandboxed disk before production. v1.0.2 added hidden file visibility and an event-saved hook, both of which expand the behaviors a reviewer must validate. Run it against a scoped disk with least-privilege credentials and keep it behind authenticated Filament access.
- Can I control whether hidden files and folders are visible?
- Version 1.0.2 added hidden file and folder visibility, which lets you decide whether dotfiles appear in the browser. Confirm whether that setting is a global config value or something you can permission per panel or per user, since the two behave very differently for security. If hidden files can contain secrets such as .env or credential files, default to hiding them and only enable visibility for trusted operators. Verify the behavior matches your policy after every upgrade.
- Does Filament Browser require migrations or change my database?
- No migrations are implied by the package, so it does not contend with your existing schema. Storage state lives on the configured disk, not in new tables, which keeps adoption additive. That also means file metadata and permissions are governed by your disk and filesystem rather than database records. If you need tracked media records or audit history, plan for that separately.
- What is the code editor in Filament Browser used for?
- The package includes a code editor alongside the file browser, so operators can open and edit text-based files directly from the Filament panel. That is convenient for back-office tooling and CMS-style apps, but it raises the stakes on authorization, since editing files on a disk can alter application behavior. Restrict editor access to trusted operators and keep it off any disk that serves executable application code. Confirm whether edits are versioned or backed up before enabling it in production.
- What are the alternatives to Filament Browser and is it actively maintained?
- Alternatives include Filament's own media and file upload components, custom controllers over Laravel storage, and third-party file managers, so compare feature parity for upload, rename, delete, and thumbnails before switching. Filament Browser is a single-maintainer project, and v1.0.2 included two first-time contributors, so bus factor and release cadence are legitimate concerns. Pin the current version, read the v1.0.1 to v1.0.2 diff, and treat the base-controller refactor as a potential minor break if you subclassed package controllers. Roll out behind a feature flag and reassess maintenance activity at each upgrade.