Date Calculator (Add or Subtract Days, Months, Years)

Pick a start date, say how far to jump, and you get the date you land on, spelled out with the weekday so you can tell right away if it falls on a weekend. It all runs in your browser, nothing you type gets uploaded, and the answer updates the moment you stop typing.

The reason a date calculator matters at all comes down to one thing people get wrong in their heads. "A month later" and "30 days later" are not the same jump. A net-30 invoice or a 30-day notice period is counted in days. A one-month notice or a lease that renews next month is counted in months. Guess the wrong unit and you land a day or two off, and you almost never notice. So this tool keeps years, months, weeks, and days as four separate fields on purpose, and runs the real calendar math on each one rather than mashing a month into a flat thirty days the way a quick guess in your head does.

1. Set the start date with the picker, or hit Use today to drop in the current date.
2. Choose Add to move forward in time or Subtract to move back.
3. Type an amount into any mix of the Years, Months, Weeks, and Days fields. A blank field counts as zero. In a hurry, the Quick jump chips (+30 days, +1 year, and the rest) fill a field for you.
4. Read the result. It shows in plain English up top with the YYYY-MM-DD form under it, plus the weekday, how far it sits from today, the total length of the jump, the day of year, the ISO week, and the quarter.
5. Put it somewhere useful. Copy the text, download an .ics file, or push it to Google Calendar as an all-day reminder. Name the event first if you want the calendar entry labeled.

Everything recalculates on the spot, so you can poke at "what if I add two more weeks" without starting over. Your last few calculations sit in the Recent row on this device, and you can copy a link that reopens the exact setup on any other device.

Days are the easy case, because a day is always the same fixed length. Add 30 days to January 15 and you take 30 fixed steps down the calendar, through the back half of January and into February, landing on the 14th, which is where you would expect.

Months are the tricky case. Add one month to January 15 and you don't count out 30 or 31 days, you jump to the same day number in the next month, February 15. The tool holds the day number steady and lets the length of the month flex, because "next month, same date" is what people actually mean by it. Trouble is, that length really does flex. One month out of a 31-day month covers 31 days of calendar. One month out of February covers 28, or 29 in a leap year.

So from the identical start you get two different answers:

• January 15 plus 30 days lands on February 14
• January 15 plus 1 month lands on February 15

The two land a day apart from the same starting point, because the instructions simply aren't the same. Which one is right depends entirely on the real-world rule you're following, and doing the swap in your head is exactly where the error creeps in, so match the field to the wording. If the contract says thirty days, use Days. If it says a month, use Months.

Now the genuinely odd one. What is January 31 plus one month? There is no February 31. That date doesn't exist, so any calculator has to make a call, and different tools make different calls, with some spilling forward into early March. This one clamps back to the last real day of the target month, so January 31 plus a month lands on February 28, or February 29 in a leap year. When it does that it tells you, a short note appears under the result so a quietly shifted date never catches you out.

Clamping is the sane default. If your lease renews "on the 31st" and you ask for one month on, you mean the end of February, not March 3rd. Nearly every serious date library clamps the same way, so the tool lines up with other systems you hand the date to.

Clamping only runs in one direction though, and that's the real trap. January 31 plus one month gives February 28. But February 28 minus one month gives you January 28, not the 31st you started from. The instant a date gets clamped, those extra days are gone for good, so a round trip through months won't always land you back home. If you need the math to stay perfectly reversible, work in days instead, days never clamp.

The same rule quietly handles the leap-day case. February 29 plus one year has no February 29 to land on in a normal year, so it clamps to February 28. Add four years and you're back on the 29th, as long as the year you land in is itself a leap year.

Enter "1 year, 2 months, and 10 days" all together and the order the tool applies them in actually changes the answer near a month boundary, so it fixes one order and sticks to it. Years and months first, clamp the day if it has to, then the weeks and days on top. Walking it from January 15, 2025, the year and two months carry you to March 15, 2026, then the ten days push you to March 25, a Wednesday. That order never varies, and it is both the standard one and the safer one, because the clamp happens before the day-level fine tuning rather than after.

Everything else the result panel shows is just context handed to you for free, the ISO week, the quarter, the day of year. The days-from-today number is the quiet useful one. "63 days from now" is often the thing you actually wanted, and it's the fastest check that you typed the right amount.