Telescope light-gathering power calculator
See how many times more light your telescope gathers than your eye: a 100 mm objective against a 7 mm pupil collects about 204.08 times as much. Enter both diameters in the same unit. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Objective diameter
- 100
- Pupil diameter
- 7
- Light gathering power
- 204.0816326531
- Factor
- 204.0816326531
- Relative to
- human_eye
A telescope gathers more light than a dark-adapted human eye because its objective lens or primary mirror has a much larger collecting area. This calculator compares those circular areas from two diameters and reports how many times as much light the telescope can collect under the ideal geometric model. Enter the objective diameter and pupil diameter in the same unit, such as millimetres, centimetres, or inches. The unit cancels in the ratio, making the result a dimensionless factor that is easy to compare across instruments.
What the light-gathering factor means
Light-gathering power describes the amount of incoming light intercepted by a telescope compared with a reference collector. Here the reference is the circular pupil of a human eye. Because the area of a circle is pi times the radius squared, comparing two circular apertures does not require calculating either area separately: the shared constants cancel, leaving the square of the diameter ratio.
A result of 204.08, for example, means that the objective has about 204.08 times the geometric collecting area of the stated pupil. This is a dimensionless comparison, not a brightness value in lumens and not a prediction of how bright an extended object will appear through an eyepiece. The calculation assumes unobstructed circular collecting areas and equal transmission.
It therefore provides a clean baseline for comparing aperture, while real instruments may deliver less light because of mirror reflectivity, lens absorption, central obstruction, dust, filters, and losses in the eyepiece or detector path.
How to enter objective and pupil diameters
Both values must use the same length unit. A 100 millimetre objective paired with a 7 millimetre pupil is valid, as is a 10 centimetre objective paired with a 0.7 centimetre pupil; both describe the same ratio and return the same factor. Mixing 100 millimetres with 0.7 centimetres would produce a wrong answer because the calculator deliberately treats the inputs as unitless matching measurements rather than guessing or converting units.
The pupil diameter must be greater than zero. A zero or negative pupil cannot define a physical comparison area and is rejected as invalid input, rather than producing infinity or a misleading signed result. The objective diameter must be finite and non-negative; zero is mathematically supported and returns a factor of zero, although it represents no collecting aperture.
Decimal strings and ordinary scientific notation are accepted by the deterministic core, while blank values, Infinity, NaN, objects, and malformed numeric text are rejected. For visual observing, choose a pupil estimate appropriate to the observer and lighting conditions instead of assuming every eye reaches the same dark-adapted diameter.
Using the result for telescope comparisons
The squared relationship makes aperture differences more important than they may first appear. Doubling the objective diameter produces four times the collecting area relative to the same eye pupil; tripling it produces nine times the area. This makes the calculator useful when comparing binocular objectives, small refractors, Dobsonian reflectors, and larger observatory instruments on a consistent geometric basis.
Students can verify exercises about circular aperture area without carrying pi through every line, while observers can turn a telescope specification into an intuitive multiple of naked-eye collection. Treat the factor as an ideal upper-level comparison rather than an exposure-time or limiting-magnitude guarantee. Two telescopes with equal clear diameter can differ in throughput, optical quality, obstruction, sky background, detector efficiency, and magnification.
Likewise, perceived brightness depends on the exit pupil and the angular size of the target. For a reflector with a substantial secondary obstruction, use a dedicated effective-area calculation before comparing its delivered flux. For this capability, supply the nominal or clear objective diameter and interpret the answer as the simple circular area ratio requested by the standard light-gathering-power formula.
What you can do with it
Compare a telescope with dark-adapted vision
Use the telescope aperture and an appropriate eye-pupil estimate to express the ideal collecting area as an easy-to-read factor.
Check astronomy homework
Verify area-ratio exercises directly from two diameters without separately calculating both circular areas.
FAQ
What formula does the calculator use?
It uses (objective diameter / pupil diameter) squared. This equals the ratio of circular areas because pi and the radius conversion cancel.
Do both diameters need to be in millimetres?
No. You may use millimetres, centimetres, inches, or another length unit, but both inputs must use the same unit.
Does the factor include optical transmission losses?
No. It is the ideal geometric area ratio and does not account for obstruction, reflectivity, absorption, filters, eyepieces, detectors, or atmospheric effects.
How much more light does a 100 mm telescope collect than the eye?
About 204.08 times, compared with a 7 mm dark-adapted pupil. The factor is the objective diameter divided by the pupil diameter, squared, because collecting area grows with the square of the diameter.
Why does doubling the aperture give four times the light?
Light collected depends on the area of the lens or mirror, and the area of a circle grows with the square of its diameter. Twice the width therefore means four times the collecting area.
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/astro/light-gathering-power \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"objective_diameter":100,"pupil_diameter":7}'const res = await fetch("https://api.kit.forhosting.com/astro/light-gathering-power", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"objective_diameter": 100,
"pupil_diameter": 7
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/astro/light-gathering-power",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"objective_diameter": 100,
"pupil_diameter": 7
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/astro/light-gathering-power", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"objective_diameter":100,"pupil_diameter":7}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"objective_diameter":100,"pupil_diameter":7}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/astro/light-gathering-power", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"objective_diameter": 100,
"pupil_diameter": 7
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "astro.light_gathering_power",
"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
What the light-gathering factor means
The response includes both light_gathering_power and factor with the same numeric value so API consumers can use an explicit scientific name or a compact presentation field. It also echoes the accepted diameters, identifies the human eye as the reference, and includes the formula used.
How to enter objective and pupil diameters
Enter objective_diameter for the clear diameter of the telescope objective lens or primary mirror, and pupil_diameter for the eye pupil used as the comparison.
Using the result for telescope comparisons
The browser calculation is free, and an automated successful API request costs $0.002.
Integration use cases
Build equipment comparison tables
Generate deterministic light-gathering factors for telescope catalogs, lessons, observing tools, or automated test fixtures.
Technical questions
Why must pupil diameter be positive?
A zero or negative pupil has no valid comparison area and would make the diameter ratio undefined or physically meaningless, so the request returns invalid_input.
How much does the API calculation cost?
A successful API request costs $0.002. You can also run the same deterministic calculation free in your browser on this page.