Campfire vs Yazar.io: one writing app or a world beside your manuscript

Campfire and Yazar.io both keep track of characters, places and history, but they make different assumptions about where your novel is written. Campfire wants the manuscript inside the app, next to its planning modules. Yazar.io assumes the manuscript stays in Word or Google Docs and keeps the world in a separate, linked workspace. Know which habit you have before you compare anything else.

This comparison is based on each company’s official documentation, not on hands-on testing. Yazar.io’s feature, pricing, wiki, privacy and update pages were checked on 21 October 2026. Campfire’s writing, timeline, pricing and FAQ pages were checked the same day, and its other pages on 11 October 2026. Campfire’s official Reddit account is the source for auto-tagging and for @ in the manuscript.

Where the manuscript lives#

Campfire’s Manuscript module is a word processor. You draft chapters, rearrange them in an Index Card View and restore older drafts from version history (word processor). You can tag characters and locations in the text and open their notes in a sidebar while you write. It imports a DOCX or EPUB file and splits it into chapters, and exports the finished manuscript to EPUB or PDF. If you want one app from first outline to a file you can send to an agent, Campfire is the only one of the two that does it.

Yazar.io focuses on the world behind the story. Its own FAQ says you keep writing the novel where you always do, in Word or Google Docs, and use Yazar.io to organize that background (FAQ). If you want the draft and the world in one window, Campfire is the one that does it. If you like your word processor, or you don’t want to move a half-finished manuscript, the split is the point.

Modules versus sections#

Campfire is built from eighteen modules, including Characters, Locations, Encyclopedia, Magic, Languages, Maps, Timeline, Calendar, Relationships and Research (writing app, worldbuilding tools). Elements are laid out as panels you can arrange. The free plan gives limited access to every module: for example 10 characters, 5 locations, 20 timeline events, 2 maps and 25,000 manuscript words (pricing).

Yazar.io opens with Characters, Locations, Organizations, Lore, Races, Creatures, Items, Spells, Beliefs and a Glossary, plus Notes, a Timeline and a drag-and-drop Family Tree (features). Yazar Pro can add up to 3 custom sections per book, each with a name and icon you choose (updates). Field templates decide which fields each section shows, and notes come in 10 types with a status from idea to used. The features page describes the workspace as simple: “Simplicity that doesn’t suffocate. No getting lost in dozens of menus.” You start in the browser, a sample book is already filled in, and the free plan asks for no credit card (features).

The free plan covers 2 books and 15 editable records per entity type in each book. Glossary, Timeline, Notes and Quotes are unlimited (pricing). Yazar Pro is $6.99 a month or $54.99 a year, as confirmed by the Yazar.io team on 21 October 2026. The pricing page shows the amount in your local currency, and prices may differ by region.

Campfire covers more ground, notably languages, calendars and flowcharts. Yazar.io asks for fewer decisions before you start.

Linking and finding a detail#

In Yazar.io, typing a character’s name in another entry links it, or you type @ to pick one, and every page has a backlink panel listing who mentions it (features). Selectable relationships, such as a character’s organization or birthplace, appear on the other record too (updates). Quick search works within one book (updates), and links are usually the faster route to a detail buried in a long description.

Campfire also auto-tags an element when you type its name. Its official account describes a setting, “Automatically tag elements,” and typing @ in the manuscript to tag an existing element or create one (automatic tagging, @ in the manuscript). Tags in the draft open that element’s notes in a sidebar, Research items can be linked to other story elements, and map pins can open any element (writing app, maps). Those pages do not describe a panel that lists every mention of an element, so that part of “where else does this name appear?” stays undocumented for Campfire.

Timelines, calendars and maps#

Timelines and calendars#

Campfire’s Timeline module is the more elaborate. Event cards sit in customizable rows, can be dragged and connected flowchart-style, and a Gantt chart view shows long spans with color-coded periods. Rows can follow individual characters, events can link to the Arcs module, and more than ten plot templates are included (timeline). The Calendar module builds custom months, weeks, moons and eras and links to the timeline in both directions (calendar). If your world runs on an invented calendar, Campfire has a documented home for it.

Yazar.io’s Timeline is a single ordered list. Each event has a short title, a free-text date label such as “Year 3, Harvest Month”, and an optional note, and you drag events to reorder them (timeline). Events can name the characters who take part and the locations where they happen, and those pages then list their events in timeline order (updates). Date labels are text you write, so ages and durations stay your arithmetic, and parallel timelines need your own labels, such as a marker in each event title.

Campfire wins on calendars and on visual structure, including per-character rows you set up yourself. Yazar.io’s strength is the list that appears on the character or place page without a view to build.

Maps#

Campfire’s Maps module takes a map you upload or link from Inkarnate, then adds pins that open any story element, including other maps, zones for regions, layers and a ruler with custom units (maps). Yazar.io keeps places as linked records, in text and fields, and does not include a map editor. If geography drives your plot, Campfire is the clear fit. Campfire’s pages describe uploading or linking a map, not drawing one, so draw it first, starting from a difficult journey.

Collaboration and sharing with readers#

Campfire supports co-writing. You can invite collaborators to view, comment on or edit a project, and they need only a free account; link sharing allows viewing only (FAQ). Its worldbuilding page describes working together in real time and viewing modes that hide panels you don’t want to reveal yet (worldbuilding tools). For readers, Campfire runs its own publishing platform, where an ebook can carry extras such as character profiles and interactive maps, and a private share link can show it to friends first (publishing).

Yazar.io keeps one account on the records, so it is not a co-writing app. For readers it offers a read-only wiki, free on both plans, with each section switched on or off (wiki). You set it to Private, Unlisted or Public, and you can add a password (who can see the wiki). Notes are never included. The Timeline can be published and is off by default: turn it on from the section list in Book Settings (updates). The same account can publish an Author Card, a public profile at yazar.io/@username with books and links, free on both plans (Author Card). The wiki suits a companion for readers or beta readers, not a writing partnership. Yazar.io stores entity descriptions, notes and custom field values encrypted with AES-256-GCM (privacy). Campfire’s pages checked for this article do not state an encryption method; they do describe automatic backups (writing app).

Backups, exports and phones#

Leaving and backing up#

Campfire’s FAQ describes File → “Download Project Backup” and restoring backups from the same menu; while online, you can export elements to formats such as DOCX (FAQ). The word-processor page also mentions daily backups.

Yazar.io exports a whole book, including characters, locations, notes, events and relationships, as Markdown or JSON; the Markdown export is a .zip that Obsidian and Notion can open (updates). There is no import tool, so an export cannot be loaded back and an existing bible has to be retyped (offline FAQ).

Mobile and offline#

Campfire runs in the browser, in a free desktop app for Mac and Windows that works offline, and in the CF Creators app for iOS and Android, which needs a connection and offers the timeline’s events only (apps). Yazar.io has iPhone, iPad and Android apps with every section, including the Timeline (mobile app). Editing needs a connection, though the mobile app keeps showing content you have already opened during a short outage (offline FAQ). If you write on trains or planes, Campfire’s desktop app is the stronger answer.

Run the Corve Light sample through both#

Enter the same small world in each free plan. Two characters: Ottilie Marr, the lighthouse keeper’s daughter, and Rhun Dace, captain of the Gannet. Two places: the lighthouse at Corve Point and the harbor at Hessle. Three events:

The contradiction: chapter 7 has Ottilie light the Corve lamp to warn the Gannet, but the lamp has been in Hessle since autumn.

In Campfire, draft chapter 7 in the Manuscript module and tag Ottilie and Corve Point. Put the events on the timeline with a row each for Ottilie and Rhun, and pin both places on a map. The missing lamp is one sidebar away while you write the scene.

In Yazar.io, add the events with their dates as written and set the participants and locations from the table. Open Ottilie’s page: the lamp’s removal is listed before the wreck, and her backlink panel shows every entry that mentions her. Then search chapter 7 in Word for “lamp”.

Neither tool’s documentation describes automatic contradiction checks; you catch the clash because the events sit in order near the scene. Finish by exporting the sample and opening the copy outside the app.

Common mistakes when choosing#

• Counting features. Campfire has more modules, which matters only if you will use them. A map you never open is setup time spent.
• Expecting the world workspace to hold the draft. Yazar.io keeps the manuscript in Word or Google Docs on purpose. If two windows annoy you, Campfire’s manuscript module settles it.
• Expecting a writing app to share like a wiki. Campfire’s link sharing is view-only and its reader features live in its publishing platform.
• Skipping the exit test. A Campfire project backup restores into Campfire; a Yazar.io export is Markdown or JSON with no way back in. Know which kind of copy you are keeping.

Who should pick which#

• You draft in one app and plan as you go: Campfire. Tags and a timeline in the same project keep planning one click from the scene, and the desktop app works offline.
• You write in Word or Google Docs and the cast keeps growing: Yazar.io. Links, a backlink panel and events on each character’s page answer “where did I mention her?”
• You co-write, or your plot turns on an invented calendar or a map: Campfire, which documents shared editing, a Calendar module and a Maps module.
• You want readers to browse the world: Yazar.io’s wiki is free on both plans. Notes are never included, and the Timeline is off until you turn it on. Campfire fits if the extras should travel inside a book you publish there.
• A series: Yazar.io’s free plan stops at 2 books and 15 editable records per entity type, and Campfire’s at 10 characters, so check which limit you would hit first.

Update, 21 October 2026: Reframed Yazar.io as the world beside the manuscript, rebuilt the comparison table so documented Yazar.io features have their own rows, and corrected the wiki (you can add a password; the Timeline can be published and is off by default; notes stay out), custom sections on Pro, and encryption wording. Campfire’s manuscript, maps, calendars, co-writing and offline desktop stay stated as its strengths. The Pro price is the figure confirmed by the Yazar.io team; the pricing page shows local currency.

For more options, including Obsidian and World Anvil, see the broader tool shortlist. For the method behind the sample, read how to build a timeline that catches contradictions.