How To Find Running Songs In Your Own Playlist

Measure your comfortable running cadence, then check the BPM of songs you already like. At 160 steps per minute, try 160 BPM with one step per beat or 80 BPM with two steps per beat. Keep the songs whose pulse is easy to follow without changing your planned rhythm.

An energetic song can still feel awkward under your feet. Starting with your own playlist gives you a smaller question to answer: which of these songs fits this run?

What are you matching: BPM or running cadence?

Running cadence is the number of steps you take per minute, counting both feet. Garmin's running dynamics manual uses that combined count. SPM means steps per minute; music BPM means beats per minute. Here, BPM refers to the song, rather than your heart rate.

If you count 80 footfalls in 30 seconds, your cadence is 80 × 2 = 160 SPM. That gives you a number to search around. It doesn't tell you which song you'll enjoy, or set a target every runner needs to reach.

Cadence and running speed are separate measurements. Our pace, cadence and step-length guide explains how steps per minute and distance per step combine to produce a pace. A song's BPM alone cannot tell you your mile time.

Build your playlist in five steps

1. Pick songs you already want to hear. Start with a small batch from your favorites. Keep track of the artist and recording version: a live performance or remix may have a different tempo from the studio track.
2. Measure the rhythm of this run. Once you're settled at a comfortable pace, count every landing from both feet for 30 seconds and multiply by two. If you use a watch, check that its cadence field counts both feet and look at a steady section of the run.
3. Check each song's BPM. Use a tempo analyzer to get candidates. You can also tap along to a clear section, count the beats over 30 seconds and multiply by two; repeat the count if you're unsure which pulse you heard.
4. Choose how your steps meet the beat. Try songs close to your measured SPM for one step per beat, then songs close to half that BPM for two steps per beat. The 160 SPM example here is arithmetic, so use your own measurement rather than chasing 160 or 180.
5. Listen first, then try the candidates on a run. Before exercising, check that you can hear a steady pulse. During the run, keep your comfortable rhythm; if you keep rushing or waiting for a beat, pick another track.

A few usable songs are enough to start. After the run, note which tracks felt easy to follow and which you kept wanting to skip. Those notes are more useful than sorting your entire library in one sitting.

Can an 80 BPM song work for a 160 SPM run?

Yes, if you take two steps per beat. One foot lands on the beat and the other lands halfway to the next beat. The next beat falls under the first foot again.

In the second row, the song plays at its original speed. You're following a subdivision between its beats. Taking one step every two beats would be a different calculation and would not produce 160 SPM from an 80 BPM song.

Tempo estimates can also use different pulse levels. Apple's BPM Counter documentation includes controls to halve or double its tempo reading and explains that a clear percussive signal is easier to analyze. That describes Apple's tool, not a promise that every analyzer or GagaRun has those same controls.

If one reading says 80 and another says 160, listen for the pulse they counted before deciding one is wrong. A free-time introduction, a quiet passage or a tempo change may also make one BPM label a poor description of the whole track.

Use a tool when your favorites list is long

For runners using Apple Music on an iPhone, GagaRun can help with the analysis step. Its official App Store listing describes importing favorite songs, BPM analysis and a target cadence you select. Start with a playlist you listen to often, then check the candidates against the beat-to-step relationship you want.

The main Apple Music version needs a separate Apple Music subscription for playback, as the GagaRun FAQ explains. Some GagaRun features also need its own subscription. If your playlist comes from another service, check the import methods your installed version supports and whether the matched recordings are available in Apple Music.

Treat an analysis result as a starting point. An imported song may still lack a BPM result, and a number can need checking. Songs you love but can't comfortably follow can stay in your everyday playlist.

What if the BPM fits but the song feels wrong?

Check the exact recording first, then listen to a clear section. A strong melody doesn't always give you a pulse you can easily follow. If the introduction wanders or the tempo changes later, you may prefer to use that track as background music rather than a step cue.

If few songs survive the check, keep that short list and add to it over time. Try the slower, two-steps-per-beat candidates before abandoning a favorite genre. An empty result means this batch didn't supply the rhythm you wanted; it doesn't require you to change the run.

Frequently asked questions

Can I run to slow songs?

You can try two steps per beat. For example, 80 BPM can accompany 160 SPM if one footfall falls on each beat and the other between beats. Listen for a clear pulse rather than choosing by genre alone.

Do I need a 180 BPM running playlist?

Use your measured cadence for the run you're planning. A 180 BPM track suggests 180 SPM only when you choose one step per beat; that number is not a requirement for every runner. You can also listen to music without deliberately stepping to it.

What should I do when a song has two different BPM results?

Check whether the readings differ by a factor of two, then count the pulse you actually hear. Confirm the recording version and try another steady section. Choose the reading and step pattern you can follow comfortably instead of treating the first number as final.