Your Story Bible's Theme Finally Shows Up, You Can Export It As A File, And The Editor Stopped Losing Your Place -- Plotiar Product Updates (September 2026)
A writer emailed support convinced her subscription was broken. She had opened her story bible's theme panel, picked an accent color and a typeface for it, and watched nothing on the page change -- not the color, not the font, nothing.
She wasn't wrong about the "not getting" part.
The panel had been saving her choices since the day it shipped. Nothing anywhere was reading them back. That's fixed now, along with a handful of other gaps between what Plotiar promised and what it actually did. Here's what shipped.
Your Bible's Look Now Actually Follows It Around
Pick an accent color and a typeface for your story bible, and it now shows up in three places instead of zero: the Lore page itself, the public wiki if you publish one, and the character list and glossary sections when you export your manuscript. The typeface carries through the whole surface; the accent is used more sparingly, on headings and small details, never on body text, so nothing gets harder to read for the sake of looking nicer. On the wiki, your cover image now appears above the title the way it was meant to from the start.
Take Your Bible Home As A File
Something a reader asked for directly: "is it possible to export the lore bible? It would be handy to have a copy in case something ever crashes." It should already have been possible -- Plotiar has been able to generate a bible as JSON, Markdown, or CSV for a while -- but nothing in the app actually offered it to anyone. There's now an export option on the Lore page in all three formats, in every language Plotiar supports. If a bible happens to be completely empty, the export says so plainly instead of quietly handing you a file with nothing in it.
A Typeahead So Finding Doesn't Mean Scrolling
Also from a reader: searching a large bible already worked, but the results landed in a list at the bottom of the screen, several hundred pixels away from the box you had just typed into. The same matches now also drop down directly under the search box, reachable with the arrow keys and Enter. Before you have typed anything, it shows you what you opened most recently instead, which covers the other half of the same problem.
The Editor Stopped Losing Track Of What It Was Showing You
A run of smaller-sounding bugs turned out to share one cause: the editor occasionally told you one thing while doing another. A document could finish loading behind the scenes before its content had actually painted on screen, so a fast typist could start typing into what looked like an empty page and lose those first keystrokes. Switching away from Plotiar and back, or letting a laptop wake from sleep, could in rare cases bring back a different chapter than the one you had left open. Spellcheck could get stuck starting up and never recover for the rest of the session. And resting a hand on a mouse without moving it could flip the editor into its mobile layout, as if you had picked up a phone. All four are fixed. None of them were common, but a writing tool that occasionally shows the wrong page, or no page, is the opposite of what Plotiar is supposed to be, and each one got closed the week it turned up rather than left to sit.
A Few Smaller Fixes Worth Mentioning
If your plan just upgraded, Plotiar now recognizes it right away. Previously, a short window right after upgrading could leave the app still showing your old plan, which meant hitting an upgrade prompt for a plan you already owned, paired with an error message telling you to try again -- advice that could not possibly have helped. That's closed. And in collaborative documents, a narrow sequence involving a paste immediately followed by an undo could silently drop a paragraph from the shared page. It is fixed, and it is exactly the kind of thing that should not happen to anyone's manuscript, however rare.
Try Plotiar at app.plotiar.com.