Scale factor from redshift calculator
Light with a redshift of 3 left its source when the universe had a scale factor of 0.25, a quarter of its present size. Enter any redshift above -1 to switch between z and scale-factor notation. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Z
- 3
- Redshift
- 3
- Scale factor
- 0.25
This scale factor from redshift calculator converts a cosmological redshift z into the dimensionless cosmic scale factor at the time the observed light was emitted. Enter a finite redshift greater than negative one and receive the original redshift, the computed scale factor, and the formula used. The calculation is deterministic, requires no cosmological parameters, and runs without network access, random values, or time-dependent data.
What the scale factor tells you
The scale factor describes how large the universe was, relative to today, when a piece of light set off. By convention its present value is one. Light that arrives with a redshift of z left its source when the scale factor was one divided by one plus z. A redshift of 3 therefore means a scale factor of 0.25: typical distances between galaxies, scaled by that factor, were a quarter of their present size. The result is a pure ratio, so it carries no unit at all, not metres, seconds or parsecs.
When to use it and common mistakes
It is handy when reading simulation snapshots, lecture notes, galaxy catalogues or papers that switch between redshift and scale-factor notation. You do not need the Hubble constant, matter density or dark energy for this identity; those only matter when you turn redshift into a distance or a lookback time. A common mistake is reading a small negative redshift as cosmic expansion, when it may simply come from local motion. Values of -1 or below are rejected, because they fall outside the range where the relation makes sense.
What the cosmic scale factor describes
The cosmic scale factor is a dimensionless way to describe the relative size of the universe at different epochs in a homogeneous expanding-universe model. Light observed with a positive cosmological redshift was emitted when the scale factor was smaller. The result has no physical unit because it is a ratio, not a distance, age, speed, or wavelength.
This calculator deliberately reports that compact relationship without introducing a Hubble constant, matter density, dark-energy density, or curvature parameter. Those parameters are necessary for turning redshift into lookback time or distance, but they are not needed for the scale-factor identity itself. The output therefore remains useful across cosmological models that share the standard definition of redshift and the normalization a today equals one.
It is especially convenient when reading simulation snapshots, lecture notes, galaxy catalogues, or papers that alternate between z and a notation and you need a quick, auditable conversion between them.
What you can do with it
Convert simulation snapshot labels
Turn snapshot redshifts into normalized scale factors for tables, plots, or simulation configuration checks.
Normalize catalogue epochs
Add a dimensionless scale-factor column to redshift-based records before later model-dependent analysis.
FAQ
Is the scale factor dimensionless?
Yes. It is a normalized ratio describing relative cosmic expansion, so it has no physical unit.
What scale factor does a redshift of 1 give?
One half. The same rule gives one quarter at a redshift of 3 and one tenth at a redshift of 9, while a redshift of zero gives exactly one, today's value.
What happens with a negative redshift?
Values between -1 and zero give a scale factor above one, which mathematically describes a future, larger universe. A measured negative shift, though, may simply come from local motion rather than cosmic expansion.
Why is a redshift of -1 or less rejected?
At -1 the formula would divide by zero, and below it the result would fall outside the physical range of this relation. The calculator rejects those values instead of returning a misleading scale factor.
Do I need the Hubble constant or other cosmological values?
No. The scale factor follows from the redshift alone. The Hubble constant, matter density or dark energy are only needed when you convert redshift into a distance or a lookback time.
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/scale-factor-from-redshift \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"z":3}'const res = await fetch("https://api.kit.forhosting.com/astro/scale-factor-from-redshift", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"z": 3
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/astro/scale-factor-from-redshift",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"z": 3
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/astro/scale-factor-from-redshift", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"z":3}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"z":3}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/astro/scale-factor-from-redshift", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"z": 3
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "astro.scale_factor_from_redshift",
"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
It applies the standard relation a = 1/(1 + z), using the present-day scale factor as one.
What the cosmic scale factor describes
By convention, cosmologists usually normalize the present-day value to a = 1. The direct relationship is a = 1/(1 + z), so redshift one corresponds to a scale factor of one half, redshift three corresponds to one quarter, and redshift nine corresponds to one tenth. These values mean that representative comoving separations scaled by a were respectively half, one quarter, or one tenth of their present normalized size at emission.
How to enter redshift and interpret the result
Negative redshifts between negative one and zero produce scale factors above one. Mathematically, that interval can describe a future expansion state under the same normalization, although a measured negative wavelength shift may instead arise from local peculiar motion and should not automatically be interpreted as cosmic expansion. Values below negative one are rejected because they lie outside the physical domain of this relationship. If you use the result in a pipeline, treat it as a numeric ratio and avoid attaching metres, seconds, parsecs, or any other unit. Provide z as a finite number, or use the redshift alias when calling the API. Positive values describe the usual cosmological redshift domain: z = 0 gives a = 1, while progressively larger z values produce progressively smaller positive scale factors. Exactly z = -1 is also rejected: its denominator, 1 + z, equals zero, so it cannot yield a finite JSON number. The response includes redshift, scale_factor, a dimensionless marker, and the formula string. For example, an input of z = 3 returns scale_factor = 0.25 because one divided by four is one quarter. No rounding is imposed on the JavaScript number, so exact binary-representable results remain exact while repeating decimal values follow standard IEEE-754 representation. A successful API request costs $0.002; the browser version uses the same pure calculation locally.
Checks, limitations, and good scientific practice
A reliable conversion starts by checking what kind of redshift you have. Each of those quantities needs additional assumptions or equations, and several depend on a selected cosmological model. Keep adequate numeric precision if you later subtract nearby epochs, because very large redshifts produce small scale factors and downstream rounding can become significant. Use the calculator as a focused algebraic conversion, then choose a dedicated cosmology solver if your scientific question requires distances, times, expansion rates, or uncertainty propagation. This calculator assumes z is the cosmological redshift that satisfies 1 + z = 1/a when the current scale factor is normalized to one. It does not infer whether a catalogue value includes peculiar velocity, gravitational redshift, instrumental calibration error, or a heliocentric correction. It also does not calculate the age of the universe, comoving distance, luminosity distance, recession velocity, or conformal time. When validating a result manually, add one to z and take the reciprocal: for z = 4, 1 + z is 5 and a is 0.2. You can reverse the check with z = 1/a - 1. The implementation rejects missing values, nonnumeric text, infinities, NaN, arrays, and inputs at or below the singular boundary as clear invalid_input errors.
Integration use cases
Check astronomy coursework
Verify hand calculations of a = 1/(1 + z) with a deterministic result and an explicit formula.
Technical questions
What is the formula for scale factor from redshift?
Use a = 1/(1 + z), assuming the present-day scale factor is normalized to a = 1.
What does redshift z = 3 give?
It gives a = 1/(1 + 3) = 0.25, meaning the normalized scale factor at emission was one quarter.
Why is z = -1 rejected?
At z = -1 the denominator 1 + z is zero, so the formula is singular and has no finite result. Values below -1 are outside the accepted domain as well.
How much does the API calculation cost?
A successful API request costs $0.002. The in-browser calculator runs locally for free.