How to Use stats.fm (Beginner Guide)

After you connect Spotify, the app asks Spotify’s servers for the listening activity your account is allowed to share. It then builds dashboards: top artists and tracks, time ranges, listening time, and other breakdowns depending on your plan and app version. It does not replace the Spotify player—you still play music in Spotify; stats.fm reads the activity that Spotify records and presents it in its own UI.

Before you link accounts, install and sign in to Spotify on the same device with the profile you want to analyze. If you still need the client or want the MODDROID listing in one place, use this page: Spotify — MODDROID app page & download. Keeping Spotify updated reduces odd sign-in or token errors when stats.fm refreshes data.

Install the package from the highlighted download section at the top, grant normal Android permissions when asked (storage or notifications only if the build prompts you), and launch the app. On first launch you will usually see a short onboarding screen explaining that stats are derived from your Spotify account—continue until you reach the connection step.

Tap the option to link Spotify or log in with Spotify. Android will hand off to a browser tab or embedded web view where Spotify’s official login appears. Enter the same credentials you use in the Spotify app, review the permissions summary, and approve. This is the standard OAuth flow: stats.fm never stores your Spotify password; Spotify issues an access token so the app can request your listening history and related metadata within the scopes shown on the consent screen.

If login fails, check the date and time on your phone, update Spotify from the link in the previous section, disable VPNs temporarily, and retry—those three fix most “stuck on a blank page” cases.

Import Spotify data into stats.fm is not a manual file upload. After authorization, the app pulls history from Spotify’s API in the background. The first sync can take a while: large libraries and years of history mean more round trips, so expect anywhere from a few minutes to longer on a slow connection. Leave the phone online; do not force-stop the app mid-import.

Later, whenever you stream in Spotify, new plays appear in stats.fm after the next refresh cycle—open the app and pull to refresh if your build supports it, or simply revisit after you have listened for a bit. If numbers look empty at first, wait for the initial import to finish before judging the charts.

Most builds organize content into tabs or a home feed: overview (recent period summary), top tracks / artists, and listening time or similar. Explore time filters (week, month, year, all time) when you see them—this is how you compare a busy release week against your long-term taste. If the app offers goals or streaks, they are optional gamification on top of the same underlying Spotify data.

Use one Spotify account per stats.fm profile so streams are not split across duplicates. Private sessions in Spotify may exclude plays from some social features; check Spotify’s own docs for how private listening affects third-party stats. Keep both apps updated so API changes on Spotify’s side do not leave you on an old token format.