The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →An FTP client is an app on your computer that connects to a game server’s file-transfer service so you can browse remote folders, upload and download files, and manage configurations, plugins, mods, worlds, logs, and backups. For most game servers, choose SFTP when the host provides SSH access: it encrypts the connection and normally uses SSH port 22. Use FTPS when only FTP with TLS is available, and avoid plain FTP on untrusted networks because it sends credentials and file contents without encryption.
What an FTP client does
The term “FTP client” describes the local program, not the server. The client supplies a graphical or command-line interface for a remote File Transfer Protocol service. After you enter the server address, protocol, port, username, and password (or a private key), it opens a session and displays the files you are allowed to access.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Most graphical clients use two panes. The local pane shows folders on your computer; the remote pane shows folders on the game server. Dragging a file from local to remote uploads it. Dragging in the other direction downloads it. Context menus usually provide rename, delete, create-directory, permissions, and “download” or “upload” commands. A transfer queue shows progress and lets you retry or pause jobs.
Clients do not run the game server and do not grant permissions that your hosting account does not have. They can only read or change paths exposed by the account and the protocol selected by the host.
#1 Best Overall
Why a game-server owner needs one
Control panels are convenient for routine actions, but file clients are useful when you need to move many files, preserve a local backup, or work with a directory tree that the panel’s editor does not expose. Common tasks include:
- Downloading a world, save, database, or complete configuration before an upgrade.
- Uploading a plugin, mod, resource pack, map, script, or server-side library.
- Editing configuration files such as
server.propertiesand restoring a known-good copy after a mistake. - Retrieving logs for troubleshooting or sending a log archive to an administrator.
- Moving backups to an external USB SSD or hard drive so a panel failure does not remove the only copy.
A March 23, 2026 game-server guide describes SFTP as the practical way to manage files outside a panel, including configurations, plugins, mods, logs, and worlds. Exact folders and permissions still depend on the game, host, and panel.
FTP, FTPS, and SFTP: which should you use?
These names describe different protocols. SFTP is not “FTP over SSH”; it is a separate SSH-based protocol with its own connection method.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Protocol | Encryption | Typical ports | How it connects | Game-server guidance |
|---|---|---|---|---|
| FTP | None for credentials or file data | Command port 21; active-mode data commonly uses port 20 | Separate command and data connections | Use only on a trusted, isolated network when no encrypted option exists. |
| FTPS | TLS encryption | Explicit FTPS commonly starts on 21; implicit FTPS commonly uses 990 | FTP with TLS added to the FTP session | Choose it when the host offers FTP with TLS but no SSH/SFTP account. |
| SFTP | SSH encryption for commands and data | Normally 22; some game panels use another SSH port, such as 2022 | One encrypted SSH connection | Preferred option when the host supplies SSH access. |
FileZilla’s protocol documentation notes that plain FTP sends credentials and data unencrypted, while SFTP carries both over one encrypted connection. SFTP also avoids FTP’s separate data-connection negotiation, which is a frequent source of firewall and NAT problems.
Information to collect before connecting
Open your hosting dashboard and copy the connection details exactly; do not substitute the website address for the file server unless the host says they are the same. You normally need:
- Host or IP address: a hostname such as the one shown in the panel, or a numeric address.
- Protocol: select SFTP, FTPS, or FTP according to the credentials supplied.
- Port: use the panel’s value. Port 22 is a normal SFTP default, but a Pterodactyl installation may show 2022 or another administrator-selected port.
- Username and password: use the SFTP/SSH account for SFTP. A regular FTP account cannot authenticate to SFTP, according to cPanel’s SFTP documentation.
- Private key, if required: some SSH accounts disable passwords and require a key file instead.
Keep the dashboard open while testing. A single wrong field can produce the same “connection failed” message as a firewall problem.
How to connect with FileZilla using SFTP
FileZilla is a cross-platform graphical client. The labels below refer to its Site Manager; equivalent fields exist in WinSCP and Cyberduck.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Install a client from its official distribution channel. Install FileZilla, WinSCP, or Cyberduck on the computer that will hold your local backups. Keep the application updated.
- Open Site Manager. In FileZilla, choose File → Site Manager → New site. Saving a site profile prevents repeated typing, but protect the computer because a saved password can grant server access.
- Select the protocol. Set Protocol to SFTP – SSH File Transfer Protocol. Do not choose ordinary FTP merely because the account is called an “FTP account”; the host must provide an SSH/SFTP login.
- Enter the host and port. Put the dashboard’s host in Host and its SSH/SFTP port in Port. Leave the port at 22 only when the provider explicitly uses the normal SSH port.
- Enter authentication details. Choose the login type required by the host, then enter the SFTP username and password or select the supplied private-key file. Do not paste a panel API key into a password field unless the host documents that behavior.
- Connect and inspect the host-key prompt. The first SFTP connection may display an SSH host key. Check that the host name and fingerprint match information supplied by the administrator before accepting and storing the key. A changed key later can indicate a server rebuild, a changed address, or a man-in-the-middle attack; verify it instead of blindly accepting it.
- Confirm the remote directory. The remote pane may open at your home directory, a container directory, or a panel-specific path. Navigate to the directory that contains the server files before transferring anything.
- Transfer a harmless test file. Upload a small text file to a permitted temporary folder, then download it again. This confirms that both directions work before you replace a world or configuration.
- Move the required files. Drag files or folders between panes, or right-click and choose Upload or Download. Watch the queue for failed items; a green completion message for one file does not prove that every queued file succeeded.
- Close the session when finished. Disconnect from the server, then restart the game server only if the changed file requires it. Read the server log and test the change in-game.
Connecting when the host offers FTP or FTPS instead
Use the same client workflow, but match the host’s protocol and encryption requirement precisely.
- In Site Manager, choose FTP – File Transfer Protocol for plain FTP or the host’s explicit/implicit FTPS setting for TLS-protected FTP.
- Enter the supplied host, username, password, and port. Explicit FTPS commonly begins on port 21; implicit FTPS commonly uses 990, but the provider’s value takes precedence.
- Set the transfer mode to passive unless the administrator specifically requires active mode. Passive mode lets the client initiate both connections and generally works better through home routers.
- Connect, verify that the client reports TLS protection for FTPS, and confirm that the remote directory contains the expected server files.
Never assume that an account labeled “secure FTP” means SFTP. Ask whether the service is SFTP (SSH) or FTPS (FTP with TLS); the port and troubleshooting steps differ.
Where game-server files usually live
Paths vary by game, container image, operating system, and panel. A game-server guide’s example container layout uses /home/container/ as the working directory:
| Path or item | Typical contents | Use caution when |
|---|---|---|
/home/container/ |
Server’s main working directory in the example layout | Uploading files intended for a subfolder; the server may ignore files placed at the root. |
server.properties |
Core settings for a server that uses this filename | Changing ports, world names, difficulty, or authentication settings; malformed values can prevent startup. |
plugins/ |
Plugin binaries and their configuration folders | Installing a plugin built for a different game or server version. |
mods/ |
Mod files and, depending on the game, mod configuration | Mixing client-only and server-compatible files. |
world/ |
World or save data in the example layout | Overwriting it without a dated backup. |
logs/ |
Runtime logs and crash reports | Deleting logs before diagnosing a failure. |
backups/ |
Panel- or script-created backup archives | Assuming this folder is an off-server backup; it may be on the same storage volume. |
If you cannot find a folder, check the panel’s startup command, working-directory setting, or documentation for the game image. Do not create a second folder with a similar name until you know which path the server actually reads.
A safe file-management workflow
1. Stop or schedule around writes
For a live world or database, stop the server through the panel before copying or replacing files unless the game documents a safe live-backup method. A running process may write half of a file while the client is downloading it, producing a backup that cannot be restored.
2. Make a dated backup
Download the world, database, configuration, and plugin/mod directories that matter. Keep a local copy on a separate external USB SSD or hard drive for important backups. Include the game version, server version, and date in the local folder name.
3. Preserve names and extensions
Many servers discover files by exact name and extension. Do not let a text editor silently append .txt, and do not rename a world directory unless the configuration points to the new name. Preserve capitalization on case-sensitive hosts.
4. Upload to the expected directory
Upload a new plugin to the game’s plugin directory, a mod to its mod directory, and a configuration beside the file that loads it. If the host supplies a container path such as /home/container/, treat it as the root shown by the panel rather than assuming it is the root of the entire operating system.
5. Handle permissions conservatively
Use the existing file’s permissions as a reference. Do not make every file executable or world-writable to “fix” an upload; that can create security problems and still leave the server unable to read the file. Ask the host which owner and permission model the service expects.
6. Restart only when needed and verify
Restart after a configuration, plugin, mod, or binary change when the game requires it. Read the startup log for parse errors, missing dependencies, or permission failures, then test the specific feature in-game. Keep the backup until the change has survived a restart.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting connection and file problems
“Connection refused” or an immediate timeout
- Recheck the host and port copied from the dashboard. A game port is not necessarily the SFTP/FTP port.
- Confirm that the server or container is running and that remote file access is enabled.
- Verify that your account is allowed to use the selected protocol. FTP credentials do not work for SFTP.
- Test from another network only if the host permits it; a local firewall, VPN, or school/work network may block the port.
Login fails even though the password is correct
Switching protocols changes the authentication system. Confirm the username belongs to SSH/SFTP rather than an FTP-only account, check capitalization, and remove accidental spaces copied from the dashboard. If a private key is required, select the correct key and ensure its passphrase is available. Reset credentials in the panel instead of repeatedly guessing.
Login succeeds, but the directory listing hangs
This is characteristic of FTP’s second data connection. In FileZilla, open Edit → Settings → FTP → Passive and select passive mode. Ask the host which passive port range is open. cPanel documents 49152–65534 as the default range for its Pure-FTPd and ProFTPD configurations, but administrators can change it and must allow the chosen range through the firewall. Active mode asks the server to open the data connection, which NAT and firewalls often block.
Files appear to upload, but the game cannot see them
- Check the remote path; you may be in a home directory rather than the server’s working directory.
- Confirm the exact filename, extension, and capitalization.
- Check that the file belongs to the correct game version and server type.
- Restart if the game reads files only at startup, then inspect the log for a parse or dependency error.
“Permission denied” during upload, rename, or delete
Your account may be restricted to a particular directory, or the file may be owned by a different service user. Do not work around this by changing broad permissions. Use the panel’s file manager or ask the host to adjust ownership, grant the required directory permission, or perform the operation for you.
Best Value
- Used Book in Good Condition
A transfer stops partway through
Check the queue for the first failed item, not just the final status. Retry that item, confirm free disk space, and avoid closing the client while a queue is active. For a large world, transfer an archive when the host supports it, then extract it with the panel or shell; this reduces the number of individual connections and preserves the directory tree.
The host-key warning changes
Do not delete the old key and accept the new one automatically. Verify the new fingerprint with the provider or administrator. A legitimate rebuild or IP change can replace a key, but an unexpected change deserves investigation before you send credentials.
The server will not start after an upload
Stop trying random edits. Restore the dated backup, start the server, and compare the log from the failed and restored starts. Reapply one change at a time, checking syntax and version compatibility after each change.
Using the client efficiently
Queue large jobs
Queue a complete backup rather than dragging hundreds of files one by one. Wait for the queue to finish and review failed transfers before disconnecting. Keep the original remote files until the local copy opens or extracts successfully.
Edit locally, then replace deliberately
Download a configuration, edit it in a text editor that preserves plain text and line endings, and upload it as a new temporary filename first when the server permits. Compare the new and old versions, then replace the original only after confirming the change.
Show hidden files only when necessary
Some clients hide dot-prefixed files by default. Enable “show hidden files” when a game stores settings in such a directory, but avoid deleting unfamiliar files merely because they are not visible in the normal view.
Use bookmarks and separate profiles
Save a bookmark for the server’s working directory and a distinct profile for each server. Label profiles with the environment, such as staging or production, so a drag-and-drop operation does not target the wrong machine.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Security practices for game-server transfers
- Prefer SFTP, or FTPS when SFTP is unavailable. Plain FTP exposes credentials and transferred files to anyone able to observe the connection.
- Use a unique account with only the directory access required for the task. Do not share a full administrative password in chat.
- Protect saved client passwords and private keys with your operating system’s account security and disk encryption.
- Verify the SSH host key on first connection and whenever it changes.
- Keep local backups disconnected or on separate storage when they are not needed for an active restore.
- Remove temporary archives and old credentials from shared computers.
A quick protocol decision
- SSH/SFTP credentials supplied: use SFTP and the supplied SSH port, normally 22 but possibly a custom value such as 2022.
- Only FTP with TLS supplied: use FTPS, select passive mode, and use the provider’s explicit or implicit port.
- Only unencrypted FTP supplied: use it only when the network is trusted and no secure option can be enabled; ask the host whether SFTP or FTPS can be added.
- Unsure which account or port applies: stop and consult the hosting dashboard or administrator rather than cycling through protocols.
Bottom line
An FTP client is the file-management program on your computer; it is not the game server itself. For routine game-server administration, connect with SFTP whenever SSH access is available, verify the host key, work in the correct remote directory, and back up worlds and configurations before replacing them. Use FTPS when that is the host’s encrypted option, configure passive mode for FTP-family connections, and treat plain FTP as a last resort because it provides no encryption.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
