muCommander
muCommander 1.6.2 is a lightweight Java dual-pane file manager for Windows, macOS, Linux and other platforms, with archives, SFTP, SMB, bookmarks, batch operations and portable settings.
What muCommander does
muCommander is a Java-based dual-pane file manager for local folders, archives and remote locations. It provides bookmarks, keyboard shortcuts, a command bar, batch operations, SFTP and SMB connections and portable configuration across several operating systems.
Version and Java requirements
Version 1.6.2 is the stable release represented here. MSI, DMG, DEB and RPM packages can provide a bundled JRE 25, while noarch, portable ZIP and TGZ packages require Java 11 or later and a correct JAVA_HOME. A nightly branch label should not be treated as stable release evidence.
Remote and file-operation boundaries
Dual-pane efficiency also makes it easy to select the wrong source, destination or account. Traditional FTP does not protect credentials or content; prefer SFTP or a controlled VPN, verify the server fingerprint and use the smallest account permission that works. Remote deletion may not have a local recycle bin.
Configuration and recovery
Bookmarks, commands and connection settings can contain hosts, usernames and paths, while custom commands can execute local code. Back up only what is understood, keep credentials separately encrypted and test copy, move, archive and checksum operations with a small disposable directory before touching important data.
Maintenance note
Review date: 2026-08-23. The page was checked against muCommander 1.6.2, bundled JRE 25, Java 11 requirements, remote protocol guidance, conflict behavior and licensing.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave muCommander to this cloud drive
Baidu Netdisk
Save muCommander to this cloud drive
muCommander 1.6.2 dual-pane file operations and SFTP guide
Practice copy, move and checksum operations with two test directories first, then establish a restricted SFTP connection and verify paths, fingerprints and credentials before handling important files.
Before you start
- Prepare two directories containing only disposable copies and keep important data in an independent backup.
- Use a bundled-JRE package when possible; portable and noarch packages require Java 11 or later and a verified JAVA_HOME.
- Create a low-privilege SFTP test account and avoid using production administrator credentials for the first connection.
Installation steps
- 01
Choose a bundled or portable package
Match MSI, DMG, DEB or RPM to the platform and architecture, or use ZIP or TGZ when portable settings are needed. Keep Java 11+ patched for generic packages.
- 02
Confirm both pane paths
Open a source test directory on one side and an empty target directory on the other, showing full paths, hidden files and sizes so both panes cannot be confused.
- 03
Set conflict and deletion behavior
Use test files to verify overwrite, skip, rename and recycle behavior. Network locations and archive contents may not offer local recovery after deletion.
Quick start
- 01
Complete a verifiable copy
Copy a small set of test files, compare counts, sizes, timestamps and sample hashes and only then try a move. Never start with the only copy of a file.
- 02
Create a restricted SFTP bookmark
Check hostname, port, server fingerprint and remote root, and log in with a low-privilege account. Do not accept an unverified host key or certificate.
- 03
Back up bookmarks and settings
Copy preferences, bookmarks, shortcuts and command-bar settings, encrypt any credential file separately and remove hostnames, usernames and paths from shared diagnostics.
Usage tips
- Version 1.6.2 can show authentication problems when the same server is used with several accounts. Give bookmarks clear names and confirm the current identity before a write operation.
- Custom commands, terminals and extensions can execute local code. Do not load an unknown configuration or pass unescaped filenames to a shell.
- A 1.6.3 nightly label in a development branch is not evidence that a stable package has changed. Keep the stable asset for production work.
- Measure file count, size and checksums after a large transfer and record the protocol, remote root and failure list for recovery.
Troubleshooting and uninstall
Why does the portable package say that Java is missing?
Install a supported Java 11 or later runtime, check CPU architecture and JAVA_HOME and inspect the actual runtime from a terminal. Use a known package source rather than a popup download.
Why can macOS not access Desktop or Downloads?
Review Privacy and Security file-access permissions and grant only the required directory. Do not solve a path issue by running the file manager as root indefinitely.
- Finish remote tasks and revoke test credentialsWait for copy queues, disconnect remote sessions, revoke test accounts or tokens and keep the required checksum and operation log.
- Remove configuration and portable dataUninstall the application or delete its portable directory, then remove bookmarks, credentials, shell history and temporary settings only after confirming that no source files are inside it.
Frequently asked questions
Do all muCommander packages include Java?
MSI, DMG, DEB and RPM packages can include a bundled JRE 25. Portable, noarch and TGZ packages usually require Java 11 or later and a correct JAVA_HOME.
Is FTP suitable for passwords or sensitive files?
Traditional FTP does not encrypt credentials or content. Prefer SFTP or a controlled VPN, verify the host fingerprint and use a restricted account.
Can dual-pane copy prevent every overwrite mistake?
No. Check both paths, conflict policy, free space and a small test transfer first. A remote or archive deletion may not have a local recovery path.