IRONBIND Home

Iron Bind v3.0.0 · Skybound Edition · Early Access

Help

The same guide as ❓ Help in the app: the first scene step by step, then every tool by task. Questions about Early Access first; the support form at the end.

Questions

Early Access, the price, your devices and your data.

What does Early Access mean?

Iron Bind 3.0.0, the Skybound Edition, is complete enough for real work and still being tested and improved: the writing tools and sync have been audited and run on real devices for weeks, while the worldbuilding and tabletop tools are still being audited. The EA tag beside the app's name marks it. Features may change, be added or be removed before the full release. Keep backups of your work, and send a report when something is wrong.

Will the price go up when Early Access ends?

No. The Archmage License is sold now at its full price, CA$29.99 once, and that price won't go up when Early Access ends. A license bought today carries on unchanged after it, on up to five devices.

I was an Insider Beta tester. Where is my license?

Whitelisted testers of the closed Insider Beta that came before Early Access receive a complimentary lifetime Archmage License: a key, emailed before Early Access opened. Enter it on the license page (⚙️ Bindings, then the license's mark in its top right corner). If yours hasn't arrived, write to support@ironbind.app from the address you signed up with. Testing during Early Access earns no further keys.

Which devices does it run on?

Android phones and tablets (Android 8 and later) from Google Play, and Windows 10 and 11 from the Microsoft Store. One Archmage key works on up to five devices of either kind. There is no Mac, iPhone or iPad app yet; a Mac is needed to build one.

Is there a web version?

Not any more. The browser build of the closed beta came down when Early Access opened. If you wrote in it, export a backup file from its Library (💾 Backup on the project's card) and import it into the Android or Windows app: Library → Import → a backup file.

Where is my writing kept? Do you have a copy?

On your device, in a database file with a second copy beside it, and nowhere else: there is no account and no server of ours that holds your projects. Backups and sync go to your own Google Drive or OneDrive, only if you turn them on. Back up often: we can't recover work from a lost or wiped device. See the Privacy Policy.

Does the AI write for me?

No, and it never will. Lore Scan is optional, off until you add your own Google Gemini key, and extractive only: it lists the names you haven't filed yet and notes the facts you wrote, with the scene each came from. The scenes it reads are sent to Google under your key's terms.

Can I get a refund?

Purchases are made through the store you installed Iron Bind from, under that store's refund policy: Google Play's or the Microsoft Store's. A refunded purchase ends the license on each device the next time it checks online.

Something is wrong. How do I reach you?

In the app, Send a report (in Help, at the foot of Bindings, or on the error screen) sends the details with the app version and the page you were on; it waits for a connection if you're offline. Or use the support form below, or email support@ironbind.app.

Start Here

Write your first scene in six steps

Write your first scene

Everything else can wait. This is all you need to start.

  1. 1Make a projectIn the Library, tap ✨ Begin Your First Project (or the ✨ card), give it a name and pick The Novelist. Leave Starter Content on: the project starts with Chapter One and Scene One inside it, ready to type in.
  2. 2Open 🪶 WritingIt's in the sidebar. The list you see is the binder: the pieces of your book, in reading order.
  3. 3Add a chapterTap + Chapter, type its title and tap Add. (Starter Content already made one.)
  4. 4Add a scene to itTap ⋯ on the chapter's row, then + Add scene. Give it a title, or leave it as Untitled Scene.
  5. 5Tap the scene and writeThe page opens. Your words are saved a moment after you stop typing, and again when you leave.
  6. 6Keep going‹ and › at the ends of the status bar open the scene before or after. 🗂️ in the header brings back the binder, where you add the next scene or chapter the same way.

Want to look around first? 🔍 Try an Example in the Library adds a finished novel, Wuthering Heights, as your own copy to explore.

How your book is built

📕Part— optional: Part One, Book II
◈Chapter— a folder of scenes
◇Scene— where you write
📝Note— private, never printed
◇Scene
◈Chapter
  • Scenes are the only place you type. Every word of your book is in a scene.
  • Chapters are folders of scenes. A chapter has no text of its own: its title becomes the chapter heading when you export. Tap it in the binder to show its scenes, or ⋯ → 📜 Scroll to read them all as one page.
  • Parts are optional folders of chapters (Part One, Book II). In the book, each gets a title page.
  • Notes sit under a scene, for you alone: they're never exported, counted as words or sent to the Lore Scan.
  • Parts hold chapters, chapters hold scenes, scenes hold notes. Any of them can also sit on its own at the top of the binder.
  • No chapters is fine: for a short story, add scenes at the top. Each one exports as a chapter of its own.
  • A scene's status, synopsis, POV character, tags and word target are in its ⋯ → ✎ Details.
  • ⋯ → ⇄ Move to… only offers places that can hold the draft, and every move shows Undo.
Getting aroundThe sidebar, the menu on a phone, settings, and the Back button.
  • The sidebar's rail holds the 🗃️ Library (your projects; a line sets it apart) and your project's pages: 📒 Ledger (its home page), 🪶 Writing, 📚 Archive (the Codex, lenses and the Vault), 🌍 Realm (the Atlas and Chronos), 🎭 Narrative, 🎲 Tabletop and ⚒️ Forge. At its foot: the ☁ sync, ❓ Help and ⚙️ Bindings, the settings.
  • Open the menu to see every page's name and what it holds. Your license is in ⚙️ Bindings: its mark in the top right corner opens it.
  • Tap the Iron Bind mark at the top of the rail (on a phone, or swipe right on the rail) to open the menu; tap the mark again, or ✕, to close it. On a phone it also closes when you pick a page, or with a swipe left.
  • Your path (Novelist, Game Master…) only decides which tools a project shows. Turn any of them on or off in ⚙️ Bindings → Tools.
  • 🗃️ Library at the top of the open menu closes the project. Iron Bind reopens the project you had open when you come back.
  • The Library shows your projects as Cards or, with Shelf, as books side by side on a shelf, each in its project's colour, thicker the more it holds, with its whole title up the spine (smaller when it's long). Tap a spine to pull the book out and see its card. This device remembers which you chose.
  • Android's Back closes what you opened last (a dialog, a menu, a panel, the sidebar), then goes back through the project's pages, then to the Library; from the Library it closes the app.
More detail
  • ⚙️ Bindings lists its sections: tap one to open it, and ‹ Bindings (or Back) to return. Search settings at the top finds a setting by its name and opens its section at it.
  • Settings belong to each project. Bindings names the project they belong to and marks the few every project shares (All projects). In the Appearance, Writing and Goals sections, Use for new projects makes those settings the starting point of every new project.
  • Before your first project, or with none open, the ⚙️ in the Library's top right corner (or Bindings at its foot) opens what's yours and the device's: your author profile, your cloud accounts (with ⬇ Restore of a backup), Lore Scan's key, and the Appearance, Writing and Goals settings new projects start with. The Library takes their colours too.
  • Don't like scrollbars? ⚙️ Bindings → Appearance → Show Scrollbars hides them on this device; the wheel, trackpad, touch and keys still scroll.
  • A tool that's on is always in the sidebar or on its hub page (the Atlas and Chronos are on the Realm page, Plot Weaver and the Arc Visualizer on the Narrative page).
  • Iron Bind works without a network: your work is on your device, and only the things you switch on (a cloud account, Lore Scan) go online.
The Ledger, your home pageToday's words, your streak, the manuscript at a glance, and the tools.
  • Today shows the words you've written today against your daily goal, your streak and the last seven days. Tap it for each day's count.
  • The Manuscript card shows your words and drafts. Deep Analytics › on it opens readability scores, passive voice, adverbs, dialogue and your most-used words.
  • Quick Scribe starts a new Codex entry of the kind you tap.
  • Tools at the foot of the Ledger holds Lore Scan, Compile (the exports), the importer, the Codex Omnibus and the Campaign Tools. Tap it to open them.
More detail
  • On a phone the Ledger is one column; on a tablet the cards sit in pairs, and on a wider screen three across.
  • The Chapter Targets card (shown when chapters have targets) says how many are reached and which chapter to write next; tap it for the whole list.
  • A tip sits under the project's name; ✕ hides it until you next open the app, and ⚙️ Bindings → Appearance → Ledger Tips turns tips off.
  • Folded, Tools says when names are waiting or a scan has paused, and it opens by itself while an export, import or scan is running. It stays open or folded as you left it.
  • Deep Analytics: the Grade Level and Reading Ease are the standard Flesch-Kincaid and Flesch formulas, the same as other tools give. Beside the grade is the range books of your Writing Genre (⚙️ Bindings → Project) usually fall in: a rough guide, not a target. On the Words tab, Hide character names leaves your characters, NPCs and titles like Mr and Miss out of both word lists. Overused words are the ones you use 1.5 times or more in every 1,000 words.
Lore Scan (optional AI)Finds the names in your manuscript that aren't in your Codex yet, using your own Gemini key.

How to

  1. 1Get a Gemini API key from Google AI Studio and add it in ⚙️ Bindings → Tools → The Oracle.
  2. 2On the Ledger, open Tools → Lore Scan and start a scan.
  3. 3Go through the names it finds: add the ones you want to the Codex, dismiss the rest.

Good to know

  • It only extracts what your text says about each name; it never makes anything up.
  • The text it reads goes to Google's Gemini API with your key, never to us. For an entry, only the scenes that name it are sent.
  • To update an entry later, open it in the Codex and tap ✨ Extract Lore under Lore Scan Notes.
More detail
  • Google handles the text under the Gemini API terms for your key: data sent with a paid-tier key isn't used to train Google's models, while free-tier use may be used to improve Google's products.
  • The names found wait in Lore Scan's list, on this device, until you add or dismiss them, even after the app closes; a new scan adds its names to the list.
  • A long manuscript is read a part at a time, with a pause between parts. If a scan stops (a rate limit, no connection), Continue the Scan reads on from where it stopped.
  • What you write in an entry's Official Record is yours; Lore Scan writes only its own notes, and asks before rewriting notes you've changed.
Try an ExampleA finished novel, set up with its Codex, map, plot threads and book, to explore.
  • 🔍 Try an Example in the Library adds Emily Brontë's Wuthering Heights as your own copy, marked Example on its card. Change anything.
  • It never changes your author profile, your words today or your streak, doesn't count toward the free tier and doesn't ask to be backed up.
  • Opening it again goes to your copy; Start Over moves that copy to Recovered Chronicles and adds a fresh one. Delete it like any project when you're done.

Writing

The editor, binder, comments, targets

The binder: your book's piecesAdd, open, move and delete parts, chapters, scenes and notes.

How to

  1. 1Open 🪶 Writing: the list you see is the binder. In a scene, 🗂️ in the header shows it again.
  2. 2Add at the top with + Part, + Chapter or + Scene. To add inside a row, tap its ⋯ → + Add chapter (in a part), + Add scene (in a chapter) or + Add note (on a scene).
  3. 3Tap a scene to write in it. Tap a part or chapter to show or hide what's inside.
  4. 4To move a row, use its ⋯: ↑ Move up, ↓ Move down, → Into the row above, ← Out of the one holding it, or ⇄ Move to… for anywhere else.

Good to know

  • Every row's actions are behind its ⋯: ✎ Details, the moves, + Add, 📜 Scroll, 📤 Send… and ✕ Delete.
  • Every move, and every delete, shows Undo for a few seconds. A deleted draft goes to 🗑️ Trash, where it stays until you empty the trash.
  • Find a scene… at the top narrows the binder to titles and synopses that hold what you type; Filter narrows it to a status, tags, POV characters or what needs attention.
  • ‹ and › at the ends of the status bar open the scene before or after the one you're in.
More detail
  • → Into and ← Out of show only where the structure allows: parts hold chapters, chapters hold scenes, scenes hold notes. ⇄ Move to… takes a draft to the end of any part or chapter that can hold it.
  • The Filter's attention choices are open comments, a word target not reached and no synopsis. Any choice in a group counts, and every group together; the parts and chapters that hold the matches stay shown.
  • The binder opens at the scene you're writing.
  • On a wide screen (a PC or a tablet held sideways), Writing's list has a desk beside it: Continue writing opens the scene you changed last at its end, with today's words and the sprint, your scenes by status and the open comments (tap one to go to its passage).
  • The type of a new draft can be changed in the row that asks for its title, before you tap Add.
Corkboard, Outline and ScrollSee your book as index cards, as a table, or as one long page.
  • In the binder, ≡ is the list, ⊞ the corkboard (a card per scene, with its synopsis) and ▤ the Outline (a row per draft, with the columns you choose).
  • ⋯ → 📜 Scroll on a part or chapter opens all its scenes on one continuous page. You can write in any of them there.
  • On the corkboard, drag a card onto another to put it before that one, or onto a chapter heading to put it at the end of that chapter. On a touch screen, hold the card still first.
More detail
  • A card's synopsis is set in the scene's details (⋯ → Details, or ✎ on a card). A line above a card, or an outline round a heading, shows where a dragged card will land. With a keyboard, Tab reaches each card, Enter opens it and Alt+↑ or Alt+↓ moves it.
  • The Outline's Columns picks what shows: the synopsis, status, POV, words and target, tags, comments, your own fields, and from Iron Bind's own tools the plot threads tied to each scene, the arc values set there, the Codex entries it names and when it happens in the story (its Place in World date).
  • Tap an Outline header to sort by it (again for the other way, a third time for the book's order); sorted, the scenes are listed on their own. Tap a cell to change the synopsis, status, POV, target or one of your fields there and then. Drag a row by its ⋮⋮ (in the book's order) onto another row to put it before that one, or onto a chapter to put it inside.
  • Rows colours each Outline row by its status or by a choice or checkbox field. On a phone each draft is a card with the chosen columns as lines, and ✎ opens its details. The columns, the sort, the colours and the widths are kept on this device for each project.
  • Notes counts the notes under each scene; tap it to open the first. With a mouse, drag a header's right edge to make its column wider or narrower; double-click the edge, or Columns → Reset Widths, to put it back.
  • A part's Scroll names each of its chapters; tap a chapter's name to open its own Scroll. Scroll sections undo with the keys.
Writing in a sceneSaving, undo, paste, formatting, and the modes that help you focus.
  • It saves by itself a moment after you stop typing, and when you leave the scene or the app.
  • Undo and redo: ↶ and ↷ at the start of the toolbar, or Ctrl+Z and Ctrl+Y.
  • The toolbar has bold, italic and the rest. Paste keeps italics, bold, underline and strikethrough from Word or Google Docs; fonts and colours are left behind.
  • 🔓 Focus mode in the header hides the sidebar so the page has the screen. On a phone, the header's ⋯ holds Focus, Scry, Add to Codex, Character arcs and the writing sprint.
  • ⚙️ Bindings → Writing has Typewriter Mode (the line you type stays at the middle), Focus Fade (dims every paragraph but yours) and Paragraph Style (space between paragraphs, or indents).
More detail
  • Saving: turn Auto-save off in ⚙️ Bindings → Writing to save only with 💾 or Ctrl+S (leaving still saves). 💾 saves the text; it doesn't keep a version (Save Snapshot Now does).
  • Undo: a pause of a second or more starts a new step, and a paste, a formatting change or a smart correction (a capital, a curly quote) is a step of its own. Your keyboard's own undo works too.
  • Paste as plain text (Ctrl+Shift+V) brings the words alone.
  • Typewriter Mode keeps the line you're typing at the middle of the editor, from the first line to the last; scroll back to read and it stays where you put it. Focus Fade dims while you write; a draft you open or read back shows in full.
  • Volume buttons (Android): ⚙️ Bindings → Writing → Volume Buttons makes them page keys on this phone: scroll the page, move the cursor a line, go to the scene before or after, or undo (down) and redo (up). Up is back, down is forward; outside a scene they scroll. Off, the default, they change the volume.
  • Words today: only what you write counts. An imported manuscript, a chapter moved to or from the trash, a Revert to an older version, a paste of 50 words or more, and the words a project already has the first day you open it don't.
Comments and footnotesPrivate notes on a passage, and footnotes that print in the book.

How to

  1. 1A comment: select some words and tap 💬 in the header (on a phone, ⋯ → Comment on selection), then write it.
  2. 2A footnote: select a word or a passage (or put the caret just after a word) and tap xⁿ in the toolbar, then write it.
  3. 3Tap a marked passage later to read, change, resolve or delete what's on it.

Good to know

  • Comments are for you: never exported, counted as words or sent to the AI. Footnotes are printed.
  • Both move with the text as you write around them.
  • The Reference panel's 💬 tab lists this scene's comments or the whole book's, and the binder and corkboard show 💬 counts.
More detail
  • If you delete a comment's whole passage the comment stays, marked "passage deleted". The Scroll and lens views mark comments too, section by section.
  • A footnote's passage is underlined with dots. Each compile setup says where footnotes print (Footnotes in its editor): at the foot of the page in the PDFs, with Word's and OpenDocument's own footnotes in the DOCX and ODT; after each chapter; after the story, under "Notes"; or left out. The EPUBs and Print, which have no pages of their own, put them after each chapter unless the setup says after the story, linked both ways. Notes are numbered again in each chapter.
  • In a Scroll or a lens view, tap into a section and use xⁿ or 💬 in the header (on a phone, ⋯).
Paragraph stylesBlock quotes, letters, poems, epigraphs, centred lines and small caps.

How to

  1. 1Put the caret in a paragraph (or select several).
  2. 2Tap in the toolbar and pick a style; Normal puts it back.

Good to know

  • The styles are Block Quote, Letter, Poem, Epigraph, Centered and Small Caps. With a keyboard, Ctrl+Shift+1 to 6 set them in that order and Ctrl+Shift+0 is Normal, in a scene and in a Scroll's or lens's sections.
  • Every export sets them: Word and OpenDocument as named styles you can change there, the PDFs and EPUBs with the book's own indents, italics and capitals. A poem's lines sit close together.
VersionsOlder copies of a scene, kept for you, to compare or go back to.

How to

  1. 1Open 🕘 History in the binder.
  2. 2Pick a version to read it, Compare it with now, or Revert to it.

Good to know

  • A version is saved when a scene grows or shrinks by 100 words, and every 15 minutes while you rework it. Save Snapshot Now keeps one whenever you like.
  • Versions you saved, and the ones taken before a Revert or a Replace, are never deleted.
More detail
  • Older automatic versions are thinned out to one a day, then one a week. A version the same as the last one isn't kept twice.
  • Compare marks what changed since, word by word: a line you edited shows once, the words taken out struck through and the words written since marked.
Goals, word targets and sprintsA daily goal, a target for each chapter, and timed writing sprints.

How to

  1. 1A daily goal: set Daily Word Goal in ⚙️ Bindings → Goals. The status bar shows "Today 120/500" as you write.
  2. 2A chapter or scene target: ⋯ → ✎ Details on its row in the binder, or one Chapter Target for every chapter in ⚙️ Bindings → Goals.
  3. 3A sprint: tap ⏱ in the header (on a phone, ⋯) or in the binder. Its length is set in ⚙️ Bindings → Goals.

Good to know

  • A chapter's words are every scene inside it; notes never count. Progress shows in the binder, on the corkboard, on the status bar ("Ch 2,410/3,000") and on the Ledger.
  • A sprint keeps running while you visit other pages and tells you how many words you wrote when it ends. Tap Stop to end it early.
More detail
  • A chapter can set its own target, or No Target, over the Chapter Target. The Ledger also says when you'll finish at your pace of the last 14 days.
  • The Ledger's Chapter Targets card shows how many are reached and the chapter to write next; tap it for the whole list (Not reached shows the ones still short), and tap a chapter to open it as a Scroll.
Stages and your own fieldsEach scene's stage (Draft, Revision…), and fields of your own for every scene.
  • Set a scene's stage in its ⋯ → ✎ Details or in the Outline.
  • ⚙️ Bindings → Writing → Stages renames, recolours and reorders Draft, Revision, Polish and Final, and adds stages of your own (With Beta Readers, With Editor).
  • Scene Fields in the same place adds fields of your own to every scene: text, a choice list, a checkbox, a number or a date.
More detail
  • The binder, corkboard, filter, heat map and compile setups all use the stages.
  • Fill your fields in a scene's details or in the Outline; a choice or ticked checkbox shows on its corkboard card, and the binder's Filter can narrow to them. Both are the project's, so they travel in its backups and sync, and Use for New Projects carries them.
Add to the Codex while you writeTurn a name you just typed into a character, place or item.

How to

  1. 1Select the name in your text.
  2. 2Tap 📖 in the editor's header (on a phone, ⋯ → Add selection to Codex).
  3. 3Pick its category, and a template if you like, add a note in Official Record, and save.

Good to know

  • The name links in your text straight away.
  • If the Codex already has that name, it offers to open that entry instead, or to add the name as an alias of an entry whose name holds it.
Linked names and the Reference panelCodex names link themselves as you type; tap one to read its entry beside your text.

How to

  1. 1Turn on Scry mode (🔮 in the editor's header; on a phone, ⋯ → Scry mode).
  2. 2Tap a linked name: its Codex entry opens in the Reference panel, where you can read and change it without leaving the scene.

Good to know

  • Names and aliases of your Codex entries link in any language (Éowyn, Zoë), never inside a longer word. Session logs, random tables and files aren't linked.
  • If a name is also an everyday word (Will, Hope), turn on Match Capitals When Linking under its aliases in the Codex: it then links only when written with its capitals.
  • 📇 in the header opens the Reference panel with its Codex, Map and Plot tabs. On a tablet or PC it sits beside your text; on a phone it slides up.
More detail
  • If several entries share the name you tapped, you pick one.
The second paneA second scene, a note, a version or the Codex beside the one you write in.

How to

  1. 1On a tablet or a PC, open the pane beside your text (📇, or Ctrl+\).
  2. 2Use its Show strip to pick what's in it.

Good to know

  • It can show a scene or a note (written in there, with its own save and undo), a chapter's Scroll, a plot thread's knots in the book's order, or a version of the open scene, read-only, with what changed since marked.
  • Or it follows the scene you're in: its notes (+ Add a note), its previous version, or the Codex entries the paragraph at the caret names.
  • On a phone, ⋯ → Second pane puts it a swipe away beside the text, with a strip at the top saying which is which.
More detail
  • It opens on what it showed last (the Reference card the first time). On a tablet held upright it sits below the text.
Bring in a Word or LibreOffice fileImport a manuscript from a .docx or .odt file, split into chapters and scenes for you.

How to

  1. 1On the Ledger, open Tools → Local Importer.
  2. 2Tap Upload .DOCX (Word) or Upload .ODT (LibreOffice) and choose the file.
  3. 3Check the chapters it found: rename, merge or leave out any of them with their ⋯.
  4. 4Tap Import Manuscript. Nothing is stored before you do.

Good to know

  • Headings start chapters, and so do lines like Chapter 1 or Prologue; Part One lines start parts.
  • ***, # or three empty lines break a scene.
  • Italics, bold, underline, strikethrough and centred lines come with the text. Imported words don't count toward today's words.
More detail
  • Chapters: CHAPTER THREE: Glass starts one too, while a sentence that begins with the word doesn't. In a document without headings, a short title in capitals on its own, or a centred title after a page break, starts one. A short centred line straight after a chapter's title is its subtitle.
  • Parts: headings above the chapters that read Part One, Book II…, or such lines in a document without headings. A lone heading above everything else is the book's title.
  • Scenes: * * * and ~~~ break a scene too, and a heading below the chapters starts a scene with that title.
  • Front Matter: text before the first chapter (a title page, a dedication) comes in as a chapter called Front Matter, for you to keep or leave out. Iron Bind's own exports come back without their title page.
  • Markers: if your chapters or scenes start with a word of your own (Log Entry), type it as the custom marker; it counts on short lines only.
  • The review: Not a chapter puts a title that was really a line of text back into the chapter before. When the document has headings at several levels, Chapters are picks the level that holds the chapters.
  • A line break within a paragraph (Shift+Enter) becomes a new paragraph.
Bring in a Scrivener projectA Scrivener 3 or 2 project comes in whole, with its research, notes and snapshots.

How to

  1. 1Close the project in Scrivener.
  2. 2In the Library, tap 📥 Import → Scrivener Project (under your projects) (or Start from a Scrivener Project in the new-project form). To add it to the open project instead, use the Ledger's Tools → Local Importer → Scrivener Project.
  3. 3Choose its .scriv folder, or a zip of the folder (on Android, the only way): on Windows right-click it → Send to → Compressed (zipped) folder, on a Mac Control-click it → Compress.
  4. 4Check what it found, choose what each research folder becomes, and import.

Good to know

  • Your Scrivener project is only read, never changed, and nothing is added until you've seen what it holds.
  • Folders of folders become parts, other folders chapters, texts scenes. Research becomes Codex entries.
  • Into an open project, it comes in after the last part or chapter.
More detail
  • The manuscript: a folder named like a part (Act, Part, Book, Volume) is a part even when empty. Texts inside a text are the scenes after it; folders deeper than a chapter are flattened into it; a folder's own text is the first scene of its chapter. The trash is left out. Only scenes hold text: a chapter is a folder, so an empty one is ready for scenes.
  • An outline: a research folder named Outline, Storyboard or Beat Sheet (as in a Save the Cat template) can come into the manuscript instead: tick Bring … into the manuscript. Each beat is a chapter with its synopsis, its cards are scenes to write in ("Scene 1", "Scene 2" when untitled), and a beat with no cards gets one. When the manuscript has acts (its parts), you pick where each act starts and every beat goes into its act, in order (Save the Cat's own breaks are chosen for you: Act II starts after Break Into 2, Act III after Break Into 3); a beat holding folders goes in as its chapters. With no acts, or with the acts switch off, they come in after the manuscript. Left off, its documents come in as research entries.
  • What each document keeps: its text with bold, italics, underline, strikethrough and centred lines; its lists with their bullets and numbers; a table's rows as lines, the cells parted by " | "; a web link's address in parentheses after the words it was on; its synopsis as the Synopsis; its document notes as a note under it, with its custom metadata as "Field: value" lines and its links to other documents or web pages listed after them; its comments and footnotes on the same words; Scrivener 3's heading styles as headings; its snapshots as saved versions; its target as its word target; its status by name (To Do and First Draft are Draft, Revised Draft Revision, Final Draft Polish, Done Final). A picture pasted into the text goes to the Vault as a relic, and a "[Picture: its name]" line stands where it was. Documents with Include in Compile off are left out of every compile setup. Placeholders such as the project's title, author and year are filled in; word counts and page breaks are taken out.
  • Research: each folder outside the manuscript (Characters, Places, Research…) is a choice: its texts become Codex entries of the category you pick, or are left out (Template Sheets are, unless you choose otherwise). An entry keeps the document's text, synopsis, notes and comments. The Template Sheets can become Codex templates instead (Make the sheets Codex templates), each field with its prompt. An empty card with no title isn't kept. Pictures and PDFs go to the Vault as relics.
  • Labels become tags in their colours, or, when they name characters, each scene's POV Character. Keywords become tags on the documents that carry them, and each of your collections a tag of its name on the documents in it (so a lens on the tag, 📚 Archive → Lenses, shows the collection). Into an open project, tags of the same name are matched.
  • A new project takes Scrivener's project title as its name and its targets as its manuscript and daily goals, the author fills an author profile still unset, and Scrivener's writing history (the last 90 days) becomes its words by day. Imported words don't count as written today.

Your World

Codex, Atlas, Chronos, Grimoire

The CodexYour world bible: characters, places, items, events and spells.

How to

  1. 1Open 📚 Archive → Codex and tap New Entry, or add one from your text with 📖 while you write.
  2. 2Pick its category and, if you like, a template.
  3. 3Fill in its name, aliases (other names it goes by) and whatever you know.

Good to know

  • Connections link entries ("Father of", "Sworn Shield to"): type the role, then the word that joins it to the other entry. 🕸️ Graph draws them all.
  • Appears In, at the foot of an entry, lists the scenes that name it. Tap one to open it.
  • Portraits, tags and templates are in the entry's editor. Save as Template keeps an entry's fields, empty, for the next one.
  • 📥 From Another Book (at the top of the Codex) brings copies of another project's entries into this one, so a sequel starts with the first book's cast. Pick the book and a category and tick the entries.
More detail
  • Connections: any word fits ("beneath", "hidden in"), or none; the list under the word offers the ones this project already uses, then the common ones. Tap a connection to change its role, word or inverse.
  • The Graph (the third view button, beside ▦ and ☰ next to the search) draws each entry in its category's shape and colour (set in ⚙️ Lore Structure) with its sigil, an arrow from each relationship's source to its target, and its name when you zoom in. Tap an entry to open it; Entries without connections shows the rest. The 🎭 Narrative page's Relationships card opens it too.
  • Appears In finds the entry by its name or an alias, as the editor links them, with the words around each mention and how many times, and the scenes told from its point of view (marked POV). It's folded to a count until you tap Show, then lists 10 scenes at a time. Sessions, tables and files have none, as they're never linked.
  • Templates: the D&D 5e Player, Pathfinder 2e Character and TTRPG Monster templates set up an entry's tabletop sheet. Save as Template asks for a name and keeps the entry's sheet blocks too, a finished stat block included (without its damage or links to other entries).
  • From Another Book: the entries are copied, so changing one book's copy leaves the other's as it was. Their connections and tags come with them when both ends come; where they were on the other book's maps, and the scene they were linked to, stay behind; their timeline dates come when the two books share a calendar. Sessions aren't offered. An entry whose name is already here is marked.
  • Portraits: a large picture is made smaller, to 1,024 px on its longest side; without one, the entry's sigil shows.
  • Tags: colour-coded labels for entries and drafts. Add them to an entry in its editor, to a draft in the binder, to a session or a relic, and search by them with lenses (📚 Archive → Lenses). + New tag beside each list makes one on the spot; ⚙️ Bindings → Story & World renames, recolours and deletes them.
  • Tabletop sheets (characters and NPCs, with the Tabletop tools on): a Health Tracker (current, max and temp HP; D&D characters also get death saves, hit dice and 🌙 Long Rest), Ability Scores (in Pathfinder, Perception and the saves show their rank; tap one to raise it), a Spell Arsenal (slot levels with pips and known spells from your Grimoire, your class's first) and a Weapon Arsenal (in D&D 5e it works out your Armour Class from your armour, DEX and shield; an AC typed in Ability Scores wins). The sheet follows your project's Rules System (⚙️ Bindings → Project). A monster's level and proficiency come from the CR in its Monster block. Removing a block you've filled in asks first, and so does closing an entry with unsaved changes.
The Archive pageYour world at a glance, your lenses and the Vault: the way into the Codex.
  • Counts of your characters and locations, then the two categories you added to last. Tap one to open that list in the Codex.
  • Recent Entries: the six entries you changed last. Tap one to open it.
  • Grimoire: your number of spells and how many belong to each school (when the Grimoire is on).
  • Lenses (saved searches of your manuscript) and The Vault (your links, photos and files) each have a card with its count and the newest few; Open Lenses → or Open Vault → opens the page, and ‹ Archive brings you back.
Codex PDFsPrint your lore: one-page dossiers, a whole world bible, or tabletop cards.
  • Dossiers: a reference page for one entry. The Omnibus: a world bible of every entry, with a contents list. Tabletop Cards: items and NPCs as 3×3 card sheets, ready to print.
  • Two styles: clean Standard and ornate Arcanist.
More detail
  • A spell prints with its school, cost, range, duration and system. A PDF that includes spells imported from the SRD or Pathfinder sets ends with the notices their licenses ask for; keep them with it when you share it.
The Atlas: your mapsUpload a map, then pin places, draw regions and roads, and measure distances.

How to

  1. 1Open 🌍 Realm → Atlas and add a map: give it a name and an image.
  2. 2Tap 📍 and tap the map to drop a pin. Each pin is a Codex entry.
  3. 3To measure, tap 📐, draw a line across something you know the length of, and type it. 📏 then measures anything.

Good to know

  • Zones are areas you draw (borders, forests, dangerous ground), and can be linked to a location in the Codex.
  • Routes are roads between places, with travel times once the map is measured.
  • A pin can lead to a more detailed map (Linked Sub-Map in its editor); double-tap it to go in, and the breadcrumb at the top leads back.
  • The Atlas opens on the map you used last.
More detail
  • Pins: 📖 Open in Codex in the pin's editor opens its entry.
  • Zones: ✏️ Edit Shape in a zone's editor changes its outline: drag a point, tap an edge to add one, tap a point to remove it. A map can sit inside a zone (Parent Zone in ✏️ Map Properties); Open … in the zone's editor goes in.
  • Routes: terrain bands slow travel, and journey nodes open when a traveller passes them. ✏️ Edit Waypoints: drag a point, tap the line to add one, select one to remove it.
  • Itinerary Builder: track a character's or item's movement across maps over time; its stops animate during Time Scry. Stops are set by date in GM and Worldbuilder modes and by chapter in Novelist mode, and a stop set by chapter stays on that chapter when you reorder the book. While a character is at a stop on another map, it shows there as a faded token, and the pin that leads to that map counts it; tap the token to see who it is and where. While you edit a pin, its journey on this map is drawn, numbered as the itinerary lists it, with each trip's length.
  • Chronicle Pins: session-log markers dropped on the map for tabletop play.
  • Scale: once measured, routes and journeys get their lengths and travel times, and a scale bar in the map's top corner follows the zoom. A map keeps the unit it was measured in, so switching ⚙️ Bindings → Backup & Sync → Distance Units converts every distance (a 100-mile line reads about 161 km) and leaves travel times and tactical grids as they were.
Time Scry: the map through timeMove a slider and watch characters travel and borders change.

How to

  1. 1In the Atlas, turn on Time Scry and pick its mode.
  2. 2Drag the slider, or tap ▷ to play through time a step a second (❚❚ pauses).

Good to know

  • Novelist: steps through your chapters or scenes. GM: runs on your world's calendar, for campaign sessions. Worldbuilder: runs over years, from your Codex's dates.
  • Coloured ticks mark where things happen; ⇤ Prev and Next ⇥ jump to them.
More detail
  • Each project keeps its own mode, range and date. ⚙ Range sets your own range; Auto goes back to the project's dates.
  • The map follows the slider as you drag it; the date is kept when you let go or pause. A journey node that opens its panel pauses play too.
  • The ticks mark sessions, journeys arriving and leaving on this map, fights and zones changing shape, and the line under the date says what happens there. ▾ folds the panel to one line, the date, to give a phone its map; it stays folded until you open it again.
Chronos: the timelineYour world's calendar, events and lifespans on one timeline.

How to

  1. 1Open 🌍 Realm → Chronos.
  2. 2Set your world's months, weekdays, hours and leap years with ⚙ Calendar System (or keep the default).
  3. 3Tap + Event to add one, or + Add from Codex in the Event List to give an entry a date.

Good to know

  • Every Codex entry with a date appears on the timeline. Characters with a birth and death date show as bars.
  • Swipe to move along the timeline; pinch or − / + to zoom. Tap a bar for its dates and to open it in the Codex.
  • To change a date by dragging: with a mouse, drag the bar; on a touch screen, hold it until it lifts, then drag.
More detail
  • The timeline, the Atlas's Time Scry and every in-world date picker use your calendar. Changing the months or hours later keeps every date on its day: Chronos tells you how many it will convert first.
  • Name the broad periods of your history (e.g. "The Golden Age") under Eras & Epochs in the same dialog.
  • A character with no death date runs on to the edge. Drag the right edge of a range event to change its length. With a mouse, the wheel scrolls the rows.
  • Remove from Timeline removes an entry's dates and keeps it in the Codex.
The Realm pageA quick look at your maps and timeline, and the way into both.
  • Atlas: your first map, with a count of the others. Tap it to open the Atlas.
  • Chronos Timeline: the five earliest entries on your timeline. Tap one to open Chronos.
  • Your in-world calendar is set in Chronos (⚙ Calendar System).
The Grimoire: magic systemsSpells, technologies or powers, grouped into schools with prerequisites.

How to

  1. 1Open 📚 Archive and tap the Grimoire (it shows with the Grimoire module on), then add a spell.
  2. 2Give it a school, a cost (Mana, Stamina, Sanity…), range and duration.
  3. 3Add Prerequisites to build skill trees; Tome View draws them as a branching tree.

Good to know

  • Wielders lists who casts it, and shows on their Codex entries too.
  • If your world doesn't call them spells, give its word in ⚙️ Bindings → Story & World → The Grimoire (Rune and Runes, say).
  • 📥 Import brings in open-license spell sets for tabletop play.
More detail
  • A Wielder is a "Wields" connection, with or without the Tabletop tools; a character whose Spell Arsenal knows the spell is listed as well. Appears In lists the scenes that name the spell, as the Codex does.
  • Spell sets: D&D 5e SRD (the 319 spells of the System Reference Document 5.1, CC BY 4.0, with abridged descriptions) and Pathfinder 2e (142 spells from the Core Rulebook, OGL 1.0a, with the rules summarized), offered when TTRPG Tools is on (⚙️ Bindings → Tools). Custom JSON imports any spell list as a JSON array.
  • A spell you already imported from the same set shows ✓ Imported; one whose name another spell already has is still offered, marked Name in use.
  • Many spell names are everyday words (Light, Fear, Wish), so an imported spell links in your manuscript only as written, capital and all: Match Capitals When Linking is on. Turn it off in the spell's editor to link "light" too.
Lenses: saved searchesGather every scene where a character, a tag or a phrase appears.

How to

  1. 1Open 📚 Archive, tap Open Lenses → on its Lenses card, then the 🧿 New Lens card.
  2. 2Pick Codex entries that must appear, tags, or words to find.
  3. 3Save it, then tap View as Scroll to read every match as one page you can write in.

Good to know

  • A lens finds the chapters and scenes that match everything you give it: every entry named, at least one of the tags, and the words in the title or text.
  • Each lens card shows how many drafts match. ✏️ changes a lens and 🗑️ deletes it.
More detail
  • For example, a lens on one character and "the locket" gathers every scene where they appear with it. In View as Scroll the matches are highlighted, in reading order, and a scene's title opens it on its own.
The Vault: your inspiration boardKeep web links, photos, images and PDFs with the project.

How to

  1. 1Open 📚 Archive and tap Open Vault → on its Vault card.
  2. 2+ Link or 📋 Paste saves a web link; 📷 Photo takes one with your camera; 📤 File adds an image or PDF.
  3. 3From another app (Android): tap Share and pick Iron Bind. Choose the project, then where it goes: a Vault relic, a new Codex entry, or a note on a scene (text and links). Change the title and notes, then Save.

Good to know

  • Each one is a relic: tap it to rename it, add notes and tags, or open its file.
  • Move to the Codex as turns a relic into a Codex entry.
More detail
  • Photos are kept at up to 2,048 pixels on their longest side, and other files can be up to 5 MB, so the Vault stays quick to open.
  • Search relics by name or notes, or filter them to images, web links or PDFs. Open in the Codex edits the rest (timeline date, aliases, attributes). The Archive's Relics count opens it too.

Story Tools

Threads, arcs, the narrative hub

The Narrative pageYour story at a glance: arcs, plot threads, draft stages, connections and POV.
  • Character Arcs: a small chart of your main arcs; Open Visualizer for the full one.
  • Plot Weaver: your open and active plot threads, each marked when it's gone quiet; tap one to open its X-Ray.
  • Heat Map: every scene coloured by its stage. Relationships: the web of your Codex's connections. POV Distribution: every scene in its POV Character's colour, with each character's share.
More detail
  • A chapter's POV Character counts for its scenes.
Plot Weaver: plot threadsFollow each storyline through the book, so no subplot is forgotten.

How to

  1. 1On the 🎭 Narrative page, tap Open Weaver under Plot Weaver and add a thread: a storyline, like "The Mystery of the Locket".
  2. 2Tie a knot wherever the thread appears: a note on the chapter or scene where it moves on.

Good to know

  • Board: your threads by status. Tapestry: a grid of threads against chapters, showing where each has a knot. X-Ray: one thread's chapters and scenes in reading order.
  • A ! warns when an open thread has gone quiet for four chapters or more.
More detail
  • The warning: an open or active thread is flagged when four or more chapters pass between two of its knots, or when it hasn't appeared in the last five chapters you've written. A scene outside any chapter counts as a chapter of its own; resolved and abandoned threads are never flagged.
  • Board: on a phone, the statuses are stacked; tap a heading to fold it. Tap a card's status to change it, or the card to read its knots and its whole description.
  • Tapestry: chapters are numbered Ch 1, Ch 2…, their scenes 1.1, 1.2…, and scenes outside a chapter Sc 1, Sc 2…. Tap a cell to read its knots, edit or delete one, tie a new one there, or open the scene.
  • X-Ray shows each knot's note and the opening lines of the text. Back from a scene you opened returns to the same thread, at that scene.
The heat mapEvery scene as a tile coloured by its stage, to see what still needs work.
  • It's on the Narrative page. Each tile is a scene, in the colour of its stage (Draft, Revision, Polish, Final, or the stages you set in ⚙️ Bindings → Writing → Stages).
  • Tap a tile to see its title, words and stage, change its stage, or open it.
  • The bar at the bottom shows how much of the manuscript is done.
Character arcsChart how a character changes across the book: courage, power, faith…

How to

  1. 1In the Codex, open a character and tap + Add Arc under Character Arcs. Name it (e.g. "Redemption"), set its range (e.g. 0–100) and, if you like, words for its ends (Min Label "Pure", Max Label "Void-Touched"); save.
  2. 2In the Editor, open a chapter or scene, tap 📈 in the header (on a phone, ⋯ → Character arcs), pick the character and move each arc's slider to where they stand there.
  3. 3On the Narrative page, tap Open Visualizer under Character Arcs to see each arc drawn across the book.

Good to know

  • A section with no value says "Not set": Set records the slider where it is (its lowest value too), and Clear removes a section's value.
More detail
  • Each new arc takes a colour no other arc has yet; change it with the colour box.
  • With one arc shown, the Visualizer's scale reads in its own values with its Min and Max Labels; with several, each runs from 0 % to 100 % of its range.

Tabletop

Sessions, tables, encounters

The Tabletop hubGame master's tools: sessions, recaps, combat logs, random tables and encounters.

How to

  1. 1Turn on TTRPG Tools in ⚙️ Bindings → Tools (a Game Master project has it on).
  2. 2Open 🎲 Tabletop in the sidebar.

Good to know

  • Five tabs: Sessions, Recap, Combat Logs, Tables and Builder.
  • Recap shows one session at a time: its dates, GM notes and loot, and the fights logged on its date.
  • Set your game in ⚙️ Bindings → Story & World → Rules System (D&D 5e, Pathfinder 2e or your own).
Session JournalA log of your sessions, newest first.
  • Each session keeps its real date and an in-world date (written however you like, e.g. "4th Frostfall"), the characters present and places visited, loot, your GM notes and tags.
  • Search finds sessions by title, GM notes or loot. 📍 Place on Map pins a session on an Atlas map.
More detail
  • 🕰 Time Scry Position (optional) puts the session on your calendar, so it shows in the Atlas's Time Scry and on the Chronos timeline; the in-world date then fills in from it, unless you've written your own.
Random tablesBuild and roll tables for encounters, weather, NPC traits or anything else.

How to

  1. 1On the Tables tab, add a table and its rows, each with a weight (1–100).
  2. 2Tap Roll.

Good to know

  • A higher weight is more likely. For a d100 table, give each row the size of its range (01–35 is 35).
  • A row can link to a Codex entry: a result that rolls it opens that entry in the Codex.
  • The last 20 results are kept, newest first.
Encounter BuilderBuild a fight from your Codex and see how hard it is for your party.

How to

  1. 1On the Builder tab, add monsters from your Codex.
  2. 2Set your party: Codex characters or members you type in, each with a level.
  3. 3See how hard it is, then Launch Encounter to fight it in the Atlas, or Inscribe to save it for later.

Good to know

  • D&D 5e uses the Dungeon Master's Guide XP budgets (Easy, Medium, Hard, Deadly); Pathfinder 2e the Core Rulebook's threat (Trivial to Extreme). Other systems get a plain list.
  • The party is remembered for the project, and a member from the Codex takes the character's current level each time you open the Builder.
More detail
  • In 5e each monster's CR comes from its Monster stat block or a CR attribute; in Pathfinder, its level. The 5e multiplier counts the monsters and your party's size: a party of one or two faces a harder fight, one of six or more an easier one.
  • Inscribe saves the encounter on a map and a planned in-world date: a ⚔️ marker that Time Scry shows on that date, and a planned fight in Combat Logs. In the Atlas, that map's Staged Encounters (or the marker) offer 🗺️ Setup Board: drag the tokens into place and save the setup, then ⚔️ Begin Combat.
Combat trackerInitiative, turns, hit points and conditions, run beside your map.

How to

  1. 1Launch a fight from the Encounter Builder, or tap ⚔️ in the Atlas to start one with the characters on the map.
  2. 2Roll or type initiative, then go turn by turn.
  3. 3Tap End when it's over.

Good to know

  • It tracks initiative, turns, HP (current, max and temp) and your rules system's conditions: tap one to add it and read what it does.
  • The party's HP and spell slots are saved to their Codex entries; enemies' changes last for the fight only.
  • Leaving the Atlas mid-fight keeps the fight. Combat Logs keeps a history of every fight.
More detail
  • A condition with a value (Frightened 2, Exhaustion 3) steps with − and +.
  • End asks first, and offers End Fight, ☕ End + Short Rest and 🌙 End + Long Rest: the last two note the rest in the fight's log; they don't restore hit points. A stat block's ⟳ Restore to max HP does.
  • On a phone, each combatant is one line; the current turn's row and a row you tap show its HP buttons and damage field.
  • It works on any map; a Tactical map adds a grid (✏️ beside the map in the Atlas's map list → ⚔️ Tactical Map, once the map's scale is measured).
  • An enemy added more than once becomes numbered copies (Goblin 1, Goblin 2…), each with its own HP, initiative and conditions. The fight reopens on its own map. Combat Logs is a tab of its own, and 📜 in the Atlas.

Export & Publish

Manuscripts, compile, the Forge

Which export do I want?Agents, beta readers, ebooks or a printed book: where to go for each.
  • Sending to an agent or editor: on the Ledger, Tools → Compile, choose Agent Submission: a Word file and a PDF in standard manuscript format.
  • Sharing with beta readers: the same place, Beta Readers: an EPUB and an easy-to-read Word copy.
  • One chapter or scene: ⋯ → 📤 Send… on its row in the binder.
  • A finished ebook or a printed book: ⚒️ Forge in the menu (tap the Iron Bind mark) sets your book like a published one, as a PDF for print, an EPUB and Print (with the Archmage License).
Compile setupsWhat goes into an export and how it looks, without changing your manuscript.

How to

  1. 1On the Ledger, open Tools → Compile.
  2. 2Pick a setup: Agent Submission, Beta Readers, Ebook or Print. It says how many scenes and words it puts in.
  3. 3Tap one of its files to export. Edit changes the setup; + New Setup makes another from the one chosen.

Good to know

  • A setup can put in only scenes of some stages (Polish and Final for a submission), with a tag, or that a lens finds, and leave out any part, chapter or scene by hand.
  • It sets the headings ("Chapter One", "1", "I"…), the mark between scenes, and replacements made only in the file ("--" to an em dash, a working name to the final one).
  • Setups are kept with the project and travel in its backups.
More detail
  • Headings: chapters and parts as "Chapter One", "Chapter 1", "One", "1" or "I", with or without their titles, or titled as you wrote them. Numbers follow the whole book, so a copy of chapters 5 to 7 still says 5 to 7.
  • Between scenes: each file's own mark ("#" in a manuscript, the ornament in the book), "* * *", a blank line, or your own.
  • Replacements have Match Case and Whole Word; the setup shows how many times each changes the text.
  • The book: a setup's Book PDF and Book EPUB open the Forge, where Compile With picks the setup and the proof shows the result.
  • Glossary: pick Codex categories and the setup adds a glossary after the story, of the entries that copy names. Each prints its Glossary Line, set in the Codex editor, or its name alone; your notes never print. Name it as you like ("Cast of Characters"). Beta Readers starts with characters and places.
  • Maps: every Atlas map but the tactical ones, or the ones you tick, a page each before the story or after it: grey in the book PDF and Print, in colour in the EPUBs. A wide map on a tall page is turned so it prints larger, its top to the left edge. The manuscript files leave maps out. Ebook starts with every map.
  • Pictures: your own art for a Chapter Opener, over each chapter's title, and a Scene Break, in place of the ornament. Grey in the book PDF and Print, in colour in the EPUBs; the manuscript files keep the scene break you chose. A PNG with see-through edges sits on the page best. Remove one and the ornament comes back.
Preview and the check before exportSee a chapter as the file will lay it out, and catch problems before you send it.
  • 👁 Preview on the Compile card shows any chapter as each file will lay it out: the manuscript page, the reading copy, the EPUB on a small e-reader, and the book.
  • Every export is checked first: scenes still marked Draft, open comments, empty scenes and the like are listed, each opening its scene. Export Anyway goes on; with nothing to report, the file goes straight out.
More detail
  • The preview's book uses the Forge's look and trim; its page numbers count from that chapter.
  • The check also lists a replacement that finds nothing, a book with no copyright page, and a map or picture too small to print sharply. The book PDF also gives its page count, its inside margin and its spine width on white and cream paper, at Amazon KDP's rates.
Send one chapter or sceneExport a single part, chapter, scene or lens, to share it on its own.

How to

  1. 1In the binder, tap ⋯ → 📤 Send… on the part, chapter or scene (or Send… on a lens card, 📚 Archive → Lenses).
  2. 2Pick a setup (Beta Readers first) and one of its files.

Good to know

  • The setup's rules, headings, scene breaks, replacements, glossary and pictures apply, and a chapter keeps its number in the whole book.
  • The file is named with the piece ("Ashfall_The_Moor_reading_copy.docx").
More detail
  • It sends everything inside what you picked. The check runs on the piece. A book file is set as the Forge has it.
Manuscript formats (on the Ledger)The PDF, Word, EPUB and OpenDocument files Compile makes.
  • PDF (Shunn): the standard manuscript format agents and publishers ask for: 12 pt Times-style type, double-spaced, 1" margins.
  • DOCX: a Word document. In Manuscript format it's set as agents and editors ask; Reading copy is single-spaced and compact, for beta readers.
  • EPUB: an ebook for Kindle, Apple Books and other e-readers. ODT: for LibreOffice, like the DOCX.
  • A project's cover (⚙️ Bindings → Project) shows on its Library card and opens both EPUBs, the manuscript's and the book's. The PDFs leave it out: a printer takes the cover as a file of its own.
  • On Android, an export opens the share sheet so you can send it to Drive, email or any app. On Windows it opens the Save dialog.
More detail
  • Manuscript format: Times New Roman 12 pt, double-spaced, a half-inch indent, 1" margins on Letter, the word count on the title page and a Surname / TITLE / page header. The PDF is set in Liberation Serif, which has Times New Roman's measurements.
The Forge: a typeset bookTurn your manuscript into a book interior ready for print, and a styled ebook.

How to

  1. 1Open the menu (tap the Iron Bind mark) and pick ⚒️ Forge (the Ledger's Compile card opens it too, from a setup's book file).
  2. 2Pick a look under Binding Style, a trim size and an ink size, and check the proof.
  3. 3Switch on the pages you want with 📄 Book Pages (copyright, dedication, contents…).
  4. 4Export the book PDF, the EPUB, or Print.

Good to know

  • Ten built-in looks: The Arcanist, Neon Pulse and eight by genre (Epic Fantasy, Romance, Thriller, Literary Fiction, Cosy Mystery, Science Fiction, Young Adult, Nonfiction). A line under Binding Style says what each is.
  • The proof shows the book page by page, as it will print. Chapter to proof shows any chapter.
  • The whole book needs the Archmage License; on the free tier, the PDF button makes a Sample PDF of the first chapter.
  • The look, trim, ink and Large Print you chose are kept for each project.
More detail
  • The Arcanist has Cinzel titles in centred capitals, Crimson Pro text, drop caps and fleurons, previewed on cream paper; Neon Pulse is Inter throughout, with left-aligned titles over a rule and spaced paragraphs, previewed on white paper. The genre looks are set from the same bundled fonts.
  • Pick a page on the strip under the proof, or step with ◀ ▶. It shows the title page, the Book Pages you switch on, a part's title page and your first chapter's pages, numbered as the book numbers them, and it updates as you change settings. Another chapter is numbered from its first page.
Book Pages: front and back matterThe title page, copyright page, dedication, epigraph, contents and the pages after the story.

How to

  1. 1In the Forge, tap 📄 Book Pages.
  2. 2Switch on each page you want and fill it in.

Good to know

  • A Copyright Page on the title page's back is written for you from the year, rights holder, ISBN, edition, publisher and credits; edit its text freely, or Rebuild from the Details.
  • Also a Dedication, an Epigraph, a Contents page, and Acknowledgements and About the Author after the last chapter.
  • About the Author starts from the bio of the name the project is written as, and you can edit it for this book. Print the photo puts that name's photo under its title: grey in print, in colour in the EPUB.
  • The pages before the story are numbered i, ii, iii, and the story starts at page 1.
More detail
  • The Contents list the parts with their chapters under them. The PDF gives their page numbers, while Print can only list them, as browsers can't print a page number they haven't reached. Only the contents show their own page number.
Pen names and your photoWrite some books under another name, each with its own bio and photo.

How to

  1. 1In ⚙️ Bindings → Author, add your own photo.
  2. 2In ⚙️ Bindings → Project → Written As, pick your own name, a pen name another of your projects uses, or A new pen name…, then give the pen name its bio and photo right there.

Good to know

  • That name is the byline on the project's manuscripts and book, and its bio and photo go on About the Author. Your legal name, email, phone and address stay on the manuscript's title page whatever the byline says.
  • A pen name is part of its project: it travels in the project's backups and, with sync on, to your other devices, so every device prints the same byline. Your own name, bio, photo and contact details are this device's (Bindings → Author) and never go in a sync file.
More detail
  • Pen names kept in your profile before 3.0.0 moved into the projects written under them, and Written As offers them for your other projects.
  • A photo is made at most 800 pixels on its longest side when you add it.
Printing with Amazon KDPTrim sizes, margins and Large Print for a paperback.
  • Trim sizes: the novel sizes Amazon KDP prints in paperback: 5"×8" Pocket, 5.06"×7.81" Mass Market, 5.25"×8" Novel, 5.5"×8.5" Digest, A5 International, 6"×9" Trade and 6.14"×9.21" Royal.
  • The book PDF is ready for KDP Paperback: it widens the inside margin on a thick book, as KDP asks.
  • Large Print sets the book in 18 pt, left-aligned and unhyphenated, with wider lines, for the book PDF, Print and the proof.
More detail
  • The Royal is a large trim on KDP, which costs more to print.
  • The inside margin is 0.9", 1" over 500 pages and 1.125" over 700. Before it's saved, the check gives the page count and the margin it chose, and warns when the book has fewer than 24 pages or more than 828 (776 on cream paper).
  • Large Print suggests the 6.14"×9.21" page, where 18 pt reads best; the EPUB lets the reader choose a size.
Your own looksMake a book look of your own, and share it as a file.

How to

  1. 1In the Forge, tap ⧉ Duplicate to start from the look in use, or ⚒️ New to start from The Arcanist.
  2. 2Change the fonts, chapter titles, paragraphs, ornament, drop caps, spacing, page numbers and the rest, watching the page as you go.
  3. 3Save it.

Good to know

  • ✏️ Edit changes a look of your own. When other projects use it too, Save asks: Save for All changes their books as well, Save as a Copy gives this project a copy.
  • 📤 exports a look as a file, 📥 imports one, 🗑 deletes one. Your looks are also saved in project backups.
More detail
  • The form covers the typography pair, chapter titles (centred capitals, or left-aligned over a rule), paragraphs (indented or spaced), ornament, drop caps, leading, kerning, alignment, hyphenation, page numbering, chapter sink depth, and the paper the preview shows.
  • Hyphenation applies to the PDF (with US English hyphenation patterns), the EPUB, Print and the preview. The page shows beside the form on a wide screen, and on its Preview tab on a phone.

Backup & Devices

Backups, Google Drive, OneDrive, sync, co-writing

Where your work is keptOn your device. Nothing goes online unless you switch it on.
  • Your work is yours, and you don't need an account. Everything is stored on your device.
  • Your writing leaves the device only through what you switch on: cloud backup or sync (to your own Google Drive or OneDrive), and Lore Scan (to Google's Gemini, with your key).
  • Two things talk to Iron Bind's own server, and neither carries your writing: a report you choose to send, and the license check, about once a week, when you have a license.
More detail
  • On Android, your work is in a SQLite database with a second copy in the app's own storage; in a web browser, in its IndexedDB; small settings also sit in the browser's local storage. Iron Bind doesn't encrypt this data itself: your device's lock screen and app sandboxing protect it.
  • In a browser Iron Bind writes from one tab at a time: opened in a second tab, that tab says so and offers Use Here, which has the first tab save what it has and step aside.
  • Lore Scan's text is handled under the Gemini API terms for your key: data sent with a paid-tier key isn't used to train Google's models, while free-tier use may be used to improve Google's products.
BackupsSave a copy of a project as a file, and open it again on any device.

How to

  1. 1Tap 💾 Backup on the project's card in the Library, or ⚙️ Bindings → Backup & Sync → Save Backup File.
  2. 2Keep the file somewhere safe: your cloud storage, a computer, an email to yourself.
  3. 3To restore, use 📥 Import → Backup File in the Library or Open Backup File in ⚙️ Bindings → Backup & Sync.

Good to know

  • Each Library card says when its project was last backed up, and a project not backed up for 14 days reminds you when you open it.
  • A backup of the open project replaces it after you confirm; any other is added as a new project.
  • On the web this browser holds the only copy, and on a phone the work goes with the device if it's lost or reset, or the app is uninstalled. Back up.
More detail
  • A backup also carries your custom templates, publishing looks and author profile. Its file is named with the day it was made.
  • Import Backup shows the backup's name, date and what it holds before adding it, then opens it.
  • A project restored on someone else's phone remembers where it came from: when its backup comes back to the device with the original, you can Replace the original with it instead of adding a second copy.
Cloud backup: Google Drive and OneDriveBack up and restore projects through your own Google Drive or OneDrive; link more than one account, and each project picks its cloud.

How to

  1. 1Link an account in ⚙️ Bindings → Backup & Sync → The Astral Link: + Link Google Drive or + Link OneDrive (a personal Microsoft account).
  2. 2With more than one account linked, This project's cloud picks the account the open project backs up to and syncs through.
  3. 3Tap ⬆ Backup to save a backup of the open project to that account. On a project that syncs, its live copy on the cloud is the sync file, and the button reads ⬆ Snapshot: a dated copy you can go back to.
  4. 4Tap ⬇ Restore to list every Iron Bind backup on that account, for all your projects, and pick one.

Good to know

  • Each project chooses its own account, so your own stories can go to your Google Drive while a book you write with someone goes to a OneDrive you both link. Each of your devices chooses for itself.
  • The account picker opens only when you link. After that the app stays signed in to each account, with no picker. Disconnect forgets an account on this device; it says first which projects use it.
  • The 20 newest backups of each project are kept in the cloud; older ones are removed. On OneDrive they sit in Apps → Iron Bind, the one folder the app can see.
  • Offline, your accounts stay linked; Backup and Restore work again once you're online.
More detail
  • If Google or Microsoft ever wants you to sign in again (you removed the app's access, or changed your password), the link is kept: Bindings shows Sign In on that account and the ☁ says "tap to sign in". Nothing asks by itself.
  • Work and school Microsoft accounts aren't supported yet: OneDrive takes a personal Microsoft account.
  • A backup of the open project replaces it after you confirm; a backup of another project is added as a new project, and nothing on the device is replaced. If it's a version of a project you have (say, the copy a friend worked on with your phone), you can choose Replace instead.
  • Your author profile changes only if you tick the box in the restore dialog. Your cloud sign-ins are stored only on your device and are never sent to Iron Bind servers.
Sync between devicesThe same project on your phone, tablet and PC, through your own Google Drive or OneDrive.

How to

  1. 1With an account linked (and chosen as this project's cloud, when you have several), turn on ⚙️ Bindings → Backup & Sync → Sync This Project.
  2. 2On your other device, link the same account (no project needed: ⚙️ in the Library's top right corner → Backup & Sync).
  3. 3In its Library, tap Add to This Device under On Your Drive.

Good to know

  • It's free, and syncs by itself: when the project opens, every 5 minutes while it's open, and when the app closes. The ☁ in the sidebar says how it went; tap it to sync now.
  • Work on different scenes on two devices is all kept. A scene changed on both keeps the newer text, and the other is in its Version History.
  • Use Add to This Device, not a backup: a backup restored on the other device would be a separate copy.
More detail
  • If that device already has a copy made separately (or of the same name), the app asks: replace it with Drive's copy (it goes to Recovered Chronicles) or keep both as two projects. A project in Recovered Chronicles shows Restore there instead.
  • A synced project's card shows ☁ Synced, or ☁ Changes waiting when another device wrote to it since this one last synced: open it and it syncs.
  • Each scene, entry, map and tag is merged on its own. The kept text is marked with the device it came from ("From Windows PC"). Something deleted on one device is deleted on the others, unless it was changed after.
  • Before its first sync, each device saves a snapshot of the project to the cloud. Typed text is saved before each sync, and a sync that finds you typing waits. If a device's copy came from a backup rather than from sync, Bindings asks which to keep, and saves the other as a snapshot.
  • Restoring a snapshot on a project that syncs puts this device back, and the next sync merges by date: anything newer on the cloud comes back, and nothing is deleted. Restore and Replace the Cloud's Copy makes the snapshot the cloud's copy too, saving the cloud's as a snapshot first. A sync file saved to your device imports like a backup.
  • Deleting a project for good takes its sync file off the cloud too, and the ✕ on an On Your Drive row removes a file a project deleted everywhere left behind; a device that still has the project puts the file back at its next sync. On Your Drive lists every linked account's projects, each row saying which.
  • Each device keeps its own theme, text size and line spacing, editor width, Keep Screen On and Backup Folder, and sync is turned on or off per device. Offline, nothing is lost: it syncs when you're back.
Co-writing: a book two of you writeWrite one project with someone else, through a cloud account you both link or by passing the book between you; each of you keeps your own words today, settings and profile, and the app says who changed what.

How to

  1. 1Pick a cloud account for the book (a personal Microsoft account for OneDrive, or a Google account) and both of you link it in ⚙️ Bindings → Backup & Sync. Choose it as the project's cloud and turn on Sync This Project.
  2. 2Switch on Co-writing under it. Your co-writer adds the project from their Library's On Your Drive.
  3. 3No account in common? Pass the book instead: ⬆ Pass the Book and ⬇ Receive the Book, with Co-writing switched on under them (see Passing the Book).
  4. 4Put the book's authors in ⚙️ Bindings → Project → Authors: each name, bio and photo. They print on the title page, the copyright line and About the Authors from either device.

Good to know

  • Changes meet at each sync. If you both change one scene between syncs, the newer text is kept and the other is in Version History, marked "From Ada (Windows PC)". A scene your co-writer changed since you last synced says so above its text when you open it; tap the line to dismiss it.
  • Words today count what you typed on this device, not what a sync brought in. Your writing preferences and goals (typewriter mode, smart punctuation, spell check, sounds, the daily goal…) are your own on a co-written project; the book's own settings sync.
  • Your author profile stays on your device: no sync file or passed book carries it, and your changes are signed with its name. A co-written book's backup asks before its profile becomes yours on another device. Pen names don't apply to a co-written book; its authors are in the project.
More detail
  • The binder's details sheet, the Outline's Changed column (Columns → Changed) and the corkboard say who last changed a scene and when ("Ada · 3 min ago"), and a comment carries the name of the writer who made it. The name is the one in ⚙️ Bindings → Author on each device.
  • The sync file names the writer who wrote it last (your profile's name and this device's own id), so your co-writer's app can say who changed what.
  • Co-writing activity on the Ledger lists who changed what, and when: scenes (with the words added or taken out), parts, chapters and scenes added, moved or sent to the Trash, Codex entries, and comments. Each device builds its own from every sync and passed book, and keeps 90 days; See all filters by writer, and a tap opens what an entry names.
  • No live editing: two of you typing in one scene at the same time meet at the next sync, with one copy kept as a version. Write in different scenes, or sync (the ☁) before you start on a scene the other was in.
  • Turning Co-writing or sync off leaves the project on each device as it is. On the free tier the project counts for each of you.
Passing the Book: co-writing with no cloud in commonHand the book to a co-writer, or carry it to another device, as a file: email, a message or a USB stick. Their changes come back the same way and are merged in.

How to

  1. 1In ⚙️ Bindings → Backup & Sync → Passing the Book, tap ⬆ Pass the Book. On a phone the share sheet opens (send it by email or a message, or save it); on a PC, choose where to save the file.
  2. 2On the other device, tap ⬇ Receive the Book and choose the file, or on Android share the file to Iron Bind; from the Library, 📥 Import → ⬇ Receive the Book takes it too. A book that isn't there yet is added to the Library.
  3. 3Writing it together? One of you turns on Co-writing in Passing the Book; it comes with the book. Then pass it back and forth: each Receive merges the other's changes into yours.

Good to know

  • A Receive merges as sync does: work on different scenes is all kept, and a scene changed on both sides keeps the newer text, with the other in Version History. Something deleted on one side is deleted on the other when the book comes over.
  • The first time a device receives a book, it asks you to save a backup of its own copy first. Cancel, and nothing is received.
  • The file is the same as a cloud's sync file: the whole book, and the deletions. It goes only where you send it, and never through Iron Bind.
More detail
  • Each device remembers what it last passed and received, so a Receive merges against the book the other writer last had from you. Bindings shows when you last passed the book and when you last received it, and from whom.
  • A book can sync through your own cloud and be passed by hand too: your phone and PC sync through your Drive, and you pass the book to your co-writer, who syncs it through theirs.
  • The file carries no author profile: yours stays on your device. A pen name the book is written under comes with the book. With Co-writing on, the scenes your co-writer changed say so above their text when you open them.
  • If the book on this device was made separately from the one received (one came from a backup), the app asks before merging: use the received book (after a backup of this one) or keep this device's copy. A copy here of the same name asks whether to replace it or keep both.
  • Restoring a backup of the book here, or replacing it from the Library, makes the next Receive merge by date, so nothing written since the backup is lost.
Iron Bind on WindowsWhere your work lives on a PC, the Backup Folder, files and keyboard keys.
  • It's the same Iron Bind in its own window. Your work is in a database file on the PC (⚙️ Bindings → Backup & Sync → Open Data Folder shows it), with a second copy beside it.
  • ⚙️ Bindings → Backup & Sync → Backup Folder picks a folder that gets a backup of every project you changed, when Iron Bind closes and once a day. Pick one in OneDrive or Dropbox and it goes to the cloud too.
  • Every export opens the Save dialog; the Forge's Print opens the system's print dialog.
  • Closing takes a moment when there's work to finish: a panel says what Iron Bind is doing (saving, the Backup Folder, syncing with your cloud), and the window closes on its own when it's done.
More detail
  • The database file is iron_tome.db, in the app's own data folder. It stays through updates and a reinstall of the installer. Nothing leaves the PC unless you link a cloud account.
  • Backups are the same files as the phone app's, so a backup made on your phone opens here through Open Backup File or your cloud account, and the other way round.
  • The Backup Folder keeps a folder per project, one file a day, the newest 20. Only the files Iron Bind wrote there are ever replaced or pruned; anything you put in the folder yourself stays. Projects in the trash and example copies are left out.
  • Link Google Drive or Link OneDrive opens the sign-in in your browser; when it's done, the app picks it up and stays linked between launches. Disconnect forgets that account.
  • "Microsoft Print to PDF" in the print dialog makes a PDF too.
  • Keys: F11 for full screen, Ctrl+= / Ctrl+− / Ctrl+0 to zoom, Escape closes what was opened last, and a right-click offers spelling suggestions. In the editor: Ctrl+S saves, Ctrl+Z and Ctrl+Y undo and redo, Ctrl+B / I / U format, Ctrl+F opens Search & Replace, Ctrl+Shift+F turns Focus mode on or off, Ctrl+Alt+← and → open the previous and next page, Ctrl+1 opens the binder, Ctrl+2 the Reference panel and Ctrl+\ the second pane, and Ctrl+Shift+1 to 6 set a paragraph style (Ctrl+Shift+0 for Normal). A page you open with the mouse is ready to type in; Shift+Tab moves out of the text.
  • The license: a key bought on Google Play or given to you unlocks the Windows app too (⚙️ Bindings → the license's mark in its top right corner → Enter a key), as one of your 5 devices ("Windows PC" in the list). In the Microsoft Store version, Buy in the Microsoft Store sells it there, and the key it gives unlocks your phone and your other devices too; Restore Purchase finds it again on another PC with the same Microsoft account.
  • Uninstalling: the installer's uninstall leaves the data folder in place. The Microsoft Store version removes it with the app, so back up, link a cloud account or keep a Backup Folder first.

License

The Novice and the Archmage

🧙 The Archmage License

Iron Bind is "buy once, own forever". The free tier (The Novice) writes, plans and exports a manuscript; the Archmage License adds the whole typeset book, for print and ebook, and lifts the limits.

The Novice (free)

  • 1 project (examples from the Library don't count)
  • 50 Codex entries
  • 3 Atlas maps
  • The manuscript exports (PDF, DOCX, ODT, EPUB)
  • The Forge's preview, and a Sample PDF of the first chapter
  • Lore Scan (optional AI, your own Gemini key)
  • Sync, co-writing and Pass the Book

The Archmage (CA$29.99 once)

  • The whole typeset book: a print-ready PDF for KDP Paperback, a styled EPUB, and Print
  • Ten built-in looks, and presets of your own
  • Unlimited projects, entries and maps
  • One key for up to 5 devices, Android and Windows
  • Every update, no recurring fees, ever
  • Priority support
  • Buy or enter a key on the license page: ⚙️ Bindings, then the license's mark in its top right corner.
  • One key, all your devices. The license has a key (IRON-XXXX-XXXX-XXXX-XXXX). Enter it on another phone, a tablet or the Windows app to unlock it there too: up to 5 devices at once. The license page lists them, and Release frees one for another.
  • A new phone with the same Google account, or a PC signed in to the Microsoft Store with the same Microsoft account, can use Restore Purchase instead.
  • Going over a free limit never takes anything away: everything you've made stays, and only making more asks for the license.
  • You may share the key's slots privately with people you choose; a key posted publicly or sold can be revoked. There's no account: the key is checked about once a week when you're online, and the license keeps working offline.

Support

Found a bug, or have a question Help doesn't answer? Write to support@ironbind.app, or use the form.

Reports go straight to the Iron Bind team. We aim to reply within 48 hours.

We use your name and email only to look into this report and reply to you. Only our team can see them, and we'll delete them if you ask. See our Privacy Policy.