Wheel and axle mechanical advantage calculator
This wheel and axle mechanical advantage calculator finds the ideal force multiplication produced when an effort turns a wheel that is rigidly attached to a smaller axle.
Run — free
Enter the wheel radius and axle radius in the same length unit, and the calculator divides the first by the second. The result is dimensionless, so centimetres, inches, millimetres, or metres all work when used consistently. It is useful for classroom mechanics, quick design checks, lab comparisons, and deterministic software fixtures. The result represents an ideal machine and does not include bearing friction, deformation, slipping, or other losses found in real equipment.
How wheel-and-axle mechanical advantage works
A wheel and axle consists of two circular parts fixed to the same shaft so they rotate through the same angle. When effort is applied tangentially at the wheel rim, its turning moment equals the effort force multiplied by the wheel radius. The axle delivers a tangential output force at its smaller radius. In an ideal static balance, the input and output moments are equal, so effort force times wheel radius equals output force times axle radius. Rearranging that equation gives ideal mechanical advantage as wheel radius divided by axle radius. A wheel radius of thirty units and an axle radius of five units therefore produce a mechanical advantage of six. In the ideal model, one unit of effort can balance six units of output force. The gain is not free energy: the wheel rim travels six times as far as the axle surface during the same rotation. This calculator assumes the effort acts at the wheel and the load acts at the axle. Reversing those roles creates a speed or distance advantage instead of the force-multiplying arrangement described here.
Enter radii consistently and read the result
Provide wheel_radius and axle_radius as finite numbers greater than zero. Both values must use the same length unit because the calculation is a ratio. You can enter thirty centimetres and five centimetres, or twelve inches and two inches, and obtain the same result of six. Do not mix a wheel radius in centimetres with an axle radius in millimetres unless you convert one value first. The fields require radii measured from the shared rotation axis to the relevant contact point, not diameters. If you only know diameters, you may use both diameters directly because halving both values leaves their ratio unchanged, but do not combine one radius with one diameter. The returned mechanical_advantage is dimensionless. An answer greater than one indicates ideal force multiplication; one indicates equal input and output force; less than one indicates that this input arrangement trades force for greater output speed and distance. Zero and negative radii are rejected because they cannot describe the circular geometry and would make the ratio undefined or physically misleading. Each successful API calculation costs $0.002 per item.
Use the ideal ratio as a benchmark, not a load rating
The calculated value is ideal mechanical advantage, which is a geometry-based benchmark. A real wheel-and-axle machine normally produces a lower actual mechanical advantage because bearings and bushings create friction, ropes may bend and stretch, contact surfaces can slip, components deform under load, and the wheel or axle itself has mass. Handles mounted inside the wheel rim also reduce the effective effort radius. Use the result to solve textbook problems, compare candidate proportions, predict a frictionless upper bound, or check whether measurements from a teaching laboratory are plausible. Do not treat it as a safe working load, torque rating, or proof that a winch, steering mechanism, screwdriver, capstan, or hoist can carry a particular load. Those decisions require material strength, shaft torque, fastener capacity, bearing ratings, fatigue, braking, stability, efficiency, duty cycle, and an appropriate safety factor. For experiments, actual mechanical advantage can be found separately by dividing measured output force by measured effort force; comparing that measurement with this ideal ratio helps estimate efficiency. The capability deliberately excludes those additional variables so its result remains transparent, deterministic, and focused on the radius ratio users requested.
What you can do with it
Check a physics exercise
Calculate the ideal force multiplier from the two radii and compare it with a hand-derived moment balance.
Compare preliminary dimensions
See how changing the wheel or axle radius changes the ideal geometric advantage before detailed component design.
Prepare a mechanics lab
Establish the frictionless benchmark that measured effort and output forces can later be compared against.
FAQ
What formula does the calculator use?
Ideal mechanical advantage equals wheel radius divided by axle radius when effort is applied at the wheel and output is taken from the axle.
Do the radii need a particular unit?
No. Use any length unit, but use the same unit for both values. The result is dimensionless.
Can I enter diameters instead of radii?
Yes, if both values are diameters. Their common factor of two cancels, so the ratio is unchanged.
Why is actual mechanical advantage usually lower?
Real machines lose useful force through friction, slipping, deformation, and other effects omitted by the ideal geometric model.
What does the API calculation cost?
Each successful request costs $0.002 per item. The same deterministic calculation is available free in the browser.
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/eng/wheel-axle-ma \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"wheel_radius":30,"axle_radius":5}'const res = await fetch("https://api.kit.forhosting.com/eng/wheel-axle-ma", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"wheel_radius": 30,
"axle_radius": 5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/eng/wheel-axle-ma",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"wheel_radius": 30,
"axle_radius": 5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/eng/wheel-axle-ma", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"wheel_radius":30,"axle_radius":5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"wheel_radius":30,"axle_radius":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/eng/wheel-axle-ma", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"wheel_radius": 30,
"axle_radius": 5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "eng.wheel_axle_ma",
"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. |