How to Write a Logline That Passes the Lie-Detector Test
A logline is not a marketing line you write at the end. It is a tool you write first, and it will tell you the truth about whether you actually have a story.
Most writers treat the logline as a chore for the end, a marketing sentence to bolt on once the real work is done. That is exactly backwards, and it is why so many scripts wander for a hundred pages without ever finding themselves. A logline is not a decoration. It is a lie detector. Write it first, and it will tell you, in one honest sentence, whether you actually have a story or just a mood.
A logline is a single sentence, sometimes two, that names your protagonist, their goal, the obstacle in the way, and what is at stake if they fail. That is the whole machine. And the discipline of fitting a film into that sentence is one of the most useful things you can do, because a story that cannot survive the compression was never solid to begin with.
The four parts every working logline needs
Strip away the variations and every strong logline carries the same load-bearing parts. The breakdowns at The Script Lab and MasterClass circle the same four.
- A protagonist, ideally with one telling trait, not a name. "A washed-up boxer," not "Rocky."
- A goal, the concrete thing they are chasing. Specific, active, visible.
- An obstacle, the force pushing back. Without it you have a plan, not a plot.
- The stakes, what it costs to lose. This is the part beginners forget, and it is the part that makes us care.
Take Die Hard: an off-duty cop must save his estranged wife and a tower full of hostages from a group of thieves posing as terrorists, alone, with no shoes and no backup. Protagonist, goal, obstacle, stakes, and a whiff of the specific irony that makes it that film and not a hundred others.
The test that exposes a broken story
Here is the real value, the reason I write the logline before the outline. If you sit down to write the sentence and you cannot, if it keeps sprawling into three clauses and a "but also," that is not a wording problem. It is a diagnosis. It means you do not yet know what your film is about. You have a situation, maybe two, fighting for the wheel.
That failure is a gift. Most first drafts die because the writer never noticed they had two films tangled together. The logline catches it on day one, before you have burned three months. So keep rewriting the sentence until it stops embarrassing you, and treat every failure to compress as information about the story, not about your sentence skills.
If you cannot say it in one clean line, you do not yet know what you are writing. That is data, not defeat.
Watching a logline get honest, draft by draft
Let me invent a writer's process to show what this actually looks like, since the diagnosis I mentioned above is easier to feel in motion than in the abstract. Say a writer, I will call him Devraj, wants to write about a cricket coach in a small town. His first attempt at a logline reads: "A dedicated coach in a small town trains a talented group of underprivileged boys, faces resistance from the local council, deals with his own troubled past, and eventually leads them to a tournament that changes everything." Read that sentence again. It has four clauses joined by commas pretending to be one idea. It is not a logline. It is a table of contents.
Devraj's second attempt narrows it, forcibly: "A former professional cricketer, disgraced after a match-fixing scandal, coaches a team of boys from his old slum neighborhood, risking the one chance he has left to reclaim his name when a rival council member tries to shut the program down over money he embezzled himself." Better. There is a protagonist, a want, an obstacle, and something at stake. But it is still clause-heavy, still trying to hold two conflicts, the redemption arc and the corrupt-official subplot, in one breath.
The third attempt, the one that actually works, drops the subplot entirely from the sentence and trusts it to live inside the script instead: "A disgraced cricketer, chasing one last shot at his own redemption, coaches a slum team toward a tournament that could clear his name, or confirm every reason the town already had to write him off." That sentence has a spine. Notice what disappeared: the council member, the embezzlement detail, half the plot. None of it vanished from the film. It just stopped needing to live in the logline, because the logline's job is the emotional throughline, not an inventory of every subplot. That is the real work of drafting a logline, cutting until only the load-bearing wall remains standing.
The irony that turns a summary into a hook
A logline that only lists the parts is accurate and dead. The ones that grip have a built-in tension, an irony, the sense of a person forced into exactly the situation they are least equipped for. The Social Network is, in a sentence, the story of a young man who builds the world's largest tool for human connection and loses every real friend he has in the process. The engine of that logline is contradiction. The thing he creates is the thing that isolates him.
Hunt for that contradiction in your own story. The best loglines have a "but" hiding in them, spoken or not. A hitman who must protect the child of his target. A deaf drummer chasing a career built on hearing. When you find the irony, the logline stops describing the film and starts selling it, because a contradiction is a question the audience needs answered.
Show the stakes, do not label them
Even in one sentence, the show-don't-tell instinct applies. A weak logline says the stakes are "high" or "life-changing," which are empty words that promise nothing. A strong one shows the concrete loss. Not "with everything on the line," but "or his daughter dies in the flood." Specific stakes make a specific promise, and the same principle that governs a whole scene, which I unpack in show, don't tell, governs the single sentence too. Concrete beats abstract, always, even here.
Common ways the logline goes wrong
A few failures I see again and again, in others and in my own drafts.
- Naming characters. A reader who does not know your script does not know who "Maya" is. "A grieving surgeon" tells them instantly.
- Listing plot instead of conflict. "This happens, then this, then this" is a synopsis. A logline is one arc of want against obstacle, not a chain of events.
- No stakes. If failing costs nothing, there is no story, and the missing stakes are usually the reason the logline feels flat.
- Vagueness dressed as intrigue. "A man discovers a dark secret" could be ten thousand films. Specificity is the whole game.
- Weak stakes disguised as adjectives. "High stakes" and "everything changes" are placeholders a lazy first draft leaves behind. Go back and name the actual, specific loss, the way raising the stakes properly requires you to do across the whole script, not just the sentence describing it.
Using the logline to pitch, not just to plan
A logline that survives the writing desk still has one more job ahead of it: the room. Whether that room is a producer's office or a five-minute conversation at a festival, the sentence you built for yourself becomes the sentence you say out loud, and it needs to hold up under a very different kind of pressure, the pressure of being heard once, cold, with no chance to explain. This is the connective tissue between the logline and the pitch itself, which I cover in full in how to pitch a screenplay. A logline that only works on paper, with time to reread it, is not finished. Say it out loud to someone who has never heard your premise and watch their face. If they ask a clarifying question you did not expect, that question is telling you exactly which part of the sentence failed to land.
The logline is your compass, not your billboard
So write it first, before the outline, before the beat sheet, before a single scene. Not because a producer will ask for it, though one will. Because the sentence is the tightest possible statement of what you are about to spend months building, and you want that statement clear before you lay the first brick. When you drift at page 50, and you will, the logline is the compass that tells you which scenes belong and which wandered in from a different film.
Once the sentence holds, the story starts to open into its shape. The next move is to map the beats without letting the map strangle the life out of it, which is what a beat sheet is for, and when to ignore it. And if you are earlier than all this, still deciding whether you even have a film, go back to the working method and start where every real story starts, with a person who wants something they might not get. The logline is just that want, said out loud, in one sentence that refuses to lie.
What are the four parts of a logline?
A protagonist described by trait rather than name, a concrete goal, an obstacle that blocks it, and the stakes if the protagonist fails. Miss any one of the four and the sentence stops functioning as a logline.
How long should a logline be?
One sentence, occasionally two. If it keeps sprawling into a third clause or a string of "and then," that is usually a sign the story itself has not been narrowed down to one clear throughline yet.
Should I write the logline before or after the screenplay?
Before, ideally before the outline. Writing it first turns the logline into a diagnostic tool that exposes a shapeless premise on day one, rather than a marketing task bolted on after months of work.
Why does my logline feel flat even though it has all four parts?
It is probably naming the stakes instead of showing them, or missing the built-in irony that makes a premise feel inevitable. A flat logline usually needs a specific consequence and a genuine contradiction, not just accurate information.