Story Mechanics – The Logline

More Than a Sales Tool

Writers who are new to the professional side of screenwriting tend to encounter the logline as a marketing requirement: the one or two sentence summary that goes at the top of a query letter, on a pitch document, in a festival submission form. In this context it feels like a necessary but slightly reductive exercise, the compression of months or years of creative work into a handful of words designed to catch the attention of someone who is reading too fast and caring too little.

This view of the logline is understandable, and it is not entirely wrong. The logline is indeed a professional tool, and learning to write one competently is part of what it means to operate in the industry. But treating it as nothing more than a marketing device misses the deeper value it offers, not just to the people you are pitching to, but to you, as the writer, at every stage of the process.

A logline that works is a proof of concept. It demonstrates that the story has a clear dramatic engine, a protagonist with a specific goal, a conflict with genuine stakes, and a shape that an audience can grasp and be drawn into. If you cannot produce a logline that does all of those things, it is very likely that the script itself is not yet doing all of those things either. The logline is a diagnostic as much as a description. It reveals whether the story is as clear in execution as it felt in conception.

This is why the logline is worth writing early, before the script is finished, before the outline is complete, even before the first draft has begun. Not because the early logline will be perfect, it almost certainly will not be, but because the attempt to write it will surface the questions the story has not yet answered. Where the logline resists compression, the story usually has a problem. Where it comes easily, the story has found its spine.

What a Logline Contains

There is no single agreed formula for the logline, and anyone who tells you there is should be treated with mild scepticism. Different writers, different teachers, and different parts of the industry use slightly different frameworks. But most effective loglines contain, in some form, the same core elements, and understanding those elements is more useful than memorising any particular template.

The first element is the protagonist. Not a name, in most cases, but a description that tells us who this person is in terms that are immediately relevant to the story. Not 'a man' but 'a disgraced detective.' Not 'a woman' but 'a grieving mother.' The descriptor should do two things at once: tell us something specific about the character and signal something about the kind of story we are in. 'A disgraced detective' carries a genre implication. 'A grieving mother' carries an emotional one. The descriptor should be the most dramatically useful piece of information about the protagonist that can be compressed into two or three words.

The second element is the goal: what the protagonist is actively pursuing in concrete, visible terms. Not a state they want to be in, but a thing they are trying to do. Not 'wants to find happiness' but 'tries to recover her stolen identity.' Not 'struggles with his past' but 'returns to his home town to confront the man who destroyed his family.' The goal should be specific enough that we can imagine what success or failure looks like. If we cannot picture a clear outcome, the goal is not yet concrete enough.

The third element is the obstacle or antagonist: the force, person, or circumstance standing between the protagonist and their goal. This is where the conflict lives, and conflict is what makes a logline feel like a story rather than a situation. 'A detective tries to solve a murder' is a situation. 'A detective tries to solve a murder while being framed for it herself' is a story, because the obstacle is built into the premise and the conflict is immediate.

The fourth element, present in the best loglines though not always explicitly stated, is the stake: what is lost if the protagonist fails. Stakes are what create urgency, and urgency is what makes an audience lean forward rather than sit back. The stake should feel genuinely significant, either in plot terms, emotionally, or both. A story in which failure is merely inconvenient is a story that is hard to care about.

Where the logline resists compression, the story usually has a problem. Where it comes easily, the story has found its spine.

The Irony at the Heart of It

The most memorable loglines do not simply describe a story. They contain an irony: a gap between what the situation appears to offer and what it actually delivers, or a contradiction between what the protagonist is and what the story is going to require of them, or a collision between two things that should not, by any ordinary logic, occupy the same premise.

Blake Snyder, in Save the Cat, identifies this quality as the single most important feature of a strong logline. He calls it the compelling irony, and argues that it is what makes someone hearing a pitch say 'I have never heard that before, and yet I completely understand it.' The irony is the hook. It is the thing that makes the premise feel both surprising and inevitable, both fresh and somehow familiar.

Consider the logline for Tootsie: a desperate actor, unable to find work as a man, disguises himself as a woman and becomes a television star, only to fall in love with his co-star, who believes he is a woman. The irony is multiple and compounding. The solution to his problem creates a new and more complicated one. The success he achieves is one he cannot own. The love he finds is one he cannot pursue without destroying everything he has built. The premise contains its own drama, and the logline communicates that immediately.

Not every logline needs to be built on irony as explicitly as that. But the best ones have some version of this quality: a tension built into the premise itself, a collision of elements that generates dramatic energy before a single scene has been written. If your logline describes a situation that could unfold in any number of directions without obvious friction, it may be worth asking whether the irony, the specific collision that makes this story this story, is present yet.

The Logline Is Not the Synopsis

A confusion that trips up many writers is the difference between a logline and a synopsis. They are not the same thing, they are not interchangeable, and conflating them produces documents that fail at both tasks.

A synopsis tells the story: what happens, in what order, with what outcome. It follows the plot from beginning to end, hitting the key turns and developments, and usually runs to at least a page, often several. It is a useful document for certain purposes: detailed development conversations, certain submission processes, coverage preparation. But it is the opposite of a logline in almost every way.

A logline does not tell the story. It communicates the premise: the dramatic situation that the story explores, the protagonist, the conflict, and the stakes, in a form that creates desire in the reader to know what happens. A good logline makes someone want to read the script. A synopsis tells them what is in it. The logline is an invitation. The synopsis is a map.

The distinction matters because the skills required to write each one are different, and the failure modes are different. A logline that tries to include too much plot becomes a condensed synopsis: dense, confusing, and dramatically inert. A synopsis that tries to generate the energy of a logline tends to sacrifice clarity for impact. Know which document you are writing and what job it is supposed to do, and resist the temptation to let them bleed into each other.

A good logline makes someone want to read the script. A synopsis tells them what is in it. The logline is an invitation. The synopsis is a map.

Writing the Logline for Yourself

The professional uses of the logline are well understood. Less discussed, but arguably more valuable, is the logline as a private working tool: the sentence or two you write for yourself, not for any submission or pitch, but as a compass to write toward.

When a script is in trouble, it is often because the writer has lost clarity about what the story is. The plot has accumulated detail and complication. Subplots have expanded. Characters have taken on life and started pulling the story in directions that feel alive in isolation but no longer connect to a clear centre. At this point, the most useful thing a writer can do is often the simplest: try to write the logline.

If the logline comes easily, the story still has its spine, even if the draft has drifted from it. The logline can then function as a correction device: a way of identifying which scenes and developments are serving the central premise and which have accumulated around it without serving it. Anything that cannot be traced back to the logline is a candidate for examination. Not necessarily for cutting, but for interrogation: why is this here, and is it earning its place?

If the logline does not come, if you find yourself unable to compress the story into a premise without losing something that feels essential, the problem is usually one of two things. Either the story has too many centres: multiple protagonists, multiple goals, multiple conflicts of equal weight, none of which resolves into a single clear dramatic engine. Or the story does not yet have sufficient conflict: the protagonist wants something, but the obstacle is not yet strong enough, specific enough, or inevitable enough to generate real dramatic tension. Both problems are solvable. The logline is what reveals them.

Loglines and Genre

As we explored in the essay on Genre, genre functions as a contract with the audience. The logline is often where that contract is first made explicit, and it is worth understanding how genre and logline interact.

A logline that does not signal its genre clearly risks creating a mismatch between what the reader expects and what the script delivers. This mismatch is not just a marketing problem. It is a clarity problem. If a reader cannot tell from the logline whether they are being invited into a thriller, a comedy, or a drama, the story's identity may not yet be fully resolved. Genre ambiguity in a logline often reflects genuine tonal uncertainty in the script.

The genre signal in a logline can be carried by the descriptor for the protagonist, by the nature of the obstacle, by the tone of the language, or by all three together. 'A burned-out homicide detective' signals crime. 'A mild-mannered accountant who discovers his wife is an assassin' signals comedy-thriller. 'A ten-year-old boy, separated from his family during wartime' signals drama. The genre does not need to be named. It needs to be felt. A reader should be able to identify roughly what kind of experience the film is going to offer from the logline alone.

Genre hybrids, as discussed in the Genre essay, require particular care in the logline. The challenge is signalling both genres clearly enough that the hybrid feels intentional rather than confused. The Silence of the Lambs logline, a young FBI trainee seeks the help of an imprisoned serial killer to catch another killer at large, carries the thriller clearly and allows the horror to be felt beneath it without announcing itself. Both genres are present. The thriller is primary. The logline reflects that hierarchy.

Common Logline Problems

Certain problems recur in loglines with enough regularity that they are worth naming directly.

The first is vagueness. Protagonists described only as 'a man' or 'a woman,' goals expressed as 'tries to find himself' or 'searches for the truth,' obstacles that amount to no more than 'faces challenges.' Vagueness in a logline almost always reflects vagueness in the story. The fix is specificity at every level: a specific kind of person, a specific and concrete goal, a specific and formidable obstacle.

The second is overloading. The logline that tries to include the subplot, the secondary characters, the thematic underpinning, and the emotional arc as well as the central premise. A logline is not a summary. It is a premise. One protagonist, one goal, one central conflict. Everything else belongs elsewhere.

The third is passivity. A protagonist who has things happen to them rather than making things happen. 'A woman discovers her husband has been leading a double life' is the beginning of a premise, not a logline, because it tells us only what happens to the character, not what she then does about it. The logline should show us a protagonist in active pursuit, not a character in receipt of events.

The fourth is the absence of stakes. A logline in which the worst that can happen is unclear, unspecified or insufficiently serious. If the reader cannot feel why this matters, if success and failure seem roughly equivalent, the logline will generate no urgency. Stakes do not need to be life and death. They need to be real: something of genuine value to the protagonist and, by extension, to the audience.

The Test of the Room

There is a simple and slightly uncomfortable test for a logline, and it involves saying it aloud to another person. Not reading it from a page. Saying it, in the room, to someone who has not heard it before, and watching their face.

If their eyes sharpen and they lean forward slightly, or if they immediately ask a question about what happens next, the logline is working. If their expression stays neutral, if they nod politely and wait for you to say something else, it is not. The logline lives or dies in the telling, and the telling requires that it be short enough to say in a single breath, clear enough to be understood immediately, and compelling enough to generate a genuine desire for more.

This test is worth running early and often. Not to get validation, but to get information. The reaction of a first-time listener to a logline is some of the purest creative feedback available, because it is uncontaminated by knowledge of the script, loyalty to the project, or understanding of what you intended. It is simply a response to what the premise communicates on its own terms. That response will tell you, quickly and honestly, whether the story has found its most essential shape.

Starting From Here

If you have a project in development, write the logline today, regardless of where the script is in the process. Do not wait until the draft is finished. Write it now, as a way of testing what you know about the story and revealing what you do not.

Write several versions. Try a version that foregrounds the protagonist. Try one that leads with the conflict. Try one that puts the stakes front and centre. Try one that leans into the irony of the premise. Lay them side by side and read them as a stranger would: someone who knows nothing about the project, who is giving you thirty seconds and no more. Which version makes them want to read the script? That is your logline.

And if none of them work, if the premise resists compression, if every version loses something essential or gains something confusing, do not despair. Sit with the resistance. Ask what it is telling you. The logline that will not come is not a failure of craft. It is the story asking to be understood more clearly. Answer that question, and the logline will follow.