JSON Validator
Check JSON syntax and get the exact line, column and cause of any error.
Work out the gap between two dates, in every unit including working days.
The Relative Time Calculator walks the calendar rather than dividing by an average, so one month after 31 January is 28 February — where a person would put it — instead of the off-by-a-day answer field subtraction gives.
Two dates in, and the gap between them broken down properly — years, months and days, plus every total, plus the working days between them.
Calendar arithmetic is where date libraries earn their keep, and it is easy to get subtly wrong. Subtracting the fields and dividing by 30 gives you a plausible-looking answer that is off by a day or two most of the year. This walks the calendar instead: one month after 31 January is 28 February, because that is where a person would put it, and the remaining days are counted from there. The relative wording — "3 days ago", "in 2 hours" — comes from the browser’s own formatter, so it matches what a native application would say.
Whole months are walked forward and clamped, so month lengths and leap years are handled rather than averaged away.
Weekends excluded, which is the figure a deadline actually depends on.
Total days, hours, minutes and seconds alongside the calendar breakdown, because different questions want different answers.
Generated by the browser’s own formatter, so it matches what a native application would say.
Either order works, and the result says which way round it went.
Type it, or use the button to take the current moment.
Either order — the calculator says which direction it went.
Years, months and days, then every total, then the working days.
The "3 days ago" form is generated too, for dropping into an interface.
As long as the actual month. The calculation walks the calendar rather than dividing by an average, so one month after 31 January is 28 February and the leftover days are counted from there.
Monday to Friday, with both weekends excluded. Public holidays are not, because they differ by country and by year — subtract them yourself if they matter.
The calendar breakdown is unaffected: a day is a day whether it contained 23 hours or 25. The total-hours figure does reflect the real elapsed time, so the two can differ by an hour across a change.
Your own, unless you enter a date with an explicit offset or a Z. Everything is calculated in the browser, so nothing about your machine leaves it.
What people who use the Relative Time Calculator 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 Relative Time Calculator. It takes half a minute and no account.
Write the first reviewCheck JSON syntax and get the exact line, column and cause of any error.
Generate a production Dockerfile with multi-stage builds and layer caching.
Build CSS keyframe animations and watch them run as you edit.
Work out a subnet: network, broadcast, host range and usable count.
Reformat a MAC address between every notation, and decode what it means.
Generate Kotlin data classes with Gson or kotlinx.serialization annotations.
Turn a curl command into working fetch, axios, Python, PHP, Go or Ruby.
Normalise YAML indentation, quoting and key order in one pass.