About TimeMeaning
TimeMeaning is a free public utility for resolving ambiguous time references. You paste a time expression — from an email, a calendar invite, a log file, a message thread — and the tool tells you what it actually means, with every assumption stated explicitly.
It is not a timezone converter. Converters assume you know what timezone you're in and what timezone you're converting to. TimeMeaning handles the step before that — figuring out what a messily written time reference actually refers to, when the timezone is ambiguous, when daylight saving time changes the answer, or when the expression is relative ("next Friday") and needs anchoring to a specific date.
The tool is deterministic. The same input with the same context always produces the same output. There is no machine learning making probabilistic guesses. When the tool makes an assumption — that EST means Eastern Standard Time rather than Australian Eastern Standard Time, that "next Friday" means the upcoming Friday rather than the one after — it says so explicitly. You can see every step of the reasoning.
Why it exists
Timezone ambiguity is a solved problem at the machine level. UTC is unambiguous. ISO 8601 with an explicit offset is unambiguous. The IANA timezone database is authoritative and comprehensive.
The problem is that humans don't write machine-readable time references. They write "3pm IST" and "next Friday morning GMT" and "end of day Thursday CET." These expressions are natural in speech and writing but genuinely ambiguous when read by someone in a different context. The sender knows which IST they mean. The recipient cannot.
Most tools that exist to help with this problem resolve the ambiguity silently — they make a guess based on your IP address, your account settings, or the most common interpretation, and present the result as if no ambiguity existed. This is worse than no resolution at all, because it creates false confidence in an interpretation that may be wrong.
TimeMeaning takes a different position: ambiguity should be surfaced, not hidden. Every assumption is shown. Every interpretation is explained. The goal is not to guess correctly — it is to make the reasoning transparent enough that you can decide whether the interpretation is right for your context.
How it works
The resolver uses a deterministic five-step pipeline: tokenisation, structural parsing, ambiguity detection, DST resolution, and output generation. It draws on the IANA Time Zone Database for timezone rules and DST transition dates. It does not learn from or retain your input — time references are processed in your browser and not transmitted to any server.
A full explanation of the pipeline, including the reasoning behind specific disambiguation choices, is available in the Learning Centre.
→ How TimeMeaning resolves a time referenceWho built this
TimeMeaning was designed and built as a precision utility for anyone who works across timezones — developers, distributed team managers, support professionals, aviation and maritime crews, and anyone who has ever spent five minutes wondering whether a meeting invite has the right time.
The tool is free to use and will remain free. An API for programmatic access is in development for teams who need to resolve time references at scale.
→ Register for API early accessThe data
TimeMeaning does not store the time references you enter. It does not create user accounts. It does not track individual sessions. Anonymous aggregate analytics help us understand which tools and articles are most useful — no personal data is involved.
Timezone rules are sourced from the IANA Time Zone Database, the authoritative global standard for timezone and DST data used by operating systems, programming languages, and standards bodies worldwide.
TimeMeaning incorporates each IANA Time Zone Database release within 48 hours of publication. The current incorporated version is IANA 2026a. Historical timezone rules for dates before the current release are resolved using the correct historical IANA data for that date, not the current rules.