Nobody opens a days-between tool because they love date math. Something is due, something already happened, and someone in the thread is about to say "that's two weeks" while another person is counting on their fingers and landing on thirteen or fifteen. The fields above are the boring part that ends the argument: pick a start, pick an end, read the number, move on.
The checkbox is where most real-world mix-ups live. "Through June 30" often means the thirtieth still counts as a work day; "by June 30" sometimes means you must be done when the day starts. Flipping include-end usually changes the total by exactly one day, which is small until it hits a filing window or a sprint commitment. Plenty of people run it both ways once, nod, and paste the version that matches how their team talks.
School terms and vendor contracts are the usual suspects. A syllabus might say the project spans March 3 to April 18; HR might list PTO from the fifteenth through the twenty-second. Write the dates the way they appear on the form, then sanity-check against a calendar you trust. If you typed the later date into the start field by habit, the count still works—you may just want to swap labels before you screenshot the result for a manager.
When "about three weeks" stops matching the calendar
Mental estimates round to neat blocks. Calendar days do not. Crossing February, a short month, or a holiday weekend can make a span feel longer or shorter than the week-and-day line in the result panel suggests. That breakdown is useful when one person thinks in Mondays and another person copied a contract that only names calendar days.
Weekends are the other silent fork. This page counts every calendar day between the anchors. If your task only advances on business days, the number here will look generous compared to a work-week estimate. For the same two fixed dates expressed as whole weeks, the May 9 to June 8 span in weeks is sometimes easier to read than dividing by seven in your head.
Forward questions from a single anchor—"what is ninety days from today?" or "what was thirty days before this invoice date?"—belong on the from-now and ago tools, not here. Ninety days forward from May 9, 2026 and thirty days back from the same anchor are the habit when only one date is fixed. Keep this calculator for pairs you already know: signed on the ninth, review on the twenty-third, handoff on June eighth.
A concrete pair before you copy the answer
Directory examples exist because vague ranges cause vague plans. May 9 through May 23, 2026 is a tidy two-week window once you decide whether the twenty-third itself counts. Longer planning stretches benefit from the same discipline—note dates as yyyy-mm-dd in your scratch pad so 05/09 and 09/05 do not trade places when someone reads them quickly on a phone.
Quarter-style planning shows up a lot in ops work. January 1 through March 31, 2026 is the kind of span people argue about in Q1 reviews: inclusive end on, both quarter endpoints in the count; flip the checkbox once if your finance sheet treats the last day as already complete.
Before the number goes into email, glance at the field labels one more time after you tab away. Confirm whether weekends matter for this decision (they all count here). Confirm nobody meant business days in the legal paragraph. If the total jumps by a single day when you toggle include-end, you found the mismatch— not a broken calculator.
Stacked timelines—design, then build, then review—are less painful when each segment gets its own pair of dates instead of adding rough mental chunks. When the finish date is what you are solving for, not the gap, the project date planning note walks through anchoring a start and stacking durations without rebuilding the whole grid every time a vendor slips.
This is ordinary planning math, not legal advice or payroll policy. When the count actually matters, keep the two source dates next to the answer so Future You remembers which convention you picked.