FTPS Server

com.siarheikuchuk.ftpsserver
by Zapstore Catalog

Run a secure FTP server and share files on your local network, with no ads.

FTPS Server turns your phone or tablet into a secure FTP server for private file sharing. Share photos, videos, and documents with a computer on the same Wi-Fi, without uploading them to a cloud. You choose who can connect, which folder they can open, and whether they can only download files or also change them. **Share files on your network, not through a cloud** Files stay on your Android device. The other device connects to this FTP server over your own network, so a copy is not sitting on someone else's storage. - Move photos, videos, and documents from your phone to a PC, or from a PC onto your phone. - Keep personal and work files off third-party cloud storage. - Use it at home, in an office, or on a hotspot you control. The client has to be on the same network: the same Wi-Fi, or the same hotspot or USB tethering link. - Leave the server running with the screen off. A notification keeps transfers going. **Choose who can open which folder** Add a separate login for each person or device, and limit what that login can do. - Create a username and password for every connection. - Give each login its own folder. That login cannot browse the rest of the files on your device. - Allow full access, or a read-only login that can download files but cannot upload, rename, or delete. - Copy or share the address, port, and logins when the other device is ready to connect. **Encrypted transfer, not plain FTP** This is an FTPS server: explicit FTP over TLS (AUTH TLS). Plain FTP, with no encryption, is not used. The password and the files are encrypted while they cross the network. - A login is not sent in the clear. Transfers use FTP over TLS. - The first start creates a TLS certificate for you, so you can connect without extra setup. - If you already have a certificate, you can use that instead. - Compare the certificate fingerprint shown in the app with the one shown by your client, so you know you reached this device. - File names in your own language are preserved, including letters that are not in the English alphabet. **See what the server is doing** - The app shows the address and port to enter in the client. - Each login is listed with its folder and whether access is read-only or full. - A log shows connection activity when something fails and you need to see why. - You choose the port and how many clients can be connected at once. **Start the FTP server in four steps** 1. Add a user, with a username and a password. 2. Pick the folder that user is allowed to open. 3. Choose read-only or full access. 4. On the other device, open an FTPS client, turn on explicit TLS (AUTH TLS), and enter the address, port, and login. **Clients that can connect** Any client that supports explicit FTPS works. Examples: FileZilla and WinSCP on Windows, FileZilla on Linux, Cyberduck or FileZilla on Mac, and an FTPS client on another phone. **Typical uses** - Copy files between a phone and a laptop on the same Wi-Fi. - Open phone files from a desktop file manager. - Hand someone a read-only login when they should download files and nothing else. **What this FTP server is not** It does not upload your files to the developer or to a cloud service. It is also not a public file host. Use it on a network you trust, such as home or office Wi-Fi. FTPS Server is open source (CC0-1.0) and contains no ads.

First release: Nov 1, 2026, 2 total releases.

Most recent release: Nov 11, 2026.

Repo

Appears in 0 app stacks.

0 sats / 0 zaps received in the past year.

Sats Received

Underlying data available via MCP: app_zaps, app_releases.

Zap Count

Underlying data available via MCP: app_zaps, app_releases.

Releases

  • Nov 11, 2026 2026.11.13
    ## Changes - Console, Windows, Avalonia: the applications target .NET 11, and runtime async is enabled. Avalonia is 12.1.6. NLog.Extensions.Logging is 6.3.0. NLog stays 6.2.2. The third-party notices list those versions. - Library: the NuGet package targets .NET 10 and .NET 11. An application that stays on .NET 10 can keep using it. The .NET 11 build enables runtime async. - Android: Bouncy Castle PKIX 1.87 and Android Gradle Plugin 9.5.1. Kotlin 2.4.21 and Compose BOM 2026.09.00 are unchanged. The Android notice lists the APK libraries on their own. ## Bug Fixes - Library, Android: a directory listing sends each name as it is read. Before, LIST, NLST, and MLSD built the whole list and wrote nothing until that finished. On Android each file was a separate documents query, so a Camera folder of about 1400 files produced no bytes for 20 seconds and the client closed the data connection (`MLSD failed`, broken pipe). - Library: a Linux or macOS data connection can resume the control session again. Passing a cipher-suite policy made .NET turn the OpenSSL session cache off, `SSL_get0_session` is only a macro so the session could not be read, and the id length was read as 8 bytes so it came out empty. Schannel's TLS 1.2 resume keeps the master secret with an empty id, and that secret has to match. Schannel's TLS 1.3 resume replaces the id and then stops resuming, so a TLS 1.3 data connection is accepted as it is on Windows. A TLS 1.2 handshake that is not a resume is still refused. A suite that is not forward-secret AEAD is still rejected after the handshake. - Android: the control connection and every protected data connection now use one SSLEngine from the same SSLContext. Before, login used SSLSocket and upload used SSLEngine, so those two caches never shared a session id. A TLS 1.2 client such as FluentFTP on Windows 10 could list and download, and STOR was rejected. A missing close_notify is still rejected. - Console: a process with no console keeps running until it is stopped. Before, `Console.ReadKey` threw and the server shut down, so a test host or `wsl.exe` without a terminal could not keep it up.
    More…
    - Library: the control connection and its data connections now share one SslStreamCertificateContext. A new context per handshake keeps a separate session cache, so a TLS 1.2 data connection can fail to resume the login session. - Library: NUGet package version changes were incorrect.
  • Nov 1, 2026 2026.11.03
    ## Changes - Console, Windows, Avalonia: NLog 6.2.2, Avalonia 12.1.4, and MessageBox.Avalonia 12.1.0. The third-party notices list those versions. - Android: Compose BOM 2026.09.00, Kotlin 2.4.21, Android Gradle Plugin 9.5.0, and the libraries listed in the third-party notices. - Console: localized. - Windows, Avalonia, Android: the server log section starts collapsed. While it is collapsed the screen is not updated and only the last two lines are kept in memory. While it is open the screen shows the last 100 lines. Windows and Avalonia still write every line to the log file. ## Bug Fixes - Android: Fix lost access to chosen paths. - Library: an upload that closes TCP on a TLS record boundary without `close_notify` is rejected, and the partial file is removed. Before, that close looked like a normal end, the server answered `226 Transfer complete`, and the short file was kept. - Android: the same truncated upload is rejected, and the partial file is removed. Before, Conscrypt reported that TCP close as the end of the file and the server answered `226 Transfer complete`.