Learning how to write a logline is one of the highest value skills a storyteller can pick up, because a single strong sentence can open a door that a whole script cannot. A logline is the one or two sentence distillation of your story: who it is about, what they want, and what stands in their way. The ToolFiddle Logline Helper walks you through that sentence piece by piece, so you end up with a line that a busy reader understands instantly and wants to follow. Type in your protagonist, their goal, the conflict, and the stakes, and the tool helps you shape them into a clean, punchy logline you can put at the top of a query letter, a pitch deck, or a contest entry.
The reason this matters is simple. Agents, producers, managers, and contest readers see far more material than they can ever read in full. The logline is the filter. A great one earns you the next ten pages, and a muddy one gets a polite pass no matter how good the script behind it is. Getting this sentence right is not a nicety, it is often the difference between being read and being skipped.
What a logline is and who needs one
A logline is a compressed pitch. In roughly twenty five to fifty words it names the main character, the event that kicks off the story, the goal that character pursues, and the opposition that makes the goal hard to reach. Done well, it also carries a spark of irony or a hook that makes the idea feel fresh. It is not a summary of everything that happens. It is the story's central question in its smallest complete form.
Screenwriters need loglines for pitches, query emails, and coverage. A reader at a production company will often decide from the logline alone whether to request the script. Contest and fellowship applications almost always ask for one, and festival programmers scan them by the hundred.
Novelists and short story writers need them just as much. The query letter that agents read starts with a logline in all but name, a hook sentence that states the premise and the stakes. If that line lands, the agent keeps reading the pages you attached. If it does not, the pages may never get opened.
Television writers, playwrights, and even game and comic creators lean on the same tool. Anyone who has to make another person care about a story before they experience it benefits from knowing how to write a logline that does the persuading in one breath.
The building blocks of a strong logline
Almost every effective logline is built from the same handful of parts. Get these clear in your head and the sentence starts to assemble itself.
The protagonist comes first, described by role and a single defining trait rather than a name. A disgraced surgeon, a stubborn farm girl, an aging boxer. That one adjective does a lot of quiet work, hinting at the flaw or quality the story will test.
The inciting incident is the event that tips the ordinary world into the story. It is the phone call, the murder, the eviction notice, the stranger at the door. This is the moment the audience meets the plot, and in a logline it usually sits near the front, often signaled by a word like when.
The goal is what the protagonist is trying to achieve once the story starts. It should be concrete and active. Win the case, escape the island, save the farm, get home. A vague goal such as find happiness gives the reader nothing to picture.
The conflict is the force pushing back, which can be a villain, a rival, a system, a storm, a ticking clock, or the character's own weakness. Without opposition there is no drama, so the logline has to make the resistance visible.
The stakes answer the question so what. What does the protagonist lose if they fail, and why should we care. Stakes can be life and death, but they can also be a marriage, a home, a reputation, or a last chance. The bigger and clearer the stakes feel, the more the reader leans in.
Irony sits on top of these as the finishing touch. It is the built in contradiction that makes a premise feel surprising: the bodyguard afraid of violence, the wedding planner who cannot fall in love. Not every logline needs a heavy dose of irony, but a hint of the unexpected is what separates a merely clear line from a memorable one.
You do not have to invent the shape of a logline from scratch. A few reliable templates carry most stories, and the helper is built around them.
The classic when template runs like this: when the inciting incident happens, a described protagonist must pursue a goal, or else the stakes. For example, when a tornado traps a small town, a widowed storm chaser must reach the shelter across the valley before the next cell hits, or lose the daughter she just found again.
A leaner version drops the setup clause: a described protagonist must reach a goal before a consequence. A washed up magician must pull off one real heist to pay the ransom on his kidnapped brother. Short, active, and clear.
A goal versus obstacle template foregrounds the conflict: a described protagonist wants a goal, but an antagonist or obstacle stands in the way. This shape suits stories where the opposition is the most interesting element, like a rookie lawyer who takes on the company that poisoned her hometown, knowing they own every judge in the county.
For an ongoing series, the template shifts from a single plot to a repeatable engine: a described protagonist, in a distinctive world, must handle a recurring kind of problem week after week. That points at the machine that generates episodes rather than one finish line.
The helper lets you slot your own pieces into these frames, then trim. Templates are a starting scaffold, not a cage. Once the parts are in place, you rearrange and cut until the sentence reads like something a person would actually say.
How the ToolFiddle logline helper works
The helper turns the abstract advice above into a fill in the blanks process. Instead of staring at a blank page, you work field by field. There is a slot for your protagonist, a slot for the inciting incident, a slot for the goal, a slot for the conflict, and a slot for the stakes, plus space to try an ironic angle.
As you fill each field, the tool assembles a draft logline from your pieces using the templates, so you immediately see how the parts read together. That instant assembly is the point. Seeing your rough inputs become a sentence shows you at once which piece is weak, which is vague, and which is doing the heavy lifting.
From there you refine. Swap a flat goal for a sharper one, tighten the protagonist description to a single vivid trait, cut a word that repeats. Because the helper rebuilds the line as you edit, you can run through many versions quickly, which is exactly how real loglines get written. The whole process runs in your browser, so your ideas never leave your device.
A step by step walk through the tool
Here is the full path from a rough idea to a finished logline.
- Name your protagonist by role and trait. Skip the character's name and reach for the description that hints at the story, like a burned out war photographer or a naive small town heir.
- Enter the inciting incident. Write the single event that starts everything. Keep it to the trigger itself, not the backstory that led to it.
- State the goal. Make it active and specific, something you could film. This is what the protagonist is chasing for most of the story.
- Add the conflict and the stakes. Name the force pushing back and spell out what is lost on failure. These two together supply the tension that makes a reader care.
- Try an ironic angle. Ask what is unexpected about this setup and see if you can fold that contradiction into the line. This is optional but often the moment a logline goes from fine to sharp.
- Read the assembled draft, then cut. Trim it toward thirty words, read it aloud, and hand it to someone who knows nothing about your story. If they understand the setup and want to know what happens, you are close. If they look confused, the tool makes it easy to swap a piece and try again.
Worked examples: turning an idea into a logline
Watching a vague idea sharpen into a logline is the fastest way to learn the craft, so here are a few worked from scratch.
Start with a fuzzy idea: a story about a chef who has a hard time. That is not a logline, it names no goal, conflict, or stakes. Add the pieces. Protagonist, a perfectionist chef losing her sense of taste. Inciting incident, a famous critic books a table for the night that decides the restaurant's future. Goal, cook the meal of her life. Conflict, she can no longer taste her own food. Stakes, the restaurant and her name. Assembled: when a ruthless critic books the table that will make or break her restaurant, a perfectionist chef who has secretly lost her sense of taste must cook the perfect menu blind, or lose everything she built. That is a logline with a hook.
Take another: something about two rival magicians. Sharpen it. Protagonist, an obsessive stage magician. Inciting incident, his rival debuts an impossible trick. Goal, uncover the secret. Conflict, the rival will destroy anyone who gets close. Stakes, his sanity and his life. Assembled: an obsessive magician becomes convinced his rival's impossible trick hides a deadly secret, and his hunt to expose it costs him everything he loves.
One more, a family drama, which writers often struggle to logline because the stakes feel soft. Protagonist, three estranged adult siblings. Inciting incident, their father dies and leaves a strange condition in the will. Goal, spend one month together in the family house to inherit. Conflict, old betrayals none of them have forgiven. Stakes, the house and any chance of a family. Assembled: three estranged siblings must live together for one month in their late father's house to inherit it, forcing them to face the betrayals that tore the family apart. The stakes are emotional, but they are concrete and clear.
Strong logline examples to learn from
It helps to study loglines built in the shape of films you already know, described here in plain paraphrase rather than any official wording.
In the spirit of a famous survival thriller: after a shark starts killing swimmers at a summer resort, a water fearing police chief must hunt the animal at sea, working against a mayor who refuses to close the profitable beaches. Notice the ironic hook, a lawman afraid of water, and the clear opposition on two fronts, the shark and the mayor.
In the spirit of a heist classic: a thief who steals secrets by invading dreams is offered a clean record if he can plant an idea in a rival's mind instead of stealing one, a job no one believes is possible. The premise itself carries the intrigue, and the stakes, his freedom, are baked in.
In the spirit of an underdog sports story: a small time boxer gets a million to one shot at the heavyweight champion and, knowing he cannot win, sets out simply to last all fifteen rounds and prove he is not a nobody. The goal is redefined in a way that makes the stakes personal rather than about the belt.
Across all three you can feel the pattern. A specific character, a clear goal, a real obstacle, stakes that land, and a twist of irony. That is the target every time you learn how to write a logline for your own project.
Real-world ways writers use a logline
A logline is not just a hoop to jump through, it earns its keep in daily writing life.
Query letters live or die on it. The first line of an email to an agent or manager is your logline, and it decides whether they read the rest. A crisp one signals a writer who understands story, before anyone has seen a single page.
Pitch meetings open with it. When you have thirty seconds across a desk, you lead with the logline and expand only if the room leans in. Having it memorized keeps you calm and keeps the pitch on track.
Contests and fellowships require it on the entry form, and readers use it to set expectations before they open the script. A logline that promises a fresh, clear story buys goodwill on page one.
Writing the script itself benefits too. A sharp logline is a compass. Whenever a scene drifts, you can ask whether it serves the goal and conflict named in the line. If it does not, you have found a cut. Many writers pin the logline above the desk for exactly this reason.
Marketing and packaging further down the line, from a book's back cover blurb to a streaming description, often grow straight out of the original logline. Get it right early and it keeps paying off.
Tips and common mistakes to avoid
A few habits will lift your loglines fast, and a few common traps will sink them.
- Cut the character names. Readers who do not know your story gain nothing from a name and lose the words you need for the hook. Use a role and a trait instead.
- Make the goal concrete. Find yourself, learn to love, and go on a journey are not goals a camera can see. Win the trial, cross the desert, expose the fraud. Give the reader something to picture.
- Do not forget the stakes. A goal with no consequence for failure feels weightless. Always answer the so what, whether the price is a life, a home, a marriage, or a last chance.
- Resist stuffing in subplots. A logline covers the main engine of the story, not every thread. If two ideas are wrestling for the sentence, one of them belongs in the synopsis.
- Avoid pure vagueness. If your line could describe a hundred other stories, it is not specific enough. Concrete nouns and a real obstacle are what make it yours.
- Read it aloud, every time. Loglines are heard as often as read, in rooms and on calls. If it ties your tongue in knots, simplify until it flows. Paste the line into our text to speech tool to hear it in another voice, and reshape it until the new version lands at once.
Logline versus synopsis versus tagline
These three get mixed up constantly, and knowing the difference sharpens each one.
The logline is one or two sentences that state the premise and raise the central question without answering it. Its job is to make an industry reader want more. It always contains a character, a goal, and a conflict.
The synopsis is longer, from a paragraph to a full page, and it does walk through the plot including the ending. Agents and producers read it after the logline has hooked them, to see whether the story holds up across its full shape. Where the logline sells the promise, the synopsis delivers the plot.
The tagline is marketing, not story. It is the short, evocative line on a poster, built for mood and memory rather than plot detail. A tagline might be three words and mention no character or goal at all. It aims at an audience buying a ticket, while a logline aims at a professional deciding whether to read.
A helpful way to keep them straight: the tagline sells the feeling, the logline sells the story, and the synopsis proves the story works. Most projects eventually need all three, and they are easiest to write in that order once the logline is solid.
Your story ideas stay on your device
Everything you type into the Logline Helper stays with you. Your premise, your character notes, and every rough draft you try are handled by code running inside your own browser. None of it is uploaded to a server, saved to an account, or logged anywhere on our side. An unsold idea is valuable and personal, and yours is simply not visible to us.
This local approach is a deliberate choice. Plenty of writing tools quietly send whatever you type to a remote server, sometimes to train a model or feed analytics, just to help you word a sentence. The helper does its work on your machine, so there is nothing to leak and nothing to collect. If you switched off your connection right after the page loaded, the tool would keep helping you exactly the same, which is the clearest proof your ideas have nowhere else to go.
Genuinely free, with no sign-up
The Logline Helper is free in the plain meaning of the word. There is no account to create, no email to hand over, and no payment at any step. You will not run into a wall that asks you to register before it shows your finished line, and there is no locked premium tier holding back the parts that matter. Every feature is here for everyone from the first click.
We say this plainly because gating simple tools has become common. Some sites collect your email or push a subscription in exchange for help you could get from a notebook and a bit of guidance. We think shaping a sentence should just be available. There are no daily limits either, so draft one logline or a hundred across a rewrite, and the tool behaves the same every time.
Instant, unlimited, and light
Because the helper runs on your device, your draft logline appears the moment you fill in the fields. There is no spinner while a request travels to a server and back, no queue at busy times, and no drag from the heavy advertising scripts that clog so many writing sites. The page is deliberately light, so it loads quickly even on a modest phone and a slow connection.
That speed matters more than it sounds. You usually want to play with a logline in the middle of thinking, when a quick response keeps you in the flow and a slow, cluttered page would break it. The helper gives you a fresh version instantly, then gets out of the way so you can keep writing. Run as many variations as you like, as often as you like, with nothing throttling you.
Works on every device, even offline
The Logline Helper behaves the same on a phone on the bus, a tablet on the sofa, or a laptop at your desk. The layout adjusts to the screen so the fields and the finished line stay large and readable. Once the page has loaded, shaping loglines no longer needs the internet, so a plane, a train tunnel, or a dead zone will not stop you from working on your pitch. Nothing depends on a particular brand of browser, as long as it is reasonably modern, and there is nothing to install.
A logline is the first rung on the ladder of shaping a story, and ToolFiddle has light, private tools for the rungs above it. Once your premise is clear, the Beat Sheet Helper maps the major story beats so you can plan the whole arc that your logline promises. When your script takes shape, the Script Runtime Estimator turns your page count into an estimated runtime for a feature, pilot, or short. To keep a query letter or synopsis inside a length limit, the Word Counter counts words and characters as you write, and the Case Converter fixes a title page or slug lines in a click. Each keeps your work on your device, just like this one.
A quick recap
Knowing how to write a logline means knowing how to compress a story to its core: a described protagonist, an inciting incident, a concrete goal, a real conflict, clear stakes, and a touch of irony, all inside one or two sentences of about thirty words. Skip the character names, make the goal something a camera could film, always name the stakes, and cut anything that could describe another story. The ToolFiddle Logline Helper turns that into a fill in the blanks process, assembling a draft from your pieces and letting you rewrite quickly until one lands. It keeps every idea on your device, stays completely free with no sign-up, and works on any device even after you go offline.