Hebrew Calendar Converter
Convert between Gregorian and Hebrew calendar dates with Jewish holiday awareness. Enter values for instant results with step-by-step formulas.
Calculator
Adjust values & calculateFormula
The conversion uses the Julian Day Number as an intermediary. First, the Gregorian date is converted to a JDN, then the JDN is converted to a Hebrew date using the molad (new moon) calculations and postponement rules (dehiyot) of the Hebrew calendar.
Last reviewed: December 2025
Worked Examples
Example 1: New Year 2025 Conversion
Example 2: Spring Date Conversion
Background & Theory
The Hebrew Calendar Converter applies the following established principles and formulas. Date and time calculations underpin a vast range of applications from financial settlement to scheduling and age verification. The complexity arises because civil timekeeping uses irregular units: months have 28, 29, 30, or 31 days; years have 365 or 366 days; hours, minutes, and seconds use base-60 arithmetic; and time zones introduce offsets ranging from -12:00 to +14:00 relative to UTC. The Gregorian calendar's leap year rule is a compound condition: a year is a leap year if it is divisible by 4, except for century years, which must be divisible by 400. Thus 1900 was not a leap year but 2000 was. This rule keeps the calendar synchronized with the solar year to within about 26 seconds per year. For algorithmic date calculations, the Julian Day Number provides a continuous integer count of days since January 1, 4713 BCE, eliminating the irregularity of calendar months and making interval arithmetic straightforward. The Unix epoch, by contrast, counts seconds since 00:00:00 UTC on January 1, 1970, and is the basis of POSIX time used in most computing systems. ISO 8601 standardizes date and time representation as YYYY-MM-DD and combined datetime as YYYY-MM-DDTHH:MM:SS±HH:MM, ensuring unambiguous machine-readable interchange across locales that would otherwise differ in day/month/year ordering. Business day calculation requires excluding weekends and, optionally, a jurisdiction-specific list of public holidays. Duration calculations expressed in years, months, and days must account for the variable length of months, making them non-commutative: the interval from January 31 to February 28 is different from the interval from February 28 to March 31. Age calculation algorithms must handle the edge case of birthdays on February 29 and ensure that a person born on December 31 is not counted as one year older on January 1 of the following year until the clock passes midnight. Zeller's Congruence provides a closed-form formula to determine the day of the week for any Gregorian or Julian calendar date using only integer arithmetic.
History
The history behind the Hebrew Calendar Converter traces back through the following developments. The need to track time and predict astronomical events gave rise to calendrical systems independently across many civilizations. The Babylonians, around 2000 BCE, developed a lunisolar calendar with 12 months of alternating 29 and 30 days, inserting an intercalary month periodically to keep pace with the solar year. They also divided the day into 24 hours and the hour into 60 minutes, a sexagesimal convention that persists in every modern clock. The Egyptian civil calendar used 12 months of exactly 30 days plus five epagomenal days, totaling 365 days. Though simple for administrative purposes, it drifted against the solar year by one day every four years. Julius Caesar, advised by the Egyptian astronomer Sosigenes, reformed the Roman calendar in 45 BCE. The Julian calendar introduced a 365-day year with a leap day every four years, a system that served Europe for over sixteen centuries. By the 16th century, the accumulated error of the Julian calendar had shifted the spring equinox ten days from its ecclesiastically mandated date, disrupting the calculation of Easter. Pope Gregory XIII commissioned the calendar reform that bears his name, and the Gregorian calendar was introduced in Catholic countries in October 1582. The transition required skipping ten days: October 4 was followed by October 15. Protestant and Orthodox countries adopted the reform slowly; Britain and its colonies switched in 1752, Russia not until 1918, and Greece in 1923. The expansion of railways in the 1840s created an urgent practical problem: each city operated on its own local solar time, making train timetables impossible to coordinate. British railways adopted Greenwich Mean Time as a standard in 1847. The International Meridian Conference of 1884 in Washington formalized the prime meridian at Greenwich and established the global framework of 24 time zones. Daylight saving time was first adopted nationally during World War I to reduce coal consumption. The development of atomic clocks after World War II led to the definition of Coordinated Universal Time (UTC) in 1960, accurate to nanoseconds. The Y2K problem of 1999-2000 demonstrated that two-digit year storage in legacy systems could cause widespread failures, prompting a global remediation effort costing an estimated 300 to 600 billion dollars.
Frequently Asked Questions
Formula
JDN = day + floor((153m+2)/5) + 365y + floor(y/4) - floor(y/100) + floor(y/400) - 32045
The conversion uses the Julian Day Number as an intermediary. First, the Gregorian date is converted to a JDN, then the JDN is converted to a Hebrew date using the molad (new moon) calculations and postponement rules (dehiyot) of the Hebrew calendar.
Worked Examples
Example 1: New Year 2025 Conversion
Problem: Convert January 1, 2025 (Gregorian) to the Hebrew calendar date.
Solution: January 1, 2025 falls in the Hebrew year 5785.\nUsing the Julian Day Number algorithm:\nJDN = 2,460,677\nHebrew date computation gives: 1 Tevet 5785\nThis date is during Hanukkah.
Result: January 1, 2025 = 1 Tevet 5785
Example 2: Spring Date Conversion
Problem: Convert March 15, 2025 to the Hebrew calendar.
Solution: March 15, 2025 Gregorian.\nJDN = 2,460,750\nHebrew year 5785 is not a leap year.\nComputing month and day offsets from Tishrei 1:\nResult: 15 Adar 5785
Result: March 15, 2025 = 15 Adar 5785
Frequently Asked Questions
What is the Hebrew calendar and how does it differ from the Gregorian calendar?
The Hebrew calendar is a lunisolar calendar used in Jewish religious practice and as the official calendar of Israel. Unlike the purely solar Gregorian calendar with its fixed 365-day year, the Hebrew calendar synchronizes both lunar months and solar years. Each month begins with the new moon, lasting 29 or 30 days, creating a base year of 354 days. To stay aligned with solar seasons, the Hebrew calendar adds a 13th leap month (Adar II) seven times within every 19-year Metonic cycle. This ensures that Passover always falls in spring and other holidays maintain their seasonal positions. The current Hebrew year count begins from the traditional date of creation.
How does the 19-year Metonic cycle work in the Hebrew calendar?
The Metonic cycle is the mathematical foundation of the Hebrew calendar, based on the discovery that 19 solar years almost exactly equal 235 lunar months. Within each 19-year cycle, years 3, 6, 8, 11, 14, 17, and 19 are leap years that receive an additional month called Adar II. This pattern ensures the calendar drifts by only about two hours over 19 years relative to the solar year, which is remarkably accurate. The cycle is named after the Greek astronomer Meton who described it in 432 BCE, though the Babylonians discovered it earlier. This intercalation scheme prevents Jewish holidays from drifting through the seasons as they would in a purely lunar calendar like the Islamic Hijri calendar.
What are the different types of Hebrew years and what determines them?
Hebrew years come in six possible lengths determined by two factors: whether the year is a regular year or a leap year, and whether Cheshvan and Kislev have 29 or 30 days. A deficient (chaser) year has both Cheshvan and Kislev at 29 days, giving 353 days in regular years or 383 in leap years. A regular (kesidran) year has Cheshvan at 29 and Kislev at 30 days, totaling 354 or 384 days. A complete (shalem) year has both at 30 days, reaching 355 or 385 days. These adjustments ensure that Rosh Hashanah never falls on Sunday, Wednesday, or Friday, following the postponement rules known as dehiyot.
What are the Hebrew months and their significance?
The Hebrew calendar has 12 months in regular years and 13 in leap years. Tishrei is the first month of the civil year containing Rosh Hashanah and Yom Kippur. Cheshvan and Kislev are the variable months that determine year length; Kislev contains Hanukkah. Tevet, Shevat, and Adar follow, with Adar containing Purim. In leap years, an extra Adar (Adar II) is inserted before Nisan. Nisan is considered the first month in biblical reckoning and contains Passover. Iyar, Sivan with Shavuot, Tammuz, Av with Tisha BeAv commemorating temple destruction, and Elul complete the cycle. Each month begins with Rosh Chodesh celebrating the new moon.
How accurate is the Hebrew calendar compared to astronomical observations?
The Hebrew calendar uses a fixed arithmetic system established by Hillel II around 359 CE, making it remarkably accurate but not perfect. The mean lunation period used is 29 days, 12 hours, and 793 parts (where an hour has 1,080 parts), totaling 29.530594 days. Modern astronomical measurements show the actual mean synodic month is 29.530589 days, a difference of less than half a second per month. However, this tiny error accumulates over centuries. The calendar currently runs about two hours ahead per 19-year cycle. Despite this, the Hebrew calendar remains one of the most astronomically precise traditional calendars ever devised and serves its religious purposes exceptionally well.
What is the difference between business days and calendar days?
Calendar days include every day. Business days (or working days) exclude weekends (Saturday and Sunday) and public holidays. A 10-business-day deadline is typically 14 calendar days. Legal and financial deadlines often specify which type applies.
References
Reviewed by Abdullah, Technical Content Specialist · Editorial policy