Screenwriting and television

How to write a logline that actually works

August 16, 2026 · The StoryProp team

A logline that works carries five moving parts in a single sentence: a protagonist, a goal, an opposition, stakes, and the irony that crosses person and situation. Every screenwriter can recite the easier definition — one sentence that says what your story is about — and fewer can say what it is for. The common answer — a sales tool you polish once the script is finished — is true and late: by then the sentence can only describe what you already built. A logline is the smallest working model of a story. Built early, it tells you whether the engine turns over before you spend a season of evenings finding out the hard way.

Learning how to write a logline is mostly learning to answer four questions so plainly that evasion becomes impossible. Who wants something? What stands in the way? What happens if they fail? And why does this particular person make the situation worse? Answer all four in one sentence and you have a story. Dodge any of them and no volume of pages will smuggle a story in later. None of this requires the page itself to be settled first — our guide to writing a screenplay for beginners covers sluglines, dialogue blocks and professional layout, and the logline comes before grammar.

The five moving parts of a one-sentence engine

Start with the protagonist, who is not a name; a name means nothing to a stranger. A protagonist is a characterization crossed with a role, chosen so the pairing predicts friction: a claustrophobic cave rescuer, a divorce lawyer who elopes, a food critic who loses her sense of taste. One adjective, one job, maximum torque between them.

The goal must be concrete enough to film. “Finding herself” is not a goal; nobody can point a camera at it. “Getting her mother's house emptied and sold before the estate's debts swallow it” is a goal — you know what success looks like in the final scene, and so does everyone you tell. Opposition obeys the same rule: a person, a force, or a deadline that cannot be dissolved by one sensible conversation.

Stakes answer the question “or else what?” If the honest answer is “or else things stay roughly as they are,” the idea is not ready. Stakes need not be global — a marriage, a child's trust, a family house are plenty — but they must be legible in the sentence itself, not implied by mood.

Irony is the crossing of person and situation, and it is the part most checklists omit. Blake Snyder put it first in Save the Cat! (2005), which lists four things a logline needs: irony, a compelling mental picture, a sense of the audience and the cost of the film, and a killer title. Only the first is structural; the other three describe how the sentence lands once the engine is built. A wedding planner plans a wedding: that is a situation. A wedding planner who doesn't believe in marriage must produce her divorced parents' remarriage to each other: that is an engine. Irony answers the question every reader silently asks — why this protagonist, out of everyone alive? When the answer is “because the premise hurts this person specifically,” the logline has found its story.

Screenplay logline examples, starting with films you have seen

The clearest screenplay logline examples are films whose engines you can already hear running. Jaws: a police chief with a terror of open water has to close a resort island's beaches at the height of the summer season, against a town council whose year depends on that money, before the shark kills again. Alien — pitched, famously, as Jaws in space: the crew of a commercial towing ship answer a distress signal on contract time and bring aboard an organism that hunts them through the corridors of their own workplace, with no weapons and no authority to help them. Die Hard: an off-duty New York cop flies out to patch things up with the wife whose career took her to Los Angeles, and has to retake her office tower from armed thieves alone, barefoot, with nobody outside willing to believe him. Get Out: a Black photographer goes away for the weekend to meet his white girlfriend's parents and discovers the family's hospitality is the trap. The Social Network: a Harvard undergraduate who cannot hold on to a friend builds the machine that will define friendship for a generation, and is sued by the only friend he had. Whiplash: a first-year drummer at the country's best jazz conservatory wants greatness badly enough to keep sitting down at the kit for a teacher whose method is abuse. Six sentences, no backstory, no second storyline, no theme — and in every one, the person chosen makes the situation cost more than it would cost anyone else.

Definitions teach less than repairs, so here is a logline rebuilt from scratch. Start with the sentence most first attempts resemble: “A woman returns to her childhood home and confronts her past.” Every word is defensible and the whole is inert. There is no goal — “confronts” has no finish line. No opposition; the past doesn't fight back on camera. No stakes, no irony, and a protagonist who could be nearly anyone.

First repair: make the person particular and give the want a clock. “An estate appraiser returns to empty her late mother's house and must sell it before the estate's debts swallow it.” Better — a job, a task, a deadline. But it is still frictionless. Any diligent person could do this; nothing about her makes it cost more.

Second repair: cross the person with the situation until it hurts. This is roughly where “The Quiet House,” the demo manuscript that recurs on this site, sits: “An appraiser who prices other families' heirlooms for a living must empty the one house she can't be objective about — her mother's — while her estranged brother Daniel contests every object, and a chipped cup on the drainboard suggests their mother's last months weren't what either of them believed.” A professional assigner of value, a house that resists valuation, an opponent with equal claim and a different memory. The irony is doing the pulling.

The shape holds across genres. Thriller: “A night-shift air-traffic controller who trusts instruments over instinct must talk down a failing plane flown by the husband she left — with the man she left him for on the passenger list.” Comedy: the wedding planner above already qualifies. Both were built in a few minutes from the same five parts, and both would start generating scenes in a stranger's head. That last property is the real test: not polish, but whether the sentence makes other people invent your movie.

The cheapest test a story idea will ever face

Discovering a broken premise at logline stage costs an evening. The same discovery at page sixty costs a month of work and a measure of heart, which is the strongest argument for writing the logline before the pages rather than after: it is the only stage at which a fatal flaw is cheap. The industry does not price when a flaw is found, but it does price how deep the repair has to go — and a broken premise always needs the deep one. Under the Writers Guild of America's published Schedule of Minimums — the rates in force through May 2026, before the increase of one and a half percent that took effect that month — a polish of a high-budget theatrical screenplay, which the agreement defines as changes to dialogue, narration or action only, carries a minimum of $22,736. A rewrite, defined as significant changes to plot, story line or character interrelationship, carries $45,470: precisely the work a broken logline creates, at twice the price. The 2026 agreement added a third tier at $57,500 for a page-one rewrite — replacing all or substantially all of an existing script — payable only when the contract says so in those words.

Those are floors for guild-covered work at signatory companies, and nobody writing alone gets paid on that schedule. What it settles is narrower and still worth having: the people who pay for screenwriting price a change to the engine at twice a change to the surface. So use the logline as a proving ground. Take the idea you're circling and write six loglines in an hour — same premise, different protagonist each time; same protagonist, different opposition. The versions that compress cleanly are showing you where the story lives. The versions that refuse to compress are telling you something more useful: a decision hasn't been made yet. Vagueness in a logline is rarely a wording problem. It is an unmade choice wearing a disguise.

This is where a drafting partner earns its keep earliest. An AI screenwriting tool that knows your project can spin out variants faster than you can type them — six oppositions for the same appraiser, six ironies for the same house — and StoryProp keeps every one: each pass saved and comparable, alternates spun off by duplicating the document or the whole work, nothing overwritten when you change your mind. That leaves you the part that was always yours, which is noticing which version quickens your pulse.

Where loglines go wrong

The most common failure is theme instead of story. “A meditation on grief, memory, and the objects we leave behind” describes the residue a story leaves, not the machine that produces it. Theme is what remains after the engine has run; a logline needs the engine itself — who, wants what, against whom, or else what. Write the machine and the meditation will take care of itself.

The second failure is placeholder vagueness: “must confront,” “a dark secret,” “a journey of self-discovery,” “everything changes.” Each phrase marks a spot where a decision should be and isn't. “A dark secret” costs nothing to write because it commits to nothing; replace it with the actual secret and the logline either comes alive or visibly dies. Both outcomes are progress. The third failure is the plot dump — a sentence groaning under subplots, backstory, and a second act's worth of reversals. A logline is the engine, not the itinerary. If it needs a semicolon and three dependent clauses to survive, it is carrying cargo the draft can keep and the sentence cannot.

A quick field test covers all three failures at once: say your logline to someone who owes you nothing and watch what happens. If they ask a story question — “does the brother know about the cup?” — the engine is turning. If they nod politely and say it sounds interesting, you have handed them theme, fog, or freight.

A compass for drafting, not a plaque for the wall

The logline's second life begins once you start pages, and it is the more valuable one. Every scene you draft should press on the want or the opposition — advance one, harden the other, or raise what failure costs. When a scene bears no relation to the logline, one of two things is true: the scene is a candidate for cutting, or the story has genuinely moved and the logline is out of date. Both are worth knowing the day it happens rather than in a rewrite months later.

Loglines are allowed to change; what matters is that they change on purpose. Treating the logline as a recorded decision — written down, visible, revised deliberately — turns drift into steering. It is exactly the kind of decision StoryProp is built to hold: promote the logline into your project's records and the agent reads it before drafting anything, so the scenes it writes answer to the engine you actually chose rather than one it half-remembers.

The same sentence does sales work eventually, in a market that reads fast: the spec-deal tallies compiled by Scott Myers and relayed by No Film School count 28 publicly reported spec deals in 2025 and 24 in 2024, against the 173 The Story Farm counts for 1995. Build the sentence at the start and it arrives at that meeting already proven on your own pages. When the day comes to pitch, the logline is the first thing out of your mouth, and one built as a working compass beats one built as a costume, because you will be describing a machine you have actually run. One sentence, honestly built: who wants what, what stands in the way, what failure costs, and why it had to be this person. Everything else in the project is downstream of getting that sentence to turn over.

Write the sentence first, then hold the pages to it. In StoryProp, the logline you promote into your project's records is the one the agent reads before it writes a scene — so the draft answers to the engine you chose, not one it half-remembers.

← All posts