How to Write a Logline That Actually Works

A logline is one or two sentences describing your film: who it is about, what they are trying to do, and what stands in the way. It exists so that someone can decide in ten seconds whether they want to know more.

That is the practical use. The more valuable use is diagnostic. If you cannot write a clean logline for your own film, it is almost never because you are bad at loglines. It is because the story has a hole in it, and the compression is showing you exactly where.

The structure that works

Most functional loglines are a version of this:

When [inciting incident], a [flawed protagonist] must [pursue a difficult goal] before [stakes / deadline].

You do not have to follow it word for word, and you should not make every logline sound identical. But when a logline is not landing, checking it against this shape usually reveals which piece is missing.

Worked example, built up in stages:

• Weak: "A man deals with his past." Nothing concrete. No situation, no obstacle, no stakes.
• Better: "A retired detective investigates a cold case." A situation, but no bind. Why now? What is hard about it?
• Working: "When a cold case is reopened by a rookie who idolises him, a retired detective who buried the original evidence has to help solve the crime he covered up, or watch her go to prison for his mistake."

The third one is not better because it is longer. It is better because every clause is doing a job: an inciting incident, a specific flaw that creates the bind, a goal that hurts, and a cost for failing.

The five ingredients

1. A protagonist defined by their problem, not their job. "A detective" tells us the profession. "A detective who buried the evidence" tells us the trap. Give the character the one attribute that makes this story hard for them specifically.

2. An inciting incident. The thing that breaks the status quo and starts the clock. Without it, the logline describes a situation rather than a story, and situations do not compel anyone.

3. A concrete, external goal. Something we could watch them succeed or fail at. "Find peace" is internal and invisible. "Get the confession before the trial" is external and filmable. Internal change is what the film is about; external goal is what the film does.

4. Real opposition. Either a person who wants the opposite thing, or a structural obstacle with force behind it. If the protagonist could achieve the goal by making one sensible decision, there is no film.

5. Stakes. What is lost if they fail. Stakes are the ingredient most often left out and the one that most reliably makes a logline feel flat.

The mistakes that make loglines vague

Abstract nouns. Grief, identity, redemption, belonging, connection. They feel meaningful and communicate nothing, because every film could claim them. Replace each one with the concrete situation that produces it.

Withholding the twist. Writers hide the best element because they want to preserve the surprise. But the logline is not the film, it is the invitation. If the twist is the reason the premise is interesting, it belongs in the logline. Save the surprise for the audience, not the person deciding whether to read your script.

Naming characters nobody knows. "When Marcus discovers Elena has been lying to Priya..." Three names, zero meaning. Use roles: a night nurse, a retired detective, an estranged brother. Names carry information only after we care.

Plot summary instead of premise. If it has an "and then... and then...", it is a synopsis. A logline describes the engine, not the journey.

Genre confusion. The reader should be able to feel whether this is a thriller, a comedy, or a drama from the sentence itself. If your logline could plausibly be any of the three, the tone is unclear, and tone confusion in development becomes tone confusion on set.

Length, and the honest version of the rule

The common advice is one sentence, under about 40 words. That is a good target and a bad religion.

Two sentences is fine, and for genuinely complicated premises it is often clearer. What matters is that it is tight, meaning every word is load-bearing. A 45 word logline where all 45 words work is better than a 30 word one that had to drop the stakes to fit.

The real limit is attention, not word count. If someone loses the thread halfway through, it is too long regardless of length.

Using it as a tool on your own story

This is the part most guides skip, and it is the reason to write a logline even if you never show it to anyone.

Write your logline. Then interrogate it:

• Is the goal external and specific? If not, you may not yet know what your character is actually doing for ninety minutes.
• Does the opposition have its own motive? If the antagonist exists only to obstruct, they will feel thin on screen too.
• Do the stakes escalate, or are they fixed? A logline with static stakes often signals a second act with no rising pressure.
• Is the protagonist active? If your logline has them mostly reacting to events, check whether the finished script has the same problem. It usually does.
• Would you watch this if a stranger described it to you? Not "is it meaningful to me". Would you sit down.

Each of those questions is really a question about the screenplay. The logline is just the cheapest place to ask it.

Ten drafts is normal

Nobody writes a good logline first try, and the useful process looks like this:

1. Write the sprawling ugly version, three or four sentences, everything included.
2. Cut every clause that is not the protagonist, the goal, the obstacle, or the stakes.
3. Replace every abstract noun with a concrete situation.
4. Replace every character name with a role.
5. Read it aloud. Anything you stumble over is unclear on the page too.
6. Say it to a person and watch their face rather than asking their opinion.
7. Rewrite. Repeat until someone asks a question about the story instead of about the sentence.

Step 6 is the one that works. People are polite about writing and honest with their faces.

A note on when you write it

There are two schools: write the logline first as a compass, or write the script first and derive the logline after.

Both are defensible, but for a first film, write it first. Not because it locks anything, but because the questions it forces are the exact questions that stop a first draft from collapsing in the second act. You are allowed to change it later. Most people do.

Next

You know what the film is and you can say it in two sentences. The next decision shapes everything downstream, including how much money you need and how long you will live with this: whether this idea is a short, a feature, or a series.