New format
FTP: what it is and how to work with site files
FTP (File Transfer Protocol) is a way to copy files between your computer and the site server: upload a theme, download a backup, fix permissions, reach places the CMS admin can’t.
Below: why you need a client, how to connect, typical jobs, and security. FileZilla and hosting-panel UIs change — use current Help. For passwords prefer SFTP or FTPS over open FTP.
Why you need an FTP client
The client syncs your PC with folders on the server: upload, download, rename, delete, change permissions.
Typical jobs: upload static files, fix a white-screen WP site, pull a copy of `wp-content`, remove malware after a breach (after a backup), rename a plugin install folder.
Not every edit should go over FTP: content and media in the CMS are safer via built-in tools when they work.
What people usually do:
- upload/download files and folders
- change permissions (chmod)
- rename and delete
- access when the admin is down.
How to connect
You need a host (domain or IP / technical address), port (21 for FTP, often 22 for SFTP — confirm with the host), login and password or a key.
Create the site in the client’s site manager; save settings without syncing the password to a cloud vault on someone else’s laptop.
After login, left is local files, right is the server (classic FileZilla layout). Transfer by drag-and-drop or transfer buttons. Panel labels may change — the idea stays.
FileZilla and alternatives
FileZilla is often praised for cross-platform support, a site manager, resume, and logs. It’s a handy start — not the industry’s only standard.
Download the client from the official source. Third-party “builds with an accelerator” sometimes bundle adware.
On Windows many pick WinSCP; on macOS — Cyberduck / Transmit. Cursor/VS Code and some hosting panels have their own file access.
Benefits of a good client:
- resume after a drop
- a file queue
- an error log
- working across several folders
- SFTP/FTPS support.
Security and practice
Prefer SFTP/FTPS. Turn off anonymous FTP if you don’t need it.
Don’t put password-bearing backups in a public `httpdocs` without protection. After installing a plugin/theme, remove or lock leftover installers.
Before mass-replacing theme files — backup. Live edits with no copy are a common downtime cause.
Key takeaways
FTP/SFTP is access to site files from your computer.
A client is for transfer, permissions, and emergency access — it doesn’t replace the admin for content.
An encrypted channel and care with passwords beat “convenient” open FTP.
FAQ
Is FTP required if I have WordPress?
Not always: much is done in the admin and the host’s file manager. FTP/SFTP matters when admin is down, you edit code/config, or move large folders.
Why is SFTP better than FTP?
SFTP runs over SSH with encryption. Plain FTP may send password and data in clear text — risky on untrusted networks.
Where do I get host, login, and password?
In the host’s email/panel: FTP/SFTP access. Sometimes a separate FTP account with limited rights is safer than root.
Is FileZilla the only client?
No. It’s popular and cross-platform, but there’s also WinSCP, Cyberduck, and built-in managers in IDEs/hosting panels.
Can I edit wp-config over FTP?
Yes, technically. Backup first; a config typo takes the site down. Don’t paste DB passwords into chats.
What is chmod / permissions?
Access rights for files and folders on the server. Too open — a security hole; too tight — the site can’t write cache/uploads.
Should I store the password in the client?
Carefully: on a shared PC, better not. Use a password manager and a separate FTP user with minimal rights.
What if a large upload fails mid-way?
Many clients support resume. Verify integrity after; for backups an archive via the hosting panel is sometimes safer.
Need SFTP access without risking live files on open FTP?
We’ll set a proper client path, backups, and permissions — for emergencies, not everyday content edits.
Discuss the task
