Work-to-break ratio calculator
A 5:1 ratio over a 120-minute session gives 100 minutes of work and 20 of rest, and the two always add back to the session. Enter any pair, whole or decimal, plus the length you have. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Work ratio
- 5
- Break ratio
- 1
- Session minutes
- 120
- Parts total
- 6
- Work minutes
- 100
- Break minutes
- 20
- Work percent
- 83.3333333333
Coaches, makers, and ops leads use the same closed-form split to plan a morning, a workshop, or a study block without arguing about spreadsheet rounding.
What a work-to-break ratio measures and how the split is computed
A work-to-break ratio is a pair of positive parts, not a pair of wall-clock appointments. Five to one means five parts of focused work for every one part of rest, whatever the session length happens to be. Work and break percents are those shares times one hundred.
The same arithmetic covers the famous published rhythms without special cases: a Pomodoro 25:5 pair simplifies to 5:1 and a one-hundred-twenty-minute session becomes one hundred minutes of work and twenty minutes of rest; DeskTime’s 52:17 over two hundred seven minutes becomes three full cycles totaling one hundred fifty-six work minutes and fifty-one rest minutes; an ultradian 90:20 block over one hundred ten minutes is ninety work and twenty rest.
The calculator also reduces the input pair to lowest terms with a Euclidean gcd on scaled integers, so 25:5 and 2.5:0.5 both report the simplified ratio 5:1. Fractional parts are allowed: a 1.5:0.5 cadence over forty minutes is thirty work and ten rest.
Who plans sessions with a work-to-break ratio
Personal productivity coaches and time-blocking workshops need a deterministic oracle so every student sees the same work and rest minutes for a shared sample session during a live demo. Makers and writers who follow DeskTime’s fifty-two seventeen cadence can convert a three-hour writing block into exact focus and walk minutes before they open a timer. Students stacking Pomodoros before an exam can turn a two-hour window into total work and rest without counting cycles by hand.
Team leads planning a half-day workshop can publish a 45:15 or 50:10 split so facilitators know how much lecture and how much stretch to put on the agenda. Failed validation does not consume balance. Keep sessions under a week of minutes, pin the rounded minute fields in tests, and you get reproducible work-and-rest allocations for worksheets, LMS modules, and edge workers without hosting custom timer math of your own.
What you can do with it
Pomodoro and study-block planning
Turn a two-hour study window and a 5:1 (or 25:5) cadence into exact work minutes and rest minutes before you start the first timer.
DeskTime 52/17 deep-work blocks
Split a writing or coding session with the 52:17 ratio so focus time and walk breaks add back to the hours you actually have.
Workshop and coaching agendas
Give a live class a deterministic work-to-break split so every participant sees the same lecture and stretch minutes for a shared session length.
FAQ
What is a work-to-break ratio?
It is a pair of positive parts that says how much focused work you want for every slice of rest. Five to one means five parts work for each one part rest. This calculator applies that pair to a session length and returns the two minute totals.
How do I enter a Pomodoro 25/5 or DeskTime 52/17 cadence?
For DeskTime send 52 and 17. Both pairs are ordinary positive numbers; 25:5 is reduced to 5:1 in the response.
Can the ratio parts be decimals?
Yes. Fractional parts such as 1.5:0.5 are valid. The pair is scaled and reduced so the reported ratio is an integer lowest-terms string such as 3:1.
Do the work and break minutes always add up to the session?
Yes. Work minutes are the session times the work share, and break minutes are whatever remains, so after rounding the two sides still rebuild the full length: 100 plus 20 is the 120-minute session.
Why does a 25:5 ratio show as 5:1?
The pair is reduced to lowest terms, because only the proportion matters. 25:5, 2.5:0.5 and 5:1 all mean five parts of work for one part of rest, so they split any session the same way.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/biz/work-break-ratio \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"work_ratio":5,"break_ratio":1,"session_minutes":120}'const res = await fetch("https://api.kit.forhosting.com/biz/work-break-ratio", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"work_ratio": 5,
"break_ratio": 1,
"session_minutes": 120
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/biz/work-break-ratio",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"work_ratio": 5,
"break_ratio": 1,
"session_minutes": 120
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/work-break-ratio", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"work_ratio":5,"break_ratio":1,"session_minutes":120}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"work_ratio":5,"break_ratio":1,"session_minutes":120}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/work-break-ratio", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"work_ratio": 5,
"break_ratio": 1,
"session_minutes": 120
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "biz.work_break_ratio",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_session_minutes | 10080 |
max_ratio_part | 1000000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
A work-to-break ratio says how much focused time you want for every slice of rest: five-to-one for a classic Pomodoro stack, fifty-two-to-seventeen for the DeskTime rhythm, or ninety-to-twenty for an ultradian deep-work block. This work-to-break ratio calculator takes those two parts and a session length in minutes, then splits the session in exactly that proportion so the work minutes and rest minutes always add back to the session. Invalid ratios or a non-positive session fail with invalid_input and are not billed.
What a work-to-break ratio measures and how the split is computed
The identities are closed form: parts_total is work_ratio plus break_ratio; work_share is work_ratio divided by parts_total; work_minutes is session_minutes times work_share; break_minutes is session_minutes minus work_minutes so the two sides always reconstruct the session after rounding. The method string is always proportional_split so clients can pin the algorithm in tests. The endpoint does not schedule calendar events, insert lunch, or invent fatigue science; it only allocates the minutes you already decided to spend.
Input contract, response shape, and error behaviour
POST a JSON body with three required finite numbers. work_ratio is the work side of the pair and must be greater than zero and at most one million; aliases work, work_parts, and work_units are accepted. break_ratio is the rest side with the same bounds; aliases include break, rest, rest_ratio, break_parts, and rest_parts. session_minutes is the total length to split, greater than zero and at most ten thousand eighty (one week); aliases session, duration, minutes, session_length, and total_minutes are accepted. Each field may arrive as a JSON number or as a numeric string. Missing fields, empty strings, NaN, Infinity, zero or negative values, and values above the published limits fail with invalid_input naming the field and are not billed. On success the body echoes the three drivers, parts_total, work_minutes and break_minutes, work_percent and break_percent, work_share and break_share as unit fractions, the reduced work_parts and break_parts, gcd, a ratio string such as 5:1, plus formula and method. Example: work_ratio five, break_ratio one, session_minutes one hundred twenty yields work_minutes one hundred, break_minutes twenty, work_percent about eighty-three point three, and ratio 5:1. Pair the numbers with your own coaching copy if you need labels such as “focus” versus “walk”; this endpoint only splits. It does not reorder a task list, talk to a calendar API, or decide whether you should stand up.
Technical questions
How does the work-to-break ratio calculator split a session?
work_minutes equals session_minutes times work_ratio divided by (work_ratio plus break_ratio). break_minutes is the remainder of the session so the two sides always add back to the length you sent.
What does the work-to-break ratio calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.