LFTP
LFTP is a versatile tool for moving files between your computer and a remote server.
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
59/100 Fair
- Maintained
- 71last commit 47 days ago
- Popular
- 621,307 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 64no serious findings, tests, OpenSSF Scorecard 3.3/10
Based on 4 of 5 factors.
- GitHub stars
- 1,307
- Open issues
- 268
- Last commit
- 2026-10-05
- Latest release
- v4.9.3
- License
- GPL-3.0
- Activity
- stale
Checked yesterday - source: GitHub (lavv17/lftp)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Use a config file for safe defaults Create a small LFTP config file at ~/.lftprc or ~/.lftp/rc before your first transfer, and keep it backed up. It can set passive mode (a way for FTP data connections to be started by your machine) and encrypted-FTP options (SSL/TLS), which can stop transfers from stalling behind home routers and help keep logins/data from being plain text. source
- Keep passwords out of scripts If you run LFTP from scripts or one-liners, let it ask for a password or use lftp -u user --env-password with an exported LFTP_PASSWORD environment variable. Avoid writing username,password directly in commands or scripts, because passwords can remain in shell history, logs, or visible process listings. source
- Run scheduled jobs from a file For backups that should run automatically, save your LFTP commands in a .lftp script and schedule it with cron (a built-in task scheduler) using the full path and a log redirect. Without the full path and logs, the job may fail silently because cron does not use your normal shell settings. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (6)
- AeroFTP - A modern, open-source file manager and client for FTP, SFTP, WebDAV, and S3, featuring an AI assistant, cloud sync, and military-grade encr…
- FileZilla - FileZilla is a cross-platform FTP, SFTP, and FTPS client for transferring and managing files on remote servers.
- Wget - Wget is a command-line utility for non-interactive downloading of files, directories, and entire websites over HTTP, HTTPS, and FTP.
- aria2 - Aria2 is a lightweight, multi-protocol, multi-source, cross-platform command-line download utility that retrieves files over HTTP/HTTPS, FT…
- cURL - cURL is a versatile tool used to send and receive information between your computer and a server via the internet.
- termscp - A feature rich terminal UI file transfer and explorer with support for SCP/SFTP/FTP/Kube/S3/WebDAV.
Checked 54 days ago - source: AlternativeTo
Common questions
How can I prevent LFTP transfers from stalling behind a home router?
Create a small LFTP config file at ~/.lftprc or ~/.lftp/rc before the first transfer. It can set passive mode and encrypted-FTP options, which can stop transfers stalling behind home routers and keep logins/data from being plain text.
How do I run LFTP from a script without leaving passwords in shell history or process listings?
Use lftp -u user --env-password with an exported LFTP_PASSWORD environment variable, or let LFTP ask for a password. Avoid writing the username and password directly in commands or scripts, because passwords can remain in shell history, logs, or visible process listings.
Why do scheduled LFTP backup jobs fail silently in cron?
Save your LFTP commands in a .lftp script and schedule it with cron using the full path and a log redirect. Without the full path and logs, the job may fail silently because cron does not use your normal shell settings.
Why does remote ls in LFTP appear outdated after file changes?
By default, LFTP caches directory listings, causing remote ls to lag behind file system changes. To fix this, run cache flush, or write set cache:enable no in your $HOME/.lftprc configuration file.
Answers sourced from context7.com, mcandre.gitbooks.io
Community
- LFTP Includes & Excludes - Help with order of operations? - Reddit (reddit)
- Secure, self-hosted FTP-server inside a single container - Reddit (reddit)
- Anyone using SeedSync for LFTP front end? : r/seedboxes - Reddit (reddit)
- Struggling to use Lftp : r/seedboxes - Reddit (reddit)
- LFTP Mirror Scripting : r/seedboxes - Reddit (reddit)
- backup - lftp mirror local directory to remote ftp server without ... (forum)
Collected 28 days ago - public community threads