Do you want to set up an FTP server but don't know where to start? FTP (File Transfer Protocol) is one of the oldest and most widely used methods for transferring files between computers. Whether you want to share files within your company, manage your website, or create a central storage location, your own FTP server offers the solution. In this step-by-step guide we explain how you can set up an FTP server on various operating systems.

Why would you set up an FTP server?

• Full control: you decide who has access and which permissions users get
• Large files: FTP is optimized for transferring large files, without the limits of email
• Automation: FTP transfers are easy to automate with scripts and cron jobs
• Website management: uploading files to your web hosting over FTP is the standard method
• Cost-efficient: your own server can be set up for free on existing hardware
• Multiple users: each user gets their own account with specific permissions and folders

Setting up an FTP server on Linux with vsftpd

Step 1: Install vsftpd

Open a terminal window and install vsftpd with your package manager:

# Ubuntu/Debian
sudo apt update
sudo apt install vsftpd

# CentOS/RHEL
sudo yum install vsftpd

Step 2: Adjust the configuration

The configuration file of vsftpd is located at /etc/vsftpd.conf. Adjust the following settings:

# Disable anonymous access
anonymous_enable=NO

# Allow local users
local_enable=YES

# Allow write access
write_enable=YES

# Restrict users to their home directory
chroot_local_user=YES

# Configure passive mode
pasv_enable=YES
pasv_min_port=40000
pasv_max_port=50000

Step 3: Create an FTP user

Create a specific user for FTP access:

sudo adduser ftpuser
sudo mkdir -p /home/ftpuser/ftp/files
sudo chown nobody:nogroup /home/ftpuser/ftp
sudo chown ftpuser:ftpuser /home/ftpuser/ftp/files

Step 4: Configure the firewall

Open the required ports in your firewall:

sudo ufw allow 20/tcp
sudo ufw allow 21/tcp
sudo ufw allow 40000:50000/tcp
sudo ufw reload

Step 5: Start and test the service

Start the vsftpd service and test the connection:

sudo systemctl start vsftpd
sudo systemctl enable vsftpd
sudo systemctl status vsftpd

Setting up an FTP server on Windows with FileZilla Server

Step 1: Download and install

Download FileZilla Server from the official website (filezilla-project.org). Run the installer and follow the wizard. Choose the default settings unless you have specific requirements.

Step 2: Configure the server

After the installation, the configuration panel opens automatically. Here you set which port the server listens on (default port 21) and configure passive mode with a port range.

Step 3: Add users

Go to Server > Configure > Users and add users. For each user you set:

1. Username and password: choose a strong password
2. Folders and permissions: assign folders and set read and write permissions
3. Speed limits: optionally limit upload and download speeds

Step 4: Configure Windows Firewall

Create an exception in Windows Firewall for FileZilla Server. Go to Windows Firewall > Advanced settings > Inbound rules and add rules for port 21 and your passive port range.

Securing your FTP server

Measure	Description	Priority
FTPS (FTP over TLS)	Encrypts the connection with an SSL certificate	High
Use SFTP	FTP over SSH, full encryption	High
Strong passwords	At least 12 characters with special characters	High
IP whitelisting	Allow only known IP addresses	Medium
Install Fail2ban	Block IP addresses after failed login attempts	Medium
Change the port	Use a different port than the standard 21	Low

Configuring FTPS on vsftpd

To enable FTPS on your vsftpd server, you need an SSL certificate. Add these lines to your configuration:

# Enable SSL/TLS
ssl_enable=YES
rsa_cert_file=/etc/ssl/certs/vsftpd.pem
rsa_private_key_file=/etc/ssl/private/vsftpd.key
allow_anon_ssl=NO
force_local_data_ssl=YES
force_local_logins_ssl=YES
ssl_tlsv1=YES
ssl_sslv2=NO
ssl_sslv3=NO

SFTP as a safer alternative to FTP

Benefits of SFTP compared to FTP:

• Built-in encryption: all data is automatically encrypted over SSH
• One port: uses only port 22, simpler for firewalls
• Key authentication: support for SSH keys alongside passwords
• No extra software: works on any server with SSH access

FTP clients: connecting to your server

Client	Platform	Price	Notes
FileZilla Client	Windows, Mac, Linux	Free	Most popular FTP client, supports SFTP
WinSCP	Windows	Free	Excellent for SFTP, scripting support
Cyberduck	Windows, Mac	Free (donation)	Also supports cloud storage
Transmit	Mac	Paid	Premium Mac client with a nice interface
Termius	All platforms	Freemium	Combines SSH and SFTP in one app

Common problems when setting up

Cannot connect

Check whether the firewall has port 21 (or your custom port) open. Also check whether the FTP service is actually running with systemctl status vsftpd.

Passive mode does not work

Passive mode requires a range of extra ports to be open in your firewall (for example 40000-50000). Configure these ports both in the server configuration and in the firewall.

Write permissions are missing

If you can download files but not upload, check the folder permissions on the server and whether write_enable is enabled in the configuration.

Connection drops

This can indicate a timeout setting that is set too low. Increase the idle_session_timeout and data_connection_timeout values in your configuration.

FTP server for website management

Typical FTP settings from a hosting provider:

• Server: ftp.yourdomain.com or the IP address of the server
• Port: 21 for FTP, 22 for SFTP, or 990 for FTPS
• Username: your hosting username or a special FTP account
• Password: the accompanying password
• Protocol: preferably choose SFTP or FTPS for a secure connection

Frequently asked questions about setting up an FTP server

Is FTP still safe enough to use?

Standard FTP sends data unencrypted and is therefore not safe. Always use FTPS or SFTP for encrypted transfer. With the right security measures, the protocol is still usable and reliable.

Which ports does FTP use?

FTP uses port 21 by default for the control connection and port 20 for active data connections. In passive mode, higher ports are used (configurable, usually 40000-50000).

Can I run an FTP server on my home network?

Yes, but you need to set up port forwarding on your router to make the server reachable from outside. Also make sure you have a static IP address or use a dynamic DNS service.

What is the difference between FTP, FTPS, and SFTP?

FTP is the basic protocol without encryption. FTPS adds TLS/SSL encryption to FTP. SFTP is a completely different protocol that works over SSH and is encrypted by default. SFTP is generally the best and most secure choice.

Alternatives to FTP in modern environments

For website management, many modern hosting platforms offer Git-based deployment, which lets you deploy files through version control instead of manual FTP uploads. Nevertheless, it remains useful to know how to set up an FTP server, because the protocol is still widely supported and is the most practical solution for many scenarios.

Setting up an FTP server is easier than you might think. With vsftpd on Linux or FileZilla Server on Windows, you have a working server within an hour. The most important thing is that you don't neglect security: use FTPS or SFTP, set strong passwords, and limit access to trusted IP addresses.

Whether you want to share files with colleagues, manage your website, or build an automated backup solution, your own FTP server gives you the control and flexibility you need. Start setting one up today and discover the possibilities.

Setting up an FTP server is a skill every web administrator should master. Whether you choose vsftpd on Linux, FileZilla Server on Windows, or a cloud-based solution, the process is comparable everywhere. Above all, invest time in security, because a poorly secured FTP server is an open door for hackers.

Do you have questions about setting up your server or are you running into problems? Always check the log files of your FTP server first. On Linux you find these in /var/log/vsftpd.log. These logs give you detailed information about login attempts, errors, and connection problems that help you solve problems. With patience and the right knowledge you will have a reliable and secure FTP server running in a short time.

Setting up an FTP server: security and access control

Use SFTP instead of FTP

Standard FTP sends all data, including passwords, as plain text. Always use SFTP (SSH File Transfer Protocol), which encrypts all communication. SFTP runs over SSH (port 22) and requires no extra configuration if SSH is already installed. It offers the same functionality as FTP but with full encryption. In most modern hosting environments, SFTP is available by default and unencrypted FTP is actively discouraged or blocked.

User management and permissions

Limit FTP access to only the users who actually need it. Create a separate FTP account with its own home directory for each user or project. Use chroot to restrict users to their own folder so they have no access to other parts of the file system. Set file permissions correctly so users can only read and write in the folders intended for them.

Security checklist for FTP

Measure	Priority	Protection against
Use SFTP	Critical	Password interception
Set up chroot	High	Unauthorized access
Strong passwords	High	Brute-force attacks
IP restriction	Medium	Unknown connections
Configure Fail2ban	Medium	Repeated login attempts
Enable logging	Medium	Undetected misuse

Setting up an FTP server: performance and maintenance

Optimize transfer speed

The transfer speed of your FTP server depends on multiple factors. Configure the maximum bandwidth per user to prevent a single user from consuming all available bandwidth. Set the maximum number of simultaneous connections to a value that fits your server resources. For large files, FTP resume offers the ability to resume interrupted transfers instead of starting over.

Log analysis and monitoring

Regularly analyze the FTP logs to detect unusual activity. Watch for failed login attempts, suspicious IP addresses, unusual download patterns, and access attempts outside office hours. Set up automatic alerts for critical events. A good monitoring system helps you detect security incidents early and prevent them from escalating into serious problems.

Also read our article about securing your website for additional security measures that protect your FTP server and website.

Setting up an FTP server: frequently asked questions and alternatives

Is FTP still relevant in 2026?

Although FTP is one of the oldest internet protocols, it is still widely used for file transfer with web hosting. The secure variant SFTP is the standard with modern hosting providers. For many users, SFTP is still the most direct way to manage website files. Alternatives such as Git-based deployment are becoming increasingly popular with development teams, but for ad-hoc file management, SFTP remains a reliable choice.

Alternatives to FTP

There are various modern alternatives to traditional FTP file management. The built-in file management in your hosting panel (DirectAdmin or cPanel) offers a web-based interface for simple file operations. Git deployment through platforms such as GitHub or GitLab automates the publishing of code changes. SCP and rsync offer command-line file transfer with better performance for large numbers of files. WebDAV offers an HTTP-based alternative that is natively supported by many operating systems.

Frequently asked questions

• Which FTP client is best? FileZilla is the most popular free FTP client for Windows, Mac, and Linux. WinSCP is an excellent alternative for Windows with native SFTP support.
• What is the difference between FTP, SFTP, and FTPS? FTP is unencrypted, SFTP uses SSH encryption over port 22, and FTPS adds SSL/TLS encryption to the FTP protocol. SFTP is the recommended choice.
• How many simultaneous connections can my server handle? This depends on your server configuration. By default, most servers support 5 to 10 simultaneous connections per user. More connections increase the transfer speed but put more load on the server.
• How do I solve a timeout error? Check your firewall settings, verify the server and port details, try passive mode, and increase the timeout setting in your FTP client.

Setting up an FTP server: summary and best practices

The three golden rules for FTP

Rule one: always use SFTP instead of unencrypted FTP to protect your data and passwords from interception. Rule two: limit access rights to the minimum needed through chroot and specific user accounts. Rule three: monitor the server logs regularly for suspicious activity and set up automatic blocking on repeated failed login attempts.

Maintenance and long-term management

A well-maintained FTP server requires regular attention. Update the FTP server software immediately when security patches become available. Check the user accounts monthly and deactivate accounts that are no longer needed. Analyze the server log files weekly for unusual patterns that could indicate security incidents. Periodically test the performance of the server by transferring large files and measuring the speed. Make regular backups of the server configuration so you can recover quickly if there are problems.

Setting up an FTP server: alternatives and more modern protocols

Securing and maintaining the FTP server

After setting up your FTP server, continuous security and maintenance are indispensable. Limit access to specific IP addresses where possible and use strong passwords that are rotated regularly. Set bandwidth limits per user to prevent misuse and protect your server resources. Monitor the server logs for suspicious activity such as repeated failed login attempts or unusual file transfers. Keep your FTP server software up to date with the latest security patches.

With the right configuration and security measures, an FTP server is a reliable and efficient method for exchanging files. Choose the protocol that fits your security requirements and invest in regular maintenance to guarantee a stable and secure file server.