Timeline tools for fiction writers, chosen by the job your timeline does

Chapter 4 says Neve was “barely fifteen” when she carried the relief letter through the siege. Your notes say she was born in year 388 and the siege began in 401. One of those is wrong, and a timeline tool earns its place only if it shows you which before a reader does.

This is a shortlist organized by need, not a scored ranking. Product details come from each vendor’s official documentation, checked on 11 October 2026; we have not tested the tools hands-on. Prices are left out.

Decide what your timeline has to catch#

Timeline errors come in three kinds, and the tools below differ in which ones they help with.

• Sequence: what happened before what, and what a character can know by a given scene.
• Arithmetic: ages, travel times and the years between events. A tool can do this for you only if it understands your calendar.
• Connection: which people and places an event touches, so that moving it shows you what else has to move.

Decide too whether you need story order beside chronological order. A flashback told in chapter 12 still happened in year 390. The timeline guide covers the method; this article is about where to keep it.

The sample: Neve’s letter and the siege of Kessin#

Enter the same records in every candidate. Two characters: Neve, a courier, and Aldous, archivist at Fort Kessin. Two places: Fort Kessin and the Tamber ford. Four events:

Chapter 4 calls Neve “barely fifteen” in that last event. She is thirteen. Note how each tool shows you the problem and how much of the arithmetic you did yourself. Then move the siege a year later and count what you had to update by hand.

Simple or calculated: a spreadsheet or Aeon Timeline#

A spreadsheet#

Give each event a row, with columns for a sortable year, the date as written, the event, the people and the place. Sort by year, filter by a name, and add a formula that subtracts the birth year from the event year. For the Neve sample, that formula flags the error at once, provided you wrote it. The limits are familiar: nothing links to your character notes, every change is manual, and an invented calendar needs a plain number column to sort on.

Aeon Timeline#

Aeon Timeline does the most arithmetic of anything here. Its worldbuilding page describes custom calendars with your own eras, months and weekdays, and automatic tracking of characters’ ages and the time between plot points. Its storytelling page adds a separate timeline per character, to make sure nobody is in two places at once, and a Narrative view where scenes can be dragged into any order regardless of dates (narrative and storytelling). Relationships can record whether someone took part in an event or only observed it, and dependencies show which events block others (assign and track). It syncs both ways with Scrivener on Mac and Windows and Ulysses on Mac, and imports and exports CSV (integrations).

Check how it fits the way you store and share work. Timeline files are stored locally, timelines cannot be published on the web, and the FAQ suggests a shared drive for collaboration while warning that simultaneous edits cause conflicts (FAQ). It runs on Mac, Windows, iPad and iPhone, with writing-app sync and auto backup on desktop only (platforms). A free 14-day trial is offered (Aeon Timeline).

Connected to your world: Yazar.io or Campfire#

Yazar.io’s Timeline#

Yazar.io keeps the timeline inside a worldbuilding workspace that sits beside a manuscript in Word or Google Docs. Each event has a title, a free-text date label, so “401, late summer” works as written, and an optional note; you drag events to reorder them (timeline). Add Neve and Aldous as participants and the Tamber ford as the location, and each of their pages lists its events in timeline order (updates). Neve’s page then holds her birth and the letter in one list, beside her profile, her relationships and a backlink panel showing every entry that mentions her (features). This is the job Yazar.io does well: the timeline is not a separate chart but part of each character’s record. It is unlimited on the free plan (pricing) and available in the iPhone, iPad and Android apps (mobile app).

The limits matter for this job. Date labels are text you write, so you still subtract 388 from 401 yourself. The timeline is one ordered list; parallel timelines need your own labels in event titles. You can publish it on the read-only wiki, but it is off by default, which keeps spoilers private until you turn it on (updates).

Campfire’s Timeline and Calendar modules#

Campfire suits writers who want the timeline in the same app as the manuscript. Its Timeline module arranges event cards in customizable rows and dividers, connects them flowchart-style, switches to a Gantt chart view for long spans and color-codes periods. A row can follow one character, events can link to the Arcs module, and more than ten plot templates are included. The Calendar module builds custom months, weeks, moons and eras, and links to the timeline in both directions (calendar).

The pages we read don’t describe automatic age calculation, so test the Neve sample before assuming it. The free plan allows 20 timeline events and one calendar (pricing), and the iOS and Android app offers the timeline’s events only (apps).

Built by you or ordered by scene: Obsidian or Plottr#

Obsidian#

Obsidian’s help describes no timeline view, but it documents the parts to build one. Notes are Markdown files in a local folder (storage). Properties add typed fields, such as numbers, dates and lists, to a note (Properties). The Bases core plugin shows notes as a table, list, cards, kanban board or map, which you can sort, filter and group by those properties or by formulas (Bases, views). Give each event note a year number and a people list, and a Bases table sorted by year becomes your timeline. If you prefer a picture, the Canvas core plugin lays out cards on an open space with lines between them, placed by hand (Canvas).

The catch is the calendar. Date properties store real calendar dates such as 2020-08-21, so an invented calendar needs a number property for sorting and a text property for the date as written. Ages and gaps are yours to work out, by hand or with a formula you set up.

Plottr#

Plottr is a plotting tool. Its drag-and-drop timeline lays out plotlines, such as the main plot, subplots and character arcs, against chapters, scenes or beats. Scene cards track characters, places and tags, and you can flip the timeline, zoom out and filter to see who is doing what, where and when. A series can have its own timeline as well as one per book, and outlines export to Word and Scrivener. It runs on Windows and Mac, and a Pro version adds a web app, cloud storage and collaborators (Plottr); a 30-day free trial is offered (free trial).

Its features page describes chapters and beats, not calendar dates or calculated ages, so treat it as a tool for story order. It will show the letter scene in chapter 4 against the siege subplot, but Neve’s age stays a detail in her character bio for you to check.

Compare by need#

Common timeline-tool mistakes#

• Treating a sorted list as a check. Sorting shows order; it doesn’t tell you Neve is thirteen. Only a calculating tool or your own formula does the arithmetic.
• Mixing story order and chronology. Keep the chapter where something is told apart from when it happened.
• Using real dates for an invented calendar. A date field that expects 2026-10-11 will fight “401, late summer”. Use a number to sort and text to display.
• Building history before the story needs it. Start with the events your chapters depend on, and add centuries only when an earlier cause matters.
• Keeping the only copy in one app. Export to a format you can open elsewhere, and reopen it once.

Who should pick which#

• A short story or a first novel with one calendar: start with a spreadsheet, and move only when maintaining it becomes the work.
• A plot that turns on ages, travel times or a long invented history: Aeon Timeline is built for that arithmetic. Expect more setup.
• A novelist writing in Word or Google Docs with a growing cast: Yazar.io keeps each character’s events on their own page alongside the rest of the world, leaving the arithmetic to you.
• A writer who wants manuscript, calendar and timeline in one app: Campfire, within its free-plan limits or on a paid plan.
• An Obsidian user: build the timeline from properties and Bases before adding another app.
• A plotter managing subplots across a series: Plottr for story order, paired with something dated if chronology matters.

For a wider look at worldbuilding software, see the best worldbuilding tools. If births and successions are what keep slipping, try a family tree for a fantasy dynasty.

Update, 21 October 2026: Described Yazar.io dates as labels you write, and corrected the wiki so the Timeline can be published and is off by default.