Extract Dates

Find dates in numeric (YYYY-MM-DD, MM/DD/YYYY) or written-month form in any text — extract dates from logs or documents as a clean list instantly.

🔒 100% Client-Side Processing

Your data is processed entirely in your browser and never transmitted to any server.

Example

Input

Invoice dated 2026-08-22, due 09/15/2026, paid Aug 30, 2026.

Output

2026-08-22 09/15/2026 Aug 30, 2026

ISO, slash-separated and written-month forms are all recognised. Dates are returned exactly as written — no normalising, so ambiguous 09/15 vs 15/09 ordering is left for you to judge.

0 / 100M Limit

Common Use Cases

Building timelines from documents

Pull every date from meeting notes or an email thread to reconstruct a chronology.

Auditing log date ranges

Extract timestamps from a log excerpt to confirm the window it covers, including the ISO 8601 form that log lines usually carry.

Finding stale dates before publishing

Sweep a draft or a docs page for every date it mentions, so a stray last year slips past review instead of past your readers.

Frequently Asked Questions

Which date formats does the extractor find?
ISO format YYYY-MM-DD (2025-03-14), numeric MM/DD/YYYY or DD-MM-YYYY with or without leading zeros (03/14/2025, 5-3-2025), and written-month formats like "March 14, 2025" or "5 Jan 2026". Two-digit years and dot-separated dates (14.03.2025) are not matched.
What is date extraction useful for?
Pulling timestamps out of log excerpts, collecting deadlines from meeting notes, and building a quick chronology from unstructured documents before sorting in a spreadsheet.
Does it find the date inside a log timestamp?
Yes. A line like 2026-08-23T14:30:00Z yields 2026-08-23, and the same holds when the timestamp carries milliseconds or sits inside brackets. Only the calendar portion is returned, never the time, so a log covering one busy day collapses to that day repeated once per line rather than to a list of distinct moments.
Does it check that a date actually exists?
No. This matches shapes, not calendars, so 2026-13-45 is returned as readily as a real date and 2026-02-30 passes too. That is deliberate for extraction work: a typo in a source document is something you usually want surfaced rather than silently dropped. Feed the results through a parser such as Python's datetime.strptime or JavaScript's Date when you need the invalid ones rejected.
How does it handle an ambiguous date like 03/04/2026?
It returns the text exactly as written and makes no attempt to decide between 3 April and 4 March, because nothing in the string itself can settle it. The practical trick is to scan the whole extracted list for a value with a first component above 12: a single 25/12/2026 anywhere in the batch tells you the source is day-first, and the rest can be read the same way. Absent that, the document's origin is the only evidence you have.
Why does the same date appear more than once?
Results come back one per occurrence, in the order they appear in the source, with no deduplication. That preserves the count, which matters when you are checking how often a deadline is restated or confirming that a log excerpt really does span the window you think it does. To collapse them, pass the output through Remove Duplicate Lines or sort it first.
Is my data private when I use this tool?
Yes. This tool runs entirely in your browser using client-side JavaScript — nothing you type is transmitted to, logged by, or stored on any server. You can safely process confidential text, tokens, or code.