Fastfetch 2.70.0 Overhauls Disk Reporting, Removes QuickJS Scripting

Fastfetch, the lightweight system information tool that runs across Linux, macOS, Windows, Android, and several BSD variants, released version 2.70.0 on October 14 with changes substantial enough to break existing configurations. Anyone running the tool with custom settings should review their setup before upgrading, because the update restructures how the software reports disk space, handles command output, and processes shell information.

The most visible change affects disk reporting. The custom format field {size-available} has been removed entirely. The {size-free} field now behaves differently depending on the disk.useAvailable setting—it reports whichever metric that option selects, rather than always showing the file system's free space as it did before. For users working with raw byte counts, the tool now provides {bytes-used} and {bytes-total}. JSON output loses bytes.available and bytes.used; users can calculate used space by subtracting free from total.

On Windows systems, the changes address a real problem. Volumes with per-user quotas—particularly network shares—were reporting incorrect totals and wrapped-around used space figures because the total was quota-limited while the free space was not. Starting with Windows 10 build 17763, fastfetch now reports the whole volume's capacity and free space by default. Users who want to preserve the old behavior, seeing only space available to the current user including quota limits, can set disk.useAvailable to true. The LocalIP flags have also shifted: they now describe the interface itself, such as IEEE80211 or SOFTWARE_LOOPBACK, and interfaces without a unicast address no longer appear in the output.

The Command and Shell modules received their own overhaul. The Command option useStdErr is gone, replaced by useOutput, which accepts "stdout", "stderr", or "both". The default is now "both", meaning commands that write to standard error will have that output captured—previously it was discarded. The Shell module now reads the shell from /etc/passwd instead of relying on the $SHELL environment variable, which can diverge from the login shell if the user changed shells after the session started.

QuickJS scripting, which was deprecated in version 2.69.0, has been removed entirely. Anyone using QuickJS scripts will need to migrate them to Lua. On Linux systems, the dependencies libpulse and libddcutil are no longer used, so package managers should remove them from their fastfetch packages.

Android users gain five new capabilities in this release: sound detection, display detection over binder, battery temperature reporting with remaining time, charger type identification, and media detection with app display names. Media detection requires fastfetch to run with app UID permissions and needs the Notification access permission granted.

The update represents a shift in how fastfetch handles edge cases and user preferences, particularly around quota-limited storage and stderr handling. For most users, the changes will be transparent. For those with custom configurations, especially around disk reporting on Windows or command output capture, the upgrade requires attention before deployment.