How to Write a Logline That Gets Your Script Read

You have spent months, sometimes years on your screenplay. You know every character's history, every structural beat, every line of dialogue you rewrote a dozen times to get right. And then someone asks the question that stops most writers cold: "What's it about?"

The answer is supposed to fit in one sentence. Maybe two.

This sentence is called the logline, and it is, in a very real sense, the most consequential thing you will write about your script more consequential, in terms of whether your work gets read at all, than almost any individual scene inside it. A logline is what appears in a query letter, what a manager repeats from memory in a meeting, what a reader writes at the top of a coverage report before they have read a single page of your actual script. It is the door. If it doesn't open, nothing behind it matters.

The good news is that a strong logline is not a matter of inspiration. It is a matter of structure and structure can be learned.

What a Logline Actually Is?

A logline is a one-to-two sentence summary of a screenplay that conveys the protagonist, the central conflict, and the stakes. That is the whole definition, and every word in it matters.

What a logline is not is a synopsis. A synopsis tells the story beginning, middle, and end, including the resolution. A logline does the opposite: it withholds the resolution entirely and instead sells the premise the specific collision of character and situation that makes the story worth telling in the first place.

This distinction trips up more writers than almost anything else in the early stages of learning the craft. The instinct, when asked to summarize a script you have lived inside for months, is to summarize everything to compress the plot down to its smallest form while still trying to include all of it. The result is usually a sentence that is both too long and somehow still vague, because it is trying to do the job of a synopsis while pretending to be a logline.

A logline does less, on purpose. It is an invitation, not a report.

The Three Jobs Every Logline Must Do

Every effective logline performs three functions simultaneously. Miss any one of them, and the sentence will feel incomplete even if the writing itself is elegant.

First, it introduces a compelling protagonist. Not just a name, and not just "a man" or "a woman" a role, a trait, or a situation that tells us something specific about who this person is before the story even begins. "A washed-up boxer." "A single father." "A disgraced surgeon." Each of these phrases does more narrative work in three words than a name ever could, because a name means nothing to a reader who has never met your character. A role or a defining trait means everything.

Second, it establishes the central conflict. What does this person want, and critically what stands between them and getting it? Conflict is not simply "something bad happens." Conflict is a collision between a goal and an obstacle, and the logline needs to make both halves of that collision visible. A protagonist with no clear want and no clear obstacle is a character without a story.

Third, it raises the stakes. What happens if the protagonist fails? Why should anyone a reader, an audience, a producer with two hundred other scripts on their desk care about the outcome? Stakes do not have to be apocalyptic. They have to be specific and personal. The fate of the world is, paradoxically, often a weaker stake than the fate of one relationship, because audiences connect to people, not to abstractions.

A logline that nails all three protagonist, conflict, stakes in a single clean sentence is doing an enormous amount of work in a very small space. That is precisely why it is hard, and precisely why it is worth getting right.

Loglines That Work

Theory is useful, but loglines are best understood by taking them apart. Here are three films radically different in tone, scale, and genre examined through the same three-part lens.

Full Metal Jacket

A platoon of young Marine recruits is shaped by the brutal discipline of boot camp before being thrown into the chaos of the Vietnam War, where the dehumanization they were trained for becomes impossible to escape.

The protagonist here is not a single named hero but a collective "a platoon of young Marine recruits" and that choice is deliberate, because the film's subject is the process itself, the machine that transforms civilians into soldiers. The conflict is twofold: the external brutality of training and war, and the internal conflict of what that process does to a human being. The stakes are not framed as "will they survive the war" in a conventional action-film sense — they are framed as something more unsettling: what happens to the self under this kind of pressure, and whether anything recognizable survives it. The logline signals, correctly, that this is not a war film about winning or losing battles. It is a film about what war does before the fighting even starts.

Bicycle Thieves

In post-war Rome, a desperate man finally finds work that requires a bicycle — and when the bicycle is stolen on his first day, he and his young son search the city to find it before he loses the job that is his family's only hope.

This logline demonstrates something important: the stakes do not need to be large in scale to be enormous in weight. A stolen bicycle is, by any conventional measure, a small event. But the logline makes clear, in a single clause — "the job that is his family's only hope" that this small event is the entire world for this character. The protagonist is defined economically: "a desperate man," which tells us his emotional state and his circumstances at once. The conflict is immediate and concrete: an object has been taken, and it must be found. There is no genre machinery here, no twist, no spectacle — and the logline doesn't pretend otherwise. It sells exactly what the film is: an intimate, urgent, human-scaled story where the smallness of the object stolen is precisely what makes its loss so devastating.

Kill Bill

A former assassin, betrayed and left for dead on her wedding day, wakes from a coma years later and sets out to systematically hunt down and kill the team of killers and the man who led them who destroyed her life.

Here, every element is turned up to maximum, and the logline reflects that. The protagonist is defined by a dramatic reversal of fortune — "a former assassin, betrayed and left for dead" — which immediately tells us this is someone dangerous who has been wronged, a combination that promises both capability and motivation. The conflict is laid out as a literal checklist: a team of killers to be hunted, one by one, plus the man at the top. And the stakes, while framed in the language of revenge, are rooted in something the logline makes clear was deeply personal — "her wedding day," "destroyed her life." The logline doesn't undersell the film's stylized, larger-than-life tone, because doing so would misrepresent what audiences are being invited into. It matches the register of the story it is selling.

The pattern across all three: despite enormous differences in scale, tone, and genre, each logline names a protagonist through role or circumstance rather than just a name, states a conflict that is concrete and active, and personalizes the stakes in a way that makes the abstract feel immediate. None of them summarize the ending. All of them make you want to know more.

Common Mistakes That Weaken a Logline

Most weak loglines fail for a small number of recurring reasons. Recognizing these patterns in your own writing is often the fastest way to fix them.

Vague protagonists. "A man struggles to find his place in the world" tells us nothing. Who is this man? What is specific about his situation? A protagonist described only by gender and a generic emotional state could be the lead in literally any film ever made — which means, for the purposes of a logline, he is the lead in none of them.

No clear conflict. Sometimes a logline describes a situation without describing a collision. "A woman returns to her hometown after many years away" is a setup, not a conflict. What does she want when she gets there? What — or who — stands in her way?

Stakes that feel abstract. "The fate of humanity hangs in the balance" has been used so often, in service of so many different films, that it has lost the ability to make anyone feel anything. Compare this to Bicycle Thieves, where the stakes — one family's ability to survive — are small in scope but enormous in specificity. Specific stakes, even modest ones, outperform abstract stakes, even cosmic ones.

Too much plot. This is the most common mistake of all, and it comes from a generous instinct: the writer doesn't want to leave anything important out. But a logline that tries to summarize the second act, the twist, and the climax is a logline that has stopped being a logline. It has become a compressed synopsis, and compression without selection is just clutter. The job is not to include everything — it is to select the one collision that defines the whole story.

Genre confusion. A reader should be able to tell, from the logline alone, roughly what kind of experience they are being offered. A logline for a broad comedy that reads like a tense thriller — or vice versa — creates a mismatch between expectation and execution before the script has even been opened.

Part Five: A Simple Formula to Build Your Own

If you are staring at a blank page trying to write your logline from scratch, a simple fill-in-the-blank structure can help you generate a working first draft:

"When [inciting incident], a [protagonist defined by role or trait] must [goal/action], or [stakes/consequence]."

Let's walk through how this works with a hypothetical premise. Suppose your script is about a small-town librarian who discovers a decades-old letter hidden in a returned book, revealing a crime that was never solved.

Plugging into the formula: "When a librarian discovers a hidden letter revealing an unsolved crime from decades ago, she must decide whether to expose the truth, even if it means destroying the reputation of the town's most respected family."

Notice what this draft does and doesn't do. It names a role ("a librarian") rather than a name. It states an inciting incident clearly. It frames a choice expose or stay silent which is itself a form of conflict. And it personalizes the stakes by tying them to a specific consequence: the reputation of a specific family, not "the truth" in the abstract.

Is this the best possible version of this logline? Probably not — and that's the point. A formula gets you to a working draft, not a finished one. The real work happens in revision. Write five, ten, even fifteen versions. Read them aloud. Show them to people who have never heard your story and watch their faces do they lean in, or do their eyes glaze over? The version that survives this process will almost always be sharper, tighter, and more specific than your first attempt. The formula is a starting point. The instinct for what's essential and the willingness to cut everything that isn't — is what makes a logline actually work.

Getting Feedback

Here is the difficulty with writing your own logline: you know too much. You have lived with every subplot, every character's interior life, every careful detail you worked hard to include. From the inside, it can be almost impossible to see which of those details actually matter to someone encountering the story for the first time and which are, to an outside reader, simply noise.

This is why outside perspective has always been part of the screenwriting process. Workshops exist for this reason. Writing groups exist for this reason. The note "I don't think this is really what your script is about" delivered by someone who just read it cold is one of the most valuable notes a writer can receive, precisely because the writer could never have arrived at it alone.

This is also where a tool like Poetika can be useful. When you upload a script to Poetika, it analyzes the structure, characters, and premise as they actually appear on the page not as the writer intended them, but as a reader would encounter them and can generate a suggested logline based on that analysis. This isn't a replacement for your own judgment. It's a second opinion: a way to see your story summarized by something that has no investment in any particular subplot, no attachment to a scene you love but that doesn't serve the premise, and no memory of the version of the script that existed in your head before you started writing the one on the page.

Used this way, an outside-generated logline can function as a kind of mirror. If it captures something you didn't expect a throughline that's stronger than you realized that's useful information. And if it captures something that feels thin, or misses what you thought the story was about, that's useful too: it may be telling you that the premise needs to be sharpened on the page, not just in the logline.

The logline is usually one of the last things a writer writes and the first thing the world ever sees. Given that asymmetry, the disproportionate effort it demands is not a quirk of the industry. It's simply the cost of admission.