LinkedIn Post Date Extractor

Stop doing this manually

Know What's Working on LinkedIn

You're here extracting one post at a time. Flux does this for every post you've ever published — automatically — and shows you what's actually driving engagement.

Which topics, formats, and posting times drive the most engagement
Weekly email digest so you never have to check a dashboard
Every historical post analyzed — works whether you post daily or weekly

$5/month

or $30/year

Start tracking →

Predictive scoring and AI access available on Edge.

Flux Edge · MCP

One post is a row. Every post is a dataset.

Flux keeps this row for every post you’ve ever published, and its MCP server lets Claude query the whole set in plain English. Works in Claude, Claude Code, Cursor, and Zed.

The row Flux stores per post

The ten fields Flux stores per post, with example values
Field	Example value
Post URL	https://www.linkedin.com/feed/update/urn:li:activity:7138259296076619777/
Post Timestamp	2023-12-06 12:13:58
Post Author	Trevor Fox
Author URL	https://www.linkedin.com/in/trevormfox
Post Content	"I just made it a whole 22 minutes into a call about how to use a new BI tool before the most important question: Is there any way to export this data as a CSV?..."
Has Image	FALSE
Has Video	FALSE
Has Document	FALSE
Likes	60
Comments	16

Run a post above and this table fills with that post’s real data.

Then ask Claude things like

When do my posts get the most engagement, by day and hour?
get_posting_insights
Find every post I wrote about hiring and rank them by comments.
search_posts
Who at HubSpot engaged with my last 20 posts?
get_post_engagers_by_company

Connect Flux to Claude — $15/mo →

Edge tier. Every Pulse plan includes 14 days of Edge.

How the MCP works →

How Does It Work?

This tool decodes the LinkedIn post URL to extract the upload timestamp, which is not visible in the standard metadata shown on the platform. Consider a LinkedIn post URL containing the number 7138259296076619777. That number is the post ID.

The post ID is a Snowflake-style 64-bit integer that encodes the timestamp when the post was created. A regular expression pulls this 19-digit number out of the URL, and it is then converted into binary. The first 41 bits of that binary representation are the actual timestamp, expressed in milliseconds since the Unix epoch (January 1, 1970). Converting those bits back to a decimal retrieves the original timestamp.

One detail matters here: the binary representation is minimal, never zero-padded to a fixed 64 bits, so "the first 41 bits" means the top 41 bits of a string whose length varies with the ID's magnitude. LinkedIn IDs run roughly 62 to 64 bits wide, so the shift is derived from the ID's actual bit length rather than assumed. That's why the decode stays correct across posts of different vintages.

Once the timestamp is recovered, it is rendered in two date formats: UTC, computed on the server, and your browser's local time, formatted in your own timezone. That gives you both a universal and a localized perspective on when the post was originally made.

What Comes Back

Alongside the timestamp, the tool reads the post's public JSON-LD structured data and returns the fields below.

Field	Description
`timestamp`	Unix timestamp in milliseconds, decoded from the post ID
`dateUTC`	The creation date and time in UTC
`dateLocal`	The same moment formatted in your browser's timezone
`author`	The post author's name and profile URL
`articleBody`	The post's text content
`image`	Whether the post carries an image
`hasDocument`	Whether the post carries an attached document
`likes`	Reaction count, when LinkedIn exposes it
`comments`	Comment count, when LinkedIn exposes it
`comment`	When the link points at a comment: its `commentId`, `timestamp` and `dateUTC`

The timestamp is decoded from the ID itself and is always available. The rest is scraped from the public page, so any field LinkedIn withholds from logged-out visitors comes back as N/A. The result panel also shows the moment as ISO 8601, Unix seconds, Unix milliseconds, and date-only and time-only in UTC, each with a copy button.

What Can You Do With the LinkedIn Post Date Extractor?

Whether you're digging into market trends, ensuring content accuracy, or conducting some serious digital investigation, each LinkedIn post URL contains more than just the location of the post.

Sales and prospect research: Brief a prospect before outreach — see when they last posted, what they post about, and how active they are. Critical signal for personalized cold messaging.
Market and competitor research: Track when competitor content lands and how their posting cadence shifts over time. Inform your own content strategy with real timestamps.
Find your best posting time: Analyze when your most successful posts were published to optimize your own schedule and maximize engagement.
Content verification: In a world of fake news, verifying when something was posted helps confirm its relevance and accuracy.
Legal evidence: Sometimes the stakes are high, and knowing the exact date of a post can serve as crucial evidence in legal cases.
Journalistic integrity: For journalists, the credibility of reporting on LinkedIn content hinges on precise dates.
Academic studies: Researchers analyzing social media patterns benefit immensely from accurate date stamps.
Personal record-keeping: For the overachievers who meticulously track their professional milestones — yes, dates matter.

Instructions

Copy the post's link. Click the ... menu at the top right of the post and select "Copy link to post".
Paste the URL above and click "Get Post Date".
Share the result. Every lookup produces a link that reproduces it — the post's ID travels in the URL, so anyone who opens it decodes the same timestamp for themselves.

The result panel shows the post's exact creation time in both UTC and your browser's local timezone, with the raw JSON available behind a disclosure if you want it. No LinkedIn login is required, and you don't need access to the post's analytics — the date is derived from the post's own ID.

What URLs work

Any link LinkedIn itself produces for a post or a comment:

linkedin.com/posts/… permalinks
linkedin.com/feed/update/urn:li:activity:… share URLs (also ugcPost and share URNs)
lnkd.in/… shortlinks, which the "Copy link to post" menu produces — resolved to the underlying post automatically
Comment and reply permalinks, from a comment's "Copy link to comment" — you get the comment's own time, with the post's time beneath it
linkedin.com/embed/feed/update/… embed URLs
linkedin.com/video/live/… live-video URLs
Any LinkedIn host, including country subdomains (in., fr., uk.) and mobile (m.)
With or without https://

Profile, company and group URLs are rejected before anything is fetched. Pulse articles (linkedin.com/pulse/…) have no timestamp in their URL, so there is nothing to decode; the tool says so rather than guessing.

The page fetch is anonymous. It has no access to your cookies or session, so anything LinkedIn hides from logged-out visitors is not recoverable here. The timestamp is the exception: because it is encoded in the ID rather than served as metadata, it decodes offline from the URL alone and doesn't depend on what the page returns.

The decoded time is when the post was created, not when it was last edited. LinkedIn issues the ID at creation and does not reissue it when a post is edited, so an edited post still reports its original publication moment.

FAQ

Can you see the exact time a LinkedIn post was published?

Yes. LinkedIn's interface only shows a rounded relative age — "2w ago", "3mo ago" — but the precise creation time is encoded in the post's ID and travels in every URL. This tool decodes it to the millisecond.

Why doesn't the date match what LinkedIn shows me?

LinkedIn rounds. A post it labels "1mo ago" could be anywhere in a multi-week window, and the label shifts as time passes. The decoded timestamp is fixed and exact, because it reflects the moment LinkedIn minted the post ID rather than a display approximation.

Do I need to be logged in to LinkedIn?

No. The timestamp is derived from the post ID in the URL, not from anything LinkedIn serves you as a signed-in member, so it decodes without an account or an API key.

Does the post's author know I looked?

No. The post page is fetched from a server, not from your browser session, so nothing is attributed to your LinkedIn account. This is not a profile view and does not appear in anyone's "who viewed" list.

Does this work on old posts?

Yes. The encoding is a property of the ID itself, so age doesn't matter — a post from years ago decodes exactly as reliably as one from this morning, as long as you have its URL.

Can I get the date of a LinkedIn comment?

Yes. Open the comment's ··· menu, choose "Copy link to comment", and paste it. The headline is the comment's time; the post it belongs to is shown beneath it. Replies work the same way.

Can I get the time as ISO 8601 or a Unix timestamp?

Yes. Every result lists ISO 8601, Unix seconds and milliseconds, and date-only and time-only values in UTC, each with its own copy button.

Can I get the date of a private or deleted post?

The timestamp will still decode, since it only needs the ID from the URL. The surrounding metadata won't: author, text, and engagement counts come from the public page, so a post that a logged-out visitor can't see returns N/A for those fields even though the date comes through.

Analyze a whole profile, not one post

These extractors decode one URL at a time. If what you actually want is to understand a whole profile — your own, a peer's, or a competitor's — I built Flux for exactly that: paste any public LinkedIn profile URL and get its full post history analyzed (engagement trends, top posts, formats, posting times), with no login and no Chrome extension, from $5/month. It's the automated version of the one-post-at-a-time workflow this tool was built to feed, and on Edge its MCP server lets Claude query that history directly.