Before a script gets read, before a meeting gets taken, before anyone in this industry invests real time in your story, they hear a logline. If it doesn't work, nothing after it gets a chance to. A logline isn't a marketing afterthought bolted onto a finished script. It's often the most important few lines a writer produces, and treating it as a craft in its own right, not an obligatory summary, is what separates a pitch that lands from one that gets forgotten in the same meeting it was delivered in.
What a logline actually is
A logline is a short summary, typically one to two sentences, of a story's core premise: who it's about, what they want, what's stopping them, and what's at risk if they fail. It's not a plot summary and it's not a synopsis. A synopsis tells someone what happens. A logline sells someone on why they should care what happens. That distinction is the difference between a professional pitch and an amateur one, and it's worth sitting with before writing a single draft.
The reason it matters before the script exists is simple: a weak logline is usually a symptom of a weak premise, and that's far cheaper to discover on page one of an outline than on page ninety of a finished draft. Writers who can't compress their story into a sharp, magnetic pitch often haven't fully figured out what their story actually is yet. Working out a strong logline early forces a kind of clarity that's much harder, and much more expensive in time, to retrofit after 110 pages are already written.
It also matters because loglines are doing real work constantly throughout a project's life. They're what a manager pitches to a producer. They're what a producer pitches to a financier. They're the first line of a query letter, the header on a marketplace listing, and often the only information someone has before deciding whether to request the full script at all. A professional treats the logline like a trailer, not like fine print.
The anatomy of a professional logline
Most strong loglines, regardless of genre, are constructed from the same four load-bearing components. Understanding what each one is for, not just what it is, is what turns a formula into an instinct.
Protagonist. Usually described by role or defining trait rather than name, since a name means nothing to someone who hasn't read the script. But the best loglines go a step further and let the descriptor itself carry irony or tension. "A washed-up boxer" is a role. "A boxer who's never lost a fight he can remember" hints at a twist without spelling it out. The protagonist description is your first chance to do double duty.
Goal. What the protagonist wants, stated with enough precision that a listener immediately understands what winning looks like. Vague goals ("find happiness," "discover the truth") are the single most common weakness in amateur pitches, because they don't give a listener anything concrete to root for.
Obstacle. What's standing between the protagonist and that goal. The strongest obstacles are specific, active, and ideally ironic in relation to the goal itself, an obstacle that's connected to the protagonist's own flaw or history lands harder than one that's simply external and generic.
Stakes. What happens if the protagonist fails, or what makes the goal urgent rather than optional. This is the component amateurs skip most often, and it's usually the one doing the most emotional work. A goal without stakes is a description. A goal with stakes is a story.
A scaffold version reads like: [Protagonist] must [goal] before [obstacle], or [stakes]. Treat that as training wheels, not a finished product. Some of the strongest working loglines break the template's word order entirely once a writer understands why each piece exists. The four ingredients matter far more than the sentence structure that carries them.
Constructing a stellar logline, step by step
Here's where craft actually happens, in the compression itself. Start wide and cut hard.
Step one: write the honest, boring version first. Describe your story in plain, complete sentences, even if it takes a paragraph. Don't worry about hooking anyone yet. You're just getting the real shape of the story onto the page.
Step two: isolate the single sharpest irony or tension in the premise. Almost every strong logline is built around one central irony: a peacemaker forced into war, a con artist who falls for their mark, a coward who has to save the one person who never believed in them. Find that friction point in your own story. It's usually the thing that made you want to write it in the first place.
Step three: build the sentence around that irony, not around plot order. Amateur loglines tend to march through the story chronologically. Professional loglines lead with whatever creates the most tension, even if it's not technically "first" in the plot.
Step four: cut every word that isn't doing one of the four jobs. If a word isn't establishing protagonist, goal, obstacle, or stakes, it's very likely dead weight. This step is brutal and it's supposed to be. Most first drafts of a logline are 30 to 40 percent longer than they need to be.
Step five: read it out loud to someone who knows nothing about the project. If they don't lean in, something is still too vague, too plot-heavy, or too low-stakes. This is the fastest, cheapest diagnostic available, and most writers skip it out of nerves rather than lack of access to it.
Strong vs. weak, in practice
A weak logline tends to read like a synopsis fragment: "A young woman navigates family secrets and past relationships while discovering who she really is." That's a mood, not a premise. There's no clear goal, no specific obstacle, and nothing that suggests where the tension is actually coming from.
A stronger version of the same idea might read: "When a woman inherits her estranged mother's restaurant, she has thirty days to save it from closure, or lose the only connection she has left to the family she never understood." Same emotional territory, completely different level of craft. Protagonist, concrete goal, hard deadline as obstacle, and stakes that are personal rather than abstract.
Real-world examples make this concrete. The premise behind Jaws compresses cleanly: a police chief must stop a killer shark from terrorizing his resort town before the summer tourist season is destroyed, or more lives, including his own, will be lost. Every component is there, and notice the construction: it doesn't open with backstory about the town or the chief's history. It opens with the collision between the goal and the threat, which is exactly where the tension lives.
Common mistakes that separate pros from amateurs
Too vague. Loglines that lean on abstract nouns like "journey," "discovery," or "finding oneself" without anchoring them to a concrete goal tend to disappear the moment someone hears them.
Too much plot. New writers often try to cram act two's complications, a subplot, and a supporting character's arc into a single pitch. A logline isn't a compressed outline. It's a hook. Everything that doesn't serve the hook gets cut, no matter how important it feels to the writer.
No stakes. "A man wants to win the race" is a goal. "A man must win the race or lose the farm his family has run for four generations" is a goal with something real behind it. That gap is the difference between a pitch that lands and one that doesn't.
Burying the hook. Loglines that spend their opening clause on setting or backstory ("In a world recovering from war, a soldier...") often lose the listener before the actual premise even arrives. Lead with the tension, not the throat-clearing.
Explaining instead of selling. A common amateur tell is a logline that reads like a book report, accurate, complete, and lifeless. A professional pitch is closer to a trailer voiceover than a Wikipedia summary. It's allowed to have a pulse.
What a great logline sets up
A logline built with this much intention doesn't just help sell a finished script, it becomes the compass for writing it. When a scene isn't sure what it's supposed to be doing, a strong logline is often the fastest way to check: does this scene serve the goal, deepen the obstacle, or raise the stakes? If it doesn't do any of those three things, that's usually a sign the scene needs work, not the logline.
It also carries forward directly into how a finished script gets represented later, in query letters, in marketplace listings, in the first thing a manager says out loud in a room the writer isn't in. A script listed on a platform like StoryMarket lives or dies on that same short, sharp hook doing its job for someone who hasn't read a single page yet. Getting it right early isn't just good writing discipline. It's building the exact pitch that's going to be doing the heaviest lifting for the rest of the project's life.