← All posts

Gear & apps

Strava is eating your mobile data. Here's how to stop it.

By Paul Rudy · Everett, WA · November 4, 2026

If you record your runs, walks or rides with Strava on an Android phone, take a quick look at your data usage today. Since an app update in late October 2026, a lot of people are reporting that Strava is using far more mobile data than it ever did. We are talking gigabytes for a single workout, and some folks are paying real money in overage charges.

This one is for everyday runners and riders, so no tech background needed. Here is what people are seeing, what Strava has said so far, and a few phone settings you can try right now.

As far as the reports I found show, this is an Android problem. I have not seen solid reports of the same thing on iPhone, so I am not claiming it affects iPhone.

What people are reporting

The complaints showed up in Google Play reviews of the Strava app starting around October 22. A few of them, in the reviewers' own words:

"I am out $40 so far because of data overages."

Mike Golebiowski, Google Play review, October 31, 2026

"an hour's run would use 10 or so MB of data. Since the upgrade, it's now using 3GB"

Douglas Couperthwaite, Google Play review, October 31, 2026

"drained several gigs of data from my family's data pool, costing me $20"

Nathan Truitt, Google Play review, October 29, 2026

These three quotes come from a review collection log made on November 4, 2026 from Strava's Google Play listing (one and two star reviews since early October). Play loads reviews dynamically, so I can't link straight to each one.

It isn't just a handful of people. App review tracker Unstar counted 41 negative Google Play reviews about data use between October 22 and 28, most written from app version 486.9, and found none like it in the months before. One reviewer they quote put it simply:

"Data Hog! Out of nowhere the app used 700mb of mobile data during a 15 minute bike ride."

Google Play review, quoted by Unstar

John Desmond, who writes the Running in Cork blog, checked his own phone: workouts in early October used about 3 to 10 MB, a session on October 22 used 2.18 GB, and a ride on November 1 still used about 1.2 GB. Reviews on Strava's newer 487.11 version, collected by RiseWatch, show people still hitting it on November 3.

For context, Strava's own help page on recording says recording normally uses no data unless you view maps or use Live Segments or Beacon, and syncing is typically about 1 MB for two hours. So gigabytes is way out of line.

Has Strava said anything?

Not publicly, as far as I can find. I looked at Strava's help center, its community forum and news coverage, and found no announcement, acknowledgment or fix for this issue. Strava's October 27 "What's New" post covers new features but says nothing about data use. Unstar notes Strava didn't reply to any of the 41 reviews. One commenter on the Running in Cork post says Strava told them it is working on the bug, but I couldn't confirm that anywhere official. If Strava posts a fix, I'll update this page.

What to try

Menu names differ a little between phone brands and Android versions, so if a step doesn't match your screen exactly, look for something with a similar name. Search in the Settings app helps a lot here.

  1. Check how much Strava has used. In Settings, look under Network & internet (or Connections on some phones) for app data usage. Many Android phones also let you open Settings, then Apps, then Strava, and see its mobile data use. This tells you if you are affected at all.
  2. Turn off Strava's mobile data while you record. This is the workaround reviewers share most. GPS does not need mobile data, so Strava can still track your route. Some phones have a per-app switch to block mobile data completely (on Samsung, look in the app's mobile data settings for allowed networks). Turn it back on at the end, or wait until you are on Wi-Fi, so the activity uploads. Strava says activities saved offline upload automatically once you reconnect.
  3. Turn off background data for Strava. Open Settings, then Apps, then Strava, then the Mobile data & Wi-Fi section, and turn off Background data. One reviewer says the update switched background data on for them. Heads up: at least one person says the heavy use came while the app was open, so this alone may not be enough.
  4. Try Data Saver. Android's Data Saver (Settings, Network & internet, Data Saver on Pixel) keeps most apps off mobile data in the background. Google notes that the app you are actively using can still use data, so this is a backup, not the main fix.
  5. Set a data warning. Most Android phones let you set a mobile data warning or limit in your network settings, as Android's own guide describes. It is a good safety net while this gets sorted out.
  6. Be careful with battery settings. Android lets you set an app's battery use to restricted, which can cut its background activity. I wouldn't do that for Strava while you record, though, because it can interrupt GPS tracking. If you change it, test it on a short walk first.
Nobody has confirmed whether these steps actually fix the drain. Treat them as a practical workaround while Strava sorts it out, and keep an eye on your data usage after your next workout.

A tip for long rides and runs

For long days out, plan to need as little signal as possible. Download offline maps before you leave, and use Wi-Fi where you can for syncing, browsing routes and updating the app. On Strava, subscribers can save routes for offline use (open Maps, pick a route, tap Save with Download for offline use on), and anyone can record without service, per Strava's offline help page. If you're not a subscriber, other map apps can download areas offline too.

Related free tools

While you're planning that long day, a free tool I built might help:

Sources

Seeing this on your phone, or found a setting that fixed it? Find me on YouTube and let me know.

Ride safe,
Paul