Turning an Old Android Phone into a Home NAS with Termux
t is surprisingly common to have an old Android phone sitting unused in a drawer. While these devices are no longer suitable for daily use, they are still capable of running lightweight server workloads. With the right setup, they can be repurposed into a simple home NAS (Network Attached Storage) system.
In this article, we build a minimal and practical NAS using Termux as the runtime environment and File Browser as the web-based file management interface. The goal is not to replace a dedicated NAS device, but to demonstrate how existing hardware can be reused effectively with almost zero cost.
The foundation of this setup is Termux, an Android terminal environment that provides a Linux-like user space without requiring root access. It allows installation of common Unix tools, background processes, and lightweight services, making it suitable for turning Android into a small server. Compared to more invasive approaches such as rooting or custom ROM installation, Termux is significantly safer and easier to maintain, especially on older devices.
On top of this environment, we run File Browser, a single-binary web application that exposes a directory as a modern web file manager. It provides a clean interface for uploading, downloading, previewing, and organizing files directly from a browser. Unlike traditional file-sharing protocols, it does not require client-side mounting or additional software on other devices, which makes it particularly convenient for cross-platform usage.
Compared to alternatives such as SMB, FTP, or WebDAV, File Browser occupies a practical middle ground. SMB offers deep system integration but is difficult to configure reliably in a mobile environment. FTP is simple but lacks security and modern usability. WebDAV is more flexible but still requires additional client-side setup. File Browser avoids these issues by providing a self-contained web interface that works on any device with a browser.
To begin the setup, Termux should be installed from a trusted source such as F-Droid, since the Play Store version is outdated. After installation, the environment is updated and basic utilities are installed.
pkg update && pkg upgrade -y
pkg install filebrowserOnce installed, we still need to configure the File Browser so that we can access it via the internal network IP address.
filebrowser config set --address 0.0.0.0
filebrowser config set --port 8080Then run
filebrowserThen, the File Browser will initialize and perform a series of operations. You need to remember the randomly generated password (the default username is admin).
$ filebrowser
2026/06/14 06:20:29 No config file used
2026/06/14 06:20:29 WARNING: filebrowser.db can't be found. Initialing in /data/data/com.termux/files/home/a/
2026/06/14 06:20:29 Using database: /data/data/com.termux/files/home/a/filebrowser.db
2026/06/14 06:20:29 Performing quick setup
2026/06/14 06:20:29 User 'admin' initialized with randomly generated password: THEPASSWORD
2026/06/14 06:20:29 Listening on [::]:8080
After starting the service, the interface becomes accessible from any device on the same network through the phone’s local IP address, typically via port 8080. The default credentials should be changed immediately after first login to avoid unauthorized access.
To improve usability, the service can be configured to start automatically when the device boots. This is optional but useful if the phone is intended to function as a continuously running home server. Termux provides a boot mechanism through the Termux add-on, which allows scripts to run at system startup.
For remote access outside the local network, tools such as Tailscale or ZeroTier can be used. These systems create secure virtual private networks between devices, eliminating the need for manual port forwarding. In practice, this allows the NAS to be accessed from anywhere as if it were on the same local network.
In real usage, this setup behaves more like a lightweight personal file hub than a full NAS system. It is suitable for synchronizing files between devices, storing media, sharing documents, or acting as a temporary download staging area. If the phone is kept plugged in and connected to stable Wi-Fi, it can run continuously with minimal intervention.
However, there are clear limitations. Android’s background process management may affect long-term stability, and storage reliability is limited by the phone’s internal flash memory. It also lacks advanced NAS features such as redundancy, snapshots, or RAID support. For heavy workloads, a dedicated NAS or server is still necessary.
Despite these limitations, the approach remains practical because it reuses existing hardware without additional cost or complexity. In many cases, simplicity is more valuable than performance, especially for personal or home use scenarios.
The result is not a professional storage system, but a functional and accessible private file server built from otherwise unused hardware.
Did you enjoy this article?
Recommend it — Standard Reader surfaces well-loved writing to more readers across the network.