January 31, 2014

Why Windows Explorer is a Slow FTP Client

Windows Explorer has a static buffer size of 4096 bytes that can't be changed, in comparison to that FileZilla has a buffer size of 256 KB. The buffer size of FileZilla is thus 64 times better than that of Windows Explorer, and that explains why it capable of doing much faster transfers.

When this buffer gets filled, which goes very fast for 4096 bytes, it starts delaying loading additional data. So rather than loading a full 256 KB and sending that it only loads up to 4 KB. This takes down the upload speed as some delay is introduced.

You can change a thousand network and I/O settings but it will likely not have much effect. FTP programs have much better support as well as features such as simultaneous transfers and resuming a failed transfer, which makes Windows Explorer the wrong tool to be used for FTP. Windows Explorer isn't really made to do FTP transfers.

Is your business properly protecting critical files?

Download this free Ebook and learn about the 20 alarming statistics about internal file sharing threats your business is at risk for so you can better protect yourself.

Tag(s): FTP

Martin Horan

Martin, Sharetru's Founder, brings deep expertise in secure file transfer and IT, driving market niche success through quality IT services.

Online FTP: What to Look for When Replacing an In-House Server

Are you tired of maintaining your in-house server? The high costs, regular... Read More

How to Choose the Right FTP Host

Choosing the right FTP host is a tall task for any business. When you started... Read More

When to Use SFTP

Do you need to transfer a file, but you’re unsure of the best way to share it... Read More