Vuefinder is an MIT-licensed file manager component for Vue 3 that provides a native-explorer-style interface for organising, previewing and managing files, aimed at teams that want to embed file browsing, uploads and search inside their own application while keeping storage, authentication and business rules on their own server.

What it is

Vuefinder is a front-end file manager component distributed on npm as vuefinder and built for Vue 3, with Tailwind CSS and Vite appearing among its topic tags. It presents files through a reactive explorer interface in the manner of a native file explorer, and it is designed to be embedded in an existing application rather than run as a separate product. The project is released under the MIT licence, with copyright held by Yusuf Özdemir and dating to 2018, and it maintains a live demo and a documentation site at vuefinder.ozdemir.be.

The problem it addresses is the file-management layer of a Vue application: rather than building browsing, previewing, uploading and searching from scratch, a team installs the component and points it at the storage it already uses, whether local disk, S3 or another object store. Vuefinder itself stays backend-agnostic. It talks to a server through a driver the developer provides, and that driver simply calls their HTTP endpoints and returns data in the expected shape, leaving authentication, storage and business rules under the application's control.

Key capabilities

• A driver-based design in which the developer supplies the driver that calls their own HTTP endpoints and returns data in the expected shape, keeping the component independent of any backend language.
• A published OpenAPI 3.0 specification of the data contracts, so the endpoints can be implemented and validated in whatever stack a team already runs.
• Plug-and-play PHP endpoints through the companion vuefinder-php package, which the README recommends for that purpose.
• Connections to local storage, S3 and similar backends, with a Cloudflare R2 on Workers example (r2-explorer-demo) covering serverless endpoints backed by object storage.
• Uploads handled through Uppy, with full control over upload behaviour and over customisation of the interface.
• Preview tooling that includes a text and code viewer built on CodeMirror 6, in-browser CSV parsing with Papa Parse, image cropping through vue-advanced-cropper, and thumbnails lazy-loaded with vanilla-lazyload.
• Supporting interface plumbing such as selection with viselect, internationalisation through @nanostores/i18n, toast notifications from vue-sonner, and server-state fetching and caching with @tanstack/vue-query and nanostores.

Who uses it and how

• Vue 3 teams that need an embedded explorer, media library or web management tool inside an existing admin interface rather than a standalone file server.
• PHP shops that want working endpoints quickly by pairing the component with the vuefinder-php server library.
• Serverless deployments that keep objects in Cloudflare R2 and serve the file manager from Workers, following the r2-explorer-demo example.
• Polyglot teams that maintain their own server side, using the older Python WSGI, Go (vuefinder-go) and Rust (vuefinder-rust) libraries built for VueFinder 3.x and earlier.
• Contributors who fork the repository and submit pull requests, with the guidance that changes should suit general use rather than a single project.

Getting started

Install the component with npm i vuefinder, then follow the installation, configuration and usage instructions on the documentation site at vuefinder.ozdemir.be. A live demo on the same domain shows the features in action before a driver and endpoints are wired up.

How it compares

The facts provide no list of paid products that Vuefinder replaces and name no directly comparable file-manager component, so it stands alone in this registry. Its nearest relations in the material are the companion server libraries — vuefinder-php, vuefinder-wsgi, vuefinder-go and vuefinder-rust — which supply HTTP endpoints for the front end rather than compete with it.

When to use it — and when not to

Adopting Vuefinder means operating the server side as well: someone must provide endpoints that match the expected data shape, host the storage whether local, S3 or R2, and implement authentication and business rules, although the PHP package covers the endpoint work. Teams that want a hosted product, or that are not building on Vue 3, should look elsewhere, because this is a component rather than a standalone application. The README is also thin on detail, deferring installation and configuration to the external documentation site, and the Python, Go and Rust integrations are explicitly labelled as older libraries for VueFinder 3.x and earlier.

npm i vuefinder