How to Create and Manage FTP Accounts in StackCP

FTP (and its more secure counterpart, SFTP) lets you transfer files between your computer and your hosting account using a dedicated FTP client like FileZilla, rather than uploading through the browser-based File Manager. StackCP has one important security behaviour every beginner should know before starting: FTP access is locked by default and has to be deliberately unlocked before you can connect.

This guide walks through the full process — unlocking FTP, finding your connection details, creating additional accounts, and connecting with a client.

Why Is FTP Locked by Default?

Unlike many hosting panels where FTP is simply "on" once an account exists, StackCP locks FTP access by default as a security measure, reducing the window of opportunity for unauthorized access attempts. You unlock it either for a limited period of time, or restricted to a specific IP address — meaning even if credentials were ever compromised, the connection still couldn't succeed unless FTP was actively unlocked and, if IP-restricted, coming from an approved location.

Step 1: Unlock FTP Access

1. Log in to StackCP.
2. Go to Manage Hosting, then select the package you want to connect to.
3. Find the Unlock FTP option.
4. Choose to unlock by time (FTP becomes accessible for a set period) or by specific IP address (FTP becomes accessible only from that address, for as long as you leave it unlocked).
5. Confirm — StackCP will show you the current unlock status and expiry, along with an option to lock it again manually at any point.

If you're connecting from a fixed home or office IP address, unlocking by IP is a good balance of convenience and security, since you won't need to repeat this step every session. If your IP changes frequently (e.g. mobile data, some ISPs), unlocking by time may be more practical.

Step 2: Find Your FTP Connection Details

Once unlocked, you'll need:

• Hostname: ftp.stackcp.com for most hosting packages, or wordpressftp.stackcp.com specifically for WordPress hosting packages.
• Username and password: shown in the FTP Details section when managing your hosting package. Your first (primary) FTP account's password is visible here directly.
• Port: the standard FTP port, or port 22 if connecting via SFTP instead.

Step 3: Connect Using an FTP Client (FileZilla Example)

1. Download and install a free FTP client such as FileZilla, if you don't already have one.
2. Open FileZilla and enter the Host (ftp.stackcp.com), your Username, Password, and Port.
3. Click Quickconnect (or the equivalent in your chosen client).
4. Once connected, you'll see your local computer's files on one side and your hosting account's files on the other — drag and drop between them to upload or download.

Step 4: Consider Using SFTP Instead of Plain FTP

StackCP also supports SFTP (SSH File Transfer Protocol), which encrypts the entire connection — including your login credentials — unlike standard FTP, which transmits data in plain text. For any transfer involving sensitive files or credentials, SFTP is the safer choice, and it uses the same unlock mechanism and account details, just connecting on port 22 instead of the standard FTP port.

One practical limit to know: the maximum single file upload size via FTP is 5GB. If you need to transfer something larger, SSH access (covered in a separate guide) is the appropriate tool instead.

Step 5: Create Additional FTP Accounts

If you're working with a developer, team member, or need separate access restricted to a specific folder (rather than sharing your primary account's full access), you can create additional FTP accounts:

1. In StackCP, go to the FTP Accounts section for your hosting package.
2. Create a new account, setting a username and password.
3. Restrict the account to a specific directory if you want to limit what that account can access — useful for giving a contractor access only to, say, a specific plugin folder, rather than your entire hosting account.

Each additional account still relies on the same unlock mechanism described in Step 1 — it doesn't bypass the lock, it simply gives that specific set of credentials scoped access once FTP is unlocked.

Step 6: Using a Custom FTP Hostname (Optional)

If you'd prefer to connect using ftp.yourdomain.com rather than ftp.stackcp.com, you can set this up via a CNAME DNS record pointing ftp.yourdomain.com to ftp.stackcp.com. As with any DNS change, allow time for propagation (commonly up to an hour, sometimes longer) before it takes effect. See our companion DNS records guide for more detail on setting up CNAME records.

Common Mistakes Beginners Make

• Forgetting FTP is locked and trying to connect immediately. If your connection fails and everything else looks correct, check whether FTP is currently unlocked for your package.
• Unlocking by IP, then connecting from a different network (e.g., switching from home Wi-Fi to mobile data) without re-unlocking for the new IP.
• Sharing your primary FTP account's full-access credentials with a contractor instead of creating a separate, directory-restricted account for them.
• Using plain FTP instead of SFTP when transferring sensitive files, missing out on the encryption SFTP provides.

Troubleshooting

"My FTP client says connection refused or times out." Confirm FTP is currently unlocked for the package, and that you're connecting from the IP address you unlocked it for (if you chose IP-based unlocking rather than time-based).

"My file won't upload via FTP." Check the file size against the 5GB per-file limit — anything larger needs to be transferred via SSH instead.

"I set up a custom FTP hostname and it's not working yet." DNS changes take time to propagate; wait at least an hour and confirm your CNAME record is configured correctly in the meantime.

Master FTP: A Note for Reseller Hosting Businesses

If you manage hosting on behalf of multiple customers, StackCP includes a Master FTP Access feature at the account level (rather than per individual hosting package), found under your reseller account's own Options. When enabled — it's off by default, the same cautious approach as standard FTP — it lets you access files across all your hosting packages using a single login, restricted to specific allowed IP addresses you configure. This can be a genuine time-saver for a hosting business managing many customer sites, since it avoids unlocking and connecting to each package's FTP individually. As with standard FTP, only enable it when needed and keep your allowed IP list current, since it grants broad, multi-package access.

Choosing Between the File Manager and FTP for Different Tasks

For a quick, single-file edit or a small upload, the browser-based File Manager (covered in our companion guide) is usually faster since it requires no unlocking step or separate software. FTP earns its place for larger, bulk transfers — migrating an entire existing website, syncing a local development environment regularly, or working with a developer's preferred workflow and tools. Many site owners and hosting resellers use both, choosing whichever fits the specific task at hand rather than treating them as competing options.

A Simple Security Habit Worth Building

Because StackCP's lock-by-default approach already does much of the security work for you, the main habit worth building on your end is discipline around re-locking. If you unlocked FTP by time, it will lock itself again automatically once the period expires — no action needed. If you unlocked by a specific IP and no longer need standing access from that location (for example, after a one-off migration project is finished), it's good practice to manually lock it again rather than leaving it unlocked indefinitely, even though the IP restriction itself already limits exposure.