WinSCP

WinSCP is a free, open-source SFTP, SCP, FTP, WebDAV and S3 client for Windows, used by sysadmins and developers to move files between a Windows PC and Linux servers, NAS boxes, web hosts and cloud storage. If you searched for “WinSCP download”, this page covers the current version, what it does well, and how to script it for unattended transfers.

WinSCP has been developed by Martin Přikryl since 2000. Besides the two-panel file manager it has a full scripting interface and a .NET assembly, which is why it shows up in so many scheduled upload and backup jobs on Windows servers.

WinSCP at a glance

What it does

• Connects over SFTP, SCP, FTP (with explicit/implicit TLS), WebDAV and Amazon S3-compatible storage.
• Two interfaces: Commander (local and remote panels side by side) and Explorer (a single remote panel that behaves like Windows Explorer).
• Password, public-key, keyboard-interactive and Kerberos authentication; offers to convert OpenSSH private keys to PuTTY format on first use.
• Synchronizes directories in either direction, compares folders, and can keep a remote directory up to date while you edit locally.
• Built-in text editor for quick config changes on the server, with the option to use your own editor.
• Opens the current session in PuTTY with one click and imports saved PuTTY sessions.
• Command-line scripting (winscp.com) and a .NET/COM assembly for PowerShell, C# and SSIS automation; it can generate script or code for the current session.
• Optional master password to encrypt stored site passwords.

How sysadmins use it

Automate a nightly SFTP upload

1. Connect once in the GUI and accept the server’s host key. Then, in the Login dialog, select the site and use Manage > Generate Session URL/Code to copy the exact open command with the host key fingerprint.
2. Save a script as C:Scriptsupload.txt:

open sftp://backup@files.example.com/ -hostkey="ssh-ed25519 255 xxxxxxxx..." -privatekey="C:Keysbackup.ppk"
put -neweronly C:Exports*.csv /data/incoming/
exit

3. Run it without touching the user’s saved settings, with a log:

"C:Program Files (x86)WinSCPWinSCP.com" /ini=nul /log=C:Logswinscp-upload.log /script=C:Scriptsupload.txt

4. Create a Task Scheduler job that runs this command under a service account; check the exit code (0 = success) or the log for failures.

Edit root-owned files over SFTP (sudo)

1. On the server, allow the user to run the SFTP server via sudo without a password prompt (a sudoers rule for the SFTP server binary).
2. In WinSCP, open Login > Edit > Advanced > Environment > SFTP and set SFTP server to sudo /usr/lib/openssh/sftp-server (Debian/Ubuntu) or sudo /usr/libexec/openssh/sftp-server (RHEL family).
3. Reconnect; files you create or edit now belong to root, so check ownership afterwards.

Mirror a local folder to a web server

1. Open both folders in Commander view and choose Commands > Synchronize (Ctrl+S).
2. Pick direction Remote, mode Synchronize files, and tick Preview changes to review deletions before anything happens.
3. For scripted runs use synchronize remote -delete C:Site /var/www/site inside a script; test without -delete first.

Install and first run

WinSCP comes as an installer, a portable package (a ZIP you can run from a USB stick or admin share) and a Microsoft Store app. The installer can install for the current user only (no admin rights) or for all users, and offers to add WinSCP to the PATH so winscp.com works from any prompt. Requirements are modest: Windows 7 / Server 2008 or newer and 40–100 MB of disk. Windows XP and Server 2003 users need 6.3.7, the last version for those systems.

On first start, create a site with protocol, host, port (22 for SFTP/SCP, 21 for FTP) and user name. Gotchas:

• The first connection asks you to verify the server host key; compare the fingerprint with the server (ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub) rather than clicking Yes blindly.
• Settings are stored in the Windows registry by default. For a portable setup, switch to an INI file under Options > Preferences > Storage.
• Stored passwords are only obfuscated unless you set a master password under Preferences > Security.
• FTP through a firewall usually needs passive mode and an open passive port range on the server; prefer SFTP where you can.
• Hidden (dot) files are hidden by default: press Ctrl+Alt+H or enable them in Preferences > Panels.

Limitations

• Windows only: no macOS or Linux version.
• No SMB/CIFS support, and fewer cloud storage back ends than Cyberduck.
• The main release is 32-bit; a 64-bit build exists only as an experimental beta.
• Not a terminal: for shell work it hands off to PuTTY or another SSH client.
• Large numbers of small files transfer slowly over SFTP compared with archiving first and moving one file.

WinSCP vs alternatives

For RDP and SSH session management that works alongside WinSCP, see mRemoteNG.

FAQ

Is WinSCP free for commercial use?

Yes. WinSCP is free and open source under the GPL, which allows use for any purpose, including in companies. Donations are optional.

Is there a WinSCP portable version?

Yes. The portable package runs without installation; store the configuration in an INI file next to the executable to keep it fully portable.

Is there WinSCP for Mac or Linux?

No, WinSCP is Windows-only. On macOS use Cyberduck or FileZilla; on Linux, your file manager’s SFTP support or FileZilla.

WinSCP vs FileZilla: which is better?

WinSCP is better for SFTP/SCP on Windows and for scripted transfers; FileZilla is better if you need the same client on Windows, macOS and Linux.

How do I show hidden files in WinSCP?

Press Ctrl+Alt+H, or enable Show hidden files under Options > Preferences > Panels.

Can I see a saved password in WinSCP?

WinSCP does not display stored passwords. If you have lost one, reset it on the server and save the new one; protect saved passwords with a master password.

Why is “winscp is not recognized as an internal command”?

The WinSCP folder is not in PATH. Call winscp.com with its full path or reinstall with the option to add it to the search path.

Is WinSCP safe?

Yes when obtained from the official site or Microsoft Store and kept updated. Always verify host keys and use a master password if you store credentials.

Last checked against official sources: 30 September 2026 (developer website: winscp.net). Versions and licence terms change — confirm on the developer's site before deploying in production.