The old faithful of file transfer, still running on a remarkable number of hosts.

Live-tested Verified against a live server

What Mountit does with it

Mount

Read and write, in Finder

Offline cache

Metadata cache, read-ahead and write-back — the same volume stack as every other service

Encryption layer

Available on this connection: client-side, rclone-compatible crypt over the data before it leaves your Mac

Editions

Both. Either edition mounts it through File Provider, so it appears in Finder — and, on Standard, in the Files app on iPad and Vision Pro

The engineering ledger lists FTP / FTPS among the services run against a real server. Which of those two things it says is read out of docs/BACKEND-COVERAGE.md in the app repository when this site is built, not typed here — so the level above moves when the ledger does, and the build stops rather than leave the paragraph above it saying something else.

The conformance record

Blocked by a finding. A lane ran and 7 findings stand between this service and a clean record. They are the return on running the corpus, and they are published rather than filtered. Every service’s standing, side by side.

Being mounted once is the floor. The conformance harness runs the same corpus of assertions at every backend — must for the contract the volume layer relies on, should for a well-behaved server, and probe for observations that become capability data — and commits the verdicts as a file. These numbers are read out of that file.

A failure here is a finding about this protocol, not a broken test. They are published rather than filtered because a page that showed only the green ones would be worth nothing.

• pyftpdlib-ftp — 123 assertions. 7 assertions tagged must failed. 2 capabilities the backend claimed were contradicted by what the server actually did. On the harness's own rule — no must failure and no capability disproved — this lane does not by itself promote the service.

FTP / FTPS questions