Gravity neutral point calculator
Two masses of 36 and 4, placed 10 units apart, cancel each other's pull 7.5 units from the heavier one and 2.5 from the lighter one. Enter both masses and their separation to see where a small object feels no net gravity. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mass1
- 36
- Mass2
- 4
- Separation
- 10
- Total mass
- 40
- Distance from mass1
- 7.5
- Distance from mass2
- 2.5
- Position fraction from mass1
- 0.75
A gravity neutral point calculator answers a classic two-body question: given two point masses and the distance that separates them, where along the line joining their centres does the Newtonian gravitational field cancel so a small test mass feels no net pull from either body alone? Students meet this gravitational null point in orbital mechanics primers, Lagrange-point intuition, and textbook problems that ask for the empty balance location between Earth and Moon or between two laboratory masses. Engineers and educators need a deterministic contract that returns distances from each mass, rejects impossible inputs such as a zero total mass, and never invents a coordinate outside the segment when the physics only supports a cancel point between the bodies. This capability accepts mass1, mass2, and separation, applies the closed-form root of equal inverse-square fields, and returns rounded distances plus the substitution formula.
What the gravitational null point means and the formula used
Newtonian gravity produces a vector field that always points toward a positive point mass. When two such masses sit a fixed centre-to-centre separation d apart, the fields point in opposite directions everywhere strictly between them: each mass pulls a test particle toward itself. Setting the field magnitudes equal therefore yields a unique balance location on that open segment.
The null sits closer to the lighter mass, matching classroom intuition that the weaker attractor must be nearer for its steeper local field to match the stronger one. Equal masses place the neutral point exactly at the midpoint. The model is point-mass inverse-square gravity only; it does not include planetary rotation, non-spherical multipoles, general relativity, or the full three-body restricted problem that defines true Lagrange points with centrifugal terms.
Callers keep mass1, mass2, and separation in one consistent unit system so the returned distances share the same length unit as d.
Classrooms and tutoring platforms use a gravity neutral point calculator so learners can check the balance location for arbitrary mass pairs without square-root algebra mistakes. Exam generators need a deterministic oracle that rejects total mass zero and non-positive separation instead of silently inventing a coordinate. Science notebooks often need a quick null-point distance when sketching field lines between two fixed centres or when comparing inverse-square balance points with co-rotating Lagrange L1 locations that also include centrifugal force.
Keep requests small, pin the rounded distances in tests, and you get reproducible null points for homework, LMS plugins, and edge workers without standing up a full orbital-mechanics stack. Prefer this capability when you already know two positive masses and their separation and only need the Newtonian field-cancel point between them; if your problem asks for orbital Lagrange points with orbital angular velocity, use a three-body formulation instead of this two-mass field null alone.
What you can do with it
Exam and LMS auto-grading
Mark gravitational null-point items with a deterministic oracle that rejects total mass zero and never invents a cancel point outside the segment.
Notebooks and field-line sketches
Scripts compute the Newtonian balance location between two fixed centres when drawing field maps or comparing against full Lagrange L1 models.
FAQ
How do I find the gravity neutral point between two masses?
Send finite mass1, mass2 (both positive) and a strictly positive separation d.
Is the null point always between the masses?
Yes for two positive point masses under Newtonian gravity: fields oppose only between the bodies along the joining line, so the cancel point lies on that open segment, closer to the lighter mass.
Does this compute Earth–Moon Lagrange L1?
No. L1 includes centrifugal terms in a rotating frame. This tool returns only the pure gravitational-field null between two fixed masses.
Why is the neutral point closer to the lighter mass?
Gravity weakens with the square of the distance, so the weaker body can only match the stronger pull when you are close to it. With masses of 36 and 4 that are 10 units apart, the balance sits 2.5 units from the lighter one.
What happens if one of the masses is zero?
The calculation is refused. With only one body pulling, there is no point between the two where the pulls cancel, so no position is given. A total mass of zero, or a separation of zero or less, is refused as well.
Which units should I use for the masses and the separation?
Any units, as long as both masses share the same one. The distances to each mass come back in the same length unit as the separation, so kilometres in means kilometres out.
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/mech/gravity-null-point \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mass1":36,"mass2":4,"separation":10}'const res = await fetch("https://api.kit.forhosting.com/mech/gravity-null-point", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mass1": 36,
"mass2": 4,
"separation": 10
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/mech/gravity-null-point",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mass1": 36,
"mass2": 4,
"separation": 10
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/mech/gravity-null-point", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mass1":36,"mass2":4,"separation":10}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mass1":36,"mass2":4,"separation":10}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/mech/gravity-null-point", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mass1": 36,
"mass2": 4,
"separation": 10
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "mech.gravity_null_point",
"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
The free browser path and the prepaid API share the same pure analytic module so homework checks and automation scripts never disagree. Successful API calls bill the published $0.002 base price; invalid input is not charged.
What the gravitational null point means and the formula used
When total mass is zero there is no physical attractor pair and the task fails with invalid_input instead of returning a hollow coordinate.
Input contract, response fields, and error behaviour
Separation must be strictly positive because a zero or negative centre-to-centre distance does not define two distinct body centres on a line. Each mass must be non-negative; a negative mass is rejected as non-physical for this classical model. If exactly one mass is zero while the other is positive, no finite field-cancel point exists between the bodies, so that case is also rejected. Failed validation is never billed. POST a JSON body with three required finite numbers: mass1 (aliases m1 and m_1), mass2 (aliases m2 and m_2), and separation (aliases distance, d, and r). The sum mass1 plus mass2 must be strictly positive: total mass zero is the named product error and fails with invalid_input and a message that names total mass. On success the response echoes rounded mass1, mass2, and separation, reports total_mass, distance_from_mass1, distance_from_mass2, position_fraction_from_mass1, mass_ratio, sqrt_mass_ratio, formula, equation, method, and a short message stating that the null lies between the masses closer to the lighter one. Example: mass1 equals thirty-six, mass2 equals four, separation equals ten yields distance_from_mass1 equal to seven point five and distance_from_mass2 equal to two point five, because the square-root weights are six and two. Prefer JSON numbers when you control the client; numeric strings that match a strict finite pattern are accepted for homework-form paste paths. Successful API calls use the published $0.002 base price per item.
Where a gravity neutral point API earns its keep
The same numbers that appear in a worksheet appear in the JSON so graders and notebooks stay aligned.
Integration use cases
Homework checks for two-mass field balance
Students enter m1, m2, and separation from textbook problems and compare distance_from_mass1 and distance_from_mass2 against hand algebra before submitting.
Technical questions
What happens when total mass is zero?
The task fails with invalid_input. mass1 + mass2 must be strictly positive; a zero total mass has no physical gravitational null point and is not billed.
What does the gravity neutral point calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.