Story bible

Your characters, houses, timelines, calendar, ties and chapter outline from this site, with your own sections, in one document to print or save as a .docx.

Free, no sign-up. It reads what the other Dankstory tools keep in this browser; nothing is uploaded.

Once you start, your story bible (title, author, your own sections, what is ticked and the order) is saved in this browser as you type, on its own; the trees, timelines and other items are read from their tools each time and never copied into it. Save the file to keep a copy or move it to another device. Safari, and most browsers on an iPhone or iPad, may delete what a site keeps after seven days of use without a visit to the site, so save the file or back up everything.

What it does

A story bible is the reference a writer keeps beside a book or a series: who everyone is, how they are related, what happened when, how the world works, and what the invented words mean. If you already keep some of that on this site, most of it is written. This page finds everything the other Dankstory tools have saved in this browser and lists it under From this browser:

Family trees (family tree and its fantasy, royal, OC and pantheon pages): every character with what their character sheet shows: title, house, birth and death, people or species, parents, brothers and sisters, partners in order, children and grandparents, and the writer's fields (appearance, personality, wants, fears, flaw, arc, notes). Then the houses, with their members counted.
Timelines: the events told in the book in story order (chapter and scene, with POV and any flashback marked) and every event in world order, dated in your own calendar and eras.
Chapter outline from the plot grid: each chapter's title and word count, and its events under each plot line.
Calendar from the fantasy calendar: the months and their days, the leap rule, the week, festivals outside the months, moons and eras.
Relationships from the relationship map: the cast with their roles, and every tie (family, love, rivalry, who serves whom) in words.
Word count projects from the word count tracker: each project's goal and total, nothing more.

Beside them go six sections of your own to fill in: premise and logline, places, rules of the world, themes, glossary and notes. Rename, delete or add sections; move any section up or down. The print has a title page, a contents page and every section on a new page, numbered at the foot. The .docx has the same title page, then a table of contents your word processor fills in, and every section as a real Heading 1 (its parts Heading 2 and 3), so the navigation pane lists them too.

A worked example. Try the example builds a bible for an invented world, The Saltglass Reach, from the site's own examples: the fantasy family tree (13 characters, 3 houses), the relationship map (10 characters, 16 ties), the calendar (10 months, a 6-day week, 2 moons, 2 eras), the story timeline (25 events in world order; none has a chapter, so its story order says so) and the word count tracker's example project, between six sections written for it. That is 11 sections. Nothing from the example is saved unless you start your own; your own bible is not touched.

The table of contents in the .docx

A table of contents with page numbers can only be made by the program that lays out the pages, and this page does not lay out the .docx's pages: your word processor does. So the file holds a table-of-contents field marked as needing an update, and its settings ask the word processor to update fields when the file opens; whether it does that by itself, asks first or waits for you depends on the program. Until it is updated, the contents page shows one line saying how. In the print from this page, the contents list gives the sections in order and the page numbers are at the foot of each page.

What it cannot do

It reads only what this browser holds. Work saved in another browser or on another device is not seen: restore a backup here first, or open each tool's file on its page.
Nothing syncs between browsers. Your story bible is saved here only; save the file to move it.
Pictures are not in the .docx or the print: no portraits, crests, coats of arms, family tree charts, timeline drawings or relationship map drawings. Export those from their own pages as PNG or SVG and add them in your word processor.
The items from the other tools are read, never edited: change a character or an event on its own page, and the bible shows the change the next time this page is opened.
Plot diagrams, saved manuscript details and manuscripts are not included.
Each word count project gives its goal and total only, not its daily log.
Your own sections are plain text: # headings and - list items, no bold, italics, tables or links.
The printed contents list has no page numbers, only the order of the sections. The page numbers at the foot of each printed page need a browser that prints page-margin boxes (current Chrome and Edge do); in another browser, turn on the page numbers in its print dialog's headers and footers.
The .docx is checked by this page's own tests (every part well-formed and declared, every checksum right, one Heading 1 per section). It has not been checked in any particular word processor.

Private by design

No account and no upload. The page reads this browser's storage and builds the print and the .docx in your browser; nothing leaves your device. The one thing sent anywhere is an anonymous count that a button was used (for example bible-print), never a name, a title or any text.