Self-hosted service
robinrodricks/FluentFTP avatar
robinrodricks/FluentFTP

FluentFTP claims no dependencies and ships a crypto project

An FTP and FTPS client for .NET & .NET Standard, optimized for speed. Provides extensive FTP commands, File uploads/downloads, SSL/TLS connections, Automatic directory listing parsing, File hashing/checksums, File permissions/CHMOD, FTP proxies, FXP support, UTF-8 support, Async/await support, Powershell support and more. Written entirely in C#.

3,414 stars688 forksC#MIT

At a glance

What is it?
FluentFTP is a managed FTP and FTPS client for .NET written entirely in C#. Its README promises no external dependency while the repository carries a project named after a cryptography library, and its own releases on GitHub stopped in 2019 while commits continue.
Who is it for?
FluentFTP fits a .NET codebase that has to keep talking to FTP servers it does not control, including several of them, and that wants directory synchronisation, hash verification and throttling without writing any of it.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 9 days ago.
What is it written in?
Mainly C#, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • robinrodricks/FluentFTP3,414 ★ · +12
Star history
Repository2026-09-242026-11-14
robinrodricks/FluentFTP3.4k3.4k

12 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

No external dependency, next to a crypto project

The README states that the library is written entirely in C# with no external dependency, and that is the sentence most people stop at. The repository layout complicates it. Among the projects at the top level there is one named after a well known cryptography library for .NET, which is the shape a pluggable transport or provider takes rather than a hard dependency. Meanwhile the documented TLS story is built on .NET's own stream class, for both control and data connections, in explicit and implicit modes. So the practical reading is that the default path uses only the framework, and the cryptography project is an alternative for cases where the framework's own implementation will not do. What the README does not do is say which is which, so a reader has to look at the projects.

SFTP is declined in one sentence

The clearest boundary in the whole file is a single line in the protocol list: SFTP is not supported, because it is FTP over SSH, a completely different protocol, and the file names a different library to use for it. That is worth reading carefully, because SFTP is what many people mean when they say FTP, and a library that quietly did not implement it would be a trap. This one says so in the feature list rather than in a footnote. The supported set is FTP, FXP for server-to-server transfers, FTPS in its several forms including TLS 1.3 and client certificates, and proxies in front of FTPS. Everything in the file after that line is about the older protocol family.

Thirty server types, each parsed differently

Automatic detection of the server software and its capabilities is listed as a protocol feature, and the file management section lists the server families the directory listing parser understands: Unix, Windows and IIS, Azure, Pure-FTPd, ProFTPD, Vax, VMS, OpenVMS, Tandem, HP NonStop Guardian, IBM z/OS and OS/400, Windows CE and Serv-U, among others, with a claim of over thirty types and integration tests for all the major ones. It also carries the commands those servers need and each other does not. There is a Unix permission command, a PRET command, the ProFTPD extensions for creating and removing directories, and a deletion command specific to one commercial server, plus realm and directory navigation support for the IBM systems. And there is an escape hatch: a method for sending arbitrary server-specific commands.

Four attack classes are named outright

The security line is worth quoting for its specificity, because naming the failure modes is rarer than claiming to prevent them. It names FTP command injection, directory traversal attacks, encoding bypasses, and parser confusion attacks. Three of those four are about how the library and the server disagree about what a path or an encoded byte means, which is exactly where a client library that parses thirty server dialects earns its keep. Two more features sit in the same area. Transfers can be verified by hash, and a mismatch triggers a retry rather than a silent pass. And conditional transfers use rule based whitelists and blacklists, so a pipeline can state which names it will and will not take.

Passwords are left out of the trace

Command logging is built on the framework's own listener abstraction, and it can go to a trace or to a log file. The detail that matters is in the parenthesis: passwords are omitted. A client library that logs every command it sends is a liability in exactly the environments it is used in, and this one carves the credential out before the output is written. The same care shows up in the connection features: automatic negotiation that finds working connection settings, and automatic reconnection when a socket breaks or degrades, which for long lived transfer jobs is the difference between a resumable operation and a failed one.

Five algorithms for comparing two copies of a file

The file comparison feature takes a local file and a remote file and decides whether they differ, using a hash or checksum. The list of algorithms is explicit: MD5, CRC32, SHA-1, SHA-256 and SHA-512, which covers everything from a fast legacy checksum to the two hashes people usually mean when they say verify this download. Combined with the verify-and-retry behaviour, the pattern is coherent. Instead of trusting a size check or a transfer result, the library recomputes and compares, and retries when the two disagree. For a synchronisation job that moves thousands of files a night, that is the feature that decides whether the job is trustworthy, and it is the one most worth reading the documentation for.

Six proxy flavours and two data connection modes

The proxy support is enumerated rather than summarised: HTTP 1.1, SOCKS4, SOCKS4a, SOCKS5, a user-at-host form and one named after a commercial appliance vendor. That list is the difference between working inside a corporate network and not working at all, since each of those appears in a different environment. The data connection side is spelled out the same way, naming the four commands the library can use for passive and active modes. Combined with the explicit and implicit TLS options for both the control and the data channel, the file is essentially enumerating the ways an FTP conversation can be shaped, which is the right level of detail for a library whose job is to be shaped by whatever is on the other end.

Releases stop in 2019, commits do not

The release history has three entries and they end seven years ago: 16.0.18 in January 2017, 17.4.2 in June of that year, and 20.0.0 in February 2019. The jump from 17 to 20 also skips two majors, which suggests the numbering follows something other than a straight count. Against that, the last commit to the default branch is dated 2026-09-25, so the branch is moving without producing releases here. The package itself is distributed through a registry rather than through these releases, and the header links that package twice. Two files at the root support the reading: a separate readme written for the package listing, and a releases document distinct from the release tags. Meanwhile the test suite runs against local server containers checked into a Docker project in the same tree, and the root also carries an ahead-of-time compilation example, a PowerShell folder and separate example projects written in C# and in Visual Basic.

Editorial conclusion

FluentFTP fits a .NET codebase that has to keep talking to FTP servers it does not control, including several of them, and that wants directory synchronisation, hash verification and throttling without writing any of it. Check four things before you rely on it: that your servers are among the thirty types it claims, that the release you get is the one you expect, since the GitHub release history stops at 20.0.0 in 2019 while the default branch has moved since, that you are not expecting SFTP, which it declines on purpose, and which library you would use if you needed it, and that the dependency story matches your build, given the claim of no external dependency next to a cryptography project in the tree. Read the security section before exposing it to untrusted filenames.

Frequently asked questions

Is FluentFTP free to use?

Its README states that it is released under the permissive MIT licence, so it can be used in both proprietary and free or open source applications. The licence file at the repository root is the authoritative text.

Is FluentFTP an alternative to SSH.NET?

No. The README says SFTP is not supported, since it is FTP over SSH and a completely different protocol, and points to SSH.NET for that instead. FluentFTP covers FTP, FXP, FTPS with client certificates and proxies.

Which protocols does FluentFTP support?

FTP, FXP server-to-server transfers, FTPS including TLS 1.3, FTPS with client certificates and FTPS proxies. Both explicit and implicit SSL are supported on the control and data connections, using the framework's own stream class.

Which FTP servers does FluentFTP understand?

The README claims full support for over 30 server types with integration tests for all the major ones, naming Unix, Windows and IIS, Azure, Pure-FTPd, ProFTPD, Vax, VMS, OpenVMS, Tandem, HP NonStop Guardian, IBM z/OS and OS/400, Windows CE and Serv-U among them.

How does FluentFTP handle large or repeated transfers?

Uploads and downloads can be throttled with a configurable speed limit, directory transfers offer synchronisation modes, multi-file error handling is configurable between ignoring, aborting and throwing, and folder monitors watch server directories and raise events when files are added, changed or removed.

How does FluentFTP verify a transferred file?

It can compare a local file against a remote one by hash using MD5, CRC32, SHA-1, SHA-256 or SHA-512, and a verification step can retry the transfer when the hash does not match. Rule based whitelists and blacklisting can also restrict which files are transferred at all.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. robinrodricks/FluentFTP on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/robinrodricks-fluentftp.svg)](https://hysenlabs.com/projects/robinrodricks-fluentftp)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/robinrodricks-fluentftp.svg)](https://hysenlabs.com/projects/robinrodricks-fluentftp)

Was this useful?