Home / Date & Time / Weeks Between Dates Calculator
Date & Time

Weeks Between Dates Calculator

Calculate full weeks plus leftover days between two dates, with decimal weeks, weekdays, inclusive counting, ISO-week context and an optional advanced schedule audit.

Elapsed spandate-only UTC arithmetic avoids daylight-saving hour shifts
Calendar decompositionfull weeks, complete months and completed years stay distinct
Boundary verificationinspect endpoint counting and clamped month/year anchors
Exact calendar-week span

Weeks between two dates

Choose two calendar dates. Get full weeks plus leftover days first, then decimal weeks, weekdays, weekend days, work-week equivalents and calendar context.

Local · date-only UTC

Presets set the end date exactly N × 7 days after the start date. Holidays are not removed here; the advanced audit below supports custom workdays and closures.

Weeks between dates
—
Choose two dates.
Decimal weeks—
Total days—
Weekdays—
Weekend days—
Work weeks (Mon–Fri)—
Fortnights—

Calendar proof

See exactly how the headline answer is formed and verify common off-by-one questions.

—
Counting rule—
Start weekday—
End weekday—
Same weekday?—
Start ISO week—
End ISO week—
—
——
Ready.
Advanced schedule audit · custom workweek, closures, week ledger & milestones
Keep the headline answer simple. Open this only when you need custom weekdays, closure exclusions, four endpoint conventions, aligned calendar-week evidence, recurring milestones, CSV/ICS/JSON or saved local spans.
Exact week-span planning & audit

Week Span Planning Studio

Keep the fast answer above, then audit the same date range for endpoint rules, ISO weeks, configurable workdays, closure dates and recurring week milestones. Everything runs locally with date-only UTC arithmetic.

4 endpoint conventionsISO week evidenceCustom workweek + closuresWeek ledger + milestonesCSV · ICS · JSON · printLocal history + share

1. Dates & counting policy

These dates stay synchronized with the quick calculator above. Reversed input is preserved as an input-direction fact while totals use the chronological span.

Date-only · UTC

2. Workweek & closure policy

Select any recurring workweek, then add exact closure/holiday dates you want excluded. No country holiday feed is applied silently.

A closure only subtracts a configured workday when it lies inside the counted endpoint interval. Duplicate closure dates are de-duplicated.

3. Exact results & calendar evidence

The primary answer remains whole weeks plus remaining days. The audit surfaces alternate planning views without pretending that months or time zones are fixed-length weeks.

Counted week span——
Counted days—
Decimal weeks—
Fortnights—
Weekdays—
Weekend days—
Configured workdays—
Workweek equivalents—
Full aligned weeks—
ISO weeks at inputs—
Week segments touched—
Same weekday at both inputs?—
Counted closure exclusions—
Arithmetic rule1 week = exactly 7 calendar days
DST/time-zone ruleDate-only UTC; clock shifts are not part of this calculator
Ready.

4. Week-by-week ledger

See how the counted interval lands inside Monday- or Sunday-based calendar weeks, with configured workdays and closure exclusions per segment.

—
#Counted datesDaysWorkdaysClosuresISO weekCalendar week

Very long spans keep exact summary totals but cap the ledger to the first and last 260 week segments so the page stays responsive.

5. Recurring week milestones

Build a weekly, biweekly, four-week or quarterly-style cadence from the literal start date toward the literal end date.

—
#DateWeeks from startISO weekLabel

Milestone planning and ICS export are capped at 104 generated occurrences per run. Exports use all-day dates and do not add clock times or time zones because this page models calendar dates only.

6. Save, export & share

Keep repeat-use spans in local browser storage or move the current workbench as a JSON file. Portable links encode the visible dates and planner settings in the URL fragment.

Current audit summary

—
Scope & trust boundary. The Studio counts proleptic Gregorian calendar dates using UTC midnight arithmetic, so daylight-saving changes do not alter a date-only span. It does not silently fetch public holidays, payroll rules, legal deadline rules or time-zone offsets. Enter closure dates yourself when they matter, and verify jurisdiction-specific deadlines against the governing source.

Core timing workflows

Start with a direct timer, stopwatch, alarm or focus workflow. Calendar, date arithmetic, clocks and scheduling specialists remain available from the full Date & Time hub.

All 76 date & time tools

Calendar consistency audit

Cross-check the same date pair as total days, full weeks, complete calendar months and completed years, with month-end anchors and inclusive-day evidence.

High-impression second pass
Independent verification layer; the primary tool remains the source of the displayed result.

How to calculate weeks between two dates

For the standard elapsed result, subtract the earlier calendar date from the later date to get total days, divide by seven for decimal weeks, then split the same day total into whole weeks and the remaining zero to six days. The quick calculator above does exactly that with date-only UTC arithmetic, so a daylight-saving clock change does not turn one calendar day into 23 or 25 hours.

Which endpoint rule should I use?

Include start, exclude end is the usual elapsed-span convention: January 1 to January 8 is seven days, or exactly one week. Include both counts calendar dates instead, making the same endpoints eight counted days. The advanced Studio also exposes exclude-both and exclude-start/include-end conventions so a handoff can state exactly which boundary rule produced the number.

Weeks versus calendar weeks

Seven elapsed days always make one duration week, but a calendar week is aligned to a chosen weekday boundary. The Studio reports how many Monday- or Sunday-based week segments the range touches and how many complete aligned seven-day blocks sit entirely inside the counted interval. ISO week labels always use the ISO Monday-based week-year convention.

Working weeks and closure dates

A working week is a policy, not a universal calendar constant. Choose the weekdays that count for your schedule and enter closure dates explicitly. The result shows configured workdays and workweek equivalents without pretending that every organization follows Monday through Friday or that a global holiday feed would be authoritative for your situation.

Recurring weekly schedules

The milestone planner walks from the literal start input toward the literal end input in exact seven-day increments. Use one week for weekly check-ins, two weeks for biweekly cycles, four weeks for fixed four-week periods, or a longer cadence. The ICS export contains all-day dates only; it deliberately does not invent a local time or time zone.

Why the date-only model matters

Questions about weeks between calendar dates are usually different from questions about elapsed hours between two instants. If clock times and zones matter, use a date-and-time duration tool instead. This page keeps the date-only model inspectable, exports the counting evidence, and leaves legal, payroll and jurisdiction-specific deadline interpretation to the applicable source.

Search by task, tool name, or category. Press Esc to close.
Start typing to find a tool.