ECLIPSE PREDICTOR
SOLAR ECLIPSE PATHS · 1900–2200
TOTAL
Date (UTC)
Greatest eclipse
Magnitude
Gamma
Central duration
Max location
Sun altitude
Path via astronomy-engine GeoidIntersect (NASA/Espenak parity)

VIEW

OVERLAYS

YOUR LOCATION

PLAN PRO

These planning tools are part of the desktop app — get Eclipse Predictor on itch.io. The globe, paths, and viewpoint durations stay free here.

DETAIL

LEGEND

Path of totality
Path of annularity
Greatest eclipse
Partial-eclipse zone
Sub-solar point
Your viewpoint (click the globe)

LEGEND

Path of totality
Path of annularity
Greatest eclipse
Partial-eclipse zone
Sub-solar point
Your viewpoint (click the globe)
GENERATING ECLIPSE CATALOG
1900 — 2200
0 / 0 new moons checked

2026 & 2027 Solar Eclipse Paths

Step through every solar eclipse from 1900 to 2200. Paths of totality are computed with astronomy-engine (sub-arcsecond ephemeris) and drawn on a rotatable 3D Earth.

First time here? This site is a free game & sim collection by one engineer — while you wait for totality, try today's Wordform, Drift, or daily Sudoku, and see the 2026/2027 viewing guide for trip planning.

Upcoming total eclipses

What you can explore

How the model works — the real astronomy

Every eclipse position in this tool comes from the open-source astronomy-engine library (astronomy.browser.min.js), which implements the VSOP87 / high-precision lunar theory used for professional ephemerides. Nothing here is a hand-rolled Kepler approximation: the Sun's geocentric vector is read from Astronomy.GeoVector(Sun, t, aberration=true) and the Moon's from Astronomy.GeoMoon(t), and eclipses are located with the library's own SearchGlobalSolarEclipse / NextGlobalSolarEclipse. The catalog spans 1900–2200, matching NASA's Five Millennium Canon of Solar Eclipses (Espenak & Meeus).

Shadow cone & geoid intersection

The path is built by the MoonShadow → GeoidIntersect pipeline — the same geometry astronomy-engine uses internally for global eclipse search, not the classical Besselian fundamental-plane elements. In outline:

Total vs annular classification

Whether the eclipse is total or annular is decided by the umbral cone radius at the actual surface intersection point, not at closest approach to Earth's centre. Using the Moon's polar radius (1736 km, the value astronomy-engine uses for this test), the code evaluates k_surface = R_sun − (1+u)·(R_sun − 1736) and classifies:

The shadow-axis miss-distance is reported as gamma, γ = r / R_earth in Earth radii; when the axis misses the globe entirely the event is partial-only.

Topocentric magnitude

Eclipse magnitude is the ratio of the Moon's apparent angular radius to the Sun's, mag = θ_moon / θ_sun. Crucially it uses topocentric distances — the Sun and Moon distances as seen from the greatest-eclipse ground point via Astronomy.Equator(..., observer) — because a surface observer sits about one Earth radius closer to the Moon than the geocentre, and a geocentric figure understates magnitude by roughly 1.5–1.7%.

The positions are sub-arcsecond and the ground path is sub-kilometre for 1900–2200, but this is a visualisation, not a substitute for official predictions: for mission-critical timing, cross-check eclipse.gsfc.nasa.gov.

Related

Discussion

Sign in with GitHub to share strategies, ask questions, or report a bug.