FileZilla Site Manager Guide for Windows
Use FileZilla Site Manager on Windows to organize FTP, FTPS and SFTP sites, choose safer logon settings, set default folders and manage multiple servers.
What Site Manager is for
Site Manager stores repeat connection profiles so you do not have to retype a host, protocol, port and username every time. It is especially useful when the same Windows PC connects to multiple websites, staging servers, NAS devices or VPS systems.
Name sites by purpose, not just hostname
A practical naming scheme makes the list readable months later. Names such as Client A Production, Client A Staging and Backup SFTP are more useful than three entries with similar hostnames. Group related servers when you manage many connections.
Choose the correct protocol first
FTP, FTPS and SFTP are not interchangeable labels. SFTP is SSH File Transfer Protocol and typically uses an SSH server. FTPS is FTP protected with TLS. Match the Site Manager protocol to what the server administrator or hosting provider specifies, then enter the corresponding port.
Handle credentials carefully
Where possible, prefer interactive passwords, SSH keys or organization-approved credential storage over leaving sensitive shared passwords on a PC. If Windows has multiple users, remember that a connection profile can reveal infrastructure details even if it does not expose a password. Lock the Windows account and apply normal device security.
Set default local and remote folders
Advanced Site Manager settings can save time by opening the project directory on the PC and the matching document root on the server. This reduces accidental uploads to the wrong folder. Verify the remote path once before relying on it, especially when the server uses chroot or virtual directories.
Use bookmarks for subfolders
Bookmarks are useful when one server contains several frequently used paths. Instead of creating many almost identical server entries, keep one connection and bookmarks for logs, uploads, public files or release folders. This keeps authentication settings centralized.
Review old entries periodically
Delete obsolete servers, rename migrated hosts and update protocols when infrastructure changes. A tidy Site Manager reduces the chance of sending files to an old production machine. If a host key changes on SFTP, verify the change independently rather than treating the saved profile as proof that the new fingerprint is safe.