Moving over
What it takes
Your saved sites become connection definitions, and the download folder you kept choosing manually becomes a property of the connection.
You already move files without thinking about it
WinSCP set the standard for what a transfer client owes you: two panes, a queue that survives, and an editor that saves straight back. Vandle builds the same surface and puts a terminal and a remote desktop next to it.
Credit where it is due
WinSCP is free, precise and scriptable, its synchronise mode has saved more deployments than most CI systems, and editing a remote file in place is exactly the right default.
What changes
Four things you get that you did not have.
- A split view between two remote hosts, so a file moves from server A to server B without landing on your laptop first.
- Inline editing on a proper editor surface: double-click a text file, save, and it goes back over the wire.
- A default download folder per connection, so an accounting server drops its files where accounting files belong.
- The same client on Linux and macOS, with the same connection list.
Side by side
WinSCP and Vandle
| Aspect | WinSCP | Vandle |
|---|---|---|
| Platforms | Windows | Windows, Linux, macOS |
| Remote to remote | Via the local machine | Direct, in a split view with a connection picker per pane |
| Terminal | A side feature | A first-class surface on the same connection |
| Routing | Per-session proxy settings | A route object per connection or inherited from the folder |
And the rest of it
Four more protocols came along
Replacing one tool gets you five. Whatever else that machine speaks is already a row on the same record - and every one of them takes the route you assigned.
Web
Real browsing, properly routed
SSH
A terminal that keeps up
SFTP
Two remote panes, no detour
WebDAV
The other half of file transfer
RDP
Desktops on a native surface
Local
Your own machine, in the same list
Also compared