How this tool counts
Enter a Gregorian UTC date and time. Julian Day integers turn over at noon. January 1, 2000 at 12:00 UTC is JD 2451545.0.
When to use it
Output is rounded to six decimal places, but input precision is one minute. This is a UTC-based mapping, not TT/TDB, leap-second modelling or a Julian-calendar conversion.
Sources & further checking
Questions before you start
How do I convert a Gregorian UTC date and time to Julian Day?
Enter the Gregorian date and its UTC clock time. The calculator maps that timestamp to a Julian Day value. If your original record is a local time, convert it to UTC first; entering local clock digits in a UTC field represents a different instant.
Why does the Julian Day integer change at noon?
The continuous Julian Day convention used here has its integer boundary at noon. For example, January 1, 2000 at 12:00 UTC maps to JD 2451545.0; midnight carries a half-day offset. This is a counting boundary, separate from the midnight boundary of ordinary civil dates.
Do six decimal places mean the Julian Day input is accurate to seconds?
No. The output is rounded to six decimal places, but the input clock has one-minute resolution. Extra displayed digits cannot create precision missing from the record. This page also does not convert UTC to the TT or TDB astronomical time scales or model leap seconds.
Can this Julian Day tool convert an old Julian-calendar birthday?
No. It accepts Gregorian UTC dates and outputs a continuous day count. The Julian calendar is a different system of year, month and day labels. Establish the original record’s calendar and region before converting a historical birthday; the similar names do not make the inputs interchangeable.