FTP vs SFTP vs FTPS (Comparison Table)
FTP, SFTP and FTPS all copy files between a computer and a server, and they are not three modes of one protocol. SFTP is a file subsystem inside SSH. FTPS is FTP with TLS wrapped around it. Plain FTP has no encryption at all.
| Dimension | FTP | SFTP | FTPS |
|---|---|---|---|
| Encryption | None | SSH, always | TLS |
| Ports | 21 + data range | 22 only | 990 or 21 + range |
| Credentials in transit | Cleartext | Encrypted | Encrypted |
| Authentication | Username and password | Password or SSH key | Certificate plus password |
| Transport | Two TCP channels | One SSH session on TCP | FTP plus TLS |
| Firewall-friendliness | Poor | Excellent | Fiddly |
| Speed on a normal upload | No cipher, extra connections | Small cipher cost, one connection | TLS cost plus extra ports |
| Verdict | Avoid on the public internet | Default choice | Only if SSH is impossible |
The shared letters cause the mix-up. SFTP is not secured FTP, and a client set to FTPS will not talk to an SFTP-only server. On WebJi® cPanel hosting the account is set up for SFTP with the panel username.
How FTP and SFTP move a file
FTP opens a command connection on TCP port 21, then a second TCP connection for the file. In active mode the server calls the client back. In passive mode the client opens a high port that the server names. The password and the file travel in cleartext on those channels.
SFTP never opens that second connection. The client starts SSH on TCP port 22, checks the server host key, authenticates, and requests the SFTP subsystem. Listings, uploads and deletes are SSH packets on that single session.

People who say ftp and sftp mean this pair. TFTP is a separate UDP tool for devices such as routers, and it is not how you publish a website.
Why plain FTP is unsafe for a website upload
Plain FTP is a poor choice on any network you do not control, because a listener on the path can read the username, the password and the file. SFTP encrypts all three, and the host-key check rejects a server that is not the one you connected to before.
Browsers removed their built-in FTP clients for that reason. Keep port 21 only for a throwaway file on a private network, never for a site backup, a mailbox export or a customer list. Active mode also asks the server to open a connection outward, which firewalls rightly refuse.
Connecting With FileZilla Over SFTP (Steps)
FileZilla uses SFTP when the protocol menu says SFTP and the port is 22. On WebJi® shared hosting, the cPanel username and the panel password are the login.
- Install FileZilla, then open File, Site Manager, and New Site.
- Set Protocol to SFTP - SSH File Transfer Protocol, Host to the domain or the server IP, Port to 22, and Logon Type to Normal. Choose Key file only when you were given an SSH key.
- Connect and accept the host-key prompt the first time. That prompt is SSH checking the server, not a failed login.
- Drag files from the left pane to the right pane. For a website, open the remote public_html folder.
A message of 530 authentication failed means the username or password does not match. Connection refused on port 22 means something on the path is blocking SSH. Try the server IP from the welcome mail before you fall back to plain FTP.
Where to put the files, including public_html, is covered in how to upload a website using FTP.
Firewall and port differences between FTP and SFTP
SFTP needs a single inbound TCP port, 22. FTP needs port 21 plus a range of passive data ports, so it often fails on a home router or an office firewall that only allows known ports.
Active FTP rarely survives client-side NAT, because the server cannot call back in. Explicit FTPS uses 21 plus a passive range. Implicit FTPS uses 990 plus that range. If FTPS has to stay, pin the range to something small such as 30000–31000 and open only those ports.
The port each protocol uses, and what to do when SSH is not on 22, is in the SFTP port number guide. cPanel can also limit SSH and SFTP logins to your IP.
Pack a large site into one archive before you send it. Thousands of tiny files spend more time opening connections than moving bytes. A one-file edit can stay in File Manager and skip the client.
SCP vs FTP, and how SSH differs from both
SCP and SFTP both use SSH. Neither one is FTP. SCP copies a file or a folder in one command and then exits. SFTP stays open so you can list, resume, rename and delete. SSH itself is the encrypted login; it does not upload the site unless you run SFTP or SCP over it.
Use SCP for a single copy. Use SFTP when you need to look around the account. Current OpenSSH carries the scp command over the SFTP subsystem, so both accept the same key or password on port 22. The command forms are in the scp guide for copying files.
Which is faster, FTP or SFTP
FTP skips the cipher, so a lab test on an empty network can show it slightly ahead. On a real upload the difference is small next to disk speed and the link itself. Encryption is not what makes a folder of images feel slow.
What does feel slow is FTP opening a new data connection per file, or waiting on a passive port that the firewall dropped. One SFTP session, or one compressed archive, usually finishes a normal site upload without that stall. Choose SFTP because the login is hidden, not because of a speed ranking.
When to choose SFTP on a cPanel account
Use SFTP for site uploads, backup downloads and theme files on a cPanel account. Use FTPS only when the other side cannot speak SSH and already requires TLS. Use plain FTP only for a disposable file on a network you control, then close it.
WebJi® shared hosting expects SFTP with the cPanel username on port 22. This page has no plan price. Ask support@webji.services for a quote before you pay, and do not use the office phone as a support line.
Frequently Asked Questions
What is the difference between FTP and SFTP?
FTP moves files in cleartext over port 21 and a second data port. SFTP moves them inside an encrypted SSH session on port 22. They are separate protocols, not two settings of one protocol.
Is SFTP more secure than FTP?
Yes. SFTP encrypts the password, the commands and the file bytes, and it checks the server host key. FTP sends all of that in cleartext, so anyone on the path can read it.
Is port 22 used for FTP or SFTP?
Port 22 is SFTP and SSH. Port 21 is FTP. FTPS starts on 21 in explicit mode or 990 in implicit mode. A client pointed at 22 with the FTP protocol selected will not log in.
Why is plain FTP being phased out?
The password and the files are visible on the network, and the second data port is awkward behind firewalls. Browsers removed built-in FTP clients for that reason. SFTP does the same upload without exposing the login.
Is SFTP still used?
Yes. SFTP is the usual way to upload a site on modern hosting, including cPanel accounts that still label the screen FTP. The label is old. The safe choice on that screen is SFTP on port 22.
Does SFTP use TCP?
Yes. SFTP runs over SSH, and SSH uses TCP port 22. It is not a UDP protocol. If a firewall allows only UDP, or blocks TCP 22, the session does not start.
Can FileZilla connect via SFTP?
Yes. Set the protocol to SFTP, the port to 22, and use the hosting username and password. Accept the host key on the first connection. A directory listing means it worked.
Do I still need FTP if I have cPanel?
No. Use SFTP with the cPanel username, or edit one file in File Manager. Plain FTP is not required to publish the site, and an open port 21 adds a cleartext login.

