Fake Data Generator
Generate realistic test rows in JSON, CSV or SQL from fields you choose.
Build a cron schedule from controls and see the next times it runs.
Each field accepts a value, a list such as 1,15, a range such as 1-5, a step such as */15, or any combination.
The Cron Expression Generator builds a schedule from controls, describes it back in plain English, and shows the next times it will actually fire — which is what catches a mistake before it costs a week.
Choose when a job should run and the expression is built for you, described back in plain English, and checked by showing the next several times it will actually fire. That last part is what catches a mistake before it costs you a week.
Every field supports the full syntax — lists, ranges, steps and names — and each control explains what it produces. The trap the generator warns about is the one nobody expects: when both day of month and day of week are restricted, cron treats them as OR rather than AND, so "the 1st and also Mondays" runs far more often than intended. The shorthand forms such as @daily and @reboot are available too, with what each expands to.
Stepped forward minute by minute and tested, exactly as cron does — not estimated from the fields.
Restricting both day of month and day of week means either, not both. It is the single commonest cron mistake and it is flagged.
Lists, ranges, steps and month and day names, each explained where you use it.
@daily, @weekly, @reboot and the rest, with what each expands to rather than just the name.
The description is the fastest way to notice that an expression does not say what you meant.
Every minute, hourly, daily, weekly, monthly, or a custom pattern.
Minute, hour, day, month and weekday, each with lists, ranges and steps.
The plain-English description is the quickest way to catch a mistake.
The next several fire times, calculated rather than assumed.
Minute, hour, day of month, month, day of week — in that order. An asterisk means every value, and the first field being minutes is why 0 0 * * * is midnight rather than every hour.
Almost certainly because you restricted both day of month and day of week. Cron ORs those two fields, so "1st of the month" and "every Monday" together means both, not their intersection.
The server's local time zone, which is often UTC and often not what you assumed. Daylight saving makes an early-morning job run twice or not at all on the changeover days.
It runs the job once when the machine starts and never again on a schedule. Useful for starting a service, and a common surprise when someone expects it to mean something periodic.
What people who use the Cron Expression Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Cron Expression Generator. It takes half a minute and no account.
Write the first reviewGenerate realistic test rows in JSON, CSV or SQL from fields you choose.
Compare two semantic versions and test them against a range.
Build and sign a JWT with HS256, HS384 or HS512 for testing.
Identify a UUID's version and variant, and extract its timestamp.
Generate ULIDs — sortable by creation time and case-insensitive.
Build an HTTP Basic Authorization header from a username and password.
Convert CSV rows into XML records with named root and row elements.
Pretty-print XML with clean indentation, or collapse it back to one line.