About the Random Date Generator
Dates come out as YYYY-MM-DD, the ISO 8601 calendar form. That layout sorts correctly as plain text, imports into SQL and spreadsheets without a locale argument, and removes the ambiguity that makes 03/04 mean two different days on two sides of an ocean.
The range spans 1990 to 2035, which covers historical records and near future scheduling in one draw. Days are chosen from the real calendar, so February 29 appears only in leap years and no month ever produces a 31st that does not exist. That is the difference between test data that exercises your parser and test data that quietly corrupts a table.
Use the results to fill created and updated columns, to build a scheduling test, to seed a chart with points across a time axis, or to hand a class a set of dates for a day of the week exercise. With no repeats on, a set of 100 dates is guaranteed distinct, which matters when the column carries a unique constraint. To reformat a batch into another pattern, run it through the Date Format Converter, and use the Unix Timestamp Converter when an API wants epoch seconds instead.
How to use
- Choose how many dates you need, up to 500 per press.
- Keep no repeats on when the dates fill a column with a unique constraint.
- Press Generate, then copy the whole column straight into your table.
- Reformat the batch afterwards with the Date Format Converter if you need another pattern.
Common questions
- What format are the dates in?
- ISO 8601, written as YYYY-MM-DD, which sorts correctly as text and imports cleanly into databases.
- Can an invalid date appear?
- No. Days are drawn from the real calendar, so February 30 never appears and leap days show up only in leap years.
- What is the date range?
- From the start of 1990 to the end of 2035, covering both historical and near future test cases.
- How do I get a timestamp instead?
- Paste a generated date into the Unix Timestamp Converter to get epoch seconds or milliseconds.