Odds to probability converter
Odds of 1 to 4 mean a probability of 0.2, or 20 percent, and 25 percent turns back into odds of 1 to 3. Enter odds, a probability or a percentage and get the other two forms at once. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- A
- 1
- B
- 4
- Odds
- 1 to 4
- Probability
- 0.2
- Percentage
- 20
- From
- odds
Sportsbooks, classrooms, and risk models all talk about the same chance in three different languages: odds written as a to b, a unit probability between zero and one, and a percentage out of one hundred. This capability converts cleanly among those three forms in both directions so you never have to re-derive a over a plus b by hand or guess whether someone meant twenty percent or zero point two. Send either the favorable and unfavorable odds components a and b, a probability in the closed unit interval, or a percentage in zero through one hundred; the response always returns the reduced odds string, both numeric parts, the probability, the percentage, and a from field that records which input mode you used.
How odds, probability, and percentage relate
When an event is described with odds a to b in the favorable sense used here, the implied probability is the ratio of the favorable weight to the total weight: probability equals a divided by a plus b. The percentage is simply one hundred times that probability, so odds of one to four become probability zero point two and twenty percent, while even money one to one becomes one half and fifty percent.
Going the other way, a known probability p maps to odds p to one minus p, which this tool reduces to the smallest non-negative integers that keep the same ratio whenever floating-point scaling allows a clean reduction; a percentage of twenty five becomes probability zero point two five and odds one to three after reduction.
Edge cases are defined explicitly: zero to one is impossible under pure odds language only when both sides are zero, which this converter rejects because the probability would be undefined; odds of zero to one give probability zero; odds of one to zero give certainty. No Monte Carlo sampling, random seeds, wall-clock clocks, or network lookups are involved—the conversion is pure arithmetic with a deterministic greatest-common-divisor reduction on the ratio.
Declared bounds keep probability inside zero through one inclusive and percentage inside zero through one hundred inclusive, and every named component must be non-negative so negative “weights” cannot sneak into a ratio that no longer means a chance. That contract matches how textbooks, fair-game demos, and simple risk dashboards already speak, while staying small enough for free-tier browser latency.
Where odds-to-probability conversion shows up in real work
Introductory probability courses constantly switch notation: a problem states odds of three to one against an event, then asks for the probability, then asks students to restate the answer as a percentage for a non-technical audience. Sports and gaming sandboxes (when used for fair-game math rather than live wagering pipelines) often store a ratio a to b in configuration files but need a unit probability for expected-value formulas and a percentage for UI labels.
Data scientists normalizing heterogeneous survey answers—some respondents write "about 30 percent," others write "roughly one in four," others write "odds of one to three"—need a single bidirectional converter so downstream models see one scale. Risk and decision-analysis notes often quote chances as percentages in slides while the spreadsheet underneath uses probabilities, so a reliable round-trip avoids off-by-one-hundred mistakes that silently break expected-value tables.
If you later need decimal or American moneyline odds formats, vig-adjusted implied probabilities for multi-way markets, or Bayesian updates that change the odds after new evidence, treat those as separate search intents rather than overloading this landing. Keep every component non-negative, send exactly one source mode, and remember that the reduced a to b display is for readability while the floating probability remains the value you should feed into further math.
What you can do with it
Homework and answer keys
Convert textbook odds a to b into probability and percentage, and check student answers that mix all three notations.
UI labels and risk notes
Show the same chance as odds, a unit probability for formulas, and a percentage for non-technical dashboards without hand conversion.
FAQ
How do you turn odds a to b into a probability?
Using the favorable reading p = a / (a + b). Percentage is 100 × p. Odds of 1 to 4 become probability 0.2 and 20%.
What happens if a or b is negative?
Every component—odds parts, probability, and percentage—must be non-negative.
What if I send both probability and percentage?
That is rejected. Provide exactly one source: both a and b, or probability alone, or percentage alone.
What does it cost?
The browser tool is free and runs locally.
How do I turn a probability into odds?
A probability p becomes odds of p to one minus p, reduced to the smallest whole numbers. A percentage of 25 becomes a probability of 0.25 and odds of 1 to 3.
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/prob/odds-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"a":1,"odds_a":0}'const res = await fetch("https://api.kit.forhosting.com/prob/odds-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"a": 1,
"odds_a": 0
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/prob/odds-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"a": 1,
"odds_a": 0
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/prob/odds-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"a":1,"odds_a":0}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"a":1,"odds_a":0}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/prob/odds-converter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"a": 1,
"odds_a": 0
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "prob.odds_converter",
"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
min_component | 0 |
max_probability | 1 |
max_percentage | 100 |
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
Any negative component is rejected with a clear invalid_input error rather than a silent absolute value or a nonsense ratio.
What you send and what you get back
Missing every source is likewise rejected. On success the response always includes integers or reduced numeric parts a and b, a human-readable odds string such as "1 to 4", probability as a floating-point number in zero to one, percentage as one hundred times that probability, and from set to odds, probability, or percentage according to the source you supplied. Provide exactly one conversion source per request. To start from odds, send both a and b under the fields a and b (aliases odds_a, for, or left for a; odds_b, against, or right for b). To start from a unit chance, send probability (aliases p, prob, or chance) in the closed interval from zero to one. To start from a percent, send percentage (aliases percent, pct, or pc) in zero through one hundred. Mixing two sources in one payload—for example both probability and percentage, or a alone without b—is rejected with invalid_input so the engine never has to invent which value wins. Classic checks include a equals one and b equals four yielding probability zero point two and percentage twenty; probability zero point five yielding odds one to one and fifty percent; percentage twenty five yielding probability zero point two five and odds one to three; a negative a or b yielding invalid_input that names the negative component; and probability above one or percentage above one hundred yielding a clear range error. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where odds-to-probability conversion shows up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Pipeline fixtures and demos
Generate deterministic golden triples (odds, probability, percentage) for tests, widgets, and fair-game math sandboxes.
Technical questions
Can I convert from percentage back to odds?
Yes. Send percentage in [0, 100]; the tool returns probability = percentage/100 and reduced odds a to b for that chance.