How Long Should a TL;DR Be? The Right Length for a Summary
TL;DR started as a two-word dismissal of a Usenet post in 2002. Somewhere between then and now, it grew into its own writing format — with a template, a word limit, and a whole content-marketing industry telling you how to write one.
TL;DR — "too long; didn't read" — began as internet shorthand for refusing to read something, not as an instruction to summarize it. The Oxford English Dictionary traces its earliest documented use to a 2002 post on the Usenet newsgroup rec.games.video.nintendo, and by 2013 it had been formally added to Oxford Dictionaries Online. Somewhere in between, the phrase flipped from an insult into a section header: instead of readers writing "TL;DR" to dismiss a post, writers started adding their own TL;DR to the top of long posts to summarize it for people who might say exactly that.
Drafting a summary and want to see the word count as you trim it? Clear Count tracks it live in your browser, nothing uploaded anywhere.
The Short Answer: Under 150 Words
Most writing and content guides converge on a similar number even though none of them cite a shared authority for it: a TL;DR should stay under roughly 150 words, and often closer to one or two sentences. One widely cited internal guide from Meta's research team puts it even more concretely — whatever "comfortably fits on a slide in 40-point font," which in practice lands in the same range.
That's a strange kind of consensus for an internet slang term with no style-guide authority behind it, but it makes sense once you consider what a TL;DR is actually competing against: the reader's decision, made in a few seconds, about whether the full piece is worth their time at all. A summary that takes as long to read as a skim of the original defeats its own purpose.
How TL;DR Compares to Other Short Forms
TL;DR isn't the only short-form summary writers are expected to produce, and the length conventions differ enough between formats that reusing one for another usually produces something too short or too padded:
| Format | Typical Length |
|---|---|
| TL;DR | 1–3 sentences, under 150 words |
| Meta description (SEO) | 150–160 characters (~25 words) |
| Academic abstract | 150–250 words |
| Executive summary | ~5–10% of the original document |
The academic abstract is the closest formal cousin to a TL;DR in terms of length, but the two are built for different readers: an abstract has to stand alone as a citable, self-contained summary of a study's methods and findings, while a TL;DR only has to work sitting directly above the thing it's summarizing.
A Simple Template That Actually Fits the Word Limit
A structure that keeps a TL;DR inside the 150-word range without feeling clipped: one sentence stating the main point, three to four supporting details at most, and a closing line with the takeaway or recommendation. The three-to-four cap on supporting points isn't arbitrary — it lines up with long-established cognitive science findings on short-term working memory, sometimes summarized as "the magic number four," which is roughly how many discrete items most people can hold in mind at once without a list starting to blur together.
There's a real tension in how TL;DR gets used today: the phrase was born as a shorthand for refusing to engage with a wall of text, and now there are templates, word counts, and cognitive-science justifications for how to write one properly. A term that started as "I'm not reading this" has become its own small writing discipline — which is either an improvement or a punchline, depending on how seriously you take the internet's own history.
When a TL;DR Is Worth Adding
A TL;DR earns its place at the top of anything long enough that a reader might reasonably bail before reaching the point — a long-form blog post, documentation, a lengthy email, a forum post laying out an argument. It's less useful, and sometimes actively distracting, at the top of something already short: a three-paragraph post doesn't need a summary of itself, and stacking one on top just adds length back in the name of cutting it.
Checking whether a draft summary is actually staying inside a reasonable range is a fast habit to build — a TL;DR that creeps past 150 words while being edited is easy to miss without counting. Clear Count gives an instant word count for anything pasted in, which makes it simple to confirm a summary is still doing its job before it goes live.
The honest summary of this post about summaries: keep a TL;DR under 150 words, lean toward one to three sentences when possible, and follow a simple structure — main point, a few supporting details, a takeaway — rather than trying to compress the entire piece into it. The format has more convention behind it now than its two-word-insult origins would suggest, but the underlying goal hasn't changed: let the reader decide fast.
For questions or inquiries contact us at info@cleartexteditor.com