Date Range Generator

Runs in browser Test Data

Produce every date, week or month between two boundaries, or random non-overlapping start/end pairs for booking and scheduling tests.

TEST DATA ONLY — all generated names, contacts, identifiers and numbers are synthetic and do not belong to real people or accounts.
Privacy: This tool runs entirely in your browser. Your input never leaves your device.

How to use Date Range Generator

  1. Choose Sequence or Random ranges.
  2. Enter the From/To dates and the step (or the number and length of ranges).
  3. Pick a date format and output format, then press Generate.

Date Range Generator features

  • Sequences by hour, day, week, month, quarter or year between two dates (up to 1,000 entries)
  • Weekdays-only filter
  • Month and year steps clamp to the shorter month (31 Jan → 29 Feb → 31 Mar)
  • Random start/end pairs with min/max length, optionally non-overlapping
  • Every row carries ISO, weekday and year/month/day parts
  • Seedable; JSON, CSV, SQL, XML, JSON Lines or table output

Date Range Generator example

Month ends of Q1

Input:

Mode: Sequence · From 2025-01-31 to 2025-03-31 · Step: Monthly · Format: EU

Output:

index,date,weekday
1,31/01/2025,Friday
2,28/02/2025,Friday
3,31/03/2025,Monday

Frequently asked questions about Date Range Generator

What does sequence mode produce?

Every hour, day, week, month, quarter or year between two dates (up to 1,000 entries), optionally weekdays only. Month steps keep the day-of-month and clamp to shorter months (31 Jan → 29 Feb).

What about random ranges?

Random start/end pairs with a configurable length in days; with "non-overlapping" enabled the ranges never intersect, which is what booking and scheduling tests usually need.

Which date formats are available?

ISO, ISO date-time, US, EU, Unix seconds/milliseconds, RFC 2822, tabular Hijri and long form.

Which time zone are the dates in, and what happens around DST changes?

Everything is computed in UTC. A plain YYYY-MM-DD is read as midnight UTC, hourly/daily/weekly steps add exact multiples of 60 minutes or 24 hours, month steps use UTC calendar arithmetic, and the weekday comes from the UTC date. No local time zone or DST rule is applied, so a daily sequence never skips or duplicates a day.