A dual-pane File Manager for every server.
File Transfer is a first-class Mongrel connection, next to databases, terminals, containers, and APIs. Browse FTP, FTPS, SFTP, SCP, S3, WebDAV, Azure Blob, or SMB in two panes, drag selections between them, resume interrupted work, and restore each profile's working folders the next time you connect.
Windows x64 and ARM64 · macOS Apple silicon · Linux x86-64
// Connections → File Transfer
Use the protocol the host already speaks.
New Connection offers Database, Container, Terminal, File Transfer, and API Client. File Transfer profiles cover FTP, FTPS, S3, WebDAV, Azure Blob, and SMB. SFTP and SCP stay on the SSH terminal profile, so keys, agent auth, and jump hosts are not duplicated. S3 uses a blank endpoint for Amazon S3 or a service URL for Spaces, MinIO, R2, B2, and Wasabi. Azure Blob uses native Blob REST, not the S3 API.
// What ships
File transfer built for daily work.
A first-class connection kind
Connections → New Connection → File Transfer creates a standalone FTP, FTPS, S3, WebDAV, Azure Blob, or SMB profile. SSH terminal profiles open SFTP from Tools → File Manager, with automatic SCP fallback.
Every protocol the host already speaks
FTP, explicit and implicit FTPS, S3-compatible object storage, WebDAV, native Azure Blob REST, and SMB/CIFS are dedicated File Transfer profiles. SFTP rides the SSH session you already configured; SCP appears when the server disables the SFTP subsystem.
Verified FTPS
Control and data channels use verified TLS, custom CA certificates, and optional PEM client certificates with encrypted private keys in the OS keychain.
Dual-pane file management
Local and remote panes sit side by side. Click Name or Size to sort locally, double-click .. to go up, drag translucent ghosts between panes, and press Delete to confirm. Context menus use this pane's selection only. Sync this folder is a header button that compares the open Local and Remote folders, previews the plan, and queues ordinary uploads and downloads. It does not delete extras.
Transfers drawer and durable queue
A slim Transfers bar stays at the bottom, expands into a resizable list of per-file cards, and can Keep open for history or Auto-hide when idle. Unfinished jobs survive quit or crash; Mongrel does not start them until you reopen that profile's File Manager.
Resume where the protocol allows
SFTP can pause and resume with random access. FTP/FTPS uses REST or APPE. S3 continues multipart uploads and Range downloads. WebDAV and Azure Blob use HTTP Range. SMB continues a local partial and a remote write offset. SCP cannot resume.
Confined local access
Native folder grants confine local access. Mongrel remembers the chosen folder and last subfolder, and can grant exactly one parent when you navigate up from the grant root.
Downloads stay available
Browsing and downloads work without a license. Uploads and remote mutations require an active license or trial. Read-only profiles cannot write remotely.
// Security boundary
Plain FTP stays visibly plain. Secrets stay in the keychain.
Mongrel warns before sending plaintext FTP credentials and marks unencrypted sessions. FTPS does not silently fall back: certificate or hostname failures stop the connection. Passwords, S3 secrets, WebDAV tokens, Azure keys or SAS tokens, and SMB passwords use the operating system credential facility. The durable transfer ledger stores paths and job state only. Transfers write to a temp file and replace the destination, so cancel does not leave a destination partial unless you chose Resume.
// FAQ
Frequently asked questions.
Which file-transfer protocols does Mongrel support?
Standalone File Transfer profiles cover FTP, explicit FTPS, implicit FTPS, S3-compatible object storage (Amazon S3, DigitalOcean Spaces, MinIO, Cloudflare R2, Backblaze B2, Wasabi), WebDAV (Nextcloud, ownCloud, IIS), native Azure Blob REST, and SMB/CIFS (Windows and Samba shares). SSH terminal profiles include SFTP, with automatic SCP fallback when a server disables the SFTP subsystem. System-ssh profiles that shell out to the OS ssh binary do not open File Manager.
How do I open the File Manager?
For FTP, FTPS, S3, WebDAV, Azure Blob, or SMB, create a File Transfer connection and click Connect. For SFTP or SCP, connect an SSH terminal profile, then choose Tools → File Manager. Connected File Transfer sessions stay on a tab strip so switching profiles does not reopen the session.
What is the difference between these protocols?
FTP is unencrypted and Mongrel keeps an Unencrypted FTP badge visible. FTPS adds TLS to FTP. SFTP is a different protocol over SSH. SCP is a fallback for locked-down SSH hosts and cannot pause, resume, or chmod. S3 and Azure Blob treat prefixes as folders; rename is copy-then-delete. Azure Blob uses native Blob REST, not the S3 API. WebDAV uses PROPFIND, GET, PUT, DELETE, MKCOL, and MOVE. SMB talks to a share over SMB2/3 with NTLM.
Does Mongrel support explicit and implicit FTPS?
Yes. Explicit FTPS sends AUTH TLS before login. Implicit FTPS starts TLS immediately, normally on port 990. Both verify certificates and hostnames and encrypt control and data. There is no insecure or clear-data FTPS mode.
Do transfers survive quitting Mongrel?
Yes. Unfinished jobs are stored as paths and job state only — never secrets or folder-grant tokens. Mongrel does not start them at launch. Reopen that connection's File Manager and the remembered local folder to continue. A transfer that was running when Mongrel quit comes back as queued and uses Resume, unless you had chosen Skip.
Can Mongrel synchronize two folders?
Yes. Sync this folder is a File Manager header button. It compares the open Local folder with the open Remote folder by size and modification time, shows a preview, and queues ordinary uploads and downloads. It is available on FTP, FTPS, SFTP, S3, WebDAV, Azure Blob, and SMB. SCP can download from the plan. Apply stays off if the walk is truncated (10,000 entries) or more than 128 files would transfer. It does not delete extras, run a script, or start at launch.
Can several files transfer at once?
SFTP, S3, WebDAV, Azure Blob, and SMB run several files at once with a global cap of 8. FTP and FTPS still send one file at a time on the control channel, but the rest of the selection stays queued.
What happens if an FTP session sits idle?
FTP and FTPS send a keep-alive on the control channel about every 25 seconds so typical server idle timeouts do not drop File Manager. A dead connection reconnects before the next listing or transfer. The destination pane refreshes after the whole queue finishes.
Are downloads locked without a license?
No. Browsing and downloads stay available. Uploads, rename, delete, new folder, chmod, and symlink require an active license or trial, and are disabled on read-only connections.
Related guides and comparisons
Files, terminals, databases, and infrastructure together.
7-day trial. Windows, macOS, Linux. No credit card.