Should you train when you're still sore?
Usually yes — soreness is a poor gauge of recovery and of workout quality. When to push through, when to train around it, and the two real red flags.
Short answer: usually yes. Ordinary muscle soreness is not a stop sign, it’s a poor and frequently misleading gauge of both recovery and workout quality. The longer answer is knowing what soreness actually signals, the two cases where it really does mean stop, and the trap on the other side that catches the dedicated.
What soreness is, and isn’t
Delayed-onset soreness is your tissue’s response to unfamiliar stress — new exercises, new ranges, big jumps, long negatives. It peaks a day or two after and fades as the muscle adapts, which it does remarkably fast: repeat the same session next week and soreness drops sharply even though the stimulus was identical. That’s called the repeated-bout effect, and it’s why soreness fades over a training block while gains continue.
Which breaks both popular readings of it:
- “Sore = it worked” — no. Novelty causes soreness; growth comes from volume and progression, which after the first weeks produce very little soreness at all. Chasing the feeling leads to program-hopping — permanently sore, rarely progressing.
- “Sore = not recovered” — also mostly no. Performance recovers on its own clock. You can be sore and lift at full strength, or feel fine and be run-down. The bar tells the truth; the ache doesn’t.
The decision rule
Warm up fully and start the first working set. Then:
- Performance is there (you match your log at normal effort) → train as planned. The soreness is cosmetic.
- Performance is clearly missing — warm-ups feel like work sets, weights that moved crisply last week grind — → that’s actual under-recovery. Cut volume, drop intensity, or train something else. The log defines “clearly”: that’s one of the quiet reasons to keep one.
- Train around, not through, mechanical interference. Squatting sore quads is fine. Squatting when soreness changes how you move is how tweaks happen. Sore chest, fine legs? Today became leg day. A sensible split absorbs this without drama — full-body layouts degrade especially gracefully.
Movement genuinely helps, too: light work sends blood through sore tissue and reliably feels better than a rest day spent on the couch. “Too sore to train” usually means “too sore to repeat that exact session”, which nobody’s asking for.
The two real red flags
Rare, and worth knowing cold:
- Sharp, joint-located, or one-sided pain is not soreness. Soreness is dull, symmetric, and lives in the muscle belly. Pain that stabs, lives in a joint, or only exists on one side is an injury conversation, not a toughness one.
- Severe soreness with dark, cola-colored urine after an extreme session is the emergency exception — possible rhabdomyolysis, which is a same-day medical visit, not a foam-rolling situation. It’s rare and it follows genuinely extreme, unaccustomed volume. Respect it.
The trap on the other side
For every lifter who trains too sore, several use soreness as the permission slip to skip — and skipping is the actual threat. One missed session becomes an “off week” with remarkable ease, and streaks break at exactly these decision points. The honest move on a sore day is almost never nothing; it’s the reduced session, the walk, the different muscle group — anything that keeps the day a training day.
This is precisely why Momentum’s streak runs on XP rather than on completed workouts: a shortened session, a logged walk, even just weighing in and hitting your protein all keep the flame alive. The system is built so that the right call on a rough day — do less, but not zero — is also the call the game rewards. And the per-muscle heat map makes “train around it” concrete: it shows you at a glance which heads got hammered and which are fresh.
The one-line version
Sore and performing? Train. Sore and genuinely weak? Do less, today only. Sharp, one-sided, or something feels wrong? Stop and get it looked at. And never confuse the ache with the work — the log measures the work.