Hubbry Logo
File managerFile managerMain
Open search
File manager
Community hub
File manager
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
File manager
File manager
File manager
View on Wikipedia
from Wikipedia

A file manager or file browser is a computer program that provides a user interface to manage files and folders.[1] The most common operations performed on files or groups of files include creating, opening (e.g. viewing, playing, editing or printing), renaming, copying, moving, deleting and searching for files, as well as modifying file attributes, properties and file permissions. Folders and files may be displayed in a hierarchical tree based on their directory structure.

Features

[edit]

File transfer

[edit]

Graphical file managers may support copying and moving of files through "copy and paste" and "cut and paste" respectively, as well as through drag and drop, and a separate menu for selecting the target path.[2]

While transferring files, a file manager may show the source and destination directories, transfer progress in percentage and/or size, progress bar, name of the file currently being transferred, remaining and/or total number of files, numerical transfer rate, and graphical transfer rate. The ability to pause the file transfer allows temporarily granting other software full sequential read access while allowing to resume later without having to restart the file transfer.[3]

Some file managers move multiple files by copying and deleting each selected file from the source individually, while others first copy all selected files, then delete them from the source afterwards, as described in computer file § Moving methods.

Conflicting file names in a target directory may be handled through renaming, overwriting, or skipping. Renaming is typically numerical. Overwriting may be conditional, such as when the source file is newer or differs in size.[4] Files could technically be compared with checksums, but that would require reading through the entire source and target files, which would slow down the process significantly on larger files.

User interface

[edit]

Some file managers contain features analogous to web browsers, including forward and back navigational buttons, an address bar, tabs, and a bookmark side bar.

Networking

[edit]

Some file managers provide network connectivity via protocols, such as FTP, HTTP, NFS, SMB or WebDAV. This is achieved by allowing the user to browse for a file server (connecting and accessing the server's file system like a local file system) or by providing its own full client implementations for file server protocols.

Directory editors

[edit]

A term that predates[citation needed] the usage of file manager is directory editor. An early directory editor, DIRED, was developed circa 1974 at the Stanford Artificial Intelligence Laboratory by Stan Kugell.[5][6]

A directory editor was written for EXEC 8 at the University of Maryland, and was available to other users at that time. The term was used by other developers, including Jay Lepreau, who wrote the dired program in 1980,[7] which ran on BSD. This was in turn inspired by an older program with the same name running on TOPS-20. Dired inspired other programs, including dired, the editor script (for emacs and similar editors), and ded. [8]

File-list file manager

[edit]
The Alto Neptune file manager program

File-list file managers are lesser known and older than orthodox file managers.

One such file manager was neptune. It ran on the Xerox Alto in the 1973-1974 time frame. It had some of the same features that would end up in orthodox file managers.

Another such file manager is flist, which was introduced sometime before 1980 on the Conversational Monitor System.[9][10][11] This is a variant of FULIST, which originated before late 1978, according to comments by its author, Theo Alkema.[12]

The flist program provided a list of files in the user's minidisk,[13] and allowed sorting by any file attribute. The file attributes could be passed to scripts or function-key definitions, making it simple to use flist as part of CMS EXEC, EXEC 2 or XEDIT scripts.

This program ran only on IBM VM/SP CMS, but was the inspiration for other programs, including filelist[14][15][16] (a script run via the Xedit editor), and programs running on other operating systems, including a program also called flist, which ran on OpenVMS,[17] and FULIST (from the name of the corresponding internal IBM program),[18] which runs on Unix.[19]

Orthodox file managers

[edit]
Midnight Commander, an orthodox file manager with a text-based user interface

Orthodox file managers (sometimes abbreviated to "OFM") or command-based file managers are text-menu based file managers that commonly have three windows (two panels and one command line window). Orthodox file managers are one of the longest running families of file managers. The concept dates to the mid-1980s: PathMinder was released in 1984, and Norton Commander in 1986. File managers based on Norton Commander are actively developed, and dozens of implementations exist for MS-DOS, Unix, and Windows. Nikolai Bezroukov publishes his own set of criteria for an OFM standard (version 1.2 dated June 1997).[20]

Features

[edit]

An orthodox file manager typically has three windows. Two of the windows are called panels and are positioned symmetrically at the top of the screen. The third is the command line, which is essentially a minimized command (shell) window that can be expanded to full screen. Only one of the panels is active at a given time. The active panel contains the "file cursor". Panels are resizable and can be hidden. Files in the active panel serve as the source of file operations performed by the manager. For example, files can be copied or moved from the active panel to the location represented in the passive panel. This scheme is most effective for systems in which the keyboard is the primary or sole input device. The active panel shows information about the current working directory and the files that it contains. The passive (inactive) panel shows the content of the same or another directory (the default target for file operations). Users may customize the display of columns that show relevant file information. The active panel and passive panel can be switched (often by pressing the tab key).

The following features describe the class of orthodox file managers.

  • They present the user with a two-panel directory view with a command line below. Either panel may be selected to be active; the other becomes passive. The active panel becomes the working area for delete and rename operations, while the passive panel serves as a target for copy and move operations. Panels may be shrunk, exposing the terminal window hidden behind them. Normally, only the last line of the terminal window (the command line) is visible.
  • They provide close integration with an underlying OS shell via command line, using the associated terminal window that permits viewing the results of executing shell commands entered on the command line (e.g., via Ctrl-O shortcut in Norton Commander).
  • They provide the user with extensive keyboard shortcuts.
  • The file manager frees the user from having to use the mouse.
  • Users can create their own file associations and scripts that are invoked for certain file types and organize these scripts into a hierarchical tree (e.g., as a user script library or user menu).[citation needed]
  • Users can extend the functionality of the manager via a so-called User menu or Start menu and extensions menu.

Other common features include:

  • Information on the "active" and "passive" panels may be used for constructing commands on the command line. Examples include current file, path to left panel, path to right panel, etc.
  • They provide a built-in viewer for (at least) the most basic file types.
  • They have a built-in editor. In many cases, the editor can extract certain elements of the panels into the text being edited.
  • Many support virtual file systems (VFS) such as viewing compressed archives, or working with files via an FTP connection.
  • They often have the word commander in the name, after Norton Commander.
  • Path: shows the source/destination location of the directory in use
  • Information about directory size, disk usage and disk name (usually at the bottom of the panels)
  • Panel with information about file name, extension, date and time of creation, last modification, and permissions (attributes).
  • Info panel with the number of files in directory, and the sum of the sizes of selected files.
  • Tabbed interface (usually in GUI file managers)
  • Function keys: F1–F10 have all the same functions under all orthodox file managers. Examples: F5 always copies file(s) from the active to the inactive panel, while F6 moves the file.

Tabbed panels

[edit]

The introduction of tabbed panels in some file managers (for example Total Commander) made it possible to manipulate more than one active and passive directory at a time.

Portability

[edit]

Orthodox file managers[21] are among the most portable file managers. Examples are available on almost any platform, with both command-line and graphical interfaces. This is unusual among command line managers in that something purporting to be a standard for the interface is published. They are also actively supported by developers. This makes it possible to do the same work on different platforms without much relearning of the interface.

Dual-pane managers

[edit]

Sometimes they are called dual-pane managers, a term that is typically used for programs such as the Windows File Explorer (see below). But they have three panes including a command line pane below (or hidden behind) two symmetric panes. Furthermore, most of these programs allow using just one of the two larger panes with the second hidden. Some also add an item to the Context Menu in Windows to "Open two Explorers, side by side".

Notable ones include:

[edit]
File Manager in Windows 10, displaying the contents of partition X:
Nemo

A navigational file manager is a newer type of file manager. Since the advent of GUIs, it has become the dominant type of file manager for desktop computers.[22][better source needed]

Typically, it has two panes, with the filesystem tree in the left pane and the contents of the current directory in the right pane. For macOS, the Miller columns view in Finder (originating in NeXTStep) is a variation on the navigational file manager theme.[dubious – discuss]

The Miller Column browser from GNUstep is a type of Navigational file manager.

Concepts

[edit]
  • The window displays the location currently being viewed.
  • The location being viewed (the current directory) can be changed by the user by opening directories, pressing a back button, typing a location, or using the additional pane with the navigation tree representing all or part of the filesystem.
  • Icons represent files, programs, and directories.

The interface in a navigational file manager often resembles a web browser, complete with back and forward buttons, and often reload buttons. Most also contain an address bar into which the file or directory path (or URI) can be typed.

Most navigational file managers have two panes, the left pane being a tree view of the filesystem. This means that unlike orthodox file managers, the two panes are asymmetrical in their content and use.

Selecting a directory in the Navigation pane on the left designates it as the current directory, displaying its contents in the Contents pane on the right. However, expanding (+) or collapsing (-) a portion of the tree without selecting a directory will not alter the contents of the right pane. The exception to this behavior applies when collapsing a parent of the current directory, in which case the selection is refocused on the collapsed parent directory, thus altering the list in the Contents pane.

The process of moving from one location to another need not open a new window. Several instances of the file manager can be opened simultaneously and communicate with each other via drag-and-drop and clipboard operations, so it is possible to view several directories simultaneously and perform cut-and paste operations between instances.

File operations are based on drag-and-drop and editor metaphors: users can select and copy files or directories onto the clipboard and then paste them in a different place in the filesystem or even in a different instance of the file manager.

Notable examples of navigational file managers include:

Spatial file manager

[edit]
The Nautilus file manager had a spatial mode, which was removed with the arrival of GNOME (and with it Nautilus) version 3.x. Each of these windows displays an open directory.

Spatial file managers use a spatial metaphor to represent files and directories as if they were actual physical objects. A spatial file manager imitates the way people interact with physical objects.

Some ideas behind the concept of a spatial file manager are:

  1. A single window represents each opened directory
  2. Each window is unambiguously and irrevocably tied to a particular directory.
  3. Stability: files, directories, and windows go where the user moves them, stay where the user puts them ("preserve their spatial state"), and retain all their other "physical" characteristics (such as size, shape, color and location).
  4. The same item can only be viewed in one window at a time.

As in navigational file managers, when a directory is opened, the icon representing the directory changes—perhaps from an image showing a closed drawer to an opened one, perhaps the directory's icon turns into a silhouette filled with a pattern—and a new window is opened to represent that directory.

Examples of file managers that use a spatial metaphor to some extent include:

Dysfunctional spatial file managers:

  • Windows Explorer in Windows 95 was set as a spatial file manager model by default; because it also worked as a navigational file manager, directories could be opened in multiple windows, which made it fail all the above criteria. Later versions gradually abandoned the spatial model.
  • Apple's Finder in macOS was designed with a similar integration of spatial and navigational modes, meaning that the spatial mode did not actually work.[23]

3D file managers

[edit]
File System Visualizer, one example of a 3D file manager
In Cubix, files sharing the same attributes are represented by cubes in a 3D environment.

Some projects have attempted to implement a three-dimensional method of displaying files and directory structures. Three-dimensional file browsing has not become popular; the exact implementation tends to differ between projects, and there are no common standards to follow.

Examples of three-dimensional file managers include:

  • File System Visualizer, or fsv, an open-source clone of fsn for modern Unix-like systems.
  • tdfsb,[24] an open-source 3D file browser, where one enters directories by flying into them (using WASD). Runs on Linux, FreeBSD and BeOS.
  • BumpTop, a file manager using a three-dimensional representation of a desktop with realistic physics, intended for use with a stylus and touchscreen.
  • Real Desktop,[25] a desktop replacement with similarities to BumpTop.
  • Cubix 3D Filer [26] is a Windows file manager which organizes files according to different attributes.
  • GopherVR, a 3D visualisation of networked Gopher resources.

Web-based file managers

[edit]

Web-based file managers are typically scripts written in PHP, Ajax, Perl, ASP or another server-side language. When installed on a local server or on a remote server, they allow files and directories located there to be managed and edited, using a web browser, without the need for FTP Access.

More advanced, and usually commercially distributed, web-based file management scripts allow the administrator of the file manager to configure secure, individual user accounts, each with individual account permissions. Authorized users have access to documents stored on the server or in their individual user directories anytime, from anywhere, via a web browser.

A web-based file manager can serve as an organization's digital repository. For example, documents, digital media, publishing layouts, and presentations can be stored, managed, and shared between customers, suppliers, and remote workers, or just internally.

Web-based file managers are becoming increasingly popular due to the rise in popularity of dynamic web content management systems (CMS) and the need for non-technical website moderators to manage media on their websites powered by these platforms.

An example is net2ftp, a PHP- and JavaScript-based FTP client.

File picker

[edit]
Main article: File dialog

Operating systems typically ship a file picker, which allows specifying in which location to save a file (usually accessed through the "Save as" option in software), and where to open a file from. Sometimes, a folder is selected instead of a file or destination path.

Some file pickers also allow file management to some degree, such as searching, moving, copying, renaming, and copying the path to clipboard.

Some software might have a customized file picker.

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

File manager

View on Grokipedia
from Grokipedia
A file manager is a computer program that provides a user interface to manage files and folders on a computer's storage devices, such as hard drives, SSDs, or flash drives, enabling users to perform operations like viewing, copying, moving, renaming, and deleting them. File managers typically display the hierarchical structure of files and directories, allowing users to navigate and organize data efficiently, and they often integrate with the operating system to launch applications for opening specific file types. They play a crucial role in user interaction with the file system, abstracting low-level operations handled by the operating system itself. These tools come in two primary forms: graphical user interface (GUI) versions, which use visual elements like icons, windows, and drag-and-drop functionality for intuitive operation, and (CLI) or text-based versions, which rely on keyboard commands for faster, scriptable management, particularly useful in server environments or for advanced users. GUI examples include Windows' (formerly Windows Explorer), Apple's Finder on macOS, and on GNOME-based distributions, while CLI examples encompass GNU Midnight Commander, Ranger, and Vifm, which offer features like dual-pane views and vi-like keybindings for efficient navigation. Historically, early file managers like the one in Windows 3.x were basic GUI tools that evolved into more sophisticated systems with the introduction of Windows 95's Explorer, which combined file management with shell functionality; modern iterations continue to add features such as search integration, metadata viewing, and support for networked or .

Introduction

Definition and purpose

A file manager is a software application that provides a for interacting with a computer's , enabling users to view, organize, and manipulate files and directories. It supports essential operations such as copying, moving, renaming, and deleting files and folders, as well as creating new directories to structure data hierarchically. The primary purposes of a file manager include facilitating the organization of digital content, navigating complex directory structures, viewing and editing file metadata (such as timestamps, permissions, and attributes), and accessing operating system tools for maintenance tasks, such as and integrity checks, where applicable. These functions help users maintain efficient access to stored data across operating systems like Windows, macOS, and . Unlike text editors, which focus on modifying the internal content of files, or command shells, which interpret and execute broad system-level commands via text input, file managers emphasize direct manipulation of file structures through intuitive interfaces, either graphical or text-based. Common universal tasks supported by file managers include searching for files by name or content, sorting lists by criteria like date or size, and previewing file contents without full opening.

Historical development

The origins of file managers trace back to the and , when was dominated by mainframe systems and early multitasking operating systems. In these environments, file relied on command-line interfaces (CLI) for basic operations on batch-processed data. The development of Unix at in 1969 marked a pivotal advancement, with the first edition released in 1971 introducing essential commands like ls for listing directory contents and cp for copying files, which became foundational tools for navigating hierarchical file systems on systems such as the PDP-11. These CLI tools emphasized efficiency in resource-constrained environments, handling file transfers and organization through scripted interactions rather than visual representations. The 1980s saw the emergence of graphical user interfaces (GUIs), influenced by pioneering work at Xerox PARC, where the computer in 1973 introduced a display and mouse-driven graphical interface, with the file editor providing early mouse-based file management using text lists, though it remained a research prototype; icons and the were further developed in subsequent systems like Smalltalk on the . This innovation inspired commercial implementations, such as Apple's Finder in 1984, bundled with the Macintosh , which provided a spatial desktop view for dragging and dropping files using icons to represent folders and documents. Microsoft's File Manager, released with in 1990, further popularized graphical file handling on personal computers by offering tree-based navigation and drag-and-drop functionality integrated with the . These developments shifted file management from text-based commands to intuitive visual paradigms, driven by hardware advances like affordable bitmapped displays. In the 1990s, file managers evolved toward specialized styles to address growing user needs for productivity. , released in 1986 for , pioneered the orthodox dual-pane layout, allowing simultaneous viewing and manipulation of two directories, which influenced a wave of similar tools for power users. By 1995, Microsoft's Windows Explorer replaced the earlier File Manager in , adopting a navigational single-pane design with an integrated and web-like browsing, standardizing file management within the OS shell and supporting long filenames. The 2000s brought further diversification, including spatial designs like GNOME's in 2001, which emphasized persistent folder windows reminiscent of early Mac interfaces to enhance spatial awareness. Early web-based file managers also appeared, with tools integrating cloud storage protocols like , as seen in services such as Apple's iDisk launched in 2000, enabling remote file access via browsers. From the onward, file managers adapted to mobile, cloud, and intelligent computing eras. Apple's Files app, introduced in in 2017, provided a unified interface for local and cloud-based files, marking a significant step in mobile file management by supporting third-party cloud providers like . Advancements in AI-assisted search emerged, with features like semantic querying in tools such as Microsoft's updates in the 2020s, using to locate files beyond metadata. Cross-platform portability gained prominence, exemplified by open-source managers like muCommander, which run seamlessly across Windows, macOS, and via since the early but saw widespread adoption in the for unified experiences. Throughout this evolution, key drivers included hardware improvements like touchscreens and SSDs enabling faster interfaces, OS standardization through APIs for , and user demand for intuitiveness, transitioning from expert CLI tools to accessible, context-aware systems.

Core Features

Basic operations

File managers provide essential CRUD (create, read, update, delete) operations for files and directories, enabling users to manage data structures within the . Creation involves generating new files or folders, often through menu commands or right-click options, using underlying system APIs such as those in the for file handling. Reading allows viewing file contents or directory listings, while updating supports modifying file data or attributes via write operations. In graphical file managers, deletion often moves files or directories to a recycle bin or trash for potential recovery, as implemented in functions like those from the Win32 file management APIs. Command-line file managers typically perform permanent deletion. Copying, moving, and renaming files or directories across local or remote locations are fundamental transfer operations supported universally. These actions leverage system calls like SHFileOperation in Windows for batch handling, displaying progress indicators during large transfers to inform users of completion status. Drag-and-drop and cut-paste mechanisms facilitate intuitive transfers, where cut operations prepare files for relocation and paste executes the move or copy based on context. ensures efficient handling of multiple items, with visual feedback like progress bars to track operations. Metadata handling in file managers includes viewing and editing attributes such as permissions, timestamps (creation, modification, access), and file sizes, which provide critical context for file management. Permissions control access rights, editable through property dialogs that invoke system security APIs, while timestamps and sizes are retrieved via file information functions for display in list views. Compression and decompression support common formats like ZIP and , allowing users to files for storage efficiency, often integrated via native tools or extensions. Search and filtering capabilities enable locating files through , such as wildcards or regular expressions, with recursive scans traversing subdirectories for comprehensive results. Advanced queries can filter by metadata like date or size, using syntax like Advanced Query Syntax (AQS) in Windows for precise searches. Duplicate detection identifies identical files by comparing hashes or contents, aiding in storage optimization without exhaustive listing. Error handling ensures robust operations, with prompting users for actions like overwriting during copies or moves, often via dialogs offering skip, replace, or rename options. Undo and redo stacks allow reversal of actions like deletions or renames, typically limited to recent operations and accessible via keyboard shortcuts such as Ctrl+Z, maintaining user control over changes. These mechanisms, presented through elements like toolbars, prevent in interactive environments.

User interface elements

File managers commonly incorporate a featuring icons for essential operations, such as creating new folders, copying, pasting, and deleting files, providing users with quick visual access to core functions. , displayed as an showing the hierarchical path to the current directory, enables users to jump to any ancestor folder by clicking on path segments, a design that enhances orientation in deep folder structures and was notably introduced in Windows Vista's . Context menus, invoked by right-clicking on files or folders, offer context-sensitive options like renaming, properties, or sharing, streamlining interactions without cluttering the main interface. Preview panes, positioned to the side of the file list, allow real-time viewing of selected file contents—such as images or document thumbnails—without launching external applications, a feature standard in tools like macOS Finder since its early versions. Interaction models in file managers balance selection and activation, with the predominant convention using single-click for selecting items and for opening or executing them, a paradigm established in early graphical user interfaces like the in 1983 to distinguish actions on limited input devices. Some implementations, such as Dolphin's configurable mode, support single-click activation to mimic web browsing behavior, reducing motor demands for users. Keyboard shortcuts facilitate rapid control, including arrow keys for navigation, Ctrl+A for selecting all items, and F2 for renaming, ensuring efficiency for power users across platforms like Windows and Nautilus. Customizable views—such as list (compact rows), grid (icon-based), and details (with metadata columns like size and date)—let users adapt the display to their needs, with options to sort, filter, or resize columns for better organization. Accessibility features ensure inclusive use, with screen reader support in Windows File Explorer allowing Narrator to announce folder contents and item details via keyboard exploration, such as Tab to move between panes and Enter to activate. High-contrast modes enhance visibility for low-vision users by amplifying color differences in icons and text, while keyboard-only navigation—using Tab, arrows, and modifiers—bypasses mouse dependency, features integrated into macOS Finder and per platform guidelines. These elements comply with standards like WCAG for perceivable and operable interfaces. Customization extends functionality through themes that alter color schemes, fonts, and layouts for personal aesthetics, as in Plasma's style system applied to . Plugins and extensions add capabilities like advanced thumbnails for media files or metadata tagging, with supporting service menus for custom right-click actions and enabling shell extensions to modify views. User interface paradigms in file managers have evolved from text-based command prompts requiring typed instructions to graphical elements with mouse-driven interactions, and further to gestures like swipes for or long-press for menus in mobile adaptations.

Networking and integration

Modern file managers support a range of network protocols to enable remote file access and management, including FTP for basic file transfers, SFTP for secure shell-based access, SMB for Windows network sharing, and for HTTP-based collaborative editing. These protocols allow users to browse, , and files over local area networks or the as if they were local resources. Additionally, many file managers facilitate mounting network drives, integrating remote storage into the local hierarchy for seamless navigation and operations. Cloud integration has become a core feature in contemporary file managers, enabling synchronization with services such as and to maintain file consistency across devices. This typically involves authentication, where users grant permissions via secure token exchange without sharing credentials directly, supporting automated backups and real-time updates. For instance, integration with allows file managers to handle uploads, downloads, and metadata operations while adhering to the service's access scopes. File managers integrate deeply with operating systems through hooks into desktop environments, such as or , using protocols like slaves for transparent remote access within the file browser. Shell extensions extend this functionality, allowing custom actions like drag-and-drop to network locations or context menu options for automation scripts. calls further enable programmatic control, permitting scripts or third-party applications to interact with the file manager for tasks like batch transfers or event-driven syncing. Security in networking features emphasizes in transit using protocols like TLS 1.2 or higher for all remote operations, protecting data from during transfer. File managers often interact with system firewalls to prompt for port allowances during connection setup and enforce user authentication, such as multi-factor prompts before accessing shared resources. These measures ensure compliance with standards like AES-256 for sensitive file handling over networks. Post-2010s advancements have enhanced multi-device support in file managers, enabling cross-platform file sharing via unified protocols that work across Windows, macOS, , and mobile ecosystems. Real-time synchronization features, such as instant syncing, leverage backends to allow multiple users to access and update shared files across devices, minimizing version conflicts. This is exemplified by mounting mechanisms that abstract underlying differences, providing a consistent interface for distributed workflows.

Types of File Managers

Command-line file managers

Command-line file managers are text-based applications that enable users to browse, organize, and perform operations on files and directories within a terminal or console environment, typically using keyboard-driven commands and libraries such as for a structured, full-screen display. These tools provide an alternative to graphical interfaces, emphasizing efficiency in resource-constrained settings like servers or remote sessions. Unlike basic shell commands, they often feature dual-pane layouts or columnar views to facilitate navigation and manipulation without leaving . Key characteristics include high scriptability, allowing integration with shell scripts for automated tasks, and lightweight operation that minimizes system overhead. Common commands mirror shell utilities, such as ls equivalents for listing files, cd-like navigation between directories, and operations like cp for copying, mv for moving, and rm for deletion, but presented in an interactive interface. Examples in systems include GNU Midnight Commander (MC), a full-screen orthodox manager supporting virtual filesystems and batch operations; Ranger, a Python-based tool with Vim-inspired keybindings, multi-column previews, and rifle for launching files; and Vifm, which extends Vim-like controls to management with features like tabs and bookmarks. Another specialized tool, (NCurses Disk Usage), focuses on interactive disk usage analysis, scanning directories to display size-ordered hierarchies for quick identification of space-consuming files. Their advantages lie in low resource consumption, making them ideal for headless servers, embedded systems, and environments with limited bandwidth, such as remote access via SSH. Automation via enables complex workflows, like bulk renaming or syncing, without graphical dependencies. Historically, these managers played a crucial role in the pre-GUI era of Unix and , where file management relied solely on command-line interfaces for all operations. Limitations include a steep for users accustomed to mouse-driven GUIs, as all interactions require memorizing keybindings, and the absence of visual previews for or binary files, relying instead on text metadata. In modern contexts, they remain popular for secure , lightweight distributions, and power users preferring terminal efficiency over graphical overhead.

Directory editors

Directory editors represent a class of file managers that treat directory listings as editable text buffers, enabling users to manipulate file names, permissions, and other attributes directly through text editing operations rather than menu-driven selections or visual navigation. This approach originated in early environments where text-based interfaces dominated, allowing for precise, scriptable control over file systems. By rendering a directory's contents in a format akin to a file, these tools facilitate inline modifications that translate into system-level file operations, such as renaming or deletion, upon saving the buffer. The concept traces its roots to the , with one of the earliest implementations being Dired, developed in 1974 by Stanley Kugel as a student at on the WAITS operating system for the mainframe. Initially a standalone program, Dired functioned as a "Directory Editor," displaying file listings in an editable format where changes to text lines directly affected the underlying . This tool predated the widespread adoption of graphical interfaces and was designed for mainframe environments, where efficient text manipulation was essential for managing large, shared file systems without visual metaphors like icons or folders. By the early , Dired was integrated into the editor as a major mode, evolving alongside Unix systems and influencing subsequent text-based file management tools. Another early example is DED (Directory Editor), a curses-based implementation begun in 1984 by Thomas E. Dickey, which enhanced the original Dired for Unix terminals and emphasized portability across systems. These early tools emerged in an era when mainframe file systems, such as those on and DEC hardware, relied on line-oriented interfaces for and administrative tasks. Key features of directory editors include inline renaming, where users can position the cursor on a file name within the buffer and edit it directly, with the change applied upon confirmation. Multi-line views support bulk edits, such as selecting multiple entries with marks (e.g., using 'm' in Dired to flag files) for collective operations like copying or deleting, streamlining without repetitive commands. Modern implementations, such as the current Dired mode, incorporate for file paths, permissions, and sizes, enhancing readability and reducing errors during edits; for instance, file types may be color-coded, and hidden files can be toggled for visibility. Additional capabilities include recursive subdirectory viewing, where subfolders are expanded inline for hierarchical editing, and integration with shell commands for advanced manipulations like permission changes via regex-based substitutions across the buffer. In practice, directory editors excel in use cases requiring precise, automated file handling, such as system administration tasks where administrators edit directory buffers to rename dozens of log files in bulk or adjust timestamps en masse. They are particularly valuable for batch renaming operations, allowing pattern-based substitutions (e.g., replacing prefixes across marked lines) that are more efficient than point-and-click methods. Integration with version control systems is a common strength; for example, Emacs Dired seamlessly interfaces with modes like VC () to commit changes, diff files, or revert revisions directly from the editable listing, making it ideal for developers managing project directories. These tools remain relevant in server environments and among power users who prefer keyboard-driven workflows over graphical alternatives. Unlike standard file managers that prioritize browsing and selection through hierarchical trees or lists, directory editors shift the focus to textual manipulation, where the directory itself becomes a modifiable rather than a static view. This enables scripting and —users can pipe directory listings through external editors or apply macros for repetitive edits—offering greater flexibility for technical users at the expense of intuitiveness for novices. While basic operations like renaming overlap with other file manager types, the editable buffer model distinguishes directory editors by embedding file actions within a familiar text-editing context.

File-list file managers

File-list file managers feature a single-pane interface that presents files in a straightforward list format, often organized into columns displaying key attributes such as file name, , and modification date. This design emphasizes scrolling through the list and selecting individual or multiple items via highlighting or /keyboard input for performing actions like viewing, copying, deleting, or renaming. Simple filters may allow sorting by attributes, but navigation remains confined to the current directory without integrated structures or multi-view options. Early examples include , the directory editor for the computer developed around 1973-1974 at Xerox PARC, which displayed files in a text-based list on a bitmapped screen, using mouse buttons for selection and basic operations like deletion or copying within a single view. In the DOS environment, , released in April 1985 by Executive Systems, offered a text-mode list view for rapid file scanning and selection, supporting operations through keyboard shortcuts while focusing on efficiency for disk management. Basic versions of such list-based tools also appear in embedded operating systems, where limited resources necessitate minimalistic interfaces for file browsing and manipulation on devices like microcontrollers or early mobile systems. These managers excel in simplicity and performance for handling small to medium-sized directories, enabling quick access without the overhead of complex visualizations, though they fall short in depicting file hierarchies, often requiring manual directory changes for broader exploration. As foundational tools, file-list managers influenced the development of later graphical interfaces by prioritizing selectable lists and attribute-based organization over advanced spatial or dual-view paradigms.

Orthodox file managers

Orthodox file managers, also known as commander-style file managers, trace their origins to the mid-1980s with the development of , a pioneering DOS-based application created by John Socha and released in 1986 by Computing. This software established the foundational paradigm for the category, emphasizing efficiency for power users through a structured, text-based interface that prioritized keyboard navigation over mouse interaction. Although initially designed for environments, its influence extended across computing ecosystems, inspiring a lineage of tools that maintain its core principles while adapting to modern platforms. The core design of orthodox file managers revolves around two symmetric panels that simultaneously display directory contents, allowing users to designate one as the source and the other as the destination for operations. File manipulation—such as , moving, renaming, or deleting—is executed via dedicated function keys (typically F3 for viewing, F4 for , F5 for , and F6 for moving), which streamline workflows without disrupting the visual layout. This rigid, pane-based structure promotes rapid transfers and comparisons, making it ideal for advanced users who value precision and speed over graphical metaphors. Prominent examples include , first released on September 25, 1993, by Swiss developer Christian Ghisler under the name Windows Commander, which evolved into a robust Windows tool while preserving the orthodox layout. Another key implementation is , a free, open-source, cross-platform alternative launched in the mid-2000s and explicitly inspired by Total Commander, supporting Windows, , and macOS through its lightweight architecture. These managers are generally portable, requiring minimal system resources and no extensive dependencies, enabling them to run efficiently on diverse operating systems from legacy DOS to contemporary desktops. Common extensions in orthodox file managers enhance usability without deviating from the core model, such as built-in viewers activated by function keys to preview files like text, images, or binaries directly within the interface. Archive handling is another staple feature, where compressed files (e.g., ZIP, RAR) are treated as virtual folders, allowing seamless navigation, extraction, and integration into panel operations as if they were standard directories. Networking capabilities, such as FTP or SFTP access, can also be incorporated via the panels for remote file management. Navigational file managers utilize a hierarchical to represent the , enabling users to browse directories through a single primary pane supplemented by a path bar that displays the current location in the . This approach simulates "drilling down" into subdirectories by selecting them, akin to traversing nested physical folders or compartments in a . The design typically features a sidebar outlining the full directory structure alongside a main content area showing files and subfolders of the , facilitating intuitive progression through the layers. Key examples of navigational file managers include Windows Explorer, first introduced in 1995 as part of , which pioneered the dual-pane layout with a left-side navigation tree for quick access to drives and folders. Similarly, the macOS Finder incorporates navigational elements through its path bar, a customizable at the window's base that outlines the sequence of folders from root to current location, supporting variants like or column views for hierarchy traversal. These tools gained prominence in the as graphical user interfaces became standard in operating systems. Core features of navigational file managers include back and forward buttons that maintain a history of traversed directories, much like web browsers, allowing users to retrace steps without re-navigating the tree. Additional functionalities encompass favorites or bookmarks for pinning frequently accessed folders in the sidebar, and integrated search tools that query across the hierarchy from the current context. These elements enhance efficiency in linear exploration while preserving a streamlined interface. The underlying user model draws on a metaphor of physical navigation through interconnected spaces, where directories function as rooms within a building, and users move sequentially deeper or upward via the tree or path indicators. This model promotes a sense of progressive discovery, aligning with how individuals mentally map file locations based on containment relationships. For casual users, the browser-like familiarity renders it highly intuitive, reducing the learning curve for basic browsing and file location tasks. However, it imposes limitations in multi-tasking scenarios, such as comparing contents across non-adjacent directories, often necessitating multiple open windows rather than simultaneous side-by-side views.

Spatial file managers

Spatial file managers utilize a in which folders appear as resizable, positionable windows on the desktop, simulating a physical workspace, while files are represented as draggable icons that can be moved between these windows to perform operations like copying or relocating. This spatial emphasizes visual organization over hierarchical navigation, allowing users to arrange elements intuitively based on their remembered positions. Pioneered by the operating system's in , this approach displayed directory contents in dedicated windows that could show icons or text lists, with support for opening multiple viewers simultaneously and drag-and-drop interactions to manipulate files across them. The reserved screen margins for quick-access icons and enabled seamless file transfers by dragging, fostering a desktop-like environment where windows could be resized and positioned freely. GNOME Nautilus exemplified spatial file management in its mode introduced around 2001, where each folder opened in a distinct that retained custom arrangements, sorting preferences, and even per-folder background images for visual distinction. Additional features included zooming with level-of-detail adjustments to scale views and persistent positioning to aid spatial recall, enhancing the of files as tangible objects on a . This design offers benefits such as improved visual memory for file locations, simplifying retrieval through spatial cues rather than path memorization, and efficient drag-based operations for multi-folder tasks. However, it suffers from drawbacks like screen clutter caused by proliferating windows, challenges in handling deep or large directory structures, and performance degradation when managing extensive file sets due to the overhead of maintaining multiple views. Today, spatial file managers are less prevalent owing to these scalability limitations and the shift toward streamlined, single-window browser interfaces, though their influence persists in icon-driven layouts and drag-and-drop conventions across modern systems. , for example, discontinued spatial mode in 2012 to address codebase complexity and maintenance burdens.

3D file managers

3D file managers represent an experimental approach to file organization and navigation by extending traditional two-dimensional interfaces into three-dimensional virtual spaces, allowing users to interact with files and directories as spatial objects. These systems typically visualize hierarchical structures using metaphors such as tunnels, spheres, or planetary systems, where directories might appear as branching paths or orbiting clusters, enabling intuitive depth-based exploration beyond flat lists or trees. This paradigm draws on principles of to enhance overview and in large file systems, though it remains largely confined to research and niche applications due to technical constraints. One seminal example is LgScope, a component of ' Project Looking Glass, an open-source 3D initiated in 2003 and released up to version 1.0 in 2006. LgScope renders files and directories as rotatable three-dimensional blocks, with metadata such as file details displayed on adjacent faces, facilitating through perspective shifts and zooming interactions. Building on this foundation, the FOLDER3D prototype, developed by researchers including Saturnino Luz, Masood Masoodian, Bill Rogers, and Simon De Schutter, extends Looking Glass's infrastructure to visualize file relationships in 3D spaces, representing folders as interconnected volumes that complement conventional 2D hierarchies. Published in 2010, FOLDER3D emphasizes non-hierarchical links, such as shared files, depicted as overlapping or linked geometric forms. Other notable prototypes include , an -based tool created by Daniel Richard G. in the early as a clone of ' fsn file manager, which arranges directories on pedestals in a cyberspace-like for hierarchical via mouse-driven and an overhead "" view. Similarly, XCruiser, a Linux-oriented browser from the mid-, models directories as empty galactic circles and files as filled planetary spheres, supporting fly-through to reveal subdirectory clusters. TDFSB, originally developed in the early and revived as 3DFSB in 2015, offers an immersive first-person perspective akin to a , where users walk through file structures with keyboard controls for movement and interaction. Additionally, 3Dfm, a C++ and implementation from 2002, employs Quake-style controls for traversing directories represented as icon-linked nodes in 3D space. Core features of these systems include gesture-based or mouse/keyboard interactions for rotating views, zooming into substructures, and manipulating objects, often with metadata encoded visually—such as determining object scale or type influencing color and shape—to aid quick assessment without textual scanning. For instance, in FSV and XCruiser, users can select and open files by pointing in 3D, while FOLDER3D incorporates link visualizations to highlight relationships like duplicates or references across folders. These elements aim to leverage human spatial reasoning for tasks like locating buried files or identifying large datasets through volumetric layouts. In applications, 3D file managers have primarily supported in immersive , with integrations into environments emerging post-2010s to enable headset-based navigation in professional workflows like or . However, challenges persist, including high demands on hardware for real-time rendering, which limited early adoption to high-end systems like those running or early desktops. Usability issues, such as disorientation in complex 3D spaces and a steep for non-expert users, have confined these tools to experimental use rather than mainstream file management. Despite ongoing open-source efforts, their niche status reflects broader difficulties in balancing visual expressiveness with practical efficiency.

Web-based file managers

Web-based file managers are browser-accessible applications that enable users to manage files stored on remote servers or without requiring dedicated software installation. These tools provide a graphical interface for operations such as uploading, downloading, organizing, and sharing files, often mimicking the functionality of desktop file explorers but operating entirely through web technologies. They are particularly suited for remote file handling in distributed teams and cloud environments. The architecture of web-based file managers typically involves a client-side interface built with HTML, CSS, and JavaScript frameworks, paired with server-side processing for file operations. For instance, elFinder, an open-source solution first released in 2010, uses JavaScript with jQuery UI for its frontend and relies on server connectors (such as PHP) to handle backend tasks like file I/O via a JSON-based API. Similarly, ownCloud's file manager component features a web interface developed in Vue.js since 2020, running as a PHP application on Apache servers to manage file metadata and storage. This separation allows for dynamic updates and responsiveness in the browser while delegating secure file handling to the server. Key features include drag-and-drop uploads for intuitive , real-time to reflect changes across devices, and for collaborative . elFinder supports drag-and-drop for moving and copying files, along with multi-file uploads and preview capabilities for media. ownCloud extends this with real-time collaborative through integrations like or , allowing multiple users to edit documents simultaneously in the browser, and provides shareable with permissions for external . These capabilities enhance by enabling seamless file interaction without leaving the web environment. Web-based file managers primarily operate over HTTP and HTTPS protocols for secure data transmission, with many integrating with cloud APIs such as those from or AWS S3 for extended storage options. elFinder includes connectors for AWS S3, , and other services via libraries like Flysystem, allowing users to browse and manage cloud-stored files directly in the interface. ownCloud supports external storage backends including S3 and through its configuration, enabling federated access where files from multiple providers appear unified in the web view. This integration facilitates hybrid setups combining local and cloud resources. Advantages of web-based file managers include inherent cross-platform compatibility via any modern browser, eliminating the need for installations and reducing maintenance overhead. Security is bolstered by encryption for all communications and (RBAC) to enforce permissions, such as read-only or edit rights per user group. In Enterprise, RBAC integrates with LDAP or SAML for granular control, ensuring compliance in organizational settings. These traits make them ideal for secure, accessible file management without platform-specific dependencies. The adoption of web-based file managers has surged in the , driven by the rise of and the shift to cloud-native infrastructures, with the global file manager software market growing from approximately USD 2.47 billion in amid increased demand for collaborative tools. This growth is supported by containerized deployments using Docker, which simplify scaling and portability; for example, solutions like FileBrowser and Filestash offer official Docker images for quick setup in cloud or on-premises environments, aligning with the broader trend where over 90% of organizations now use or evaluate such platforms.

Specialized Variants

Mobile file managers

Mobile file managers are specialized applications designed for smartphones and tablets, prioritizing touch-based interactions over traditional or keyboard inputs to facilitate file organization, browsing, and manipulation on resource-constrained devices. These tools emerged prominently in the late , adapting desktop paradigms to mobile contexts by incorporating swipe gestures for actions like deletion or sharing, long-press selections for multi-file operations, and thumb-friendly interfaces that minimize deep nesting in folder hierarchies. Representative examples include Google's Files app, released in 2017 as a lightweight solution for Android devices running version 5.0 and above, which emphasizes quick scans for duplicates and junk files to reclaim storage. Similarly, Apple's Files app, introduced with in 2017, integrates seamlessly with the ecosystem to provide a unified view of local and remote content. Core features of mobile file managers revolve around gesture-driven navigation, such as tapping to expand folders or swiping to preview thumbnails, enabling intuitive access without dedicated hardware. Hybrid views combine local device storage with cloud services—for instance, Files by Google supports integration with and Quick Share for seamless offline transfers, while the iOS Files app aggregates Drive, third-party providers like and , and external drives via or connections. Permission handling is critical, as these apps must navigate platform-specific restrictions; on Android, users grant granular access through the Storage Access Framework, allowing file pickers to request visibility into app-specific directories without full system exposure. The built-in file picker on Android, implemented as DocumentsUI via the SAF, focuses on picker dialogs and basic browsing for secure file access across providers, ensuring privacy without direct filesystem access. Files by Google is a separate, optional full-featured file manager with tools like cleaning and offline sharing; it can act as a document provider in the SAF picker but is not required for the picker's function. On devices like Pixels, Files by Google may appear prominently but can be disabled, leaving DocumentsUI operational. OEMs like Samsung may skin DocumentsUI with their own manager, but the underlying SAF picker remains built-in and independent. On iOS, apps leverage the system's document picker for secure, user-initiated access to files outside their sandbox. Battery optimization is embedded in design, with features like on-demand scanning rather than continuous background indexing to conserve power, aligning with Android's Doze mode and iOS's low-power modes that throttle resource-intensive operations. Significant challenges in mobile file management stem from platform security models, particularly sandboxing, which confines apps to their own data containers to prevent unauthorized access. In , third-party file managers are restricted to reading and writing within designated directories, relying on user-mediated sharing via the Files app or URL schemes, which limits comprehensive system-wide operations and complicates bulk management across apps. Android's scoped storage, enforced since API level 30 in , further restricts access to protect user , requiring file managers to use media store APIs or declarations for legacy compatibility, often resulting in fragmented visibility and developer workarounds like virtual file systems. These constraints enhance security by mitigating risks from malicious apps but demand careful UI design to guide users through permission flows without overwhelming them. Integration with app ecosystems adds complexity, as files generated by one application may remain siloed, necessitating explicit exports or shares to enable broader utility. Battery demands arise from intensive tasks like file scanning or cloud syncing, prompting optimizations such as deferred processing during charging or idle states to extend device runtime. Emerging trends in the 2020s focus on enhancing usability through for automated organization, such as smart sorting in Files by Google, which uses on-device AI to categorize media by content type or recency without uploading data. Augmented reality previews are gaining traction, particularly on via AR Quick Look, which allows users to visualize 3D files like USDZ models in their physical environment directly from the Files app, bridging file browsing with immersive interaction on compatible ARKit devices. Cross-device continuity is another key development, enabling seamless file handoffs; Apple's Handoff syncs Files app states across , , and Mac, while Android's Quick Share (formerly ) facilitates wireless transfers between devices and Windows PCs. Web hybrids for lighter devices, such as progressive web apps mimicking file manager functionality, are also rising on both platforms to bypass native installation limits and support low-end hardware. These advancements, driven by AI integration, prioritize efficiency and interoperability while adhering to privacy standards.

File pickers

File pickers serve as lightweight, temporary interfaces embedded within applications to enable users to select files for opening, saving, or importing without providing full file management capabilities. These dialogs, often modal to focus user attention, originated as standardized components in graphical user interfaces during the early 1990s, evolving from earlier graphical file interfaces in 1980s systems like the and Apple Macintosh. In design, file pickers typically present filtered views of directory contents, including list or thumbnail previews, alongside navigation elements such as a path bar, sidebar for frequent locations, and dropdowns for recent files. Operating system-native implementations, such as the Windows Common Dialog or macOS's NSOpenPanel, ensure consistency across applications by rendering in a sheet or standalone window attached to the parent app. These interfaces prioritize simplicity, displaying only relevant files based on predefined filters to streamline selection. Key features include path auto-completion for quick , multi-selection to choose multiple files simultaneously, and format restrictions via file type filters that limit visible items to supported extensions. Additional enhancements, like quick previews of selected files and bookmarks for common directories, improve without overwhelming the interface. For instance, in GTK-based systems, the GtkFileChooserDialog supports these alongside action-specific modes for opening or saving. Integration occurs through API-driven calls, allowing applications to customize aspects like initial directory, allowed actions (e.g., choosing files or directories), and prompt text while leveraging the OS's rendering for and . Developers initialize these via structures like OPENFILENAME in Win32 or methods in NSOpenPanel, enabling seamless embedding since their introduction in systems like and Mac OS X. This approach has persisted, with updates in modern versions adding support for and enhanced previews. Limitations of file pickers include their constrained scope, restricting users to selection only without options for renaming, deleting, or organizing files, and their session-bound nature, where changes do not persist beyond the dialog's dismissal. As modal overlays, they can interrupt if not dismissed, and customization is bounded by OS guidelines to maintain , such as sandboxing access to user-selected paths.

References

  1. https://www.pcmag.com/encyclopedia/term/file-manager
  2. https://www.computerhope.com/jargon/f/filemana.htm
  3. https://www.tecmint.com/linux-terminal-file-managers/
  4. https://developer.apple.com/documentation/Foundation/FileManager
  5. https://www.lenovo.com/us/en/glossary/file-manager/
  6. https://www.geeksforgeeks.org/linux-unix/file-management-in-linux/
  7. https://www.quora.com/What-is-the-difference-between-a-shell-and-text-editor-Are-you-not-able-to-just-open-the-file-in-the-shell-and-edit-the-text-there-instead-of-opening-another-program-to-edit
  8. https://askubuntu.com/questions/506510/what-is-the-difference-between-terminal-console-shell-and-command-line
  9. https://unix.org/what_is_unix/history_timeline.html
  10. https://www.redhat.com/en/blog/unix-linux-history
  11. https://arstechnica.com/features/2005/05/gui/
  12. http://toastytech.com/guis/alto.html
  13. https://www.bleepingcomputer.com/news/microsoft/windows-30-file-manager-reborn-in-all-its-nostalgic-glory/
  14. https://ui.codexpanse.com/norton-commander.html
  15. https://gekk.info/articles/explorer.html
  16. https://blogs.gnome.org/mclasen/2012/08/30/on-nautilus/
  17. https://pk.org/articles/big-ideas-fs.html
  18. https://thenextweb.com/news/apple-ios-files-management-app
  19. https://cyberpress.org/microsoft-adds-ai-windows-file-explorer/
  20. https://www.youngwonks.com/blog/operating-system-evolution
  21. https://learn.microsoft.com/en-us/windows/win32/fileio/about-file-management
  22. https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html
  23. https://learn.microsoft.com/en-us/windows/win32/shell/manage
  24. https://userbase.kde.org/Dolphin/File_Management
  25. https://learn.microsoft.com/en-us/windows/win32/fileio/obtaining-and-setting-file-information
  26. https://developer.apple.com/library/archive/documentation/CoreServices/Reference/MetadataAttributesRef/Reference/CommonAttrs.html
  27. https://support.microsoft.com/en-us/windows/find-your-files-in-windows-5c7c8cfe-c289-fae4-f5f8-6b3fdba418d2
  28. https://learn.microsoft.com/en-us/windows/win32/lwef/-search-2x-wds-aqsreference
  29. https://apps.gnome.org/Nautilus/
  30. https://support.microsoft.com/en-us/windows/file-explorer-in-windows-ef370130-1cca-9dc5-e0df-2f7416fe1cb1
  31. https://docs.kde.org/stable5/en/dolphin/dolphin/using-dolphin.html
  32. https://phabricator.kde.org/T8187
  33. https://support.microsoft.com/en-us/windows/use-a-screen-reader-to-explore-and-navigate-file-explorer-in-windows-e7d3a548-87dd-459f-a991-9fde3f7ce927
  34. https://support.microsoft.com/en-us/windows/discover-windows-accessibility-features-8b1068e6-d3b8-4ba8-b027-133dd8911df9
  35. https://develop.kde.org/docs/plasma/theme/theme-elements/
  36. https://develop.kde.org/docs/apps/dolphin/service-menus/
  37. https://extensions.gnome.org/
  38. https://www.geeksforgeeks.org/linux-unix/10-best-file-managers-for-linux/
  39. https://www.turnkeylinux.org/fileserver
  40. https://ecsoft2.org/applications-network-file-transfer
  41. https://advancedfilemanager.com/docs/integrations/google-drive/
  42. https://www.filestack.com/docs/tutorials/google-drive-oauth/
  43. https://docs.cloud.google.com/integration-connectors/docs/connectors/onedrive/configure
  44. https://developers.google.com/workspace/drive/api/guides/api-specific-auth
  45. https://docs.kde.org/trunk5/en/krusader/krusader/remote-connections.html
  46. https://developer.gnome.org/documentation/guidelines/maintainer/integrating.html
  47. https://phoenixnap.com/kb/ubuntu-file-manager
  48. https://www.kiteworks.com/managed-file-transfer/encryption-capabilities/
  49. https://www.advsyscon.com/blog/data-security-tips-protect-file-transfers/
  50. https://www.opswat.com/blog/secure-file-transfer-how-to-protect-data-during-transit
  51. https://www.getapp.com/collaboration-software/file-sharing-api/f/real-time-synchronization/
  52. https://pubs.aip.org/aip/acp/article-pdf/doi/10.1063/5.0133828/18275449/050085_1_5.0133828.pdf
  53. https://midnight-commander.org/
  54. https://github.com/ranger/ranger
  55. https://www.linuxcommand.org/lc3_adv_mc.php
  56. https://vifm.info/
  57. https://dev.yorhel.nl/ncdu/man
  58. https://www.tldp.org/LDP/LG/issue23/wkndmech_dec97/mc_article.html
  59. https://dev.to/ccoveille/terminal-file-managers-1b5l
  60. https://itsfoss.com/vifm-terminal-file-manger/
  61. https://www.digitalocean.com/community/tutorials/basic-linux-navigation-and-file-management
  62. https://invisible-island.net/ded/dating-dired.html
  63. https://invisible-island.net/ded/
  64. https://www.inmotionhosting.com/support/edu/emacs/dired/
  65. https://www.computerhistory.org/revolution/input-output/14/347/1857
  66. https://www.pcmag.com/encyclopedia/term/xtree
  67. https://www.edn.com/embedded-operating-systems-part-6-i-o-and-file-system-management/
  68. https://winworldpc.com/product/xtree
  69. https://fman.io/blog/dual-pane-file-manager-history/
  70. https://www.techradar.com/news/software/applications/6-best-orthodox-file-managers-for-linux-605506
  71. https://winscp.net/eng/docs/ui_commander
  72. https://www.ghisler.ch/wiki/index.php/History_of_Total_Commander
  73. https://doublecmd.sourceforge.io/
  74. https://www.ghisler.com/featurel.htm
  75. https://www.microsoft.com/en-us/research/wp-content/uploads/2002/02/tr-2002-17.pdf
  76. https://copytrans.studio/support/what-is-windows-explorer/
  77. https://www.zdnet.com/article/how-to-add-the-macos-finder-path-bar-for-easier-navigation/
  78. https://eclecticlight.co/2025/02/01/a-brief-history-of-the-finder/
  79. https://nou.edu.ng/coursewarecontent/CIT381.pdf
  80. https://www.howtogeek.com/you-should-enable-finders-path-bar-and-path-icon-on-mac-heres-why/
  81. https://ir.canterbury.ac.nz/bitstream/handle/10092/8968/thesis_fulltext.pdf?sequence=1&isAllowed=y
  82. https://trepo.tuni.fi/bitstream/10024/82681/1/gradu05185.pdf
  83. https://www.osnews.com/story/7548/how-to-deal-with-the-spatial-paradigm/
  84. https://delta.cs.cinvestav.mx/~mcintosh/comun/rec-f/node4.html
  85. https://www.levenez.com/NeXTSTEP/redirect_NeXTSTEP_pdf.html
  86. https://www.osnews.com/story/7344/opinion-why-users-blame-the-spatial-nautilius/
  87. https://www.linuxpromagazine.com/content/download/63272/487629/version/1/file/3D_File_Browsers.pdf
  88. https://fsv.sourceforge.net/
  89. https://www.linux-magazine.com/content/download/63327/487804/version/1/file/Looking_Glass_3D_Desktop.pdf
  90. https://www.scitepress.org/Papers/2010/28248/28248.pdf
  91. https://github.com/3dfsb-dev
  92. https://www.icewalkers.com/linux/software/516470/ThreeDFM.html
  93. https://github.com/Studio-42/elFinder
  94. https://owncloud.com/news/owncloud-web-new-frontend/
  95. https://oc.owncloud.com/rs/038-KRL-592/images/Whitepaper_ownCloud_Architecture_Overview_ENG.pdf
  96. https://www.drupal.org/project/elfinder
  97. https://owncloud.com/product/collaboration/
  98. https://owncloud.com/features/
  99. https://www.techtarget.com/searchsecurity/definition/role-based-access-control-RBAC
  100. https://owncloud.com/product/
  101. https://growthmarketreports.com/report/file-manager-software-market
  102. https://hubstaff.com/tasks/state-of-remote-project-management
  103. https://virtualization.info/2025/02/23/state-of-docker-and-the-container-industry-in-2025/
  104. https://support.google.com/files/answer/9848742?hl=en
  105. https://apps.apple.com/us/app/files/id1232058109
  106. https://support.apple.com/en-us/102570
  107. https://source.android.com/docs/core/storage/scoped
  108. https://developer.apple.com/documentation/security/protecting-user-data-with-app-sandbox
  109. https://itnext.io/navigating-the-challenges-of-scoped-storage-lessons-for-modern-android-apps-b5fd8318a02c
  110. https://developer.android.com/develop/background-work/background-tasks/optimize-battery
  111. https://blog.google/outreach-initiatives/accessibility/android-gemini-ai-gaad-2025/
  112. https://developer.apple.com/documentation/arkit/previewing-a-model-with-ar-quick-look
  113. https://rsmobile.net/mobile-app-development-trends-2025/
  114. https://www.sitepoint.com/real-history-gui/
  115. https://learn.microsoft.com/en-us/windows/win32/dlgbox/open-and-save-as-dialog-boxes
  116. https://developer.apple.com/documentation/appkit/nsopenpanel
  117. https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.openfiledialog
  118. https://developer.apple.com/documentation/appkit/nsopenpanel/allowsMultipleselection
  119. https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/UsingtheOpenandSavePanels/UsingtheOpenandSavePanels.html
  120. https://developer.apple.com/documentation/security/accessing-files-from-the-macos-app-sandbox
  121. https://learn.microsoft.com/en-us/uwp/api/windows.storage.pickers.filesavepicker
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.