Fastest FTP Client?



I have tried 2-3 different ones about 1 month ago, and went back to filezilla, which if I'm not wrong still stores unencrypted passwords (if you store your websites details in its website manager).

This obviously isn't good and caused me problems in the past: there's a virus that searches for known ftp programs installed, sends the passwords somewhere and some software will replace all your files with some crappy js that distributes such virus....

I don't remember which clients I tried, but sure they were those recommended on download.com, and all of them were slower than fz.
I'm using filezilla but not saving passwords at the moment.
 
I've been using FileZilla since the very beginning. I tried a couple others like cute FTP, but FileZilla gets my vote.
 
I like SecureFX by VanDyke Software, Inc., it has some amazing features; like being able to use expressions to tell the server how to synchronize your files on both ends of the transfer. This is great for many sites.

It's not free, but it's worth every penny. I mainly got it because I wanted a secure client to put on my thumb drive that supported drag and drop (FileZilla was getting annoying). But the tech people E-mailing me during my 30-day trial (and even gave me 30 more days when I needed longer to evaluate it) for feedback on their product and giving tutorials and implementing my suggestions into future releases sold me.

As far as speed, it's pretty fast. As with anything, it's dependent on your internet connections, but I have transferred a 6GB file (twice) in a day with it. It will thread files if it is possible for that file-type.
 
Agreed!

Unless I'm mistaken, Fillzilla makes you download files, edit them locally, and then upload them. CuteFTP let's you work right on the server. Way better in my book!

True dat! Plus PRO allows for SSH on your server. Which is nice to have.
 
You have to pay for SFTP?

No.

Some hosts offer/require it for added security.

Most, not all, consumer or 'home' versions of FTP applications do not have SFTP/Secure Shell as an option for your uploads. Which can cause issues. Typically, not always, you have to pay for the PRO/Professional version to get it.
 
No.

Some hosts offer/require it for added security.

Most, not all, consumer or 'home' versions of FTP applications do not have SFTP/Secure Shell as an option for your uploads. Which can cause issues. Typically, not always, you have to pay for the PRO/Professional version to get it.

That's what I'm saying you have to pay for the feature? (I do hosting, and I'm a developer, I know what SSH itself is). I mean heck WinSCP is free.
 
No.

Some hosts offer/require it for added security.

Most, not all, consumer or 'home' versions of FTP applications do not have SFTP/Secure Shell as an option for your uploads. Which can cause issues. Typically, not always, you have to pay for the PRO/Professional version to get it.

Every FTP Client I have seen has the ability to choose your hostname and port number. Just change the port to 22 and you are good to go.

Now, SSH is a different story. You'll need a client for that. If you buy SecureFX you can bundle it with SecureCRT for a couple dollars more and have shell access. I just got it so that I could have all my accounts stored in one place.
 
Every FTP Client I have seen has the ability to choose your hostname and port number. Just change the port to 22 and you are good to go.

Now, SSH is a different story. You'll need a client for that. If you buy SecureFX you can bundle it with SecureCRT for a couple dollars more and have shell access. I just got it so that I could have all my accounts stored in one place.

It doesn't work that way you can't do straight FTP over the SSH port, unless the FTP client has built in the ability to do SFTP/SCP (and understands to switch to that mode on a standard port like 22).
 
Right, because they are basically two different services on the server. I was under the impression that you and the OP were debating on whether or not free FTP clients can connect with SFTP.

Secure transfer has become so common, that just about every FTP client will support it.

I was just pointing out that you can easily check it if you change the port number. If the client wasn't geared to work with multiple ports - they wouldn't have the textfield for it.
 
It doesn't work that way you can't do straight FTP over the SSH port, unless the FTP client has built in the ability to do SFTP/SCP (and understands to switch to that mode on a standard port like 22).

Well said Kbizzle my nizzle.
:rasta:
 
I was just pointing out that you can easily check it if you change the port number. If the client wasn't geared to work with multiple ports - they wouldn't have the textfield for it.

Incorrect, its because some like myself don't like using the standard ports for certain protocols, for example SSH into my server is not on port 22 for security reasons. The same can be said of the FTP port 21, as long as you keep the new port and 1 port below it (data) open. So the port field is there simply because, FTP may not always be on port 21. Doesn't mean that it supports other protocols simply because it lets you pick a port.