# Why your book lives in plain files InkSpine stores your book as a folder of plain Markdown chapters and JSON notes on your computer, so you can read and open your manuscript anywhere. - - Published 29 October 2026 - Updated 29 October 2026 A book takes years. Sometimes a series takes a decade. Over that kind of time, laptops are replaced, operating systems drop old libraries, and software companies change pricing, pivot, or shut down. The quiet risk of writing in a dedicated app has never been that the editor is bad today. It is that ten years from now, when you want to read an early draft or pull a cut chapter into a new novel, your words are locked inside an opaque project bundle that nothing on your new machine knows how to open. When we started building InkSpine, the storage rule came before the interface: the project on disk had to remain readable on its own, without InkSpine installed. Your manuscript is never tracked, and it stays on your computer unless you turn on an optional connected feature. It lives in a normal folder you choose on your own drive, saved as plain Markdown files and human-readable JSON notes that any text editor can open. > A writing tool should earn its place every morning by being a good room to work in, not by holding the keys to the filing cabinet. ## What is actually inside an InkSpine project folder When you create a project or click **Show in file manager** from the Dashboard top bar, Finder or Explorer opens an ordinary directory on your computer. Nothing is tucked inside a hidden application container or a single binary database. ```text my-epic-trilogy/ books/ 01-the-first-book/ manuscript/ 01-prologue.md 02-chapter-one.md front-matter/ dedication.md back-matter/ acknowledgements.md figures/ cover.jpg characters/ arwen.md locations/ rivendell.md lore/ magic-system.md factions/ the-northern-compact.md ideas/ .inkspine/ series.json continuity.json books/ 01-the-first-book/ book.json export-presets.json characters/ arwen.json ``` *An InkSpine project on disk: numbered Markdown chapters for each book, long-form Markdown notes for your worldbuilding, and structured JSON metadata inside .inkspine/.* Each chapter is a numbered `.md` file inside `books//manuscript/`. Front-matter pages such as a dedication or epigraph sit in `front-matter/`, back-matter pages sit in `back-matter/`, and any maps or illustrations you place in the text sit in `figures/`. Long-form notes for your characters, locations, lore, and factions live in their own top-level folders as Markdown files too[^1]. Everything that describes structure rather than prose lives inside `.inkspine/` as indented JSON: `series.json` holds the series name and author, each book's `book.json` holds chapter order, status labels (`planned`, `draft`, `revising`, `final`, `cut`), POV, summaries, and scene-card beats, and each worldbuilding entry's `.json` file stores details such as its aliases, tags, and relationships. Because the prose and the metadata sit side by side in plain text, you never need a special converter to read either one. ## Why plain Markdown is the right floor for a long manuscript Writers sometimes hear "Markdown" and picture raw punctuation cluttering the page. In InkSpine's editor, you write on a warm paper canvas with proper typography, typographic quotes, scene-break ornaments, and real footnotes. You only see the `**` or `*` syntax while your cursor is inside the phrase it formats. Underneath that calm surface, keeping the saved file in plain Markdown solves three practical problems that binary document formats struggle with over the life of a book: 1. **Formatting stays clean across every chapter.** Word processors accumulate invisible style overrides every time you paste a paragraph from an old draft or a notebook. Plain Markdown records what a piece of text *is*—a heading, an italic phrase, a block quote, a footnote (`[^1]`), or a scene break—so the [EPUB, DOCX, and PDF exporters](https://inkspine.app/#features) can style every chapter consistently when the book is ready. 2. **Word-level version comparison is exact.** Because chapters are plain text rather than compressed XML bundles, InkSpine's [History and Compare view](https://inkspine.app/guides/compare-versions-copy-passage) can show exact word additions and deletions across versions and let you copy a single cut paragraph back into your draft. 3. **Search and cross-references are always rebuildable.** InkSpine keeps a fast full-text search index and a cross-link index in a local cache folder so finding a phrase across three books or hovering a character's name is instant[^2]. Those indexes are derived from your files, never the source of truth. If you ever move the folder to a new computer, InkSpine rebuilds the index automatically when you open the project, or on demand from **Preferences → Project → Rebuild indexes**. ## Working well with the rest of your computer Because your chapters are real files in a folder you picked, standard computer tools work the way you expect them to. If you open a chapter in another text editor while the project is open in InkSpine, InkSpine checks the file on disk when you return to the window or switch chapters. When you have no unsaved edits in InkSpine, the chapter reloads on its own and the footer notes `Reloaded: changed by another program`. When you have unsaved typing in InkSpine and the file on disk has also changed, InkSpine never overwrites either side silently: the footer shows `Changed by another program` with two buttons, **Reload** and **Keep mine**, and saves a snapshot to **History** before applying your choice so both versions remain available in **Compare**. > **Backups without a lock-in ceremony** > > Because an InkSpine project is a normal folder, Time Machine, Backblaze, a USB drive, or a cloud folder you manage yourself backs up your manuscript alongside the rest of your documents. When you want a single dated file before a major structural edit, open **Preferences → Project → Backup → Export archive…** to save a portable `.inkspine` file of your whole project (manuscript, worldbuilding, pictures and project settings; saved versions are not included). ## Moving in and moving out A tool that respects plain files should make arriving and leaving equally straightforward. If your draft currently lives in Scrivener or Microsoft Word, you can [move your book from Scrivener](https://inkspine.app/guides/move-from-scrivener) or [bring a Word manuscript into InkSpine](https://inkspine.app/guides/import-word-manuscript) and turn heading styles directly into numbered Markdown chapters. And if you ever want to hand a raw copy of your manuscript to another program, the files are already waiting in `manuscript/`—or you can use **Quick export…** in the Export screen to write the whole book as Markdown (a `.zip` of your chapters) or HTML on every plan, including [InkSpine Free](https://inkspine.app/faq). [^1]: In Memoir and Non-fiction projects, the app calls this section **Knowledge** (`People`, `Places`, `Themes & periods` or `Works & topics`, and `Threads` or `Organisations`), while the underlying folders on disk remain the same plain `.md` and `.json` files. [^2]: The derived search and cross-link data lives in `.writing-app/` inside the project folder and is rebuilt from your files, so it never holds the only copy of a word of your manuscript or worldbuilding notes. You never need to delete anything there: **Rebuild indexes** does the job for you. ## Questions ### Where does InkSpine save my book on disk? Where you tell it to. You pick a folder when you create or import a project, and every chapter is saved as a plain Markdown (.md) file inside that folder. ### Can I edit a chapter in another text editor while InkSpine is open? Yes. When you return to the InkSpine window or switch chapters, InkSpine checks the file on disk. If you have no unsaved edits in the app, it reloads automatically; if both changed, the footer shows Reload and Keep mine and saves a version to History first. ### What happens if I stop using InkSpine ten years from now? Your manuscript is still a folder of numbered Markdown files and JSON notes on your computer. Any text editor, Markdown app, or command-line tool can open it without converting or exporting first. ## Related reading - [Move your book from Scrivener](https://inkspine.app/guides/move-from-scrivener): Compile your Scrivener draft to a Word (.docx) file, run InkSpine's Import wizard to split chapters by heading, and bring your notes into Worldbuilding. - [Bring a Word manuscript into InkSpine](https://inkspine.app/guides/import-word-manuscript): Click Import on the Welcome screen, pick your .docx file, choose which Word heading level marks chapters, and review the chapter list before importing. - [Compare an earlier version and copy back a passage](https://inkspine.app/guides/compare-versions-copy-passage): Open the inspector's History tab (⌥⌘5 / Ctrl+Alt+5), click a saved version to open Compare, and click ⤴ copy beside any passage to bring it back.