How to Proofread a Ren'Py Script in a Spreadsheet (Step-by-Step)
How to export every dialogue line from your Ren'Py game into a spreadsheet, give it to a proofreader, and put the corrections back into your .rpy files without breaking your game. It includes a column template, a brief for your proofreader and a checklist for putting edits back.
If you write your visual novel in a second language, or you just want another person to check your English, you will run into a problem. Proofreaders don't want to read .rpy files. Those files are full of `show`, `scene`, `jump` and `$` lines that have nothing to do with the writing. You also don't want them editing your code.
The fix is to move only the dialogue into a spreadsheet, have the proofreader edit it there, and then put the changes back carefully. This guide covers each step, including the step where most people break their game.
Step 1: Freeze the script before you export
Proofreading a script that keeps changing creates problems. Before you export:
- Commit or back up your whole game/ folder. Use Git if you have it. If not, a dated zip copy is fine.
- Tell your team the script is locked for the proofreading period. If someone has to change a line, write it down so you can fix that row by hand later.
- Run Lint from the Ren'Py launcher and fix any errors first. You want a clean starting point, so that any error that shows up later was caused by the edits.
Step 2: Export the dialogue
Ren'Py has a built-in exporter. In the launcher, choose your project, then Extract Dialogue, then Tab-delimited Spreadsheet (dialogue.tab). You get a file called dialogue.tab in your project folder, and any spreadsheet program can open it.
The first column is a line identifier. The other columns describe each line: who says it, what it says, and where it is in the script. The exact columns can vary between Ren'Py versions, so check the header row of your own file.
Tips for this step:
- Open it as tab-separated, not comma-separated. In Google Sheets, use File > Import and choose "Tab" as the separator. In Excel or LibreOffice, use the import dialog and choose Tab. If you double-click the file, your dialogue may split into the wrong columns wherever a line contains a comma.
- Check the encoding is UTF-8, especially if your game uses accented letters or non-Latin text. If you see characters like "é", re-import and choose UTF-8.
- Keep the original export file untouched. Work on a copy. You will need the original text later to check that nothing changed underneath you.
Step 3: Set up the proofreading sheet
Add columns so the proofreader never types over your original text. A layout that works:
- ID: the identifier from the export. Don't edit it.
- File : Line: where the line lives, for example `script.rpy : 214`.
- Speaker: who says it (empty for narration).
- Original: the text as exported. Lock this column or protect the range.
- Edited: empty. The proofreader writes the corrected line here only if it needs changing.
- Note: optional. Questions, alternatives, or "check with writer".
The rule that makes everything else work: an empty Edited cell means "no change." You then only have to deal with the rows that changed, which is often a small share of the script.
Also worth doing:
- Freeze the header row and turn on text wrapping for the Original and Edited columns.
- Keep the rows in script order. Proofreaders need context, and lines in random order are hard to judge.
- Add a Status column if more than one person is reviewing (for example "to check", "done", "query").
Step 4: Brief your proofreader (copy this)
Paste this into the first tab of the sheet, or send it with the file. Fill in the brackets.
Proofreading brief: [Game title]
- What I need: spelling, grammar, punctuation and natural-sounding English. [Say whether you also want style or tone suggestions, or only corrections.]
- Where to write: put your corrected line in the Edited column. Leave it empty if the line is fine. Do not change the Original or ID columns.
- Characters' voices: [Name] speaks [casually / formally / with slang]. Please don't "correct" deliberate dialect, slang or broken speech for these characters: [list].
- Text tags: do not remove or change anything in curly braces. Examples: `{w}` (pause), `{i}...{/i}` (italics), `{b}...{/b}` (bold), `{color=#f00}...{/color}`. Keep them where they are, around the same words.
- Square brackets are variables. `[player_name]` and similar get replaced in the game. Don't translate, respell or remove them.
- Quotes inside a line: if you need quotation marks inside dialogue, tell me in the Note column instead of typing them. They can break the script.
- Questions: use the Note column, or mark the line "query."
- Deadline: [date]. Scope: [all routes / chapter 1 only / rows X to Y].
Step 5: Review the edits before touching any code
When the sheet comes back:
- Filter to rows where Edited is not empty. These are the only rows you need.
- Read each change against the original. You are the writer, so accept, reject or adjust each one. If you reject a change, clear the Edited cell.
- Check every row for broken markup:
- The number of `{` matches the number of `}`.
- Every opening tag like `{i}` still has its `{/i}`.
- `[variables]` are unchanged.
- There are no new straight double quotes `"` inside the text. In a .rpy file they must be written as `\"`, or you can use curly quotes (“ ”) instead.
- There are no new line breaks inside a cell.
- Look out for stray spaces at the start or end of edited cells. Spreadsheets hide them, but they will show up in your text box.
Step 6: Put the changes back into your .rpy files
Most problems happen at this step. Ren'Py's dialogue export only goes one way: there is no built-in "import corrections" button. You have to apply the edits yourself, either by hand or with a script.
Doing it by hand safely:
- Make a fresh backup of game/ (or commit in Git) right before you start.
- Sort the changed rows by file, then by line number.
- For each row, open the file in your editor and go to that line (most editors have Ctrl+G / Cmd+L "go to line").
- Check that the line still matches the Original column exactly. If it doesn't, the script changed after the export, so stop and handle that row by hand. Don't paste blindly.
- Replace only the text inside the quotes. Keep the indentation, the speaker name, and anything after the closing quote (such as `with vpunch` or an `id` clause).
- Mark the row "applied" in the sheet so you never apply it twice.
Why go file by file and line by line: a normal edit changes one line in place and does not shift the line numbers below it. If you add or delete whole lines while working, though, every number below that point is now wrong. Avoid adding or removing lines during this pass. If a proofreader suggests splitting one long line into two, write it down and do it afterwards, separately.
If you have translations: Ren'Py matches translations to dialogue using an identifier based on the original line. If you edit the original English, the existing translation blocks for that line may stop matching. Check your translation files after a proofreading pass, and regenerate or update them as needed.
Step 7: Test before you call it done
- Run Lint again. It catches many syntax errors, such as unclosed quotes and bad tags.
- Compare the result with your backup. In Git, run `git diff` and read every change. Each changed line should be one you approved, and nothing else should have moved.
- Play through the changed scenes, or at least use skip mode through them, and look for text that overflows the box, missing pauses, or wrong italics.
- Spot-check 10 random rows from the sheet against the game to confirm they went in correctly.
Quick checklist
- [ ] game/ folder backed up and script locked
- [ ] Lint clean before export
- [ ] dialogue.tab exported and imported into a spreadsheet as tab-separated UTF-8
- [ ] Original column protected, empty Edited and Note columns added
- [ ] Brief sent, with character-voice rules and the "don't touch tags or [variables]" rule
- [ ] Edited rows filtered and reviewed by the writer
- [ ] Every edited row checked for braces, tags, variables and quotes
- [ ] Fresh backup made right before applying changes
- [ ] Each line checked against Original before it was replaced
- [ ] No lines added or removed during the apply pass
- [ ] Translation files checked, if you have them
- [ ] Lint run again, diff read, changed scenes played
When to automate it
For a short game with a few dozen corrections, applying them by hand with this checklist works fine. With hundreds of changed rows across many files, doing it by hand gets slow and mistakes become likely. That's when a script that checks each row against its original text, refuses rows that no longer match, makes backups and gives you a diff report pays for itself. Whether you build that yourself or use a ready-made tool, the safety rules above still apply: check the original, change only the text inside the quotes, and read the diff.
GuestBrief DIY Kit: Research Any Podcast Guest and Write Your Interview Prep in About an H · $8.99
Get it on Gumroad