ForHosting KIT · Developer Utilities

Star trail length calculator

The star trail length calculator estimates how far a celestial object appears to move during an exposure when the camera or telescope does not track the sky.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the exposure duration in seconds and the object's declination, and it returns the ideal angular trail length in degrees. The calculation uses Earth's mean sidereal rotation rate and the cosine projection for declination, making it useful for planning night-sky photographs, comparing exposure choices, and checking expected motion across an imaging sensor.

What the calculated trail length represents

Earth turns once relative to the distant stars in a sidereal day, so stars appear to travel across a fixed camera's field throughout an exposure. The calculator reports the angular length of that ideal apparent motion in degrees. A target on the celestial equator traces the largest circle and receives the full sidereal rotation rate. As declination approaches either celestial pole, its circle around the pole becomes smaller, so its angular trail becomes shorter for the same exposure. Positive and negative declinations at equal magnitudes produce equal lengths because the cosine projection is symmetric. This result describes angular sky motion, not a distance measured in pixels and not the object's physical movement through space. Converting the answer to a sensor length requires the image scale, usually expressed in arcseconds per pixel. The model assumes a stationary, perfectly fixed optical system and ideal sidereal motion. Tracking, polar alignment error, atmospheric refraction, field rotation, lens distortion, and a star's proper motion are outside its scope.

How exposure and declination enter the formula

The calculation uses L = t × (360 / 86164.0905) × cos(δ). Here, L is angular trail length in degrees, t is exposure duration in seconds, 86164.0905 seconds is the adopted mean sidereal day, and δ is declination converted from degrees to radians for the cosine. Exposure scales the answer directly: doubling the exposure doubles the ideal trail length. Declination supplies the geometric projection: zero degrees keeps the complete rate, 60 degrees reduces it by half, and either pole reduces it to zero in the ideal model. The calculator accepts finite declinations from -90 through +90 degrees, inclusive. Exposure must be finite and cannot be negative, because a negative duration has no physical meaning; an exposure of zero is valid and returns a zero-length trail. Results are rounded to twelve decimal places for stable browser and API output. The rotation-rate field is also returned so the adopted constant is explicit and results can be audited or reused in a larger imaging calculation.

Using the result for astrophotography planning

Use the angular length to compare candidate exposure times before a fixed-tripod photograph or an intentionally trailed composition. To estimate the trail in arcseconds, multiply the returned degree value by 3,600. If the camera system's plate scale is known in arcseconds per pixel, divide that arcsecond length by the plate scale to estimate the trail across the sensor in pixels. This helps assess whether motion will remain below a chosen sharpness tolerance or become visibly elongated. Remember that the formula depends only on exposure and declination; focal length, pixel pitch, and sensor dimensions do not change the angular motion, though they strongly affect how that motion appears in an image. Very wide lenses may make short trails inconspicuous, while long focal lengths reveal the same angular displacement across many more pixels. For tracked mounts, the result represents the motion the mount is intended to cancel rather than the residual trail. Each automated API calculation costs $0.002, while the deterministic calculation can also run locally in the browser.

Choose a fixed-tripod exposure

Compare trail lengths for several exposure durations at a target's declination before taking an untracked night-sky photograph.

Plan intentional star trails

Estimate the angular arc accumulated by stars in a single frame when composing a deliberate star-trail image.

Convert motion to sensor pixels

Combine the angular result with an imaging system's arcseconds-per-pixel scale to estimate trail length across the detector.

What formula does the calculator use?

It uses trail length = exposure seconds × (360 / 86164.0905) × cos(declination), with the resulting angular length reported in degrees.

Why does declination change star trail length?

Stars near the celestial equator trace larger apparent circles than stars near a celestial pole, so the cosine of declination projects the sidereal rotation rate onto a smaller path.

Can exposure time be zero?

Yes. A zero-second exposure is valid and returns a trail length of zero; a negative exposure returns an invalid-input error.

How do I convert the result to arcseconds or pixels?

Multiply degrees by 3,600 to obtain arcseconds, then divide by your imaging system's arcseconds-per-pixel scale to estimate pixels.

Does the calculation account for a tracking mount?

No. It gives ideal apparent sidereal motion for a fixed system. A tracking mount attempts to cancel that motion, and its residual errors require a separate model.

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.

POSThttps://api.kit.forhosting.com/astro/star-trail-length

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.

curl -X POST https://api.kit.forhosting.com/astro/star-trail-length \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"exposure_seconds":120,"declination_deg":30}'
{
  "exposure_seconds": 120,
  "declination_deg": 30
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "astro.star_trail_length",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →