Math on a calendar
The calendar is a clumsy thing to do arithmetic on. Months have different numbers of days. Years have different numbers of days. Adding 90 days to a date isn't "three months later" — it's "three months later, give or take a few days, depending on which months." If you've ever opened your phone's calendar and counted forward day by day, you know the drill.
The Date Time Calculator does the counting for you. Pick a start date, pick what you want to add or subtract (days, weeks, months, years, hours, minutes), and the answer appears below. You can also flip it around: give it two dates and it returns the difference between them, broken down into years, months, weeks, and days.
Useful when you're working out a project deadline, a lease end date, a contract notice period, a baby's due date, or counting down to a flight. The math is exact and accounts for leap years automatically. Calculation happens in your browser — your dates don't get logged anywhere.
How to use the Date Time Calculator
The tool runs in two modes: add/subtract from a date, or compute the difference between two dates. Pick whichever fits.
Mode 1: add or subtract.
- Pick a start date from the date picker.
- Choose add or subtract.
- Enter how many days, weeks, months, years, hours, or minutes to apply.
- Read the resulting date and time below.
Mode 2: difference between two dates.
- Pick the start date.
- Pick the end date.
- Read the difference broken down into total days, total weeks, total months, total years, and a combined "X years, Y months, Z days" breakdown.
Both modes update as you type. There's no Calculate button. Nothing gets sent anywhere — the date math runs in your browser.
Worked example: a project starts on May 13, 2026 and runs for 90 days
This is the kind of math that comes up constantly in contracts: "delivery within 90 days of signing." Counting 90 days by hand from May 13 means tracking the day count across May, June, July, and August. Let's walk it through.
May 13 + 90 days:
- Days remaining in May after the 13th: 31 − 13 = 18 days. We've used 18 of the 90. Date is now May 31. (62 days left to add.)
- Add all of June: 30 days. We're now at June 30 with 32 days left.
- Add all of July: 31 days. We're now at July 31 with 1 day left.
- Add 1 day to land in August: August 1, 2026.
Hmm — that's not what people often guess. "Three months from May 13" feels like it should land on August 13, which is 92 days. The Date Time Calculator gives the exact answer: 90 days after May 13, 2026 is August 11, 2026. (Counting from the day *after* the start, which is the convention most contracts use, gets you to August 11. Counting inclusive of the start gets you to August 10. Read your contract for which convention applies — the calculator gives both interpretations.)
The math is short on paper but easy to slip on. The calculator's value here isn't doing impossible math; it's removing the off-by-one mistakes that creep in when you count by hand.
The difference between two dates
The other direction is just as useful: you have two dates and you want to know how far apart they are. The Date Time Calculator gives the answer in several units at once because "how long" has different right answers for different questions.
Take two dates: a wedding on June 15, 2024 and a first anniversary check on August 22, 2025. The difference is:
Total days: 433
Total weeks: 61.86
Total months: 14.23
Total years: 1.19
Breakdown: 1 year, 2 months, 7 days
All five of those describe the same length of time. Which one you want depends on context:
- "How old is the baby?" → years and months breakdown
- "How many days until the lease ends?" → total days
- "How long until my visa expires?" → total days (often what immigration forms want)
- "How many weeks pregnant?" → total weeks (medical convention)
- "How many years on the job?" → total years, decimal (for HR records)
The calculator gives all five so you can copy whichever fits your form.
Common date math the calculator handles
| Query | Example | How the calculator handles it |
|---|---|---|
| "What's the date 30 days from today?" | Today + 30 days | Add 30 to today's date, accounting for month-end |
| "What's the date 6 months from now?" | Today + 6 months | Same day of month, 6 months later; clamps to month end if needed |
| "What was the date 90 days ago?" | Today − 90 days | Subtract 90 days, wrap across months and years as needed |
| "How many days between two dates?" | Date A → Date B | Exact day count, leap years included |
| "How old is someone born on X?" | Today − birthdate | Years, months, days breakdown (see also the Age Calculator) |
| "What date is the 100th day of the year?" | Jan 1 + 99 days | April 9 in a common year, April 8 in a leap year |
| "What's the date 18 weeks from now?" | Today + 18 weeks | Same weekday, 18 weeks later |
| "Add 36 hours to right now" | Now + 36 hours | Result includes time, not just date |
The "add 6 months" case has a subtle behavior. If you start on January 31 and add one month, you land on February 28 (or 29 in a leap year), because February doesn't have a 31st. The calculator clamps to the last valid day of the target month. Same thing with March 31 + 1 month → April 30. This is the behavior most calendar apps and most contracts assume; some date libraries do it differently, so it's worth checking if you're comparing answers across tools.
Leap years (the calendar's only real complication)
Every fourth year, February has 29 days instead of 28. The rule is: a year is a leap year if it's divisible by 4, except if it's divisible by 100, except if it's divisible by 400. So 2024 is a leap year (divisible by 4, not by 100). 2100 will not be a leap year (divisible by 100, not by 400). 2000 was a leap year (divisible by 400). The calendar repeats every 400 years.
For date math, leap years matter in two ways. First, if your start or end date is February 29, that date only exists every fourth year — adding "exactly one year" to Feb 29 lands on Feb 28 of the following (non-leap) year. Second, the day count across long spans depends on how many leap years are in between. The number of days from Jan 1, 2020 to Jan 1, 2030 is 3653 (10 years, including the leap days in 2020, 2024, 2028) — not 3650.
The Date Time Calculator accounts for all of this. The implementation uses the underlying JavaScript Date object, which knows the Gregorian calendar's leap-year rule and handles dates from about 271,000 BC to 271,000 AD without overflow.
Time zones (the part that gets people)
If you're adding or subtracting time in pure days, time zones don't matter — May 13 is May 13 in every time zone (well, almost every — see below). But if you're adding hours or minutes that might push the result across midnight, the time zone affects what day it lands on.
The Date Time Calculator does its math in UTC internally. The dates you see are interpreted as midnight UTC on that calendar day. For most purposes this is fine because you're working with dates as labels, not as specific moments in time. But two cases trip people up:
- Crossing the International Date Line. If you fly from Auckland to Honolulu on May 13, you arrive on May 12 (local). The calendar day shifts backward. The Date Time Calculator works with calendar days as input — it doesn't know about flight paths.
- Adding hours across DST. If you add 24 hours to 11 PM on the night before a Daylight Saving spring-forward, the result is midnight + (DST shift), which lands on a different wall-clock time than you might expect. Day-based math sidesteps this entirely; hour-based math through DST transitions is messy in any tool.
For most date arithmetic (lease end dates, due dates, contract deadlines), days-and-months math is what you want and time zones don't enter into it. The calculator's UTC handling is the right default.
Why "exactly 3 months" is ambiguous
If someone says "the deposit is due in 3 months," the answer depends on which 3-month definition they mean. The Date Time Calculator handles two:
- Calendar months. 3 calendar months from May 13 is August 13. Same day of month, just three months later. This is what most contracts mean.
- 90 days. 90 days from May 13 is August 11 (as worked out above). Two days earlier than the calendar-month version.
Three calendar months can be 89, 90, 91, or 92 days depending on which months are involved. May 13 to August 13 spans May (18 remaining days after the 13th), June (30), July (31), and August (13) = 92 days. November 13 to February 13 spans November (17), December (31), January (31), and February (13) = 92 days, or 93 days if it's a leap year. So "3 months" and "90 days" are often close but not equal.
When a contract is specific, it'll say one or the other. When it's not, the answer is usually calendar months unless the document is unusually pedantic. The calculator gives you both modes so you can produce whichever version your situation needs.
Related calculators
- Hours Calculator — for time-of-day arithmetic on a single shift, including overnight handling and break deduction.
- Age Calculator — same year/month/day breakdown logic, framed for birthdays. Tells you how old someone is in any unit.
- Age Difference Calculator — for the gap between two people's ages (or any two specific dates), broken down into years, months, days.
- Days Between — just the day count between two dates, when that's the only number you need.
Frequently asked questions
How does the calculator handle leap years?
Automatically. The Gregorian leap-year rule (divisible by 4, except divisible by 100, except divisible by 400) is baked into the underlying date library. So adding "one year" to February 29, 2024 lands on February 28, 2025 (because 2025 doesn't have a February 29), but adding four years lands on February 29, 2028 (which does). Spans that cross leap years include the extra day automatically — 365 days plus the leap days in between.
What's the difference between "90 days" and "3 months"?
"90 days" is exactly 90 calendar days. "3 months" is three calendar-month boundaries, which can be 89, 90, 91, or 92 days depending on which months. Same day of month, three months later. Most contracts that say "3 months" mean the calendar-month version; contracts that need exact day counts use "90 days." The Date Time Calculator does both — you pick whether you're adding months or days.
Does it handle time zones?
The math runs in UTC internally, which means the day-and-month arithmetic is unaffected by your local time zone. For pure date math (lease ends, due dates, deadlines), this is the right default — May 13 is May 13 regardless of where you are. If you're doing hour-level math through Daylight Saving transitions or across the International Date Line, the result may shift relative to your local wall-clock time. For most purposes, this isn't an issue.
What happens when I add a month to January 31?
It clamps to the last valid day of the target month. January 31 + 1 month = February 28 (or February 29 in a leap year). January 31 + 2 months = March 31 (March has 31 days). This is the convention most calendar apps and most contracts use. A few date libraries do this differently — they'd return "February 31" as "March 3" — but that's surprising behavior and the Date Time Calculator avoids it.
Can it count business days?
Not directly — it counts calendar days, including weekends and holidays. If you need business days only (Monday through Friday, excluding public holidays), you'd need a tool that knows the holiday calendar for your country. For most contractual "X days from notice" math, the convention is calendar days unless the contract says "business days" specifically. Read the document.
How precise is the time math?
The calculator can add and subtract down to the minute. Adding hours and minutes produces an exact result. Seconds aren't exposed in the UI because date pickers don't typically include them and they're rarely useful for calendar math. If you need sub-minute precision, a stopwatch or duration calculator is a better fit.
What's the largest date span it handles?
Effectively any span you'd encounter in real life. The underlying JavaScript Date object handles dates from roughly 271,000 BC to 271,000 AD without overflow. For dates more than a few centuries in the past, the Gregorian calendar didn't exist (it started in 1582 in Catholic countries, much later in Protestant and Orthodox ones), so the calculator's answers are "what the Gregorian calendar would have said if it had been in use" — not historically accurate to what people of the time would have used. For modern dates and short historical research, this is fine.