Converter Console
Calendar Date to JDN

JDN to Calendar Date
Astronomical Output
Julian Day Number (JDN)
2451545
Fractional JD: 2451545.0000
Modified Julian Day (MJD)
51544.5000
MJD = JD - 2400000.5 (midnight-based epoch)
Reduced Julian Day (RJD)
51545.0000
RJD = JD - 2400000
Calendar System Applied
Gregorian
January 1, 2000 AD at 12:00:00 UTC
Telemetry and Reference
Current System JD (Live)
calculating...
Days from J2000.0 Epoch
0.0000
J2000.0 = JD 2451545.0 (Jan 1.5, 2000 TT)
Days from Unix Epoch
10957.5000
Unix Epoch = JD 2440587.5 (Jan 1, 1970 00:00 UTC)
Epoch origin: Jan 1, 4713 BC noon UTC (Julian)
J2000.0 reference: JD 2451545.0
MJD epoch: Nov 17, 1858 (JD 2400000.5)
Key Terms Explained
Julian Day Number (JDN)
A continuous integer count of days since January 1, 4713 BC (Julian calendar) at noon UTC. Astronomers use it to compute time intervals without calendar ambiguity.
Modified Julian Day (MJD)
MJD = JD - 2400000.5. Created in 1957 for satellite tracking. Uses 5 digits instead of 7, and moves the day boundary from noon to midnight to match civil dates.
Reduced Julian Day (RJD)
RJD = JD - 2400000. A compact alternative to JD that retains the noon-based day boundary. Produces 5-digit values for modern dates while preserving the traditional astronomical convention.
Gregorian Calendar
The civil calendar introduced by Pope Gregory XIII in October 1582 to correct drift in the Julian calendar. Refines the leap year rule: century years must be divisible by 400 to be leap years.
Proleptic Calendar
Applying a calendar system retroactively before its official adoption. The Proleptic Gregorian Calendar uses Gregorian rules for all historical dates, even prior to 1582. ISO 8601 uses this standard.
Heliocentric
Sun-centered. In astronomical contexts, heliocentric time corrections account for light travel time from a distant body to the Sun, rather than to Earth. Julian Day forms the basis for these reductions.
Epoch
A fixed reference point in time from which other times are measured. J2000.0 (JD 2451545.0) is the standard modern astronomical epoch, defined as January 1, 2000 at 12:00 Terrestrial Time.
Ephemeris
A table giving the computed positions of celestial bodies at regular time intervals. Ephemerides use Julian Dates as their time coordinate, enabling precise interpolation between tabulated positions.

The Complete Guide to Julian Day Numbers and Astronomical Date Conversion

If you are working with astronomical data, historical records, satellite ephemerides, or any scientific dataset that spans centuries, you have likely encountered Julian Day Numbers. This guide explains what they are, how the conversion mathematics works, and how to use this tool confidently for any date in recorded history.

How to Use This Tool

The Converter Console (left panel) accepts input in both directions. To convert a calendar date to a Julian Day Number, enter the year, month, day, and optional UTC time. The year field uses astronomical year numbering: year 0 represents 1 BC, year -1 represents 2 BC, and so on. To reverse the conversion from a JDN back to a calendar date, enter any Julian Day Number (integer or fractional) into the JDN field at the bottom of the console.

The calendar system toggle controls which formula is applied to your input. Auto mode matches historical reality: the Julian calendar formula is used before October 15, 1582, and the Gregorian formula from that date onward. Proleptic Gregorian applies Gregorian rules to all dates regardless of era, which is the mode used by ISO 8601, SQL databases, and most programming language date libraries. Julian mode applies the older Caesar-era rules to all dates.

The Mathematics Behind JDN Conversion

The standard algorithm for converting a calendar date (Y, M, D) to a Julian Day Number uses the Meeus-Jones formula from Jean Meeus's Astronomical Algorithms. The procedure: if M (month) is 1 or 2, set Y = Y - 1 and M = M + 12. For Gregorian dates, compute A = floor(Y / 100) and B = 2 - A + floor(A / 4). For Julian dates, set B = 0. Then: JDN = floor(365.25 x (Y + 4716)) + floor(30.6001 x (M + 1)) + D + B - 1524. This formula is verified to produce JDN = 0 for January 1, 4713 BC (Julian) at noon, and JDN = 2451545 for January 1, 2000 (Gregorian) at noon.

Fractional Julian Dates represent exact moments in time. Because the astronomical day begins at noon UTC, a time of 12:00 UTC corresponds to a fractional offset of exactly 0.0 from the integer JDN. Midnight (00:00 UTC) preceding that noon corresponds to JD = JDN - 0.5. A time of 18:00 UTC gives JD = JDN + 0.25. This tool computes the full fractional JD for any entered time and derives MJD and RJD from it automatically. The live clock in the telemetry panel shows the current system time expressed as a continuous fractional JD, updated every second.

The 1582 Gregorian Calendar Reform

In October 1582, Pope Gregory XIII introduced the Gregorian calendar to correct roughly 10 days of drift that had accumulated in the Julian calendar since the Council of Nicaea in AD 325. The reform skipped 10 days: October 4, 1582 (Julian) was followed directly by October 15, 1582 (Gregorian). Dates from October 5 to 14, 1582 simply did not exist in the civil calendar of countries that adopted the reform immediately.

Different nations adopted the Gregorian reform at different times. England and its colonies switched in 1752. Russia kept the Julian calendar until 1918. For this reason, historical research often requires specifying which calendar a given date refers to, and the Julian Day Number is invaluable precisely because it is calendar-agnostic: two historians using different calendar systems can both refer unambiguously to JD 2299161 and know they mean the same moment in time.

Leap Year Rules: Julian vs. Gregorian

The Julian calendar adds a leap day every 4 years without exception, giving a mean year of exactly 365.25 days. The Gregorian calendar refines this: a year is a leap year if it is divisible by 4, except for century years, which must also be divisible by 400 to qualify. So 1900 was not a leap year (100 is not divisible by 400), but 2000 was (divisible by 400). This gives a Gregorian mean year of 365.2425 days, much closer to the true tropical year of approximately 365.24219 days. The JDN calculation in this tool automatically applies the correct leap year rule based on the calendar system selected.

Why Astronomers Use Julian Day Numbers

Astronomers need to calculate precise time intervals between observations that may be separated by centuries. Calendar arithmetic is notoriously awkward: months have different lengths, leap years appear at irregular intervals (especially at century boundaries), different cultures used different calendar systems, and the historical calendar switch of 1582 creates an ambiguous gap. JDNs eliminate all of these complications. The interval between any two events is simply JDN2 - JDN1. Modern ephemerides (tabulations of planetary positions), satellite tracking databases, and telescope scheduling software all store times as Julian Dates for exactly this reason.

FAQ: Julian Day Numbers and Astronomical Date Conversion
What is a Julian Day Number and why do astronomers use it? +

A Julian Day Number (JDN) is a continuous integer count of days since January 1, 4713 BC (Julian calendar) at noon UTC. Astronomers use it because it provides a single, unambiguous integer for any date in history, eliminating the confusion of different calendar systems, month lengths, and leap year rules. It makes calculating the number of days between two events as simple as subtracting two integers.

How does JDN differ from the Julian Calendar? +

The Julian Day Number (JDN) is a continuous astronomical day count invented by Joseph Scaliger in 1583. The Julian Calendar is a civil calendar system introduced by Julius Caesar in 45 BC, which uses a 365.25-day year with a leap year every 4 years. The two systems are unrelated despite sharing the name Julian. The JDN system counts elapsed days; the Julian Calendar is a way of naming specific dates. JDNs can represent dates in either the Julian or the Gregorian calendar system.

Why do astronomers start the day at noon? +

Historically, astronomers worked through the night making observations. If the civil day (midnight to midnight) were used, a single observing session would span two calendar dates, creating ambiguous record-keeping. By starting the astronomical day at noon, a full night of observation from dusk to dawn falls entirely within one Julian Date. This convention was established in the 19th century and remains in use so that historical astronomical records remain consistent.

What is the difference between Modified Julian Day and standard Julian Day? +

The Modified Julian Day (MJD) was introduced by the Smithsonian Astrophysical Observatory in 1957 for satellite tracking. MJD = JD - 2400000.5. Subtracting 2400000.5 reduces the number of digits required (modern MJDs are 5-digit numbers vs. 7-digit JDs) and shifts the day boundary from noon to midnight, aligning MJD with civil calendar dates. The Reduced Julian Day (RJD) applies a similar shortcut where RJD = JD - 2400000, retaining the traditional noon day boundary.

How does this tool handle the historical calendar transition of 1582? +

This tool offers three calendar modes. In Auto mode, dates before October 15, 1582 use the Julian calendar formula and dates from October 15, 1582 onward use the Gregorian formula, matching the historical reform by Pope Gregory XIII. In Proleptic Gregorian mode, the Gregorian rules are applied to all dates even before 1582, which is the standard used by ISO 8601 and most modern software. In Julian mode, the Julian calendar rules are applied to all dates. The 10-day gap from October 5 to 14, 1582 is flagged as invalid since those dates did not exist in either system.

This tool performs purely mathematical calendar conversions using published astronomical algorithms (Meeus-Jones formula). Results are intended for reference and educational use. For mission-critical scientific applications, cross-verify with a peer-reviewed ephemeris or dedicated astronomical software package.