What Is an FTP Account?

FTP Accounts Defined (Per-User File Access)

An FTP account is one named login on the hosting server: a username, a password, and a directory it is allowed to touch. It is not a copy of your control panel — whoever holds it can move files but cannot create databases, change DNS records, or open your invoices. cPanel formats the username as user@yourdomain.com so two accounts on different domains cannot collide.

• Per-user access — developers, clients and contractors each get their own login.
• Directory scoping — an account can be confined to one folder, so a client touches only their site.
• Quotas — a per-account disk limit stops one login from filling the drive.
• Revocable — delete the account when the engagement ends, without touching your cPanel password.

Connection uses an FTP client such as FileZilla, ideally over SFTP — the encrypted variant of the protocol. The full connection walkthrough is in the upload website via FTP guide, and the panel that issues these logins is covered on cPanel hosting.

Creating FTP Accounts in cPanel

In cPanel, open Files → FTP Accounts. Fill the Log In field with a short name only — cPanel appends @yourdomain.com automatically — then pick the domain, set a password, and let the Directory field define the account’s ceiling. cPanel pre-fills public_html/domain.tld/username; delete everything after public_html/ to grant the whole site. Set a quota or leave it Unlimited, then click Create FTP Account. The new account appears in the table below with Change Password, Change Quota and Delete controls beside it.

Directory Scoping and Quotas (Client Logins)

Scoping works like a ceiling, not a cage: the account sees its assigned folder and everything inside it, and cannot climb above. To move the boundary later, delete and recreate the account — the directory cannot be edited after creation. Quotas are per-account disk ceilings; set one whenever you hand a login to a client whose uploads you do not watch. One caveat: servers running ProFTPD ignore quotas entirely, so confirm which FTP daemon your host runs before promising a limit to a client.

Connecting: FileZilla Step-by-Step

Open FileZilla and fill four fields at the top: Host (ftp.yourdomain.com or the server hostname), Username (the full user@yourdomain.com string), Password, and Port — 22 for SFTP, blank for plain FTP on 21. Click Quickconnect and the remote pane opens inside the account’s assigned directory; drag files across to upload. If you would rather not type credentials, cPanel’s Configure FTP Client button downloads a ready-made config file for Core FTP or Cyberduck that logs you in on open.

FTP Login Failing? Common Causes

Five causes cover most failed logins. Wrong username format — cPanel wants the full user@yourdomain.com, not the short name, unless the account sits on a dedicated IP. Wrong port or TLS mode — plain FTP on 21 fails when the client is set to SFTP. A directory that no longer exists after the account was deleted or recreated. A full quota — uploads stop once the account hits its disk ceiling. A firewall blocking port 21 — corporate and hotel networks often do; SFTP on port 22 usually passes.

FTP vs SFTP: Use the Secure One

Plain FTP sends the username, password and file contents unencrypted — anyone on the network path can read them. SFTP wraps the same file operations inside SSH: a single port (22), optional key-based logins, no separate firewall rule to request. cPanel’s own guidance points primary accounts at SFTP and notes one quirk: FTP has no SNI support, so encrypted FTPS connects must use the server hostname, not your domain. Keep plain FTP for throwaway test uploads on a trusted network only.

When to Use File Manager Instead

When to use File Manager instead: cPanel's File Manager is the browser-native alternative for quick jobs — uploading a handful of files, editing one config line, extracting a zip — with no client install and no credential handout. The division of labour: File Manager for the owner's occasional work, FTP accounts for recurring contributors who need their own access, and SFTP/SSH for bulk operations like migrations that would time out in a browser.

Everything File Manager does an FTP account does too; the choice is about who is doing it and how often. Give clients their own scoped FTP account rather than your cPanel password — the audit trail alone justifies it.