How Chronicler Keeps Your Worldbuilding Data Private and Offline

Chronicler stores everything on your own machine as plain-text Markdown files. There is no account, no server, and no cloud sync in the loop, so your characters, places, and factions never leave your computer unless you move the files yourself. This matters most if you write on a laptop you control, want your notes readable in any text editor decades from now, or are migrating away from a subscription wiki that could raise prices or shut down.

What "offline and local" actually means here

When you create a page in Chronicler, the app writes it to a folder on your disk as a .md file. The app is a reader and editor layered on top of that folder, not a database you can only open through the app.

That single design choice drives most of the privacy and ownership claims:

• No servers involved. Nothing is transmitted to a Chronicler backend because there isn't one in the data path. There's no login step that hands your notes to a third party.
• No subscription gate. The site describes Chronicler as free, with no subscription and no cloud. Because the files live locally, there's no monthly bill tied to keeping access to your own writing.
• No data lock-in. Markdown is a plain, widely supported format. If you stop using Chronicler, your files still open in Obsidian, VS Code, or any text editor.

Why local storage changes your risk profile

Cloud-based worldbuilding platforms keep your lore on their servers. That model creates three recurring problems the site calls out directly: server outages, monthly bills, and the risk of losing access to years of writing if a service changes terms or shuts down.

Local storage removes those specific failure modes:

The trade-off is that you own the backup problem. There's no vendor syncing your work to redundant servers, so if your drive fails and you have no copy, the data is gone. A local-first tool shifts responsibility for backups onto you.

How to verify your data is really local

You don't have to take the claim on faith. After installing Chronicler on Windows, macOS, or Linux:

1. Create a test page with a character or location.
2. Find the folder you pointed Chronicler at (or the default vault location).
3. Open that folder in your file manager. You should see a .md file matching the page you made.
4. Open the file in a plain text editor. Your content should be readable as Markdown, not garbled binary.

If step 4 works, your world is genuinely portable and not trapped in a proprietary store.

Moving in and out without losing work

Because the format is open, migration runs both directions:

• Coming from elsewhere: Chronicler has built-in importers for Word, Google Docs, and Fandom/MediaWiki sites, and it works natively with Obsidian vaults. So an existing Obsidian folder can be opened rather than rebuilt.
• Leaving: Since pages are Markdown, you can point another Markdown-based tool at the same folder. The site frames this as the opposite of being "held hostage" by a subscription.

Who this fits, and who it doesn't

Local-only storage suits you if you want full ownership, work offline, dislike recurring fees, or plan to keep your notes for years. It fits less well if you rely on automatic multi-device sync, real-time collaboration, or a hosted backup you never think about — those aren't part of the offline model described here, so you'd need to add your own sync or backup layer.

One practical note: the site states no subscription and no cloud, but it doesn't describe a paid tier or login requirement either way. Treat "free" as the stated positioning for the tool as described, and confirm current terms on the site before committing a large existing world to it.