Date & Timezone Normalizer - Parse, Convert, ISO 8601 avatar

Date & Timezone Normalizer - Parse, Convert, ISO 8601

Pricing

from $1.00 / 1,000 date normalizeds

Go to Apify Store
Date & Timezone Normalizer - Parse, Convert, ISO 8601

Date & Timezone Normalizer - Parse, Convert, ISO 8601

Parse messy dates and convert them to a timezone you choose. Returns ISO 8601, UTC and a Unix timestamp. $0.001 per unique date. Strings we cannot parse are free. Works from Apify MCP and the API.

Pricing

from $1.00 / 1,000 date normalizeds

Rating

0.0

(0)

Developer

Tidy Byte Tools

Tidy Byte Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 hours ago

Last modified

Features

Limited permissions

Share

Parse messy dates and convert them to a timezone you choose. Returns ISO 8601, UTC and a Unix timestamp. $0.001 per unique date. Strings we cannot parse are free. Works from Apify MCP and the API.

Also searched as: ES: convertir zona horaria, normalizar fechas / PT: converter fuso horário / DE: Zeitzone umrechnen, Daten normalisieren / FR: convertir un fuseau horaire / JA: タイムゾーン変換、日付正規化

Website and local versions

  • Website — Tidy Byte Tools product page

What it does

  • Parses messy dates, times and relative phrases like "tomorrow at 2pm".
  • Converts each result to a timezone you choose.
  • Returns ISO 8601, UTC, a Unix timestamp and an optional custom format.
  • Marks numeric dates that could be read two ways (for example 03/04/05) as ambiguous, and flags relative phrases.

Price

You pay $0.001 per unique date we parsed and saved. Blank lines, repeats and strings we cannot parse are free. There is no start fee from us. Apify adds its normal small platform cost. Set a max cost for the run and we stop there. We never charge for work we did not save.

How to use

  1. Paste dates, add a list, or add file links (one date per line).
  2. Set the source timezone (used when a string has no timezone of its own) and the target timezone.
  3. Click Start, or call this Actor from Apify MCP and the API.
  4. Get results in the Output tab.

Input

  • Dates: One date or time string per line.
  • Or paste dates: Paste dates, one per line.
  • File links: Links to text files with one date per line.
  • Source timezone: Used when a string has no timezone of its own. Prefer IANA names like America/Chicago or UTC.
  • Target timezone: Timezone for the converted result.
  • Date order for numeric dates: Guess, or force month/day/year, day/month/year, or year/month/day.
  • Custom output format: Optional Python strftime pattern such as %Y-%m-%d %H:%M. Leave blank for ISO 8601.

Example (before and after)

Before: messy dates such as 3/4/26 9pm or next Tuesday, plus a target timezone such as America/Chicago. After: one row per unique date with ISO 8601, UTC, and a Unix timestamp, plus flags when the numeric date is ambiguous or the phrase is relative. Strings we cannot parse are free.

Good to know

  • Relative phrases such as "tomorrow" or "in 3 hours" use the time of the run.
  • If a numeric date could be read two ways, we mark it as ambiguous and include the other reading.
  • US abbreviations such as CST and EST are accepted. CST means US Central (America/Chicago). Prefer IANA names when you can.
  • This is not a legal or payroll clock. It does not cover every historical timezone change.
  • Your data is only used for your run.
  • Made by Tidy Byte Tools. Questions? Open an issue on this Actor's page.

More tools from Tidy Byte Tools

These Actors work well together:

Free local tools (no Apify account needed): pdf-table-pull-lite, doc2md-lite, link-check-lite, md-chunk-lite, json-shaper-lite.

Website: https://tidybytetools.github.io. All Actors: apify.com/tidybytetools.