WinSCP With a Seedbox: Setup, Speed Limits, and When to Switch

A WinSCP seedbox setup takes under a minute: create a site with SFTP, your server hostname from the client area, port 22, your username and password, and you are browsing your downloads in under a minute. It is free, open source, actively maintained and Windows-only. The catch is speed on big files: out of the box WinSCP pulls each file over one SSH connection, and its own FAQ explains why that gets slow across an ocean. You can switch on multi-connection downloads for SFTP, but it is an opt-in sub-option in Preferences that only applies to queued transfers. If you mostly download large files from a seedbox, evoftp segments every file by default and connects from a one-click file; if you also sync folders, script transfers or want deep Windows integration, keep WinSCP.

At a glance

Where WinSCP is better

• Sync and keep-up-to-date. The Synchronize dialog runs in either direction or both, compares by modification time, size or checksum, and shows a preview checklist before touching anything. Keep remote directory up to date watches a local folder and re-uploads on every change. evoftp has no sync of any kind.
• Scripting and automation. winscp.com runs scripts with /script and /command, there is a .NET assembly, and the GUI can generate a script from a transfer you just did. evoftp has no command line.
• Windows integration. Send To uploads, jump lists, an optional drag-and-drop shell extension, protocol URL handling and PuTTY cooperation. evoftp is a plain portable window.
• Maturity and error handling. WinSCP documents 55 error messages one page each, auto-reconnects during a transfer, while idle and on stall, and sets a speed limit per queued item. evoftp 0.2.0 has retry and instant cancel, no speed limit.
• Signed installer. WinSCP’s installer is signed with an EV certificate and the docs tell you which name to check on the Digital Signatures tab. evoftp’s Windows build is unsigned, so SmartScreen warns you the first time.

Where evoftp is better

• Segmented by default. Every file over 8 MB is split into pieces pulled over several SSH connections at once and written straight into place, with no setting to find and no merge step. Balanced profile: 4 segments per file, 3 files at once, 8 connections. Long distance profile: 8 segments and a 16 MB in-flight window, sized from your measured ping.
• No settings hunt. WinSCP’s single-file segmentation is a sub-option under Preferences → Background, only for SFTP, only above a size threshold, and only when the transfer goes through the queue. In evoftp the per-download override is a dropdown next to the Download button.
• Cross-platform. Windows, macOS (Apple Silicon and Intel) and Linux. WinSCP is Windows only.
• One-click connection. The client area builds an .evoftp connection file for your server; double-click and you are in. Nothing to type, nothing to get wrong.
• Resume without prompts. Re-download the same file into the same folder and the .evoftp-part sidecar continues.

If you use a seedbox

Set WinSCP up for your seedbox

You need the server hostname, username and password from the client area, which shows SFTP / FTP port 22 / 21; use SFTP. The SFTP setup guide shows where each value lives.

1. Install WinSCP (or unzip the portable executables, which are identical) and open it. The Login dialog appears.
2. Set File protocol to SFTP. The port number fills in as 22.
3. Type your server hostname into Host name, your seedbox username into User name and your password into Password. WinSCP’s docs suggest leaving the password empty if you save the site; set a master password under Preferences → Security if you want it stored.
4. Press Save and give the site a name so you do not retype it, then Login.
5. On the first connection WinSCP asks you to confirm the server’s host key. Accept it once; it is remembered.

You land in your home folder; drop a .torrent into downloads/watch and rTorrent picks it up. Uploading a file is F5 in the Commander interface, or drag it from Explorer onto the remote pane. The transfer files guide compares this with lftp, rclone and mounting.

The speed reality

WinSCP’s own FAQ, File transfer speed is very low, names two limits. First, encryption is CPU intensive and “it’s actually a capacity of a single CPU core that limits the transfer speed”. Second, SFTP is request/response: the client “sends a read/write request to the SFTP server, waits for a response; and repeats, until the end of the file”, so every millisecond of latency is paid over and over. The FAQ adds that the cap is partly inherited from the PuTTY code WinSCP is built on.

The remedies it lists, and how they play on a seedbox:

• Change cipher (“Blowfish is usually a lot faster than AES”). Only helps if your CPU is the bottleneck, and the server has to accept the cipher.
• Toggle compression. The FAQ itself says this has small effect on media files, which are already compressed. That is most of what a seedbox holds.
• Use SCP instead. SCP needs a shell on the server. The standard seedbox login on port 22 is SFTP-only, so this is not an option unless you install the OpenSSH app.
• Optimize connection buffer size in either direction. Worth one try.
• Parallel connections. The one that actually fixes latency. In Preferences → Background, tick Use multiple connections for single transfer (this parallelises files in a queued batch), then the sub-option Use multiple connections for single file and set a size threshold such as 100M. SFTP only; not used with the Upload/Download and Delete command or when directory timestamps are preserved. Raise Maximal number of transfers at the same time too, since that caps the background connections.

Set up like that, WinSCP will split large seedbox downloads across connections. With evoftp none of the above is needed: segmentation is the default for every file, on every OS, and the in-flight window adapts to your ping. In our tests a Mac in India at 250–700 ms RTT went from about 2.4 MB/s per connection to line speed with the 16 MB window and 8 segments. Your numbers will differ; the mechanism will not.

How to switch in two steps

1. Download evoftp-windows.exe from neo.myseedbox.site/share/evoftp. It is portable: no installer. SmartScreen will warn because the build is unsigned; choose More info → Run anyway.
2. In the client area, open the Desktop app row and click Connection file. Double-click the downloaded .evoftp file and you are connected. Your password is stored encrypted with your Windows login.

Keep WinSCP installed; there is nothing to migrate, and you will still want it for sync, scripting or remote editing.

FAQ

Does WinSCP support segmented downloads?

Yes, but only for SFTP, only as an opt-in: Preferences → Background → Use multiple connections for single transfer, then the sub-option Use multiple connections for single file with a size threshold. It applies to queued transfers and is disabled by the Upload/Download and Delete command or when directory timestamps are preserved. Without it, each file uses one connection.

Why is WinSCP slow with my seedbox?

Almost always latency. SFTP sends a request, waits, and repeats for the whole file, so a single connection from far away crawls. WinSCP’s FAQ lists cipher, compression and buffer tweaks, but the fix that scales is more connections per file: enable the multi-connection option above, or use a client that segments by default.

Does WinSCP resume interrupted downloads?

Yes on SFTP and FTP. By default files over 100 KB are written under a temporary .filepart name and renamed on completion; if the transfer breaks, WinSCP detects the partial file on retry and offers to resume. SCP and WebDAV do not support resume.

Can I use WinSCP on a Mac or Linux?

No. WinSCP is Windows-only. On macOS or Linux, evoftp ships Apple Silicon and Intel builds and a Linux AppImage.

Can I run evoftp and WinSCP side by side?

Yes. Both talk plain SFTP to the same server with separate settings. Use evoftp for bulk downloads and WinSCP for sync, scripting and remote editing.

WinSCP is a good free client and a great automation tool; for pulling big files off a seedbox it needs a settings hunt that evoftp skips. Grab the Windows build from neo.myseedbox.site/share/evoftp, download the connection file from your client area, and see which one wins on your line.