Game Story Loglines: One-Sentence Pitches That Sell

Before the trailer, before the Steam page, before the vertical slice — there is one sentence. The logline is the smallest possible version of your game's story, and writing it well forces every bigger decision into focus. This guide teaches the formula.

What a logline is (and isn't)

A logline is a single sentence — twenty-five to forty words — that describes your game's story: who the protagonist is, what they want, what stands in the way, and what makes it a game rather than a film. It is not a tagline ("In space, no one can hear you grind") and not a synopsis. Taglines sell mood; synopses explain plot. Loglines do something harder: they make a stranger understand the playable story in one breath.

You need a logline long before you need marketing copy. It is the sentence you say when someone asks "what's your game about?" — at meetups, in pitch emails, in funding applications. If you can't say it in one sentence, you don't yet know what your game is about.

The four-part formula

Strong game loglines contain four elements, usually in this order:

1. Protagonist with a trait — not just "a knight" but "a disgraced knight," not "a pilot" but "a retired smuggler." The trait is a promise of character arc.
2. Goal — what they want, stated actively. "Must escort," "races to build," "hunts."
3. Obstacle — what stands in the way, with a face or a force. Obstacles create the game's conflict and, by extension, its gameplay.
4. The game-ness — the playable twist. This is what film loglines don't need and game loglines can't skip: the mechanic, the loop, or the player agency embedded in the premise.

Worked example: "A disgraced knight must escort the last dragon egg across a war-torn kingdom where every faction hunts it — choosing which roads to risk and which allies to trust." Protagonist, goal, obstacle, and the player's decisions are all in the sentence.

Writing it: the compression draft

Nobody writes a logline in one pass. The reliable method:

1. Write the paragraph. Describe the story in five or six sentences without worrying about length.
2. Cut to three sentences. Keep protagonist, goal, obstacle. Lose subplots, lore and worldbuilding.
3. Cut to one. Merge ruthlessly. Every word must earn its place.
4. Add the game-ness. Read the sentence and ask: could this describe a film? If yes, weave in the player's role.
5. Read it aloud. If you stumble, the sentence is too complex. Simplify until it flows.

Common logline failures

• The lore dump: "In the shattered Seventh Dominion of Kael..." — worldbuilding before character. Start with a person, not a place.
• The passive protagonist: "A young mage discovers..." — discovering is not a goal. Give them something to do: "...must steal back," "...races to warn."
• The missing obstacle: a goal with no opposition is a to-do list, not a story. Name what fights back.
• The genre tag masquerading as story: "An epic sci-fi RPG..." — genre is not story. The logline after the genre tag still needs all four parts.

Testing your logline

A finished logline should pass three tests. First, the stranger test: say it to someone who knows nothing about your game — can they repeat the premise back? Second, the gameplay test: does it imply what the player does? Third, the excitement test: does it make you want to build it? A logline that bores its author will not excite a publisher. Once the story is locked, name the pieces players will actually see; mission names by genre shows how to title chapters and quests in your game's tone.

Frequently asked questions

How long should a logline be?

One sentence, roughly 25-40 words. Longer than that and it stops being sayable in conversation; shorter and it usually drops one of the four elements.

Should the logline mention the genre?

Only if the genre is doing work the sentence can't do otherwise. Usually the vocabulary (starships, spells, trenches) signals genre naturally. Don't waste words on labels.

Can a logline change during development?

It should. As the game finds its identity, the logline sharpens — and a logline that resists sharpening is telling you the design is still fuzzy. Revisit it at every milestone.

Logline vs. elevator pitch — what's the difference?

The logline is the story in one sentence. The elevator pitch is the game in thirty seconds: logline plus genre, platform, hook mechanic and audience. Write the logline first; it becomes the pitch's opening line.

What if my game is systems-driven with minimal story?

You still need the sentence — frame the fantasy instead of a plot: "A lone engineer must keep a generation ship alive as systems fail and the crew panics — every repair a choice about who survives." The game-ness carries it. For tabletop one-shots the premise does the same job; see one-shot adventure names for story-first campaign titles.

Still shaping the story behind the sentence? LoreLoom generates game story ideas and premises to riff on — find the spark, then compress it into the one sentence that sells it.