Date Range Calendar Generator

The date-range calendar draws a month grid for every month that overlaps a start date and an end date. A span from January 20 to March 5 includes January, February, and March grids even though the span is not three full months. That “months touched by the range” rule is the job, distinct from a fixed month count and distinct from a 12-month civil year.

Months touched, not days listed

The page shows month calendars, not a day-by-day agenda of only the in-range dates. Dates before the start and after the end still appear on those month pages because a month grid is a complete month. Use shading or notes in your own printout to mark the true start and end if you need a highlighted span.

If you think in “how many months from June” rather than two dates, use multi-month calendar. If you think in “all of 2026,” use calendar generator. This form is for people who already have two civil dates from a contract, ticket, or court order.

How to enter the range

Enter a start date and an end date, then calculate. If the end is before the start, swap them before trusting the grids. Ranges that sit inside one month return a single month grid. Ranges that cross a year boundary include December of the first year and January of the next, plus any months between.

Leap day is included in February’s grid when the range touches a leap February, even if the start and end dates are both in March. The month is touched if any day of that month lies between start and end inclusive.

Worked examples

A lease runs from August 15 to July 31 of the next year. The tenant enters those two dates and prints every month the lease touches for a move-in binder. Utility start dates are written on the grids by hand.

A conference committee has a planning window from March 3 to June 12 of 2026. They generate the four month grids, then mark hotel cutoff dates. Holiday conflicts are checked on 2026 holidays for months inside 2026.

Inclusive month membership

If the start date is March 1 and the end date is March 1, only March is touched. If the start is March 31 and the end is April 1, both March and April are touched. People who expect “full months only” will be surprised by one-day overlaps; the rule is any overlap, not a majority of days.

Same-day ranges still produce the month that contains that day. Empty ranges are invalid. Extremely long ranges produce many month grids; for multi-year archives consider generating year by year instead of one huge strip.

What the grids omit

There is no automatic workday shading, no federal holiday glyphs, and no ISO week column unless you add them elsewhere. The deliverable is month shapes covering the span. Pay dates, shifts, and school days are other tools.

ICS export of the range as events is not this page. Build .ics files on the ICS generator with explicit event titles. Here you are looking at calendars, not writing calendar files.

Compared with quarter and fiscal views

Civil quarters are fixed month groups (January–March, and so on). A date range of February 10–April 2 is not a quarter; it is three touched months. Use the quarter calendar when Q1–Q4 of a year is the frame. Use fiscal calendar when month labels follow a fiscal start month.

Retail 4-4-5 periods are week-based, not month-touched. A date range that is thirteen weeks long still displays civil months here, not NRF periods. Keep retail generators for retail weeks.

Contracts and tickets

Airline tickets and court orders name two dates. The months those dates touch are the months a binder needs. A ticket from January 31 to February 2 still needs both January and February grids. People who generate only February miss the 31st. The overlap rule exists for that one-day-in-January case.

Multi-year ranges produce many grids. For a three-year lease, consider generating each civil year separately on the custom year generator, then using this range tool only for the stub months at the start and end. Very long walls are hard to hang; the range tool will still draw them if you insist.

Inclusive ends

End dates are inclusive: a project that ends on the last day of June includes June. A project that ends on July 1 includes July even if work that day is only a signature. If your contract is exclusive of the end date, subtract a day before entering it so the extra month does not appear.

Leap day at the edge of a span

A range that ends on February 28 in a leap year does not include February 29, so the 29th is not in the span even though February is touched. A range that ends on February 29 includes the leap day. Inclusive end dates make that difference. Write the end date from the contract, not from a habit of using the 28th every year.