TL;DR means too long; didn't read. It introduces a short summary of a long post or article, and it's also used, rudely, as a reply to a message someone thinks is too long. Wikipedia says the phrase dates from at least 2002. In business writing, a TL;DR puts the main point first.
You've probably seen it at the top of a long forum post, under a rambling thread or in a colleague's message: "TL;DR". It's one of the few pieces of internet shorthand that's really useful to a business owner, because it describes something every reader wants, which is the short version first. Here's what it means, where it came from, how people use it and how to write a good TL;DR of your own.
The meaning of TL;DR
TL;DR, also written TLDR or tl;dr, stands for "too long; didn't read". Dictionary.com defines it two ways. It's used online to introduce a summary of a lengthy text, and it's also used, usually considered rude, as a comment on a post or message thought to be too long. It can be a noun too: a TL;DR is the short summary itself. Dictionary.com's own example sentences show the typical pattern, where a writer gives the quick answer and says the detail follows below.
Where TL;DR came from
Wikipedia says the phrase dates from at least 2002. It cites the Oxford English Dictionary, which gives its earliest known use as a message on a Usenet newsgroup about Nintendo video games. Wikipedia adds that the term turned up in a book based on Urban Dictionary in 2009, appeared in a Twitter slang book the same year, and was added to Oxford Dictionaries Online in 2013. Dictionary.com says it was first recorded in 2000 to 2005 from its use in digital communications, which fits.
So the habit is old. People were skimming long posts long before social media made it normal, and TL;DR is simply the polite (or impolite) name for that habit.
TL;DR in texts, comments and emails
The same four letters can mean two quite different things depending on who's typing them. Here's how to tell:
| How it's used | What the writer means | Tone |
|---|---|---|
| At the top of a long post | Here's the quick version before the detail | Helpful |
| At the bottom of a long post | In short, this is the point | Helpful |
| As a reply to someone's long message | Your message was too long for me to read | Dismissive |
| In a work email | Summary first, for readers short of time | Practical |
The first two are the ones that matter for business. The third is the one that gets people into arguments, so I'd avoid it unless you know the person well.
Example TL;DR messages
These are invented examples to show how it sounds. None are real messages:
- Example (helpful): "TL;DR: the meeting has moved to Thursday and you don't need to prepare anything."
- Example (helpful): "Long post below, but TL;DR, the new booking page is live."
- Example (summary at the end): "That's the full story, and the TL;DR is that we're changing supplier."
- Example (dismissive): "Tl;dr. Can someone sum this up?"
- Example (from a friend, joking): "Your holiday story is brilliant but I'm going to need a tldr."
Why a TL;DR works for business writing
Most people skim. That isn't laziness, it's how we all cope with a full inbox. A TL;DR respects that by putting the answer where the reader's eye lands first. It's also the idea behind the news-writing habit of putting the bottom line up front, a concept Wikipedia lists as a related topic. I use this principle on every page I write: give the direct answer first, then let people read on if they want the detail.
A TL;DR helps in several places in a small business:
- Long emails to clients, where a two-line summary at the top gets read even when the rest doesn't.
- Blog posts and guides, where a summary box helps visitors decide whether to stay.
- Newsletters, where the first line can carry the main point.
- Social posts with a long caption, where the first sentence is what shows before the "more" button.
- Reports and proposals, where a decision-maker may only read the summary.
How to write a good TL;DR
A bad summary just repeats the opening. A good one gives someone who reads nothing else the thing they most need. Try these steps:
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
- Decide the one thing you'd want the reader to know if they read nothing else.
- Write it in one or two short sentences, in plain words.
- Put any decision or action they need to take inside it, such as a date or a request.
- Place it at the top for emails and reports, or directly under the headline for posts.
- Read it on its own. If it makes sense without the rest, it's done.
Writing the words out is often better in formal settings. "Summary:" or "In short:" reads more professionally than TL;DR in a message to a new customer, and it's clearer for readers who don't know the abbreviation. For a casual newsletter or a post aimed at an online audience, TL;DR is fine. If you send a lot of messages to customers, my WhatsApp Business greeting messages guide shows how to keep short openers friendly, and these Messenger tips help with handling replies quickly.
Replying when someone sends you a TL;DR
If someone sends a TL;DR with a long post, they're doing you a favour. Reply to the summary first, and read the detail only if you need it. If someone replies "TL;DR" to your own long message, don't take it personally. Either send a shorter version or lead with the main point next time. It's useful feedback about how people read.
The same goes for your posts. If followers keep asking for a summary, your content may need a clearer opening. My guides on hashtags that work on TikTok and Instagram and how Stan Twitter slang works show how short, punchy writing travels on social platforms.
Frequently asked questions
What does TL;DR stand for?
TL;DR stands for too long; didn't read. It's used to introduce a summary of a long text, or as a comment saying a post was too long to bother with.
Where does TL;DR come from?
Wikipedia says the phrase dates from at least 2002, citing the Oxford English Dictionary, which found its earliest known use in a Usenet message about Nintendo games.
Is TL;DR rude?
It depends how it's used. Offering a TL;DR of your own post is helpful. Replying TL;DR to someone else's message is usually seen as dismissive.
Should I use TL;DR in a work email?
It's fine with colleagues who use it. For clients or formal messages, write "Summary:" or "In short:" instead, which is clearer to everyone.
How long should a TL;DR be?
One or two short sentences. It should give the main point and any action the reader needs to take, and make sense even if nothing else is read.
