Tabularia compared with Microsoft Word

A document editor, and a manuscript

Word is a general-purpose document editor, built for letters, reports and memos. A book in it is a single very long document, or a folder of chapter files you keep in order by naming them carefully. Style your chapters as headings and the Navigation Pane will list them, which is real and useful — but it is a convention you maintain rather than a structure the document has, and nothing below that level exists at all. A scene is just more paragraphs, and a character's arc is something you track in your head. The ribbon above it is built for every kind of document at once, down to a Mailings tab for form letters and citation tools for a thesis. Tabularia shows what a book needs and keeps the structure in the sidebar.

Tabularia gives that same writing a shape a word processor has no word for. A scene sits inside a chapter, a chapter inside an act and an act inside a book, and all of it is one composition, so outline and minimap keep your position across the whole of it and timelines hold a thread to the paragraphs carrying it. It is also built for the length: scrolling, resizing and typing are proportional to what is on screen rather than to how much you have written, measured at ten thousand words and at a million. And a trilogy is not three folders: the second book joins the first inside the same project, with search, outline and threads running the length of all of them.

Keeping the handoff a professional editor expects

DOCX with Track Changes is what most professional editors work in, and Tabularia is built to meet that rather than argue with it. It imports DOCX, comments and all, and exports DOCX alongside every other format a manuscript travels in. Draft where the project stays in view, hand over the file they asked for, and import the edited copy when it comes back.

The round trip is also where Word itself struggles. Microsoft's own support article says Word "becomes very slow or stops responding if an open document contains excessive tracked changes or comments," and a novel collects both, one editing round after another. A collaborator's changes in Tabularia stay in their own draft until you merge them, a difference at a time or all at once, so your manuscript never carries a backlog of someone else's markup.

If your editor is willing to come to you, there is a second route. Invite them by link and they work in the manuscript itself — writing into a draft of their own, which returns as a redline you read in place and merge a difference at a time or all at once. They need no paid account to do it.

Why to switch

Word is where your collaborators already are, and DOCX opens everywhere — which is exactly why Tabularia exports it. If the manuscript is short enough that one document has never once got in your way, there is nothing here you need.

Move to Tabularia once the document no longer fits in your head and you keep a second file of notes to find your way around the first. Here that file is unnecessary. The Outline is built from the manuscript itself, so it never falls out of date, and an anchor left where chapter 4 makes its promise is one press away when chapter 30 has to keep it. Character and place details sit in Sheets beside the page rather than in a document you switch to. And when you plan before you draft, a story shape lays the acts and chapters down for you to write into.

It also sets the page as a book while you write, which is a pleasant side effect rather than the reason. Plenty of self-publishers lay out the print edition in Word as well, starting from the templates Kindle Direct Publishing offers, and it works; the difference is that here you are looking at the typeset book the whole time, not formatting it once the writing is done. The DOCX goes in and a DOCX comes back out, so it is not a decision you have to be certain about first.

Opening your Word manuscript here

Import the .docx as it is. Every paragraph styled Heading 1 starts a Chapter. Comments come across as annotations where their place in the text is unambiguous. Accept or reject your editor's tracked changes before you import: any still open are taken as accepted, and the import review tells you it did so.

If your chapter titles are bold text rather than a heading style, apply Heading 1 to them in Word first — or fix them after the import. Your footnotes and endnotes come with the text as live notes. A table's words arrive as plain paragraphs; headers stay behind, and the import names each thing it left.

Staying with Word for now

• Why does Word freeze on my long manuscript?
• How do I move chapters around in Word?
• Word AutoSave replaced my chapter with an older version
• Word crashed and AutoRecover didn't save my chapter
• How do I combine comments from several beta readers in Word?
• My editor uses Word and I write in Scrivener
• I fixed typos in Vellum. Now my Word file is out of date
• Exporting from Pages to Word messed up my manuscript
• How do I export an Obsidian novel to Word for my editor?
• My chapters were lost or reordered when I imported a Word file