Counted in your browser, nothing uploaded
LinkedIn post counter and what the Posts API documents
Short answer
LinkedIn's own Posts API reference is explicit that a maximum exists and silent about what it is. It returns HTTP 400 with the error code FIELD_LENGTH_TOO_LONG and the message "Reduce the length of the commentary or other text fields", and it never states the number that trips it. The counter on this page therefore measures in three units and sets no pass mark.
Key takeaways
- LinkedIn documents that a limit exists: the Posts API returns 400 FIELD_LENGTH_TOO_LONG for a commentary field that is too long. The pages read on 2026-10-08 do not state the number.
- The text field on a post is called commentary in the API, not post text, and it carries mentions and hashtags in a documented template format.
- The counter shows characters, UTF-16 code units and UTF-8 bytes, because none of the three can be chosen without a documented limit to match.
- Nothing is uploaded.
The counters
No denominator, because no LinkedIn page read on 2026-10-08 gives a number to divide by. All three measurements are shown so that a draft can be compared with a platform whose limit is documented in a stated unit.
commentary
The Posts API reference states that a maximum exists and returns FIELD_LENGTH_TOO_LONG for it, but the pages read on 2026-10-08 do not state the number.
No denominator, because the commentary pages read on 2026-10-08 state no length limit. All three measurements are shown because the three units disagree on every non-ASCII character, and a platform that documents its limit in one of them cannot be compared against text counted in another.
Where the text is cut off
LinkedIn truncates a long post in the feed with a "see more" control. The pages read on 2026-10-08 state no character count at which it appears, and it is not the same number as the API maximum even if that number were published. This page claims neither.
A limit that LinkedIn documents but does not number
The Posts API reference is consistent and unusually informative about the shape of the rule. In its error table it lists status 400, code FIELD_LENGTH_TOO_LONG, and a message that names the offending field and then says "Reduce the length of the commentary or other text fields." The field name is a placeholder in that message, so the response tells a caller which field failed rather than only that something did.
That is an official statement that the commentary field has a maximum. It is not a statement of what the maximum is, and the rest of the reference does not supply it. A field described in the resource section as "The user generated commentary of this post in little format" carries the same silence.
So the honest position is a known-unknown, and this page states it as one rather than filling the gap with a figure from a source that is not LinkedIn.
The error code is still useful to a builder. It names the field that failed, which is a difference from a generic validation error, and it distinguishes a length failure from a policy failure. That much is documented and quotable.
Mentions and hashtags ride in the same field
LinkedIn documents how the commentary field encodes references to other entities. A mention is written as the display text followed by a URN in parentheses, for example "Hello @[Devtestco](urn:li:organization:2414183)", and the reference explains that a developer supplies "the URN for the referenced entity and indicate which part of the text should be rendered as a link to that entity".
Hashtags use a template rather than plain text. The reference builds the hashtag out of four parts in this order: the word hashtag, a pipe character, an escaped number sign, and the term itself, so "Follow best practices " plus that four part template with coding as the term is a complete example. It states that "The commentary field hashtag data is returned with a template. For more information on the hashtag template, please refer to the little Text Format."
This matters to a length check for a concrete reason: the encoded form is longer than what a reader sees. A rendered hashtag is four characters and the template that carries it is much longer. Nothing in the pages read states whether that expansion counts toward the maximum, so this page does not say.
The three measurements, computed
The table is computed by the same code the counter runs, and is here because a post drafted on a platform with a documented limit needs to be checked in that limit's unit.
Every row is a length Koldflux computed, not a length LinkedIn states. The point of the table is that the answer to "is this too long" depends entirely on which unit the limit is written in, and LinkedIn does not write one down.
Frequently asked questions
What is the LinkedIn post character limit?
The LinkedIn pages read on 2026-10-08 do not state one. The Posts API reference documents that a maximum exists by returning 400 FIELD_LENGTH_TOO_LONG with the message "Reduce the length of the commentary or other text fields", but it does not give the number, so this page does not either.
How many characters before LinkedIn shows "see more"?
The pages read on 2026-10-08 state no character count for the fold, and the fold position is a separate thing from the API maximum in any case. The counter on this page measures length only.
What is the commentary field?
It is the post text. The Posts API reference describes it as "The user generated commentary of this post in little format", and it also carries mentions and hashtags in a documented template form.
Does LinkedIn count the markup for a mention or a hashtag?
The pages read on 2026-10-08 do not state whether the encoded form counts toward the maximum, so this page does not claim that it does or does not.
What does LinkedIn say a post length limit does not exist?
LinkedIn does not say that. Its Posts API reference lists the error code FIELD_LENGTH_TOO_LONG with the instruction "Reduce the length of the commentary or other text fields", which documents that a maximum exists. The pages read on 2026-10-08 do not give the number, and this page does not invent one.
Sources
- LinkedIn Posts API (commentary field, mentions, hashtags, error table) (checked 2026-10-08)
Every figure on this page is quoted from the platform document named above, with the date it was read. Where those pages state no limit, this page states none and says so, rather than filling the gap with a figure from somewhere else.