Days ago calculator

What date was N days before today? Pick a shortcut or enter a custom count.

Custom days ago

Enter how many days before today to look up.

Days ago finds the calendar date that was N days before a reference day — usually today. It answers what date was ninety days ago for refunds, retention policies, journalism timelines, and audit windows without counting backward on a paper calendar or guessing across uneven month lengths.

Backward lookup versus forward planning

Days ago subtracts from a reference date. The date calculator can subtract too, but this page phrases the question in plain N-days language consumers recognize from return policies and compliance checklists.

Forward equivalents use add mode on the date calculator or days from today shortcuts when the site exposes common offsets. Measuring span between two known fixed dates is days between dates, not this page.

Reference date flexibility

Audit logs anchor on transaction date, not necessarily today. Change the reference date to reconstruct historical cutoffs for chargebacks, warranty claims, or public-records response windows. Inclusive language still matters when contracts say within thirty days of receipt — confirm whether day thirty is included before comparing to a calendar date output.

Store reference date, N, and result date together in ticket comments so finance can reproduce the lookup months later without debating whether someone used order date versus delivery date as the anchor.

How to use the page

Enter N days and an optional reference date; read the resulting calendar date and weekday. Verify weekday-sensitive deadlines with the business days calculator when weekends exclude. Cross-check federal holidays on 2026 holidays only when the policy mentions business days, not calendar days.

Named dates read better in customer-facing copy than N days ago alone. Support macros that say eligible if within ninety days should append the computed calendar cutoff so customers do not recompute in a different timezone.

Leap years and month boundaries

Subtracting ninety days from March 1 crosses February with correct length, leap or not. Do not approximate with three months unless the policy explicitly says months instead of days. Subtracting three hundred sixty-five days from a date is not always one civil year ago when leap day sits in the span.

Software retention policies that say delete after ninety days should compute cutoff dates from event timestamps in the same timezone as storage. Use the deletion event date as reference when policies start at account closure, not last login.

Worked examples

Return windows: ninety days before today for eligible refunds on consumer goods — pair with proof-of-purchase date as reference if the policy starts at delivery, not order. Newsrooms reconstruct what calendar date was one hundred days before an election for recap stories; named dates anchor filing deadlines better than relative phrasing alone.

Legal discovery windows frequently ask for documents from N days before a filing. Use the filing date as reference, not today, when the order names a specific anchor. Log the computed calendar date in chain-of-custody notes so opposing counsel can reproduce the window.

Common mistakes

Confusing calendar days with business days on legal text produces refunds approved a day late. Using order date when policy starts at delivery date shifts the window. Rounding N to about three months in support macros without recomputing per case creates inconsistent outcomes across agents.

Writing forty-five days ago without the civil date invites weekend-boundary disputes later. Log both the count and the resulting date when closing 2026 incident reviews or SOC2 retention proofs that attach named cutoff dates alongside raw epoch timestamps.

Chargebacks and payment disputes

Card networks publish windows measured from transaction post date or shipment date depending on reason code. Use the post date as reference when the issuer’s letter cites posting, not the in-store visit day. Quote the computed civil cutoff in dispute responses so cardholders see the same anchor the bank uses.

Merchants storing “dispute eligible until” fields in CRM should compute once from authoritative processor timestamps rather than letting sales reps subtract mentally during phone calls. Timezone on the processor ledger matters when post date near midnight UTC splits from local receipt date.

Data retention and compliance holds

SOC2 and GDPR retention policies often say delete records older than N days from collection or account closure. Use closure date as reference when the policy starts at termination, not last login. Backup restore drills must recompute cutoffs from restore point, not from today, when auditing what should still exist.

Legal holds suspend deletion math entirely — days ago still helps define what would have aged out absent the hold, but counsel must approve any automated purge job regardless of calculator output.

Journalism and historical anniversaries

Newsrooms planning “one hundred days since” packages should convert N to a named date before assigning reporters to clip searches. Human archives index by date, not by day offset. Pair the civil date with day of the week when verifying whether an anniversary falls on a weekday newscast slot.

Museum and nonprofit “on this day N years ago” social series should compute the historical anchor from the publication date of the post, not from when the intern drafted copy three days early. Stale drafts publish wrong anniversaries when N was computed from an old reference.

Insurance proof-of-loss forms that ask for incident date minus N days should use the loss date as reference when the policy specifies that anchor. Photograph the receipt or post date when disputing warranty cutoff arithmetic with manufacturers so support can reproduce the same civil cutoff without debating which day started the window.

Health and fitness apps that export streak data by timestamp benefit when coaches convert N days ago to a named civil date before comparing with paper logs indexed by calendar day. Human memory anchors on dates, not three-digit offsets, during retrospective reviews.

Related tools

See days until, days between dates, and the date tools hub.

Frequently asked questions

What is the difference between days ago and days until?

Days ago subtracts N calendar days backward from a reference date to find a past civil date. Days until counts forward to a target. Pick the direction that matches whether your policy anchors on a historical event or a future deadline.

Can I use a date other than today as reference?

Yes. Audit and legal workflows often anchor on transaction date, filing date, or delivery date rather than today. Enter that reference so the result matches the policy window instead of a generic rolling cutoff from the current day. Using today when the policy anchors on delivery or filing date shifts the window by days.

Does this handle leap years correctly?

Yes. Subtracting across February uses the correct month length for leap and common years. Do not replace day counts with approximate months unless the governing text explicitly defines months instead of calendar days. Do not substitute approximate months unless the governing text defines months instead of days.

When should I switch to business days?

When the policy says business days, weekdays, or working days rather than calendar days, use the business days calculator. Mixing calculators produces cutoffs that are early or late relative to the actual contract language. Mixing calculators produces cutoffs that are early or late relative to the policy language.

Why log both N and the resulting date?

Relative phrases like ninety days ago mean different anchors to different readers. Storing the computed civil date and weekday removes ambiguity during chargeback disputes, discovery requests, and retention audits months later. Storing the civil date removes ambiguity when chargebacks or discovery requests arrive months later.

Is subtracting 365 days the same as one year ago?

Not always. A 365-day subtraction ignores leap day when it falls inside the span. Use this tool for day-based policies; use years-between-dates or date duration when the rule speaks in calendar years or anniversaries instead. Use years-between-dates or date duration when rules speak in anniversaries instead of day counts.

Processing, please wait...