Running Shoes

How to Track Mileage on Running Shoes: My Simple System

To track mileage on running shoes, I give every pair its own record, assign each run to the pair I wore, and review the total alongside grip, fit, structure, and how the shoe feels. A mileage alert tells me to inspect a shoe; it does not tell me that every shoe expires at the same distance.

I have tested 63 pairs over 12 years of running, and the tracking method that survives a busy training week is deliberately small. It takes a few seconds after a run and a few minutes once a month. Here is the exact system I use, including the messy cases that make a neat app total misleading.

The four-step system I actually use

  1. Create one entry for each physical pair. I include a unique name, first-use date, starting mileage, and intended role.
  2. Assign the shoe after every run. I check the gear field when I save or review the activity, especially when I rotate pairs.
  3. Record meaningful use outside the running log. Long walks, hikes, and untracked runs get a note or an estimated adjustment.
  4. Inspect the shoe when mileage prompts me. I look at outsole traction, upper hold, midsole behavior, and damage before deciding whether to keep, reassign, or retire it.

I do not need a perfect account of every step. I need a trustworthy history that helps me make the next decision.

Set up a record for each pair

My first rule is that a shoe model is not a shoe pair. If I own two pairs of the same trainer, each gets a separate record. I use a short label such as “Tempo Blue — Mar 2026” and “Tempo Black — Jul 2026.” The purchase month or a discreet mark inside the tongue prevents me from confusing them later.

I add the model and version, size, width, first-run date, starting mileage, and role. A new pair starts at zero. A used pair starts with an estimated range if I cannot document its history. I write “about 80–100 miles” rather than inventing “93.6 miles.”

Before the first run, I photograph the heel and forefoot outsole, both sidewalls, and the upper. Those baseline photos make later comparisons far clearer than memory. If one side wears unusually quickly, I use the same camera angles and my guide to uneven shoe wear to decide what to inspect next; a wear pattern alone does not diagnose my stride.

I also name the shoe’s job: daily easy runs, faster workouts, racing, trail, or walking. That role matters because “still usable” is too vague. A shoe may lose wet-road grip before it loses enough cushioning to bother me on dry, short runs.

The fields worth keeping

FieldWhat I recordWhy it earns a place
Pair IDUnique label for this physical pairSeparates identical models
First use and starting milesDate plus zero or an honest estimateMakes the total interpretable
Assigned activityDate, distance, and shoe wornBuilds the running total
Other useWalking, hiking, gym, or untracked runReveals what GPS misses
Surface and roleRoad, treadmill, trail; easy or raceAdds context to wear
Condition noteGrip, upper, platform, damage, comfortTurns a number into a decision
Next actionKeep, inspect sooner, reassign, or retirePreserves the reason for the change

I can keep this in a training app, watch platform, spreadsheet, or paper notebook. I choose one place as the source of truth. If I also use a second app, I treat it as a view of the data, not a second independent mileage total.

Add mileage immediately after a run

When I finish on the Atlantic City Boardwalk, assigning the pair is part of saving the run. I know which shoes are on my feet at that moment. Three days later, a row of similar easy runs can blur together.

If my platform lets me assign a default shoe, I review that setting whenever my running-shoe rotation changes. Defaults are useful for a runner who mostly wears one pair. During a rotation they can quietly put every run on yesterday’s shoe. I check the gear assignment before accepting the total.

For a run that uses two pairs, I split the distance. If I warm up for 2 miles in trainers, run 3 miles in spikes, and cool down for 1 mile in trainers, the trainers receive 3 miles and the spikes receive 3. Assigning the entire 6-mile session to both doubles the recorded wear. Separate activities or a manual note both work.

Treadmill runs count. I use the most reasonable recorded distance and note any large discrepancy between watch and treadmill rather than chasing false decimal accuracy. If a GPS run records a clear error, I correct the activity before I trust the shoe total.

When I forget a shoe assignment, I reconstruct it from the route, workout, photos, and pair I packed. If I still cannot identify the shoe, I mark the run unassigned. A visible gap is better than a confident but false entry.

Decide how to count walking and other use

Running mileage is often a lower bound on a shoe’s total use. A pair worn for airport travel, daily commuting, or long dog walks has experienced more loading and outsole contact than its running log shows. A trail pair also sees hiking days that may be rougher than some runs.

I set a rule based on the pair’s role. For running-only shoes, I ignore trivial steps between the door and the car. For shoes I wear on substantial walks, I add those walks if my activity log can assign gear; otherwise I enter a weekly estimate in my master record. I label an estimate as an estimate.

I never count the same outing twice. A walk already assigned to the shoe in an app does not get another spreadsheet adjustment. And I do not convert time on my feet to running miles with a universal formula. Time, terrain, load, and movement differ too much. I record the actual walk or hike distance when I have it, then add a condition note.

For a trail shoe, I also note technical rock, mud, long descents, and damage. Eight rocky miles can tell me more about a torn upper or worn lug than a simple lifetime total. My trail-shoe lifespan guide explains the terrain-specific checks I use.

Use a spreadsheet if your app leaves gaps

My simplest spreadsheet has one row per activity and a separate summary for each pair. The activity rows contain date, pair ID, distance, type of use, and a short note. The pair summary adds the starting estimate and all activity distances assigned to that ID.

Pair total = starting mileage + assigned running miles + logged non-running miles. I do not add an unlogged walking allowance on top of walks already captured by my app.

For example, if “Tempo Blue” began at zero, received 124 logged running miles, and was used for two 4-mile walks that were not in the app, my working total is 132 miles. If the walks are only estimates, I mark the total approximate. The number is a prompt to look at the pair, not a laboratory measurement of its remaining life.

I keep retired pairs in the sheet. The final mileage, role, and reason for retirement become useful buying history. Deleting the record throws away what I learned.

Let the number trigger an inspection

I have no universal replacement number. Different foams, outsoles, runners, surfaces, fit problems, and shoe roles make one cutoff unreliable. I set a reminder early enough that I will look at the pair before I am forced to make a rushed race-week decision. Then I move the next check based on what I find.

Here is my inspection order:

  1. Outsole and traction. I check the high-wear zones and test grip on the surfaces where I actually run. A smooth patch matters most when it removes grip I need.
  2. Upper and heel hold. I look for tearing, stretched material, heel slip, and pressure that has appeared as the shoe aged.
  3. Platform and structure. I inspect uneven collapse, separation, and a shoe that no longer sits or moves normally. Visible compression lines alone do not prove the foam is finished.
  4. On-run response. I compare the older pair with a familiar, newer shoe over similar easy routes. I note repeated changes in feel, not one bad run after poor sleep.

My guide to how long running shoes last goes deeper on the replacement decision. Here I use mileage primarily to know when to look and to understand what happened to a specific pair.

What I findMy next move
No meaningful change in fit, grip, or behaviorKeep using it; set the next check
Grip is weaker only in wet conditionsStop using it for wet routes; consider a dry-road role
Repeated discomfort appears with this pair, while comparable runs in another pair feel normalPause this pair and examine fit and condition; do not diagnose an injury from mileage
Outsole, upper, or structure fails for its intended useRetire it from that running role

If a shoe is no longer fit for running, I do not automatically make it an all-day walking shoe. I first check whether its grip and structure are adequate for the new job. My old-running-shoes guide covers sensible next uses and disposal.

My ten-minute monthly audit

Once a month, I compare the distance in my training log with the distance assigned across active shoes. They do not have to match exactly when I deliberately include walks or have an unassigned run, but every difference should have an explanation.

I scan for duplicate uploads, runs credited to the default pair during a rotation, and workouts credited in full to two pairs. I check shoes that have crossed an inspection reminder, photograph any material wear change, and date the next action. This takes less time than rebuilding half a season from memory.

I also look at the notes across retired pairs. If the same model repeatedly loses the grip I need, tears in the same location, or stops feeling secure well before another model on the same routes, that is a better purchasing signal than a generic mileage claim. Conversely, a lightly used shoe that never fit well is a fit lesson, not proof of poor durability.

If I am keeping a broader training record, I put the pair ID beside the workout in my running journal. That small cross-check helps me recover gear assignments after an app migration.

Frequently asked questions

Can I track mileage for two identical pairs?

Yes. I create two records and give them distinct names or discreet physical marks. A shared model name cannot tell me which physical pair took a run.

Should I count treadmill miles?

Yes. The shoe still flexes and loads with every stride. I log the best reasonable distance and keep the treadmill surface in the note because visible outsole wear may differ from road use.

What if I started tracking halfway through a shoe’s life?

I reconstruct a range from training history, purchase date, and known workouts, then label it estimated. I inspect the shoe more closely until I have a reliable record of its current condition. I do not invent an exact starting total.

Should walking miles count toward running-shoe mileage?

Meaningful walking use should appear somewhere in the record. I log walks when practical or add a clearly labeled estimate. For a pair reserved for running, I do not spend time counting incidental steps.

Does a shoe become unsafe at a particular mileage?

I do not use a universal cutoff. Mileage cannot by itself tell me the shoe’s grip, fit, structural condition, or how it behaves for a specific runner. I use it to schedule inspections and make the decision from the shoe’s actual job and condition.

My takeaway

Give each pair a unique identity, assign every run while you still remember it, account for substantial use your running app misses, and inspect the shoe when its history gives you a reason. That is enough to turn mileage from a vague replacement myth into a useful record of what your shoes actually did.

Ken — NextGait Founder

Written by Ken — 12 years of running, 12,500+ miles, 63 shoes tested, 36 races from 5Ks to a 50K ultra. I run 30–40 miles a week on the Atlantic City Boardwalk and review every shoe with real training miles, not one-run demos. More about me →

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top