Swim CSS & Pacing: Finding Your Threshold in the Pool

Critical Swim Speed (CSS) is the swimming equivalent of Functional Threshold Power on the bike or lactate threshold pace in running. It represents the fastest pace you can theoretically sustain indefinitely without accumulating lactate beyond your body's ability to clear it. In practical terms, CSS approximates the speed you could hold for a continuous 25-30 minute swim -- roughly equivalent to a 1500m race pace for most well-trained swimmers.

The beauty of CSS is its simplicity. You do not need a laboratory, a blood lactate analyzer, or expensive equipment. All you need is a pool, a pace clock, and two time trials: a 400m and a 200m. From those two data points, you can calculate your threshold pace and derive an entire set of training zones that take the guesswork out of every workout.

The Science Behind Critical Swim Speed

Origins: The Critical Power Concept

CSS is rooted in the critical power concept first formalized by Ettema in 1966 and later applied to swimming by Wakayoshi and colleagues in 1992. The underlying principle is elegant: for any exercise above a certain intensity, there is a finite amount of work you can do before exhaustion. That intensity boundary -- the critical velocity -- represents the highest rate of energy expenditure that can be sustained entirely by aerobic metabolism.

Below critical velocity, lactate production and clearance are in balance. You could, in theory, swim at this pace for a very long time. Above it, you are dipping into your anaerobic work capacity (sometimes called W', pronounced "W-prime"), a finite reserve of energy that depletes progressively. The harder you go above CSS, the faster that reserve drains.

The Two-Trial Protocol

The standard CSS test uses two maximal efforts at different distances. The most common and validated protocol is:

1. Warm up thoroughly -- at least 400m of easy swimming with drills and some build efforts.
2. Swim a 400m time trial -- maximum sustainable effort, as if racing a 400m event.
3. Rest 10-15 minutes -- enough to recover substantially but stay warm.
4. Swim a 200m time trial -- all-out effort over the shorter distance.

The CSS formula is:

CSS (m/s) = (D2 - D1) / (T2 - T1)

Where D2 = 400m, D1 = 200m, T2 = time for 400m (in seconds), T1 = time for 200m (in seconds).

In per-100m pace terms:

CSS pace (per 100m) = (T400 - T200) / 2

This simplified version works because the distance difference between 400m and 200m is exactly 200m, so dividing the time difference by 2 gives you the pace per 100m.

Why Two Distances Work

The logic relies on the assumption that your anaerobic work capacity (the energy above threshold) is roughly the same whether you swim 200m or 400m flat out. Both distances are short enough that you will tap into that anaerobic reserve. By subtracting one from the other, the anaerobic contribution cancels out, leaving you with the aerobic component -- your critical velocity.

Research by Dekerle et al. (2002) validated this approach, showing that CSS from the 200-400m protocol correlates strongly with maximal lactate steady state velocity measured in the lab. The test-retest reliability is excellent (r=0.97), meaning you get consistent results if you repeat the test under similar conditions.

CSS-Based Training Zones

Once you know your CSS pace, you can build a complete set of training zones. The following seven-zone system is widely used in competitive swimming programs:

Zone	Name	% of CSS	Purpose	RPE
Zone 1	Recovery	< 80% CSS	Active recovery, technique work	2-3
Zone 2	Aerobic Endurance	80-87% CSS	Base aerobic development, fat oxidation	3-4
Zone 3	Aerobic Threshold	88-95% CSS	Steady-state aerobic conditioning	5-6
Zone 4	Threshold	96-100% CSS	Lactate threshold development	7
Zone 5a	Overload	101-105% CSS	VO2max stimulation, threshold extension	8
Zone 5b	Max Aerobic	106-120% CSS	Maximum aerobic power, race-pace work	9
Zone 5c	Anaerobic	> 120% CSS	Anaerobic capacity, sprint power	10

Zones 1-3 comprise your aerobic base work -- the "easy" swimming that should make up the bulk of your training volume. Zone 4 is the bread-and-butter threshold training zone. Zones 5a through 5c are reserved for targeted high-intensity sets with appropriate recovery.

Worked Example: Calculating CSS and Training Zones

Meet Sarah, an age-group triathlete who wants to structure her swim training more effectively. She completes the CSS test protocol and records:

• 400m time trial: 6:00 (360 seconds)
• 200m time trial: 2:50 (170 seconds)

Step 1: Calculate CSS pace per 100m

CSS pace = (T400 - T200) / 2 CSS pace = (360 - 170) / 2 CSS pace = 190 / 2 CSS pace = 1:35 per 100m (95 seconds)

Step 2: Calculate CSS velocity

CSS = 200 / (360 - 170) = 200 / 190 = 1.053 m/s

Step 3: Derive all training zones

To convert percentage of CSS to pace, remember that a faster speed means a lower time per 100m, so the math inverts. If CSS = 1:35/100m, then 90% of CSS speed means the pace is 1:35 / 0.90 = 1:45/100m (slower).

Zone	% CSS Speed	Pace per 100m	Example Use
Zone 1 (Recovery)	< 80%	> 1:59	Warm-up, cool-down, recovery days
Zone 2 (Endurance)	80-87%	1:49 - 1:59	Main aerobic sets: 10x200m on 3:40
Zone 3 (Aerobic Threshold)	88-95%	1:40 - 1:48	Steady sets: 5x300m on 5:15
Zone 4 (Threshold)	96-100%	1:35 - 1:39	CSS sets: 8x100m on 1:55
Zone 5a (Overload)	101-105%	1:31 - 1:34	Race-prep: 6x100m on 2:00
Zone 5b (Max Aerobic)	106-120%	1:19 - 1:30	VO2max: 8x50m on 1:15
Zone 5c (Anaerobic)	> 120%	< 1:19	Sprint: 12x25m on :45

Step 4: Build a sample threshold workout

Here is a CSS-focused session Sarah might use:

• Warm-up: 400m easy choice (Zone 1), 4x50m drill/swim (Zone 2), 4x50m build to CSS pace
• Pre-set: 4x100m on 2:00, descending from Zone 2 to Zone 4 (1:50, 1:45, 1:40, 1:36)
• Main set: 3 rounds of (3x100m at CSS pace on 1:55, with 30s extra rest between rounds). Target: 1:35-1:37 per 100m.
• Cool-down: 200m easy backstroke

Total: 2,400m. The main set delivers 900m of threshold-intensity work -- enough stimulus to drive adaptation without destroying her for the next day.

Practical Rules

1. Retest CSS every 6-8 weeks. As your fitness improves, your CSS pace will drop. Training with an outdated (too slow) CSS means your threshold sets become comfortable endurance swims -- still useful, but not targeting the right system.

2. Pace the 400m TT like a race, not a death march. The most common testing error is going out too fast on the first 100m of the 400m trial and then fading badly. Aim for even splits or a very slight negative split. An erratic 400m corrupts the CSS calculation.

3. Use the pace clock relentlessly. In swimming, the pace clock is your power meter. Learn to read your split at every wall. If your CSS is 1:35/100m, you should be hitting the wall at approximately 0:24 per 25m, 0:48 per 50m, and 1:35 per 100m during threshold sets.

4. Do not swim your easy sets too fast. This is the single most prevalent mistake in age-group swimming. If your CSS is 1:35/100m, your Zone 2 endurance pace should be around 1:49-1:59/100m. That feels painfully slow. Do it anyway. Use the extra mental bandwidth to focus on stroke technique, catch timing, and body rotation.

5. Send intervals on a fixed cycle, not with fixed rest. Instead of "8x100m with 20 seconds rest," use "8x100m on 1:55." The fixed cycle creates natural accountability: if you swim slower, you get less rest. If you swim faster, you earn more recovery. This teaches honest pacing.

6. Account for pool conditions. A CSS test in a 50m pool will yield a different result than a 25m pool due to the effect of turns (push-offs are faster than swimming). If you train in a 25m pool but race in open water, your effective CSS in open water will be a few seconds slower per 100m due to sighting, currents, and drafting dynamics.

7. Use CSS for triathlon race pacing. For an Olympic-distance triathlon (1500m swim), most athletes should target a pace 2-5 seconds per 100m faster than CSS -- dipping slightly into Zone 5a. For a half-Ironman (1900m), aim for CSS pace or 1-2 seconds per 100m slower. For a full Ironman (3800m), swim 3-6 seconds per 100m below CSS.

Evidence Base

The critical velocity concept in swimming was rigorously validated by Wakayoshi et al. in their 1992 paper. They tested competitive swimmers across multiple distances (50m through 400m) and demonstrated that the slope of the distance-time regression -- the critical swim speed -- correlated strongly (r=0.91) with swimming velocity at the onset of blood lactate accumulation (OBLA, 4 mmol/L). This established CSS as a practical, non-invasive field test for threshold estimation.

Dekerle et al. (2002) further refined the methodology by comparing various distance combinations for calculating CSS. They found that the 200m-400m pairing provided the best balance of reliability and validity, with test-retest correlations of r=0.97. Importantly, they showed that CSS slightly overestimates the true maximal lactate steady state velocity by approximately 3-5%, meaning athletes can sustain CSS pace for roughly 25-30 minutes rather than indefinitely. This small overestimation is well understood and generally considered acceptable for training prescription purposes.

The mathematical foundations trace back to Ettema's 1966 work on human performance limits, which established the hyperbolic power-duration curve that underpins both critical power (cycling) and critical velocity (swimming and running) models. The core insight -- that endurance performance can be decomposed into an aerobic capacity component and a finite anaerobic reserve -- has proven remarkably robust across exercise modalities and populations.

More recent work by Zacca et al. (2016) extended the validation to younger swimmers and confirmed that the 200-400m CSS protocol provides a practical threshold marker across age groups. They also highlighted the importance of maximal effort during both time trials, noting that submaximal performance on either trial will systematically bias the CSS estimate.

One limitation worth noting: CSS, like all critical power/velocity models, assumes that the anaerobic work capacity is fully utilized in both trials. In practice, pacing errors, motivation differences, or technical breakdowns can introduce noise. This is why consistent testing conditions -- same pool, same time of day, adequate warm-up, and genuine maximal effort -- are essential for accurate results.