Description
Moving a few files onto a server leaves you with a short list of options: the veteran FTP clients still look like 2013 and arrive with bundled extras, while the modern-looking ones open with a sign-up form and cloud sync — for files that live on your own server.
Ghost FTP is aimed squarely at both problems. No telemetry, no ads, no product account and no hidden cloud backend — install it and connect. FTP, explicit FTPS and SFTP share one dual-pane workspace, local on the left and remote on the right, with a Site Manager holding your saved servers and keeping passwords, SFTP private keys and passphrases as separate, per-save decisions.
The transfer side is more careful than it looks. The queue has bounded concurrency with pause, resume, cancel, retry and clear-finished; progress, bytes moved, speed and ETA come from real transfer events rather than an estimate. A name collision asks explicitly whether to skip, replace, or replace and keep a recovery backup, and writes are staged to a temporary file and switched over atomically, so an interrupted transfer cannot corrupt the file already on the server. Only errors classified as retryable are retried; trust, permission and path failures surface instead of looping all night.
One more convenience: a remote text file opens in the window, is edited there and saved straight back, with no download-edit-upload round trip. Saving runs a SHA-256 revision check, so somebody else editing the same file mid-session is caught rather than overwritten. Written in Go, with portable and installer builds for Windows and Linux and an interface in 24 languages.
Three protocols, one window: FTP, explicit FTPS and SFTP share the interface and transfer engine, with the secure protocol chosen explicitly and never silently downgraded.
Dual-pane workspace: Local and remote panes navigate and sort independently, and recursive directory transfers run through the same engine.
Site Manager: Saved profiles keep host, port, protocol and starting directories; password, private key and passphrase are separate fields, and whether a secret is stored is decided per save.
A bounded transfer queue: Concurrency is capped, with pause, resume, cancel, retry and clear-finished, and progress, speed and ETA derived from actual transfer events.
Explicit conflict policy: Skip, replace, or replace with a recovery backup — and writes are staged then activated, so a broken transfer never leaves a corrupted remote file.
Remote text editing: Open a remote text file in place, with UTF-8 validation, line-ending preservation, SHA-256 revision tokens and verified read-back on save; binaries are rejected.
Secure defaults: FTPS certificate and hostname validation, strict SFTP host-key verification and pinning, bounded secret lifetimes and local root and path protections.
No telemetry, no account: No analytics, advertising, tracking pixels, fingerprinting or automatic crash uploads, and no product account — settings and credentials stay on the machine.
Ghost FTP is aimed squarely at both problems. No telemetry, no ads, no product account and no hidden cloud backend — install it and connect. FTP, explicit FTPS and SFTP share one dual-pane workspace, local on the left and remote on the right, with a Site Manager holding your saved servers and keeping passwords, SFTP private keys and passphrases as separate, per-save decisions.
The transfer side is more careful than it looks. The queue has bounded concurrency with pause, resume, cancel, retry and clear-finished; progress, bytes moved, speed and ETA come from real transfer events rather than an estimate. A name collision asks explicitly whether to skip, replace, or replace and keep a recovery backup, and writes are staged to a temporary file and switched over atomically, so an interrupted transfer cannot corrupt the file already on the server. Only errors classified as retryable are retried; trust, permission and path failures surface instead of looping all night.
One more convenience: a remote text file opens in the window, is edited there and saved straight back, with no download-edit-upload round trip. Saving runs a SHA-256 revision check, so somebody else editing the same file mid-session is caught rather than overwritten. Written in Go, with portable and installer builds for Windows and Linux and an interface in 24 languages.
Features
Three protocols, one window: FTP, explicit FTPS and SFTP share the interface and transfer engine, with the secure protocol chosen explicitly and never silently downgraded.
Dual-pane workspace: Local and remote panes navigate and sort independently, and recursive directory transfers run through the same engine.
Site Manager: Saved profiles keep host, port, protocol and starting directories; password, private key and passphrase are separate fields, and whether a secret is stored is decided per save.
A bounded transfer queue: Concurrency is capped, with pause, resume, cancel, retry and clear-finished, and progress, speed and ETA derived from actual transfer events.
Explicit conflict policy: Skip, replace, or replace with a recovery backup — and writes are staged then activated, so a broken transfer never leaves a corrupted remote file.
Remote text editing: Open a remote text file in place, with UTF-8 validation, line-ending preservation, SHA-256 revision tokens and verified read-back on save; binaries are rejected.
Secure defaults: FTPS certificate and hostname validation, strict SFTP host-key verification and pinning, bounded secret lifetimes and local root and path protections.
No telemetry, no account: No analytics, advertising, tracking pixels, fingerprinting or automatic crash uploads, and no product account — settings and credentials stay on the machine.
