story bible software

Story Bible Software That Builds Itself

Stop maintaining your story bible by hand. PlotLens reads your manuscript and builds a complete canon automatically.

Join the Waitlist

What is a story bible?

A story bible is a reference document that tracks every character, location, timeline, relationship, and world rule in your story. For series writers, screenwriters, and game teams, it's the single source of truth that keeps everyone on the same page. The problem: building and maintaining one by hand is tedious, error-prone, and never complete.

Traditional story bible tools require you to manually enter every character, location, and plot point. PlotLens takes the opposite approach: it reads your manuscript and extracts canon automatically. Your story bible stays in sync with your draft because it’s generated from the text itself.

Characters, locations, and lore — extracted automatically

PlotLens reads your manuscript and builds a structured canon. Every character trait, location detail, and timeline event is tracked without manual entry.

  • Automatic entity extraction from your manuscript
  • Character profiles with traits, relationships, and arcs
  • Location details and world-building rules captured as you write
Character Entity
Character Entity 5 aliases · 4 traits
S
Sarah Chen
Protagonist · Detective · First appeared Ch. 1
Sarah Detective Chen the detective Mom the woman in red
Brown eyes, 5'6"
Scar on left cheek
Partner: James Ortiz
Daughter: Lily, age 7
Contradiction detected: Ch. 14 describes scar on right cheek — conflicts with Ch. 3 (left cheek).

Timeline validation that catches what you miss

PlotLens tracks chronological consistency across your entire story. If a character appears in two places at once or an event contradicts the established timeline, you'll know before your readers do.

  • Cross-chapter timeline consistency checks
  • Automatic detection of chronological contradictions
  • Visual timeline view of story events
Timeline View
Story Timeline
Story Writing
Winter, Year 1
The Battle of Ashenmoor
Ch. 3, p.47 · Written Feb 12
Spring, Year 1
Treaty signed at Greyhaven
Ch. 8, p.142 · Written Mar 3
Spring, Year 1 (?)
"The battle raged through the spring rains..."
Ch. 20, p.310 · Written Apr 18
Conflicts with Ch. 3 — battle was winter
Draft 2, revision
Author changed Ashenmoor to autumn in revision notes
Revision note · Apr 20

PlotLens vs. the way you track canon today

Spreadsheets

No auto-extraction. No cross-referencing. No drift detection.

Notion / Wikis

Manual upkeep. Goes stale as drafts evolve. No validation.

Scattered docs

No single source of truth. Easy to lose track of changes.

Manual re-reading

Doesn't scale past one book. Readers remember what you miss.

PlotLens replaces the workflow, not your writing tools.

See how PlotLens compares to dedicated tools →

Who uses PlotLens

Ready to try PlotLens?

Join the waitlist or explore pricing.