Unix Timestamps, Date Formats and Cron Schedules Explained

Prepared and reviewed by the ProWorkstack editorial team.

Before converting a date or reading a schedule, identify its format, unit and time zone. A Unix timestamp in seconds is different from one in milliseconds. A written date such as 03/04/2026 is ambiguous without a format rule. A cron expression describes a schedule under a particular scheduler’s conventions, not a universal appointment time.

The Unix Timestamp Converter, Date Format Converter and Cron Expression Explainer help with those distinct questions. This guide explains their supported inputs and how to check the interpretation before using it in a record, import or scheduled task.

Distinguish seconds from milliseconds

A Unix timestamp represents an offset from the Unix epoch. Many systems express it in seconds; JavaScript date values commonly use milliseconds. The same instant therefore has different numeric values depending on the unit. Never choose a unit simply because the number looks familiar in another system.

In Unix Timestamp Converter, enter an integer and select seconds or milliseconds. The output is a UTC ISO date. A timestamp of 0 represents 1970-01-01T00:00:00.000Z in either selected unit. For a nonzero value, changing the unit changes the interpreted instant, so the dropdown is part of the input rather than a display preference.

As an arithmetic example, 86,400 seconds is one day after the epoch. The corresponding millisecond value is 86,400,000. If you enter 86,400 and choose milliseconds, it represents only 86.4 seconds after the epoch. This example makes the thousand-fold unit difference visible without relying on the length of a modern timestamp.

Read the UTC output correctly

The Z at the end of the output indicates UTC. It does not mean the converter has applied your local time zone. When someone needs a local appointment time, the time-zone conversion is another step. Record the intended location or zone, especially when a task crosses regions or daylight-saving changes.

A date in UTC can fall on a different local calendar date. Do not remove the time and zone from a timestamp unless the receiving record is supposed to represent only a date. A deadline, a log entry and a birthday are different kinds of information, even when each can be displayed using familiar date characters.

The tool accepts supported integer values and rejects invalid or out-of-range timestamps. Decimal values or a pasted timestamp label are not the expected input. Check the source specification before stripping characters. A value may describe elapsed time or another counter rather than a Unix timestamp at all.

Convert written dates using an explicit rule

Date Format Converter accepts one date per line and lets you choose YYYY-MM-DD, DD/MM/YYYY or MM/DD/YYYY as the input and output format. Choose the source format deliberately. The tool does not guess whether the first field in an ambiguous slash-separated date means a month or a day.

For example, 03/04/2026 means 3 April under DD/MM/YYYY, but March 4 under MM/DD/YYYY. Both are valid dates, so validation alone cannot identify the intended one. Ask how the source produced its dates, then apply the correct rule consistently across that dataset.

Invalid calendar dates are rejected. February 29 is valid in an appropriate leap year, while 2023-02-29 is not a real calendar date. Fix the source rather than accepting an automatic rollover into March. A format conversion should change representation, not quietly replace an impossible date with a different one.

Use consistent dates in exported records

An explicit year-month-day representation is often easier to review across locales than an ambiguous numeric slash format. That does not mean every receiving application accepts it. Check the import instructions and run a small sample. A spreadsheet may also reinterpret a pasted value according to its locale settings.

After conversion, compare several dates where the day is above twelve, along with ambiguous dates where both fields are twelve or lower. The unambiguous examples can reveal an incorrect source-format assumption. Keep the original column until the receiving system’s imported values have been verified.

Read the five fields in a cron expression

Cron Expression Explainer supports five numeric fields in this order: minute, hour, day of month, month and day of week. It accepts asterisks, ranges, lists and steps. It does not support named months, a seconds field or every scheduler-specific extension. Check the scheduler’s dialect before treating its expression as supported.

An asterisk allows every supported value in that field. A range selects a span, a comma-separated list selects particular values, and a step divides a range or wildcard into repeated intervals. The explainer lists matching values so you can inspect which minutes or hours are included.

Work through a weekday schedule example

The expression */15 9-17 * * 1-5 selects minutes 0, 15, 30 and 45 during hours 9 through 17 on weekdays. That means the 17th hour is included; it is not an instruction to stop exactly at 17:00. The last matching minute of that hour is 17:45 under the ordinary interpretation.

The time zone comes from the scheduler or its configured environment, not from these five fields alone. A server using UTC and a scheduler using a local zone can run the same expression at different local times. Check the actual configuration and watch a test run before relying on the schedule for an important operation.

Check day rules and daylight-saving behaviour

Under common Unix cron rules, when both day of month and day of week are restricted, they match with OR. An expression specifying a calendar day and a weekday can therefore run on either matching condition rather than only their intersection. The tool explains this distinction, but the scheduler’s own documentation remains the authority for its behaviour.

Daylight-saving transitions can create missing or repeated local times in some scheduling environments. This explainer does not simulate a complete future calendar or manage job execution. Test the schedule in the actual system, including its zone and daylight-saving rules, instead of treating an expanded set of numeric fields as a complete run history.

Keep conversion and scheduling checks separate

A timestamp converter tells you what a value represents. A date formatter changes a supported date’s written form. A cron explainer describes a supported schedule pattern. None of these tools creates the scheduled job. Keep that distinction clear in documentation so a successfully explained expression is not mistaken for a deployed task.

For related record preparation, read the CSV guide and the JSON guide. The crontab manual provides primary documentation for common cron conventions. Verify your own scheduler’s supported syntax, time zone and execution logs before using a converted date or schedule in production.