Skip to content
The Dialogue Lab

HomeFormat

Stored lines, not a scene dump

How to Write Dialogue for Video Games and Branching Narrative

By Jonah Ellery · Updated 21 October 2026 · Reviewed by Amira Solt, manuscript editor · 13 min

On this page
  1. A line is a record
  2. Bark, cinematic, and player choice
  3. Length, localization, and the recording bill
  4. Interruption is part of the format
  5. What you still owe the scene

Rule

Store a record, not a paragraph.

A line needs a speaker id, a line id, and the string. A scene in a document is a draft. The game can only interrupt, translate, and pay for a record it can find.

Rule

The label is not the line.

Menu text and spoken text are two strings. They may differ in length. They may not differ in the move they promise. A lying label teaches the player not to choose.

Rule

Front-load the point.

Players skip, get hit, and walk out of range. Put the fact in the first words. A clever clause at the end is the clause that dies.

Rule

Count the recordings.

A branch is not one scene. Every unique leaf an actor must say is a cost, and so is every string a translator must fit. Write the ones you mean.

Game dialogue is stored, not just typed. A line needs a speaker id, a line id, and a mode, because a bark, a cinematic, and a player choice are not the same object and they do not survive the same interruption. Localization will lengthen the string. Voice-over will bill you for every leaf of the branch. This is the format that makes those costs visible before someone records the wrong paragraph and calls it interactive.

A line is a record

A game line is a record, not a paragraph you hope someone will break up later. The record needs a stable speaker id, a line id, and the string the player might hear or read. The speaker id is a key, not a display name. sera is the key. Sera Voss can change if the character is renamed in a later pass, and the key should not change with her. The line id is how audio, localization, and the quest graph find the sentence again. If the only name the line has is its position in a scene you wrote in a document, the line will be duplicated, lost, or translated twice. Write the draft however you need to hear it. Before it is real, store it as rows. A screenplay of the cinematic is a useful rehearsal. It is not the dialogue file. The game cannot interrupt a block of prose. It can interrupt a line with an id, and interruption is not a special case. It is the usual case.

Three modes cover most of what you will be asked to format, and they should not share one blob of text. A bark is fired by a system: combat, idle, a door, a repeated failure. A cinematic is a scene where the player is closer to an audience, the camera held, choices paused or absent. A player choice is a menu, sometimes with a spoken line that is not the same string as the menu label. Tag the mode on the record. Writers who keep one long scene and figure out the barks later end up recording cinematic speeches for moments the player will hear while sprinting, and writing menu labels that were never meant to be said aloud. The mode is a format decision because it changes length, interruption, and whether a branch exists. If you do not know the mode, you do not know how long the line is allowed to be, and you will write the wrong object with great confidence and a nice rhythm.

  • speaker id: a stable key, not the display name and not a sentence.
  • line id: unique enough that audio and translation can find it after you rewrite the words.
  • mode: bark, cinematic, or player choice. Do not make one blob serve all three.
  • text: the string that can ship. Notes to yourself do not go in the string.
  • interrupt flag: flavor or critical. If everything is critical, nothing is.

Bark, cinematic, and player choice

A bark has to survive being heard once and being heard fifty times. It cannot say as I told you, because it may be the first time, and it cannot depend on a previous bark having played, because systems do not promise order. Keep it inside a breath. The player is doing something else, and your line is a guest in that action. Format the bark as speaker, trigger, and text, and if the system needs a priority so a damage line can beat an idle mutter, put the priority on the record instead of in a paragraph of hopes. Do not write a bark that only makes sense if the whole sentence finishes. The player will get hit, open a menu, or leave the trigger. Front-load the noun. The kettle is cold beats a windup about last night that finally mentions the kettle. The second version dies on its adverb. The first version can be cut off and still have done the job you stored it to do.

Barks that can fire alone
mode: bark
trigger: player_enters_kitchen
interrupt: flavor

id: sera_kettle_01
speaker: sera
The kettle’s cold.

id: sera_kettle_02
speaker: sera
You left the light off again.

id: idris_drive_01
speaker: idris
I heard the car.

A cinematic can hold an exchange, but it is still stored as line records with ids, in order, with the speaker on each row. You can draft it in screenplay form so the scene has rhythm, then break it. Do not leave it as a screenplay and call the breakdown someone else’s formatting job. The breakdown is where you discover you wrote a speech no skip button can honor. Cinematics sometimes suppress interruption. If yours can be skipped, the skip is part of the writing. Any fact the quest needs must be delivered in a line that is flagged to survive the skip, or it must be written into the world another way. A beautiful last sentence that contains the only mention of the car in the drive is a bug with good diction. Put the car where a skip cannot eat it, and let the beautiful sentence be the one the player is allowed to miss. Beauty that carries a plot flag is being held hostage. Free it, or move the flag.

A cinematic, already broken into rows
mode: cinematic
skip: allowed

id: kit_01
speaker: idris
interrupt: flavor
You said you were home.

id: kit_02
speaker: sera
interrupt: flavor
I said the kettle was on.

id: kit_03
speaker: idris
interrupt: critical
The car is in the drive.
1

“The car is in the drive.”

The fact the quest cannot lose is its own short record, marked critical, and it is the whole line. The argument around it can be skipped. If the car only appeared in a trailing clause after a speech about the marriage, the skip button would delete the plot.

Player choice is two strings that must promise the same move. The menu label is what the player selects. The spoken line is what the character says if the scene speaks it. They are not required to be identical. The label is shorter, blunter, and has to fit a column that will get longer in translation. The spoken line can carry voice. They are required not to contradict. If the label says agree and the spoken line picks a fight, you have lied, and the player will stop trusting the menu, which is the only agency you gave them. Format both, even when they match, so a later edit to the performance does not silently change the contract. Include silence as a real choice when silence is one of the moves: its own id, its own result, not an empty box that falls through into the next line and treats muteness as consent. A choice the player cannot see is not a choice. A choice that does not change the next record is decoration, and decoration gets expensive the moment someone has to record it.

A choice with a spoken line that keeps the promise
id: kitchen_return
mode: player_choice
speaker: sera

SERA
The kettle is cold. I was home. I did not want the porch light on.

CHOICE
> Where were you, then?
  spoken: Then where were you? The light was off.
> Leave it.
  spoken: Forget the light.
> Say nothing.
  spoken: [silence]
  result: idris waits. Silence is not agreement.

Weaker

CHOICE
> Agree to stay.
  spoken: Then where were you, if you are so sure I left?
> Be honest.
  spoken: Fine. I’ll make tea and we can pretend the drive is empty.

Better

CHOICE
> Ask where he was.
  spoken: Then where were you? The light was off.
> Leave it.
  spoken: Forget the light.
> Say nothing.
  spoken: [silence]

The weaker menu lies. Agree to stay produces an interrogation, and Be honest produces tea and a dodge. The player selected a move and got a different one, which is how choice dies. The repair makes the label and the spoken line the same tactic, and it stores silence as a result instead of an empty hole. Shorter labels will also survive translation. Clever labels that wrap are already a format bug before anyone records them.

Length, localization, and the recording bill

Localization will make many of your lines longer. German, among other languages, often runs a fifth to two-fifths longer than English, and a menu that was snug in your draft will wrap, clip, or push a button off the screen. Write the English as if the string has to survive that growth. Idioms that need a paragraph of explanation in another language are a format bug, not a flourish you are owed. Leave room for names. Sera is short. A localized name, a title, and a grammar marker are not. Subtitles have a line length too, often two lines for a bark before the text covers the face the cinematic spent money to show. Do not plan to let localization fix the length. Translators can cut a joke. They cannot invent space in a layout you already shipped tight. The constraint is a character budget you respect in the first language, not an apology you attach in the second and call collaboration.

Write whole lines, not fragments glued together in code. A sentence built by stapling you have to a number and then to the word keys is a localization disaster, because other languages do not keep that word order, and they may need a different word depending on the number. Give the translator a full sentence with a clear place for the number, and a note if the grammar changes at one. This is format, not a programming lesson. The record should contain the speakable sentence. If the pipeline requires concatenation, the failure will show up as a subtitle that is almost English with a noun shoved in the middle, and players can hear it even when they cannot name it. Gendered agreement, articles, and plural rules are not edge cases. They are most languages. A line that only works in English word order is a line you have not finished storing. Finish it before you congratulate yourself on the branch.

Every line an actor has to say is a cost: session time, direction, and a pickup later when the quest changes and the old recording is now a lie. Count the leaves, not the summary. A conversation with three choices that each open three unique replies is not a short branch. It is the opening line, plus three, plus nine, if you fully unique them, and that is before barks and before the alternate you will write when a playtester misunderstands the middle option. Reuse a bark when the trigger is the same and the character would actually repeat themselves. Do not reuse a line that contains a proper noun the plot has since retired. Subtitles cost localization even when nobody records them. Silence, a held face, a button that does the action without a quip, is a valid design and it is free. The format question before you add a variant is simple. Will a human have to perform this, will another human have to translate it, and did the last version already do the job?

Interruption is part of the format

Interruption is not a rude player. It is the medium. Damage, menus, sprinting out of range, a higher-priority bark, a skip: the line will be cut. Format for that by putting the point in the first words and by marking each record as flavor or critical. Flavor may die mid-sentence. Critical must complete, or the fact it carries must live somewhere that is not the tail of a speech. If you mark everything critical, you have marked nothing, and the audio team will interrupt your critical lore the first time it talks over a crisis the player actually feels. Be severe. Most barks are flavor. Most jokes are flavor. The warning that the floor is lethal, the line that locks a companion out, the car in the drive if the quest checks for it: those are critical, and they should be short enough to finish. A critical line that runs thirty words will be skipped by design and by impatience. Write it so the skip still leaves the player with the fact, or stop calling it critical and find another way to stage the fact.

Players will not read a speech just because you formatted it cleanly. A cinematic that runs past a few exchanges without a choice, a bark that explains a faction’s history, a menu of three paragraphs: these fail even when every id is perfect. Format makes the failure measurable. If the menu label wraps to three lines before translation, it was already too long. If the cinematic’s record count passes what your own attention survives when you read the rows aloud, it will not survive a player who slept badly. Read the rows, not the prose draft. The rows are the scene. Anywhere you feel the need to add a note that the player will understand from context, the line is asking context to do a job you did not write. Either put the noun in the line or put it in the world. Then delete the note. Notes are not subtitles, and they do not ship, no matter how reassuring they were to you at two in the morning.

Weaker

id: sera_warn_01
speaker: sera
interrupt: critical
Given everything that happened after the shift, and I do not say this lightly, the kettle is cold and the car is still in the drive.

Better

id: sera_warn_01
speaker: sera
interrupt: critical
The car is in the drive.

id: sera_warn_02
speaker: sera
interrupt: flavor
The kettle never boiled.

The weaker line hides two facts behind a preface, then marks the whole speech critical, which means a skip or a hit deletes the preface and maybe the facts with it. The repair gives the quest fact its own short critical line and lets the kettle be flavor. Front-loading is not a style preference. It is how a line survives the way games are actually played, which is badly, quickly, and with the menu open.

What you still owe the scene

The container does not matter as much as writers hope. A spreadsheet, a narrative document, the tool the producer already paid for: all of them can hold a speaker id, a line id, a mode, a string, a menu label, and an interrupt flag. None of them will invent those fields if you deliver a wad of scene prose and a note that says to make it feel reactive. This page is not a recommendation of software, and it will not become one. A program will not rescue a branch you did not count or a label that lies about the spoken line. What you owe the scene is the same thing you owe a play or a screenplay, under meaner constraints: a want, a voice, and a line that can be cut off without becoming a different plot. Store the line so the game can find it, lose it, translate it, and pay for it on purpose. If you cannot point at the record, you do not have game dialogue yet. You have a scene from another medium, waiting to be broken into pieces you should have owned before anyone booked a booth.

Exposition is the temptation the record makes easy, because a cinematic feels like a cutscene-shaped bucket and a bark feels like a tooltip with a voice. Do not pour the briefing into either. If Sera needs Idris to know about the car, the line is the car, not the history of the driveway. If the player needs a rule, the world should enforce it once before a character explains it twice. The related problem, saying the quiet part as a speech because you are afraid the system is unclear, is an exposition problem wearing a dialogue id. Format will not stop you. It will only show the length. Read the critical lines in isolation, with no cinematic around them, and see if they still sound like people. Then read the flavor lines and see if any of them secretly became critical while you were being thorough. Thoroughness is how games grow speeches. The format’s last job is to make that growth visible early enough to cut it while the cut is still cheap, which is before the performance, not after the bug report.

Questions writers actually ask

What belongs in a video game dialogue line?
At minimum, a stable speaker id, a line id, the mode, and the string a player might hear or read. Choices also need the menu label stored separately from the spoken line, even when the words match, so a later performance pass cannot change the contract by accident. Add an interrupt flag if the line is flavor that may be cut off or critical and must not be. A paragraph in a document can be the draft. It is not the line until those fields exist and a person other than you could find the row.
How is a bark different from a cinematic line?
A bark is fired by a system while the player is doing something else, so it has to make sense alone, survive repetition, and still work if it is cut off. A cinematic is a held scene, closer to an audience, and it can carry an exchange, but it is still a sequence of records, not a screenplay left for someone else to slice. If the cinematic can be skipped, any quest fact in it needs a short line marked to survive the skip. Do not record a speech for a moment that is actually a bark. The mode decides the length.
Why do choice labels and spoken lines both need writing?
The label is the move the player thinks they selected. The spoken line is what the character does with that move if the scene has a voice. The label must fit a narrow column and still fit after translation lengthens it. The spoken line can be a little more particular. They are allowed to differ in wording. They are not allowed to differ in tactic. If the label says agree and the line starts a fight, the menu has lied. Silence, if it is one of the moves, needs its own result. An empty slot that falls through is not a choice to be quiet.
How do I write lines that will be translated and recorded?
Write the English short enough that a language which runs longer will not break the menu or cover the face with subtitles. Use whole sentences, not fragments glued around a number, because word order and grammar will not survive the glue. Then count recordings, not summaries. Three choices that each open three unique replies are thirteen lines if you also count the opener, not one conversation. Every unique performed variant costs a session, and every on-screen string costs a translator even when nobody speaks it. Reuse only what the character would truly repeat.
How should game dialogue handle being interrupted?
Assume it will be. Put the point in the first words, and mark the record flavor or critical instead of hoping the audio team will guess. Flavor may die halfway. Critical must be short enough to finish, or the fact must also live somewhere a skip cannot delete. If you flag every line critical, the flag means nothing and the important sentence will still be talked over. Most jokes are flavor. A door code, a lethal warning, or a quest fact is critical, and it should not be hiding behind a clause about how the character feels.

Try this

Split one cinematic exchange into line records with speaker ids, mark which lines can be interrupted, and cut any choice whose menu label promises a different move from the spoken line.

All thirty exercises

Jonah Ellery

Narrative designer

Jonah Ellery is a narrative designer who has written game barks, comic scripts, and branching scenes. He edits the Lab’s interactive and balloon-economy pages.

More from this desk

Workbook

Thirty exercises, a voice sheet, and a punctuation card.

Leave an address and we’ll open a note to [email protected]. The workbook is also here, with no account.

Post a line

Put up a line of your dialogue and say what you were trying to do. Notes stay in this browser — they are a scratch margin, not a public thread.