WinSCP moves and manages files between a Windows computer and a remote server. Its two-pane workspace can show local files on one side and remote files on the other, while the Explorer-style layout uses one main file panel. WinSCP works with SSH-based file transfer and several other remote-storage protocols. It changes files on the selected source or destination; it does not publish a website, configure the remote service, or resolve permissions that the server account does not have.
Remote file panels
A saved site records the server address, protocol, and login settings. After connection, common actions include upload, download, rename, delete, and permission changes when the protocol supports them. Dragging between panels starts a transfer, while dragging within one remote panel can request a remote move rather than a download.
The visible folder and selected side matter before every destructive command. The same filename can exist locally and remotely with different contents. An overwrite prompt compares the available size and time details, but those details do not establish which copy is correct. Open or compare the file when either side may contain unsaved work.
Trust the host
On an SSH connection, WinSCP displays the server’s host-key fingerprint if the identity is not yet trusted. The user should compare that fingerprint with a value supplied through an independent trusted route. Accepting an unverified fingerprint merely because the hostname looks familiar removes the check that distinguishes the intended server from an intercepted connection.
WinSCP stores the accepted identity for later sessions. A changed fingerprint then triggers another warning. A server reinstall or deliberate key rotation can cause that change, but interception can cause it as well. Confirm the change with the administrator before replacing the stored key. A password proves the user’s identity to the server; it does not prove the server’s identity to the user.
Text or binary
Binary mode transfers file bytes unchanged. Text mode can convert line endings between local and remote conventions, which is useful for genuine plain-text files read by platform-specific tools. It is unsafe for executables, archives, office documents, images, and other binary formats because conversion can alter valid byte sequences.
Automatic mode chooses text treatment from a filename mask. The decision therefore follows the name, not an inspection of what the file contains. A misleading extension or an incomplete mask can select the wrong mode. Use binary mode when exact bytes matter, and verify a checksum after transferring a deployment archive or another file whose integrity matters.
Sync direction
Directory synchronization compares local and remote trees, then prepares uploads, downloads, or deletions according to the selected direction. Local direction updates the computer from the server. Remote direction updates the server from the computer. Two-way mode considers changes on both sides and needs clearer conflict decisions.
Mirror and delete choices require special care because they can remove destination-only files. The preview checklist exposes planned actions before WinSCP runs them; review deletions instead of treating the list as a confirmation screen. Time-based comparison can also misread changes when a server records timestamps differently or a previous copy failed to preserve them. Size or checksum comparison may suit a sensitive one-time reconciliation better, though checksum work can take longer.
Automation boundaries
WinSCP can run scripted transfers without the graphical window. The console interface handles sequences of connection and file commands, while the .NET assembly supports programs that need structured control and error handling. Automation still needs a fixed expected host key or certificate decision. A script that accepts any presented identity turns a security warning into silent behavior.
Graphical preferences and stored site settings can influence a later script when both use the same configuration. A change made for an interactive transfer may therefore alter overwrite rules, transfer masks, or another automated choice. Keep production automation explicit and isolated from casual interface changes. WinSCP also lacks a normal direct server-to-server panel transfer; moving files between two remote sites commonly sends the data through the local computer, which adds local bandwidth and another failure point.
