SWOLF
Combining Time and Stroke Count as a Rough Swimming Efficiency Indicator
SWOLF is one of the most commonly displayed swimming efficiency metrics on watches and training platforms.
The name combines:
SWIM + GOLF
The idea is similar to golf scoring:
lower is generally better.
SWOLF combines two things from a pool length:
time
and:
stroke count
In plain terms:
SWOLF adds the time for a length, in seconds, to the number of strokes taken in that length
For example:
Length time:
20 seconds
Stroke Count:
18
SWOLF:
20 + 18 = 38
The metric is intended to provide a quick indication of how efficiently a swimmer covers a pool length.
But SWOLF is only a rough efficiency indicator.
A lower score does not automatically mean better swimming, and SWOLF values should not be compared blindly across different swimmers, pool lengths, strokes, or speeds.
In simple terms:
Its value comes from tracking your own performance under similar conditions over time.
What Is SWOLF?
SWOLF is a calculated swimming metric that combines:
how long it takes to complete a pool length
with:
how many strokes are used to complete that length.
The basic formula is:
SWOLF adds the time for a length, in seconds, to the number of strokes taken in that length
Suppose you swim 25 metres in:
22 seconds
using:
17 strokes
Your SWOLF is:
22 + 17 = 39
If you later swim the same length in:
20 seconds
using:
17 strokes
your SWOLF becomes:
37
You are now swimming faster with the same number of strokes.
That usually represents a meaningful improvement.
Why SWOLF Exists
Swimming efficiency is difficult to summarize with one simple number.
Pace alone tells you:
how fast you swam
but not how many strokes were required.
Stroke Count tells you:
how many strokes you used
but not how quickly you travelled.
SWOLF attempts to combine both.
This gives it an intuitive purpose:
That makes SWOLF useful as a compact summary of swimming mechanics and performance.
A Simple Example
Consider two 25 m lengths.
Length A
Time:
- 20 seconds
- Stroke Count:
- 20
- SWOLF:
- 40
Length B
Time:
- 22 seconds
- Stroke Count:
- 16
- SWOLF:
- 38
Length B has the lower SWOLF.
But it is also slower.
This immediately shows one of the key limitations of SWOLF:
The second swimmer reduced stroke count enough to lower the score, but did so while taking longer to complete the length.
Whether that is actually better depends on the purpose of the swim.
The Basic Trade-Off
SWOLF combines two variables that often trade off against each other:
speed
and:
stroke economy
A swimmer can lower SWOLF by:
- swimming faster with the same stroke count
- using fewer strokes at the same speed
- improving both
But SWOLF can also fall for less useful reasons, such as:
- gliding excessively
- slowing down substantially
- pushing farther off the wall
- staying underwater longer
That is why SWOLF must always be interpreted with context.
SWOLF and Pace
Pace should always be considered alongside SWOLF.
For example:
Earlier
Pace:
- 1:45 /100 m
- SWOLF:
- 42
Later
Pace:
- 1:38 /100 m
- SWOLF:
- 40
This is a strong pattern.
The swimmer is:
faster
and:
using a lower SWOLF score.
That suggests improved performance and potentially improved efficiency.
Now consider:
Earlier
Pace:
- 1:45 /100 m
- SWOLF:
- 42
Later
Pace:
- 2:00 /100 m
- SWOLF:
- 38
SWOLF improved numerically, but pace became much slower.
The athlete may simply be gliding more.
The lower score is not automatically better.
SWOLF and Stroke Count
Stroke Count directly influences SWOLF.
If length time stays constant, fewer strokes produce a lower score.
For example:
Time:
20 seconds
20 strokes
SWOLF:
- 40
18 strokes
SWOLF:
- 38
16 strokes
SWOLF:
- 36
This appears straightforward.
But fewer strokes are only useful if they still produce appropriate speed.
Stroke Count should not be minimized at the expense of performance.
SWOLF and Stroke Rate
Stroke Rate provides additional context.
Suppose:
Session A
Pace:
- 1:40 /100 m
- Stroke Count:
- 18 per length
- Stroke Rate:
- 58 spm
- SWOLF:
- 38
Session B
Pace:
- 1:40 /100 m
- Stroke Count:
- 18 per length
- Stroke Rate:
- 64 spm
- SWOLF:
- 38
The SWOLF score is identical.
But the movement rhythm is different.
This shows that SWOLF does not fully describe stroke mechanics.
Two lengths can produce the same score through different movement strategies.
SWOLF and Distance Per Stroke
SWOLF is indirectly related to Distance Per Stroke because lower Stroke Count usually means more distance is covered per recorded stroke.
However, this relationship is complicated by:
- push-offs
- underwater distance
- turns
- pool length
For example, a swimmer may reduce Stroke Count simply by staying underwater longer after the wall.
SWOLF would improve even if surface swimming technique did not change.
Therefore, SWOLF should not be treated as a pure measurement of Distance Per Stroke.
Why Lower SWOLF Is Usually Better Only Under Similar Conditions
SWOLF is most useful when comparing:
the same swimmer
in:
the same pool length
using:
the same stroke
at:
a similar pace or workout intensity
under:
similar conditions.
For example:
Week 1
25 m freestyle:
- 21 sec + 19 strokes = SWOLF 40
Week 6
25 m freestyle:
- 20 sec + 18 strokes = SWOLF 38
This is a meaningful comparison.
The swimmer is both faster and using fewer strokes.
Why You Should Not Compare SWOLF Between Swimmers
Suppose:
Swimmer A
SWOLF:
- 35
Swimmer B
SWOLF:
- 42
You cannot conclude that Swimmer A is more efficient.
Why?
The swimmers may differ in:
- height
- arm length
- stroke type
- speed
- push-off distance
- technique
- pool length
- underwater ability
A taller swimmer may naturally use fewer strokes.
Another swimmer may have a longer underwater phase.
SWOLF is therefore primarily useful as a personal longitudinal metric, not a ranking system between athletes.
Pool Length Has a Major Effect
SWOLF depends directly on the distance of each pool length.
A score from a:
25 m pool
should not be compared directly with a score from a:
50 m pool.
Why?
Because a 50 m length takes longer and requires more strokes.
The resulting SWOLF will naturally be much higher.
For example:
25 m pool
Time:
- 20 seconds
- Stroke Count:
- 18
- SWOLF:
- 38
50 m pool
Time:
- 42 seconds
- Stroke Count:
- 40
- SWOLF:
- 82
The larger number does not mean efficiency became dramatically worse.
The measurement distance changed.
Metres vs. Yards
The same issue applies to:
25 m
and:
25 yd
pools.
A yard is shorter than a metre.
Therefore, SWOLF values from short-course yards and short-course metres are not directly equivalent.
Always compare SWOLF only when the pool format is known.
Stroke Type Matters
SWOLF should generally be compared within the same stroke.
Freestyle, backstroke, breaststroke and butterfly have different:
- stroke mechanics
- stroke frequency
- propulsion
- pace
- stroke counts
A SWOLF of:
40 freestyle
cannot be interpreted the same way as:
40 breaststroke.
The numbers may be identical.
The movement patterns are not.
Push-Offs Can Lower SWOLF
Strong wall push-offs can reduce both:
- length time
- surface Stroke Count
That can significantly improve SWOLF.
For example:
Short push-off
Time:
- 21 sec
- Stroke Count:
- 19
- SWOLF:
- 40
Stronger push-off
Time:
- 19 sec
- Stroke Count:
- 16
- SWOLF:
- 35
That looks like a major efficiency improvement.
But part of the improvement may come from:
better wall and underwater performance
rather than better surface stroke mechanics.
That is still valuable in pool swimming, but the source of the improvement should be understood.
Underwater Distance Matters
Suppose one swimmer travels:
8 m underwater
after each push-off.
Another surfaces after:
4 m.
The first swimmer has fewer metres of surface swimming to complete.
Their Stroke Count is likely lower.
Their SWOLF may also be lower.
This is one reason SWOLF should not be treated as a direct measurement of stroke efficiency.
It reflects the entire length, including wall and underwater behaviour.
SWOLF and Gliding
One of the easiest ways to artificially lower SWOLF is to glide excessively.
For example:
Normal swimming
Time:
- 20 sec
- Stroke Count:
- 18
- SWOLF:
- 38
Excessive glide
Time:
- 24 sec
- Stroke Count:
- 13
- SWOLF:
- 37
The SWOLF score improved.
The swimmer became four seconds slower.
This is why chasing the lowest possible SWOLF can lead to poor technique decisions.
The goal is not:
minimize SWOLF at all costs.
The goal is to improve the relationship between:
speed and stroke economy.
SWOLF and Fatigue
SWOLF can be useful for detecting fatigue.
Suppose a swimmer completes repeated 100 m efforts.
Early
Length time:
- 20 sec
- Stroke Count:
- 18
- SWOLF:
- 38
Later
Length time:
- 22 sec
- Stroke Count:
- 21
- SWOLF:
- 43
- The swimmer is:
- slower
- taking more strokes
- producing a higher SWOLF
This pattern can indicate deteriorating efficiency with fatigue.
Possible causes include:
- poorer body position
- weaker catch
- shorter effective stroke
- increased drag
- muscular fatigue
SWOLF and Durability
Durability describes how well performance characteristics are maintained as exercise continues.
SWOLF can provide a simple view of this.
For example:
First 500 m
Average SWOLF:
- 38
Final 500 m
Average SWOLF:
- 39
The swimmer maintains a relatively stable relationship between speed and stroke count.
Another swimmer might show:
38 → 46
over the same session.
If pace also deteriorates, this may indicate substantial mechanical fatigue.
SWOLF can therefore provide one piece of the durability picture.
SWOLF and Heart Rate
Heart rate adds physiological context.
Suppose:
Earlier
Pace:
- 1:40 /100 m
- SWOLF:
- 40
- Heart Rate:
- 158 bpm
Later in training
Pace:
- 1:40 /100 m
- SWOLF:
- 38
- Heart Rate:
- 148 bpm
- Under comparable conditions, the athlete is:
- maintaining the same pace
- using a lower SWOLF
- showing lower cardiovascular demand
That is a much stronger efficiency signal than SWOLF alone.
SWOLF and Training Intensity
SWOLF naturally changes with intensity.
During easy swimming, the swimmer may take fewer strokes but move more slowly.
At threshold or sprint pace, Stroke Rate and Stroke Count may rise.
This means SWOLF at:
easy pace
should not automatically be compared with SWOLF at:
sprint pace.
The athlete may produce a higher SWOLF during faster swimming even though race performance is substantially better.
Intensity context matters.
SWOLF During Sprinting
Sprint swimming often involves:
- higher Stroke Rate
- more strokes per length
- much faster time
For example:
Easy
Time:
- 22 sec
- Stroke Count:
- 16
- SWOLF:
- 38
Sprint
Time:
- 15 sec
- Stroke Count:
- 22
- SWOLF:
- 37
The SWOLF values are similar.
But the sprint performance is dramatically faster.
This shows why SWOLF should not be used as a replacement for pace.
SWOLF During Long-Distance Swimming
Long-distance swimmers may use SWOLF to monitor whether efficiency deteriorates over time.
For example:
Early
SWOLF 39
Middle
SWOLF 40
Late
SWOLF 44
- The gradual rise may reflect:
- slower length times
- increased Stroke Count
- or both
This can provide a simple summary of fatigue-related change.
But the underlying components should still be inspected.
The Two Ways SWOLF Can Get Worse
A higher SWOLF can occur because:
1. You Swim Slower
Time increases while Stroke Count stays similar.
2. You Take More Strokes
Stroke Count increases while time stays similar.
Or both may occur together.
These two patterns have different implications.
A useful platform should ideally show:
SWOLF + Pace + Stroke Count
rather than the score alone.
The Two Ways SWOLF Can Improve
Similarly, SWOLF can improve because:
1. You Swim Faster
Time decreases.
2. You Use Fewer Strokes
Stroke Count decreases.
The strongest improvement is when:
time decreases
and:
Stroke Count also decreases or remains stable.
That suggests the swimmer is producing better performance without needing additional strokes.
SWOLF and Technique
SWOLF can provide a useful warning that technique may be changing.
Suppose pace is stable but SWOLF rises:
Early
1:40 /100 m
- SWOLF:
- 38
Late
1:40 /100 m
- SWOLF:
- 44
If pace is unchanged, the increase must largely be coming from higher Stroke Count or changes in length timing.
The athlete is needing more mechanical actions to produce the same performance.
That may indicate technique deterioration.
But SWOLF cannot identify the specific technical cause.
SWOLF Cannot Diagnose Technique
A high SWOLF cannot tell you:
- whether your catch is poor
- whether your hips are dropping
- whether your kick is ineffective
- whether your head position is wrong
- whether your breathing is disrupting alignment
It tells you only that the relationship between time and Stroke Count changed.
Detailed technique diagnosis requires:
- video
- coaching observation
- additional stroke metrics
SWOLF is an indicator, not a diagnosis.
SWOLF During Drills
Technique drills can make SWOLF misleading.
For example:
- catch-up drill
- single-arm drill
- sculling
- fist drill
- kick-only work
These deliberately change:
- Stroke Count
- speed
- rhythm
A SWOLF score from a drill should not be compared with ordinary freestyle swimming.
Platforms should ideally exclude or separately classify drill segments.
SWOLF and Training Equipment
Equipment can also change SWOLF.
Examples include:
paddles
fins
pull buoy
Paddles may increase distance travelled per stroke.
Fins may significantly increase speed.
A pull buoy may improve body position.
These can lower SWOLF without representing the same kind of improvement as unaided swimming.
Comparisons should therefore use similar equipment conditions.
Average SWOLF
Many devices report:
Average SWOLF
for the entire session.
This can be useful as a quick summary.
But pool workouts often contain:
- warm-up
- drills
- easy swimming
- threshold work
- sprints
- cool-down
Each may have different pace and Stroke Count.
A single average can therefore hide important variation.
SWOLF is often more useful at the:
length
interval
or:
set
level.
SWOLF Variability
The consistency of SWOLF can also be informative.
Suppose a swimmer performs:
10 × 100 m
and records:
39, 39, 40, 39, 40, 40, 41, 40, 41, 41
The score remains relatively stable.
Another swimmer might record:
38, 40, 44, 39, 47, 45...
Greater variability may reflect:
- pacing inconsistency
- technique variation
- fatigue
- different turns
- data-quality problems
Again, the cause requires context.
SWOLF and Data Quality
SWOLF depends on two underlying measurements:
length time
and:
Stroke Count
If either is wrong, SWOLF is wrong.
Potential problems include:
- missed lengths
- false turns
- incorrect pool length
- missed strokes
- extra detected strokes
- drill misclassification
This means SWOLF should only be trusted when the underlying pool data is credible.
Incorrect Pool Length Can Break SWOLF Interpretation
Suppose the swimmer is actually in a:
25 m pool
but the watch is configured for:
50 m.
Distance, pace, and segment structure may become incorrect.
SWOLF values may also become difficult or meaningless to interpret.
Correct pool configuration is therefore fundamental.
Is SWOLF a Physiological Metric?
No.
SWOLF is primarily a performance-mechanics metric.
It does not directly measure:
- oxygen consumption
- heart rate
- lactate
- fatigue
- energy expenditure
- Load
It combines:
time together with stroke count
and uses that combination as a rough proxy for swimming efficiency.
The word rough is important.
Is SWOLF the Same as Swimming Efficiency?
No.
True efficiency is more complex.
A swimmer's efficiency involves the relationship between:
physiological energy input
and:
mechanical/performance output.
SWOLF does not measure energy input.
Therefore, it cannot directly measure physiological efficiency.
It is better described as:
a simple proxy for the relationship between swimming speed and stroke economy.
Why SWOLF Is Still Useful
Despite its limitations, SWOLF has several advantages.
It is:
- easy to calculate
- easy to understand
- available from ordinary pool-watch data
- useful for personal tracking
- sensitive to changes in pace and Stroke Count
When used correctly, it can help answer:
Am I maintaining speed with fewer strokes?
Am I becoming slower and taking more strokes as I fatigue?
Is my swimming becoming more economical under similar conditions?
That makes it a useful supporting metric.
Tracking SWOLF Over Time
SWOLF becomes particularly useful when tracked longitudinally.
For example:
January
Pace:
- 1:45 /100 m
- SWOLF:
- 43
April
Pace:
- 1:40 /100 m
- SWOLF:
- 40
August
Pace:
- 1:36 /100 m
- SWOLF:
- 38
The athlete is progressively swimming faster while the score decreases.
That is a meaningful trend.
Now compare:
January
1:45 /100 m — SWOLF 43
August
2:00 /100 m — SWOLF 37
The score improved, but swimming performance deteriorated.
That is why pace must remain visible.
The Best Use of SWOLF
The strongest use case is:
Same swimmer
Same stroke
Same pool length
Similar intensity
Similar equipment
Similar push-off behaviour
Then compare:
SWOLF over time.
Under these conditions, a lower score alongside equal or faster pace can provide useful evidence that swimming mechanics have improved.
What Is a Good SWOLF?
There is no universal good SWOLF.
A score of:
35
is not automatically better than:
45
unless the context is the same.
SWOLF depends on:
- pool length
- swimmer height
- stroke type
- pace
- underwater distance
- turns
- technique
- equipment
Therefore, population comparisons have limited value.
The useful question is:
“Is my SWOLF improving while I maintain or improve pace under comparable conditions?”
Lower SWOLF Is Not the Goal
This is the most important practical principle.
The objective of swimming is not to minimize SWOLF.
If it were, you could simply:
- push very far underwater
- glide excessively
- slow down
- take as few strokes as possible
and potentially produce a lower score.
That does not necessarily make you a better swimmer.
The goal is:
better performance at an appropriate physiological and mechanical cost.
SWOLF is simply one tool for evaluating that relationship.
How Should Swimmers Use SWOLF?
SWOLF becomes useful when it helps answer specific questions.
For example:
Am I swimming faster without increasing Stroke Count?
Can I maintain the same pace using fewer strokes?
Does my SWOLF deteriorate late in long sets?
Does fatigue cause both pace and Stroke Count to worsen?
Is my SWOLF improving under the same conditions over time?
Does equipment change the relationship between pace and Stroke Count?
Am I artificially lowering SWOLF by gliding more slowly?
Do my turns and push-offs influence the score?
These questions make SWOLF useful rather than simply treating it as another number.
The Most Important Relationships
SWOLF becomes much more informative when combined with other swimming metrics.
SWOLF + Pace
Shows whether a lower score is accompanied by better performance.
SWOLF + Stroke Count
Shows how much of the score comes from stroke economy.
SWOLF + Stroke Rate
Adds information about movement rhythm.
SWOLF + Distance Per Stroke
Provides further mechanical context.
SWOLF + Heart Rate
Adds physiological cost.
SWOLF + Duration
Shows whether efficiency deteriorates as fatigue accumulates.
SWOLF + Pool Length
Ensures comparisons are meaningful.
SWOLF + Stroke Type
Ensures like-for-like mechanical comparison.
SWOLF + Historical Data
Shows whether the swimmer's performance-efficiency relationship is improving over time.
No single relationship tells the whole story.
The Most Important Thing to Remember
SWOLF is:
time together with stroke count
It is designed as a simple indicator of swimming efficiency.
But it is not a direct measurement of physiological efficiency.
A lower SWOLF can be a positive sign when:
pace stays the same or gets faster
while:
Stroke Count stays the same or falls.
It can be misleading when:
the swimmer slows down dramatically just to take fewer strokes.
The score also depends heavily on:
pool length + stroke type + push-off + underwater distance + equipment + swimming speed.
For this reason:
Conclusion
SWOLF combines time per pool length and Stroke Count into a single score intended to provide a rough indication of swimming efficiency.
The calculation is simple:
SWOLF adds the time for a length, in seconds, to the number of strokes taken in that length
Lower values can indicate improvement—but only when interpreted correctly.
A swimmer who becomes faster while maintaining or reducing Stroke Count will usually produce a lower SWOLF, and that can be a useful sign of improved performance.
But a swimmer can also lower SWOLF by:
- slowing down
- gliding excessively
- pushing farther underwater
without necessarily becoming more effective.
This is why SWOLF should never replace:
pace
Stroke Count
Stroke Rate
or:
physiological context.
The most useful question is not:
“How low is my SWOLF?”
It is:
“Am I producing equal or greater swimming speed with fewer strokes and an appropriate physiological cost, and can I maintain that relationship as the swim gets longer?”
That is where SWOLF becomes more than a score—and becomes a useful rough indicator of how effectively you move through the water.
KEY TAKEAWAY
- SWOLF tries to reward swimming that is both fast and economical in stroke count.
- A lower SWOLF does not always mean better performance.
- SWOLF is only a rough efficiency indicator.
- SWOLF is best used to compare yourself with yourself under similar conditions.