Smekys
Ad Space

Julian Date Calculator

Convert any Gregorian calendar date and UTC time to the astronomical Julian Date (JD), plus Modified Julian Date (MJD) and days since the J2000 epoch.

Enter Values

yyyy

Four-digit year in the Gregorian calendar. Astronomical year 0 = 1 BC.

mm

1 = January, 12 = December.

dd

Day of the month, 1 through 31 (leap-year aware).

h

Coordinated Universal Time hour. Julian days start at noon, so 12:00 UT gives a whole .5 offset.

min

Minutes past the hour in Universal Time.

Result

Julian Date (JD)
2,461,338
Modified Julian Date (MJD)
61,337.5
Days Since J2000.0
9,793
Fractional Day Past Noon
0

Most of the world marks time with a messy mix of months, leap years, and calendar reforms. Astronomers, spacecraft engineers, and satellite operators need a clock that never repeats itself, so they count days as a single running number: the Julian Date. This calculator converts any Gregorian calendar date and Universal Time into that continuous count, and also gives you the Modified Julian Date and the elapsed time since the standard J2000.0 epoch.

Enter a year, month, day, and the UTC hour and minute, and the Julian Date updates instantly. Because a Julian day begins at noon rather than midnight, a date at 12:00 UT lands on a clean .5 fractional value — which is why the output is so easy to diff against a star catalog or an orbit report.

How to Use

  1. Type the Year you want. Use four digits for modern dates (for example 2026). Astronomical year numbering treats year 0 as 1 BC, so the count extends backward without a gap.
  2. Set the Month from 1 (January) to 12 (December).
  3. Enter the Day of the month. The calculator is leap-year aware, so February 29 is accepted only in years that are actually leap.
  4. Choose the Hour (UT) and, optionally, the Minute (UT). These are in Coordinated Universal Time, not your local time zone. If you leave the hour at the default 12, you get the noon Julian Date directly.
  5. Read the result card. Julian Date (JD) is the main number. Modified Julian Date (MJD) subtracts 2,400,000.5 to give a smaller, modern-friendly number, and Days Since J2000.0 tells you how far the input sits from the standard reference epoch.

If you are matching an ephemeris or an observation log, always convert your local clock to UTC first — a one-hour time-zone mistake shifts the Julian Date by 0.04167, which is enough to misalign a star position.

The Julian Date Formula

The engine uses the Fliegel–Van Flandern integer algorithm, the same conversion published by the U.S. Naval Observatory and used by astronomy libraries such as Skyfield. For a Gregorian date Y, M, D:

  • a = (14 − M) / 12 (integer division)
  • y = Y + 4800 − a
  • m = M + 12a − 3
  • JD(noon) = D + (153m + 2)/5 + 365y + y/4 − y/100 + y/400 − 32045

All divisions are integer divisions, which keeps the arithmetic exact on dates ranging far into the past and future. The time of day is then added as a simple fraction:

JD = JD(noon) + (hour − 12)/24 + minute/1440

The epoch — day count zero — is 12:00 UT on 1 January 4713 BC in the proleptic Julian calendar, a reference chosen by Joseph Scaliger in 1583 so that all known historical and astronomical events fall on a positive day number.

Precision. The integer day count (JDN) is exact. The fractional day is rounded to four decimal places (about 8.6 seconds), and JD, MJD, and Days Since J2000 are each rounded to four decimals as well, so every output line in the result card shares the same precision and never shows a long floating-point tail.

Why Julian Date Instead of a Normal Calendar Date?

A calendar date like "October 24, 2026" tells a human what happened, but it is a nightmare for a computer. The difference between two dates requires knowing leap years, month lengths, and which calendar reform applied. A Julian Date has none of that: subtracting two JDs gives the elapsed days directly, to any precision you want.

This is why JD appears everywhere behind the scenes:

  • Astronomy — star positions, planet ephemerides, and telescope scheduling are all tabulated against JD.
  • Space operations — spacecraft events and satellite orbits are logged in JD or MJD.
  • History and geology — deep-time timelines use the same continuous-count idea.

The fractional part carries the time of day. At noon UT the fraction is 0.0; at midnight it is exactly 0.5, meaning 50% of the Julian day has elapsed since the previous noon. At 18:00 UT it is 0.25, and at 06:00 UT it is −0.25. That noon convention is the single most common source of confusion, so the default hour of 12 is chosen to make the fraction zero.

Modified Julian Date

The full Julian Date for a modern date is around 2,460,000 — a large number that wastes digits and invites typographical errors. In 1957, astronomers introduced the Modified Julian Date:

MJD = JD − 2,400,000.5

This resets the clock so that MJD 0.0 falls at midnight on 17 November 1858, and it also moves the day boundary to midnight, which is more intuitive for daily operations. Satellite engineers usually report MJD rather than JD for exactly that reason. The calculator shows both so you can match either kind of document.

Examples

Example 1 — The reference epoch. Set year 2000, month 1, day 1, hour 12, minute 0. The Julian Date is 2451545.0, MJD is 51544.5 (because 2451545.0 − 2400000.5 = 51544.5), and Days Since J2000.0 is exactly 0.0. This single instant — 1 January 2000 at noon UT — is the standard anchor (called J2000.0) from which nearly all modern star coordinates are measured.

Example 2 — A modern date at noon. With year 2026, month 10, day 24, hour 12, minute 0, the calculator returns a Julian Date of 2461338.0 and an MJD of 61337.5. Because the hour is 12, the fractional day is 0.0 — the cleanest value to write into an observation log. If you instead set the hour to 18 and minute to 30, the fractional day becomes (18−12)/24 + 30/1440 = 0.2708, shifting JD to 2461338.27 and MJD to 61337.77.

Example 3 — Scheduling against an orbit report. Suppose a satellite pass is listed as MJD 61337.25 on your mission sheet. That MJD corresponds to 06:00 UT on 2026-10-24 (because 61337.25 − 61337.0 = 0.25 day past midnight, i.e. 06:00), not 18:00, because MJD days start at midnight. Convert it back through this calculator — year 2026, month 10, day 24, hour 6, minute 0 — to confirm the local clock time before scheduling.

FAQ

What is a Julian Date?

A Julian Date is the continuous count of days since noon UT on 1 January 4713 BC. Unlike a calendar date, it never repeats and has no leap-year gaps, so the difference between two Julian Dates is simply their subtraction. It is the standard time base used in astronomy and space operations.

Why does the Julian day start at noon?

Julius Scaliger chose noon so that astronomers of the 16th century would not have to change the date in the middle of a night's observing run. The convention stuck, and it is why a date at midnight carries a .5 fractional part rather than a whole number.

What is the difference between JD and MJD?

The Modified Julian Date is defined as MJD = JD − 2,400,000.5. It produces smaller numbers and moves the day boundary to midnight, which is more convenient for everyday operations. Astronomy papers often use JD, while satellite and mission-control teams usually prefer MJD.

How do I convert local time to a Julian Date?

First convert your local clock time to Coordinated Universal Time (UTC) by subtracting your time-zone offset, and apply daylight-saving corrections if they apply. Then enter the resulting UTC year, month, day, hour, and minute into this calculator. Entering local time directly without conversion will shift the JD by your time-zone offset.

What is the J2000.0 epoch?

J2000.0 is the reference instant 1 January 2000 at 12:00 UT, which equals Julian Date 2451545.0 and MJD 51544.5 (since MJD = JD − 2400000.5). Modern star catalogs, orbital elements, and reference frames are defined with coordinates valid at this instant, so the "Days Since J2000.0" output tells you how far your event sits from that standard anchor.

Does this calculator handle leap years and BC dates?

Yes. The Fliegel–Van Flandern integer algorithm is leap-year aware and uses the proleptic Gregorian calendar, so it correctly handles February 29 in leap years and every month-length variation. The input range spans year 1583 (the year Joseph Scaliger first published the Julian period) through year 3000.

Disclaimer

This Julian Date calculator is provided for informational purposes only and does not constitute astronomical, legal, or scheduling advice. Results are based on the Gregorian calendar and Universal Time; historical dates before the widespread adoption of the Gregorian calendar use the proleptic Gregorian convention and may not match older historical reconstructions. Always verify critical times against the authoritative ephemeris, star catalog, or mission document you are working with before relying on them.

Related Calculators

Disclaimer

Results are estimates for illustration only. Verify important figures independently.