Find the exact date, time, and second any X (Twitter) post was published, decoded straight from the tweet ID.
One per line, up to 50. Accepts x.com and twitter.com status URLs, or a bare tweet ID. Works for tweets posted after November 2010 (when Twitter switched to Snowflake IDs).
The X post date extractor shows the exact date, time and second a tweet was published. Paste an x.com or twitter.com status link, or a bare tweet ID, and the tool decodes the creation time for you. It is free, needs no sign-in and works for posts made after November 2010.
A tweet ID timestamp is the creation time built into the number at the end of every post URL. Since November 2010, X (formerly Twitter) has generated post IDs in a format called Snowflake, and the first part of each ID counts the milliseconds since a fixed starting point.
That starting point is November 4, 2010 at 01:42:54.657 UTC. Shifting the ID's lower 22 bits away and adding the starting point gives the moment the post was created. The remaining 22 bits identify the machine and a sequence number, so they say nothing about time.
This is why you can learn the date of a post without opening it. The date is not hidden metadata that someone could edit. It is part of the ID itself, so the result is the same whether the post is public, deleted, or sits behind a login wall you cannot pass.
X shows relative times such as "3h" or short dates in the interface, and the full timestamp sits behind a hover or a click. The ID in the address bar already holds that information, which makes extraction fast and consistent across every post.
You can decode a post date in under a minute. The steps below match the fields and buttons on this page.
https://x.com/username/status/1609338612741046272.The tool accepts x.com and twitter.com status links, mobile links, links that use the /i/web/status/ form, and plain numeric IDs.
Take the sample ID 1609338612741046272. Paste it, click Extract Dates and leave the time zone on UTC. The decoded moment is midnight UTC on January 1, 2023.
Now switch "Show times in" to America/New_York. The same post now reads as 7:00 PM on Saturday, December 31, 2022. Nothing about the post changed. Only the clock used to display it did.
This matters when you cite a post. If a news article says a tweet went out "on New Year's Eve" and you see January 1, check which zone your result uses before you call either one wrong. For records, UTC is the safest choice because it is the same for everyone.
Each card gives you the same set of values, and each one fits a different job.
| Result | What it shows | Best used for |
|---|---|---|
| Published | Full date and time in your chosen zone | Reading and quoting |
| ISO 8601 (UTC) | Standard timestamp with milliseconds | Spreadsheets and databases |
| Unix timestamp | Seconds and milliseconds since 1970 | Scripts and sorting |
| Age | Time since posting, such as 2 years ago | Quick freshness checks |
Use the ISO value when you need a precise, unambiguous record. It ends in Z, which means UTC, so nobody has to guess the zone. Use the Unix value when you want to sort many posts in order, because a plain number sorts correctly in any spreadsheet.
The post type label tells you how the line was read. "Post (tweet)" means the tool found a status link, and "Raw ID" means you pasted a bare number. Both decode the same way.
No. This tool works in one direction: you give it a post, and it returns the date. It does not search X, list posts from a date range or sort an account's timeline.
If you want to find posts from a certain period, X's own advanced search lets you set a date range, and search operators such as since: and until: narrow results by day. Once you have the links, bring them here to confirm exact times or export them with their dates as a CSV file.
This combination works well for audits. Collect the post links you care about, paste up to 50 at a time, and export. You get a sortable sheet of when each post went live.
Anyone who has to prove when something was said benefits from an exact timestamp. These are the most common situations.
If you work across platforms, there are matching tools for dating a post from Instagram, LinkedIn and TikTok. You can also browse the full YouTube and social media tools category.
A few habits prevent most mistakes with decoded dates.
Write the zone next to every time you record. A post made at 11:30 PM in California is already the next day in UTC. Switching the "Show times in" menu to UTC before you export keeps a whole batch consistent.
A repost points to the original post's ID, so the date you get is for the original, not for when someone shared it. A reply or a quote post has its own ID and its own date. Copy the link of the exact post you want to date.
The decoded time is the moment X assigned the ID, which is the moment the post was created. Edits, later replies and likes do not change it. The result is precise to the millisecond, and the full date view shows seconds.
The tool reads the ID only. It does not check whether the post still exists, who wrote it or whether the text was changed. For a deleted post, the ID still gives a date, but you may have no other proof of the content. Keep a screenshot and the link together when the record matters.
Paste your post links into the box above, click Extract Dates and choose the time zone that fits your report. In a few seconds you will have the exact publish time of every post, ready to copy or export. If you are drafting posts of your own next, the Twitter thread generator can help you plan them.
Your report has been submitted. We will look into this issue.
A VPN changes your network exit. It does not guarantee anonymity.
Themes, plugins, code, video, audio, graphics & more from 90,000+ authors.
Web Development
Design & Media
Unlimited Access
Explore Envato Market