Wcharacters.docx
¶1
The connected workshop where your whole book gets made, for novelists, memoirists, poets, screenwriters, and worldbuilders.
We'll write when there's something worth saying.
Private by default Never training data Export anytime
Characters with histories. Places with textures. Timelines that fold and diverge. They used to live in different tabs, different apps, different notebooks. Now they share one canvas, and you can see how they connect.
Your next book is not stuck. It's just tied up.
— Unbind the writer. Unbind the world.
Your story has been holding its breath.
Time to let it out.
Consider this the table of contents.
Late in the draft, you reach for a detail, what the harbor smelled like the night she arrived, and it is gone. You search three apps and lose an hour. The canvas is where that stops. Put a character down. Put a place beside her. Draw what they are to each other. The world holds its shape while you write into it, and tomorrow it is exactly where you left it.
The book remembers, so you do not have to.
You think spatially on Sunday, in chapters on Monday, in dates on Tuesday, in arcs on Wednesday. Most weeks, that means four different files quietly drifting out of sync. Here, the same world holds still while you walk around it. Open the manuscript and the cards rearrange into chapters. Open the timeline and they line up by date.
Nothing is copied. Nothing forks.
The harbor was holding its breath when Aelin Vance stepped down from the gangplank, salt cracking under her boots.
She had not expected to recognize the lamp at the lighthouse — and yet there it was, the same crooked seam in the glass, the same bruised glow.
Eight years. Long enough for a town to forget. Not, she suspected, long enough for it to forgive.
Maybe Cael, after the grandfather. Check the dates against the harbor fire.
Storm rolls in from the north. Lighthouse goes dark before the Pact, not after.
"She had not expected to recognize the harbor — and yet."
You are mid-sentence and you need her brother's name. You alt-tab. The wiki loads. The browser eats your cursor. By the time you are back, the sentence has gone cold. Here, you type @ and her brother surfaces in the line itself: the room beside it, the year she met him, all a glance away, none of it asking you to leave the prose.
You never leave the sentence.
She never thought she'd see Aelin again, much less in Saltwhistle Harbor, the year after her brother @Marek
You rewrote the opening. Then you rewrote it again. Then you wished you had the first one back. Every version of every chapter is kept by name, and the differences between them are visible at a glance: what you cut, what you saved, what you tried before you knew better.
Revision stops being a wager.
The harbor was quiet that night holding its breath, and Aelin walked slowly without hurrying toward the lamp — its glass cracked, its light still kind.
She did not call her brother's name. Not yet. She had practiced not calling it for eight years; one more night was nothing.
Somewhere past the third chapter, the draft goes quiet. Not abandoned, you tell yourself. Resting. The Compass keeps a gentle ledger of your writing life: the words you added on Tuesday, the chapter that has waited a month, the pace you actually keep rather than the one you promised yourself. You watch the finish line move closer, week by honest week.
Books are written on more days than not.
~80,000 words. At your current pace, the finish line is in sight — about ten weeks out.
The draft is done. Now begins the part nobody warned you about: margins and bleed and ISBNs, and a different file format for every store. The book you have been writing already knows it is going to be a book. It paginates itself the way printers expect. It checks the small things that get covers rejected, before you upload.
The last mile stops being a wall.
You have lost work to a vendor before. Maybe a service shut down. Maybe a subscription lapsed and the lock came down. Maybe the internet blinked at the wrong moment. Here, the book lives on your machine first. Editing on a flight, on a train, in a cabin with one bar of signal: same book, no warning bar, no anxious reload.
Your world belongs to you, regardless of our weather.
"Works without us."
Different shapes of story, the same connected workshop.
Forty chapters, nine viewpoints, one thread you must not drop.
A life never happens in order. The telling doesn't have to either.
A manuscript of moments, and the motifs that run beneath them.
Every beat, every scene, and who knows what in which act.
Six notebooks of lore, finally in the same room.
A canon of your own, kept straight across a hundred chapters.
Unbind never writes your sentences. It holds your world steady while you find the words.
Private by default. Never training data. Export the whole manuscript anytime, to files that open anywhere.
Your book lives on your machine first and syncs when you're online. If we vanished tomorrow, your files would not.
Why Unbind exists, what it will never do, and the person accountable for both. When something feels wrong, write me. I read every note.
Meet the builder →The rest is written down. Read the manifesto →
We'll write when there's something worth saying.
Free to start when your cohort opens. Your work exports anytime.
Unbind is a visual canvas for long-form writers — novelists, memoirists, essayists, screenwriters, poets, and worldbuilders. Plan characters, locations, events, chapters, and lore as connected elements on an infinite canvas, then export the result as a manuscript ready for publishing.
Long-form authors — novelists, memoirists, essayists, screenwriters, poets, and worldbuilders — who need to keep track of how characters, places, events, and ideas connect across a long project. If you have written a 60,000-word draft and lost track of a thread, Unbind is for you.
No. Unbind builds for the writer, not in place of them. What it helps with is the work of remembering: checking continuity across chapters, surfacing lost notes, finding the thread you misplaced. It never writes the page for you. The voice is yours. See the manifesto at unbind.page/manifesto .
Unbind is in early access in 2026 and admitting authors in small cohorts. Join the waitlist at unbind.page/join — confirmed referrals move you up the line.
Unbind has a free tier that covers personal worldbuilding, and paid tiers for authors who need more projects, more storage, or the assisted features. See unbind.page/pricing for current plans and prices.
Unbind runs in any modern web browser today, with desktop apps for macOS and Windows. Native apps for iPhone and iPad are on the roadmap for 2026; until they ship, the web canvas works on tablets and phones in the browser.
Yes. Unbind is offline-first — your work lives locally and syncs to the cloud when you are online. Lose Wi-Fi mid-sentence and nothing is lost. The desktop app stores your data encrypted on disk using your operating system's keychain.
Yes. Unbind has a built-in importer that takes a long manuscript in Word (.docx), EPUB, or Markdown, detects chapter breaks, lets you preview and adjust the splits, and lands every chapter on your canvas as an element. Scrivener, Notion, Obsidian, and Google Docs all export to one of those formats.
Not yet. Unbind today is a single-author workspace; live co-authoring and shared editing are on the roadmap. You can export drafts to PDF or EPUB to share with editors and beta readers in the meantime.
Unbind holds the world and the manuscript on one connected canvas. Scrivener drafts well but has no visual graph; World Anvil and Campfire model worlds but do not compile to a print-ready book. Unbind unifies the visual canvas, author-specific entity types, relationship mapping, and manuscript export in a single offline-first product.
Yes. Your projects are private by default, served over TLS, and never sold or shared. The desktop app encrypts local data using your operating system's keychain.
Yes. Unbind exports complete manuscripts to PDF and EPUB with print-ready presets for KDP and IngramSpark, plus per-element exports for individual characters, locations, events, chapters, and lore. Your project data is portable.