If you work at a keyboard all day, you’ve probably heard some version of:
“Take more breaks.”
That advice is right in spirit, but vague in practice.
How long? How often? Does it actually help?
Here is the honest answer, up front: nobody knows. The trials that have been run are small, and when they are pooled the effect on pain is not distinguishable from zero.
Not medical advice. If you have persistent pain, numbness, or weakness, get medical advice.
TL;DR
- The pooled evidence is a null. Cochrane combined the randomised trials of extra work breaks against no extra breaks and found a standardised mean difference of -0.08, 95% CI -0.35 to 0.18, three studies, 225 participants, rated low quality. The confidence interval straddles zero (Luger et al., Cochrane 2019).
- The evidence got weaker, not stronger. The October 2025 update concludes the evidence is very uncertain about the effect of additional work breaks on musculoskeletal pain intensity and on productivity (Luger et al., Cochrane 2025).
- One 2001 study of real keying work did report reduced discomfort with no evidence of harm to productivity, with 20-minute intervals looking favourable (McLean et al., 2001). It is a single study from 2001, and it is the one nearly every microbreak article is built on.
- No trial anywhere has tested break duration. So any specific number of seconds you read online, including ours below, is a guess.
- Microbreaks remain worth trying because they are free and carry no known risk, not because the trials show a benefit.
What counts as a “microbreak”?
In ergonomics, “microbreak” typically means seconds to a couple of minutes, not “take a walk for 30 minutes.”
The design advice you will see everywhere is that they should be frequent, tiny, and automatic, so that strain does not accumulate and you do not have to rely on willpower. That is reasonable and it is untested. No trial has compared break durations or frequencies against each other well enough to say.
What the research actually says
The strongest evidence is a systematic review, and it found nothing
Start with the review rather than the individual studies, because that is the correct order.
A Cochrane review examined randomised trials of work-break schedules for preventing musculoskeletal symptoms in healthy workers. For the comparison that matters, additional breaks versus no additional breaks, it pooled three studies and 225 participants and reported a standardised mean difference of -0.08, 95% CI -0.35 to 0.18 for musculoskeletal pain, discomfort or fatigue. That is an effect of roughly zero with a confidence interval wide enough to contain a small benefit and a small harm equally. Across the whole review, six trials and 373 workers, every trial was judged at high risk of bias, and no trial tested break duration at all (Luger et al., Cochrane 2019).
The whole picture is that line through the middle. Source: Luger et al., Cochrane 2019.
Cochrane updated the review on 8 October 2025. The conclusion moved in the direction people rarely expect: the evidence is very uncertain about the effect of additional work breaks on the intensity of musculoskeletal back and neck pain, and on productivity (Luger et al., Cochrane 2025, CD012886.pub3).
Six years of additional research made the picture less clear, not more. Any page that tells you microbreaks are proven is working from the individual studies and ignoring the pooled result.
The single study people quote
In a study of computer terminal work, participants did their usual keying under different protocols: no breaks, breaks at their own discretion, or microbreaks at set intervals of 20 or 40 minutes. The authors reported microbreaks reduced discomfort and found no evidence of a detrimental effect on productivity, with the 20-minute interval looking most favourable (McLean et al., 2001).
This is the study almost every microbreak article is built on, including, until this revision, ours. One positive result from 2001 does not outweigh a pooled analysis that came out null. It gets quoted because it is the one with a positive finding, which is exactly the selection problem a systematic review exists to correct.
A study we used to cite here, and why we removed it
This page previously cited a 2014 trial of 3-minute breaks every 20 minutes in symptomatic computer operators as evidence that scheduled breaks help. That was wrong, and the error is worth naming rather than quietly deleting.
The trial randomised 30 people to three kinds of break activity: stretching, dynamic movement, or sitting. It had no no-break control arm. It therefore cannot show that taking breaks beats not taking breaks, because it never tested that comparison. Its own Results section reports "no significant differences between the types of activities during breaks on neck and shoulder muscle activity, muscle discomfort or productivity." We had quoted the more upbeat sentence from the paper's Conclusions and left the null out.
We have removed the claim. The finding that survives is narrower and less useful: three different things to do during a break are indistinguishable from each other.
A microbreak schedule that actually gets used
A schedule you will not follow is worth nothing, so this one is short, fixed, and needs no decision at the moment it fires. Try it for one week:
The 20/20 protocol
The 20-minute interval is the one number here with any study behind it, from the 2001 experiment above. The break lengths are not evidence-based, because no trial has tested break duration. Treat them as a reasonable starting point to adjust, not a prescription.
- Every 20 minutes: take a 30 to 60 second microbreak
- Once per hour: take a 3 to 5 minute break (stand up, refill water)
Judge it on whether you feel better after two weeks. That is a sample size of one, which is weak evidence in general and the only evidence that is actually about you.
What to do during a microbreak:
- Stand up and reset posture
- Relax your shoulders, unclench jaw
- Shake hands out / open and close fists gently
- Look at something far away for a few breaths
For what these look like in practice, this short video has examples: Fit Ergonomics, “3 Microbreaks at Work to Boost Your Focus and Productivity”.
Why microbreaks pair well with voice typing (RSI strategy)
Microbreaks reduce continuous load.
Voice typing reduces keystroke volume.
When you combine them, you get a workflow that’s easier to sustain:
- Dictate drafts (fewer keystrokes)
- Edit precisely (short burst of typing)
- Microbreak before the next burst
If RSI is your main reason for exploring voice typing, start here: /solutions/rsi.
If you want an overview of dictation tradeoffs, including the voice strain risk, see: /blog/voice-typing-for-rsi.
Making it stick
The hard part is not the schedule, it is remembering. Two patterns show up repeatedly in threads where people compare reminder tools:
- People want obnoxious reminders because gentle ones get ignored.
- People want reminders that are dismissible, not lockouts.
Examples:
- Reddit: “Scheduled break app with really obnoxious reminders?” (r/productivity)
- Reddit: “App to remind breaks?” (r/productivity)
On Hacker News, an open-source microbreak reminder app called Stretchly got discussed as a simple “make it happen” tool:
- HN: “Stretchly: System tray app that reminds you to take microbreaks” (thread)
- Stretchly repo: github.com/hovancik/stretchly
Sources
- Work-break schedules systematic review, current version: Luger et al., Cochrane 2025, CD012886.pub3 (PubMed)
- Work-break schedules systematic review, superseded 2019 version with the pooled estimate: Luger et al., Cochrane 2019, CD012886.pub2 (PMC)
- Microbreaks in computer terminal work: McLean et al., 2001 (PubMed)
- Break activity types in symptomatic operators, no no-break control: Nakphet et al., 2014 (PubMed)
- Microbreak examples (video): Fit Ergonomics (YouTube)
- Community threads: r/productivity thread, r/productivity thread, HN thread
