studio-42/elfinder

📁 Open-source file manager for web, written in JavaScript using jQuery and jQuery UI

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 52 minutes ago
Added to GitGenius on September 14th, 2026
Created on November 19th, 2010
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 1,431
Total Stargazers: 4,804 (+0)
Total Subscribers: 229 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.5 days
Mean response time: 58.1 days
90th percentile: 74.9 days
Tracked items: 39

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 0 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • stale (35)
  • question (5)
  • documentation (2)
  • howto (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

elFinder is a web-based file manager written in JavaScript using jQuery and jQuery UI that provides a graphical interface for managing files through a web browser.

The tool solves the problem of enabling file management operations in web applications without requiring users to access server file systems directly. It presents a desktop-like interface inspired by Mac OS X Finder, allowing users to browse, upload, download, and manipulate files through an intuitive visual interface. The project uses AJAX for responsive interactions and HTML5 capabilities to deliver a modern file management experience within the browser.

elFinder suits projects that need to embed file management functionality into web applications, such as content management systems, document repositories, or administrative interfaces. The tool is designed for integration into larger applications rather than standalone use. It provides connectors for multiple backend languages and supports third-party volume drivers and themes, making it adaptable to different deployment environments and visual requirements. The README emphasizes that users running older versions on public servers should update immediately due to serious security vulnerabilities in earlier releases.

The project maintains multiple active branches supporting different development tracks and release cycles. Development occurs on the master branch with a separate 2.1 development branch that auto-builds to a nightly release branch, indicating an organized approach to managing concurrent versions. The tool has accumulated a substantial ecosystem of third-party connectors, volume drivers, and themes contributed by the community, suggesting ongoing adoption and extension by external developers.