Every novelist has the moment. You cut a scene, tighten a chapter, rewrite an opening, and then realize the version you deleted was the one that worked. A good novel draft is full of these small losses, and most of them are avoidable. Pendrilo's Version History gives you two ways to get them back: automatic versions that accumulate as you write, and named versions that stay put until you delete them yourself.
This article walks through both, plus a practical routine for protecting your manuscript before a major revision. None of it is complicated, but it works best if you set it up before you need it.
Why overwritten chapters happen
Most lost text does not vanish in one dramatic keystroke. It goes in small pieces. You select a paragraph to move it, paste over it by accident, run a find-and-replace that catches more than you meant, or spend an afternoon "improving" a chapter and discover on Tuesday that Monday's version was better. Each change looks reasonable on its own. Added together, they leave you with a chapter you cannot reconstruct from memory.
The problem gets worse when you are revising for a specific reader or deadline. Beta feedback often asks for structural changes: moving a reveal earlier, merging two characters, cutting a subplot that three people said dragged. Those are the edits most likely to cost you something you wanted to keep.
How automatic versions work
Version History keeps up to 50 automatic versions of your book. You do not have to start it or manage it day to day. Each time a version is recorded, you get a point in the manuscript's history you can return to, and you can compare that point against your current draft.
The limit matters. Fifty sounds like a lot until you have been drafting for several months and revising every evening. Once the list is full, older automatic versions eventually fall away. That means the snapshot from three weeks ago, the one you were going to check against, may no longer be there. Automatic versions are a good short-term net. They are not an archive.
That is where named versions come in.
Name a version before a big revision
A named version is a snapshot you label yourself and keep permanently. It does not count against the rolling automatic list in the way that ordinary history does, so it survives while the automatic versions cycle through. Use names that describe the state of the book, not the date.
A workable routine looks like this:
- Finish a draft pass, or reach a point you are happy with, and save a named version before you touch anything else.
- Name it after the milestone, such as "Draft 3, before beta notes" or "Full read-through complete."
- Make your revisions. Let automatic versions keep recording as you go.
- When the revision is done, save another named version with a clear label, such as "Revision 1, merged subplots."
- If the new direction does not work, restore the earlier named version rather than trying to reverse each edit by hand.
The names matter more than they seem. Six months from now, "Version 14" tells you nothing. "Before cutting the lighthouse subplot" tells you exactly what you are looking at.
A named version is cheap insurance. Make one before every change you would hate to undo.
Recover one overwritten chapter
Not every problem needs a full rollback. Often you want one chapter back and the rest of the book as it is now. Pendrilo's Version History lets you compare an older version with your current draft, so you can see what changed and decide what to keep.
Here is the usual approach for recovering a single chapter:
- Open Version History and find the version from before the damage. If you have a named version nearby, start there, since it will not have rolled off.
- Use the comparison view to find the chapter you want. Check that the passage you need is in the version you picked.
- Copy the recovered text into your current draft, or restore the older version if the whole book was better at that point.
- Read the restored chapter in context. Chapters often reference events that changed in the meantime, so check the transitions on either side.
Restoring the whole book is the blunt option. It is the right tool when the revision failed across many chapters. If the damage is limited to one scene, copying the passage back is less disruptive and keeps your other recent work intact.
Keep a backup outside the version list
Version History protects you from edits. A backup protects you from everything else: a corrupted file, a disk failure, or a day when you open the wrong project. Pendrilo can create a backup as a single zip per book, or back up all your books at once from Studio.
Make a backup before any large operation, not just at the end of the month. Keep at least one copy somewhere other than the computer you write on. A named version and a backup do different jobs, and you want both before a risky revision. The version list lives with the book. The zip gives you a copy you can open even if the book itself is in trouble.
Because Pendrilo runs on your computer and does not need an internet connection to write, the backup is the file you control. Store it where you would store anything else you could not afford to lose.
Limits to keep in mind
Pendrilo is still in beta, and Version History is one feature among many still being refined. A few practical points follow from that and from the limits above:
- Automatic history is capped at 50 versions, so do not rely on it to hold a months-old state.
- Named versions are the right way to keep a milestone, but they are only one layer. Keep the backup zip as well.
- Restoring an older version replaces the current state of the book. If you want to keep your latest work, save a named version first, so you can return to it.
- Version History tracks your manuscript. It does not replace a separate copy of your research notes or outside reference files.
If you have not tried the workflow yet, the cheapest test is to save a named version right now, make a deliberate change to a non-critical scene, then restore the earlier version and confirm the text came back. Five minutes of testing is much better than finding out the process fails on the day you need it. You can create a free Pendrilo account and run through the steps on a copy of your current draft.
The best time to set up a safety net is before the big revision. The second best time is now, before the next edit you might regret.
