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:

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:

Step 3: Set up the proofreading sheet

Add columns so the proofreader never types over your original text. A layout that works:

  1. ID: the identifier from the export. Don't edit it.
  2. File : Line: where the line lives, for example `script.rpy : 214`.
  3. Speaker: who says it (empty for narration).
  4. Original: the text as exported. Lock this column or protect the range.
  5. Edited: empty. The proofreader writes the corrected line here only if it needs changing.
  6. 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:

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]

Step 5: Review the edits before touching any code

When the sheet comes back:

  1. Filter to rows where Edited is not empty. These are the only rows you need.
  2. 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.
  3. Check every row for broken markup:
  1. 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:

  1. Make a fresh backup of game/ (or commit in Git) right before you start.
  2. Sort the changed rows by file, then by line number.
  3. For each row, open the file in your editor and go to that line (most editors have Ctrl+G / Cmd+L "go to line").
  4. 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.
  5. 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).
  6. 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

Quick checklist

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.

Want the full done-for-you kit?
GuestBrief DIY Kit: Research Any Podcast Guest and Write Your Interview Prep in About an H · $8.99
Get it on Gumroad