Rise over run calculator
A rise of 3 over a run of 4 is a slope of 3/4, or 0.75. Enter the vertical and the horizontal change and get the slope as a reduced fraction and as a decimal, with signs handled for you. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Rise
- 3
- Run
- 4
- Slope
- 0.75
- Slope fraction
- 3/4
- Numerator
- 3
- Denominator
- 4
Rise over run is the first slope identity every algebra course teaches: the vertical change between two points divided by the horizontal change between those same points. This rise over run calculator accepts a finite rise and a non-zero run, reduces the ratio to lowest terms, and returns the slope both as a fraction and as a decimal so a homework check, a grading script, and a drawing tool can share one contract. A rise of three over a run of four is three fourths, or zero point seven five. A rise of six over a run of eight simplifies to the same fraction.
What rise over run means and how the fraction is reduced
Slope measures how steep a line is: how much the line rises, or falls, for each unit it runs to the right. In classroom language that ratio is written rise over run, and in symbols it is m equals rise divided by run. Rise is the vertical change, often called delta y.
Run is the horizontal change, often called delta x. When both numbers are integers the slope is already a fraction; the useful work is reducing that fraction to lowest terms so three over four and six over eight report the same slope. The sign convention is part of the definition.
A positive rise with a positive run is an increasing line. A negative rise with a positive run is a decreasing line. Two negatives cancel, so a fall of three over a leftward run of four is still a positive three fourths.
This calculator always places the sign on the numerator and keeps the denominator positive, which matches how students are taught to write reduced improper fractions and how clients parse a stable string. A rise of zero over a non-zero run is a horizontal line with slope zero, written zero over one. Decimal inputs are first snapped to a ten-place decimal snapshot and then converted to a rational, so one point five over two becomes three halves over two, which reduces to three fourths.
That is the same arithmetic a teacher does on paper when a word problem hands out measurements that are not whole numbers.
Where a rise over run calculator earns its keep
Classrooms and tutoring platforms use a rise over run calculator so learners can check the reduced fraction for arbitrary rise and run without flipping a sign or forgetting to divide out a common factor. Exam-prep generators need a deterministic oracle that marks a zero run as undefined instead of silently returning Infinity that a buggy grader might treat as a large finite slope.
Drafting, carpentry, and ramp-design notes often start from a measured rise and a measured run rather than from two coordinate pairs, and they want the slope as a fraction they can write on a drawing and as a decimal they can feed into a later percent-grade or angle step. Two-point slope tools that also emit an inclination angle serve a different query, and converters that swap percent grade, degrees, and a rise-over-run ratio serve yet another; this landing is only the classroom identity m equals rise over run.
Failed validation does not consume balance.
What you can do with it
Classroom and homework checks
Let students submit a rise and a run and verify the reduced fraction and the decimal against the textbook method, including the sign on a falling line.
Exam and LMS auto-grading
Mark rise-over-run items with a deterministic oracle that rejects a zero run as undefined slope and never invents Infinity.
Drawings, ramps, and measured segments
Turn a measured vertical rise and horizontal run into a reduced slope you can print on a drawing and a decimal you can pass to a later step.
FAQ
How do I calculate slope from rise and run?
Send finite numbers rise and run (run must be non-zero).
What happens if the run is zero?
A zero run is a vertical line, so the slope is undefined; those failures are not billed.
How is this different from a two-point slope calculator?
A two-point tool starts from coordinates (x1, y1) and (x2, y2) and often also returns an inclination angle.
Why does 6 over 8 give the same slope as 3 over 4?
Because the fraction is always reduced to lowest terms. 6/8 and 3/4 describe the same steepness, so both come out as 3/4 and 0.75, which makes answers easy to compare.
How are negative rises and runs handled?
A negative rise with a positive run gives a falling line and a negative slope. When both are negative they cancel and the slope is positive. The sign always goes on the top of the fraction, never the bottom.
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/math/rise-over-run \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"rise":3,"run":4}'const res = await fetch("https://api.kit.forhosting.com/math/rise-over-run", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"rise": 3,
"run": 4
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/math/rise-over-run",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"rise": 3,
"run": 4
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/math/rise-over-run", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"rise":3,"run":4}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"rise":3,"run":4}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/math/rise-over-run", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"rise": 3,
"run": 4
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "math.rise_over_run",
"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.
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 zero run is a vertical line, where slope is undefined, and that case fails with invalid_input instead of Infinity.
What rise over run means and how the fraction is reduced
A run of zero is not a slope at all: the line is vertical and m is undefined, so the endpoint refuses the request instead of returning Infinity or a fake huge number.
Input contract, response shape, and error behaviour
A zero run is rejected because slope is undefined on a vertical line; those failures are not billed either. Example: rise six and run eight yields the same reduced fraction and the same decimal, which is the whole point of reducing. POST a JSON body with two required finite numbers: rise, the vertical change, and run, the non-zero horizontal change. Each field may arrive as a JSON number or as a numeric string. Common aliases are accepted when the canonical name is omitted: dy, delta_y, or vertical for rise; dx, delta_x, or horizontal for run. Missing fields, empty strings, non-numeric text, NaN, and Infinity fail with invalid_input naming the field and are not billed. On success the body echoes the cleaned rise and run, returns slope as the decimal rise divided by run, and returns slope_fraction as the reduced numerator-slash-denominator string with the sign on the numerator. It also names numerator and denominator as integers, direction as positive, negative, or zero, is_integer when the reduced denominator is one, restates the formula string m equals rise over run, and includes a one-line message you can show next to a graph. Example: rise three and run four yields slope zero point seven five, slope_fraction three over four, direction positive, and is_integer false. Example: rise four and run two yields slope two, slope_fraction two over one, and is_integer true. Pair the payload with your own sketch of the line; this endpoint does not emit plots or multi-step classroom prose beyond the message and formula fields.
Where a rise over run calculator earns its keep
Keep requests small, pin slope and slope_fraction in tests, and you get a reproducible reduced slope for homework, LMS plugins, and edge workers without standing up a computer-algebra stack of your own.
Technical questions
Does the calculator reduce the fraction?
Yes. Rise six and run eight returns slope_fraction 3/4 and slope 0.75, the same reduced result as rise three and run four. The sign always sits on the numerator.
What does the rise over run calculator cost?
The browser tool is free. API requests use prepaid balance at $0.002 per successful call; invalid input is not billed.