Add or subtract bounded whole calendar days from an exact Gregorian date without local-time shifts, hidden today defaults, or business-day assumptions.
A quick decision brief for this specific tool
One explicit Gregorian calendar date and one bounded signed whole-calendar-day offset
Preserved ISO result date, long date, weekday, ordinal day and quarter
Parses the entered YYYY-MM-DD fields strictly and moves on a UTC-stable whole-calendar-day axis; it never converts the date through local midnight or silently substitutes zero
Choose your path
Move one explicitly entered Gregorian calendar date by a bounded whole-day offset without shifting the date through local time or pretending the result excludes weekends, holidays, or clock changes.
Move a documented date forward or backward by an exact number of calendar dates.
Enter the source ISO date and a signed whole-day offset, then verify the result ISO date and weekday.
Can reproduce the result and does not mistake calendar days for working days or elapsed 24-hour periods.
Keep a date-only deadline from moving by one day because of the local UTC offset.
Use the date-only record, inspect the preserved ISO fields, and route elapsed-time needs to a time-zone-aware tool.
Gets the same calendar result regardless of browser time zone and knows clock duration is outside scope.
Use negative offsets and understand supported boundaries.
Enter a negative whole-day value and resolve explicit fraction, out-of-range, or result-range errors.
Receives a named backward result without zero fallback or silent coercion.
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
This tool is part of these guided projects. Each project provides step-by-step instructions with checklists and all the tools you need in one place.
Tools you might need next
Calculate a strict calendar difference, elapsed days, inclusive dates, completed months, and Mon–Fri dates without DST off-by-one errors.
Calculate Gregorian calendar age and UTC-stable elapsed days between two dates, with an explicit February 29 countdown rule and labeled illustrative context.
Count or add working days with a custom weekly schedule, selected OPM-observed U.S. federal holidays, and configurable work hours per day.
The engine accepts an exact YYYY-MM-DD Gregorian date from 1600-01-01 through 9999-12-31 and rejects impossible month/day combinations.
Entered date = validated year + month + day fieldsA bounded whole signed offset is applied to a calendar serial day. Positive values move forward, negative values move backward, and zero preserves the date.
Result serial day = start serial day + signed whole-day offsetThe result reports calendar dates, not elapsed hours, local deadline times, working days, weekends, holidays, or jurisdiction-specific cutoffs.
Updated: August 2026
A coordinator enters 2026-08-24 and +30 to create a reproducible calendar-date milestone, then checks work schedules and local cutoff time separately.
An operations reviewer enters a target date and a negative whole-day notice interval, preserving both inputs in the record.
A distributed team uses calendar-day arithmetic for the date, then routes the exact local hour and time-zone conversion to a separate workflow.
Use this result for date fields only; calculate elapsed time from explicit zoned instants when clock hours matter.
Verify weekends, holidays, inclusive wording, local cutoff time, time zone, and the controlling policy or agreement separately.
Move one entered Gregorian date forward or backward by a signed whole-calendar-day offset. The result preserves the ISO date and shows its weekday, ordinal day, and quarter without converting through your local clock.