Atticus vs Vellum: which one, and why Mac decides it

Most comparisons of these two are a feature table with a winner at the bottom. That is not how the decision actually goes, because for about half the people asking there is no decision: Vellum is Mac-only software, and no amount of feature advantage matters on a Windows laptop.

So this starts with the question that eliminates one of them, and only then compares what is left.

Does it run on your computer?

Vellum is a native macOS application. Not a web app with a Mac skin — a Mac program, and there is no Windows version, no Linux version, and no plan for one.

The workarounds people suggest are all worse than they sound:

• Renting a Mac in the cloud (MacinCloud and similar) works and costs a monthly fee on top of the licence, and you are formatting a book over a remote desktop.
• A virtual machine is against Apple's licence terms on non-Apple hardware and is fragile in practice.
• Borrowing a friend's Mac is fine once and miserable for the third correction.

Atticus runs in a browser and in a small desktop wrapper, on Windows, macOS, Linux and Chromebook, and it works offline once loaded. If you are not on a Mac, the comparison ends here and the rest of this page is context.

What each one actually is

Vellum sells two tiers: ebook only, or ebook plus paperback. Atticus is one purchase that includes both. Prices move, so check each site rather than a blog post — including this one.

Which produces the better book?

Vellum, and the gap is in the defaults rather than the ceiling.

Vellum ships ten styles designed by someone who knows what a book looks like. You pick one, and the chapter openers, drop caps, ornaments, running heads and page numbers are all already right. It is hard to make an ugly book in Vellum because the choices that would make it ugly are not offered.

Atticus gives you more control and fewer guardrails. That is genuinely better if you know what you want and you are willing to check the output — and worse if you do not, because you can set a 9pt body face with 1.1 line spacing and nothing will stop you. The things that go wrong are the ordinary typesetting ones: margins and measure, widows and orphans, and hyphenation.

For a plain novel — chapters, scene breaks, nothing unusual — both produce a file a store will accept and a reader will not question. The difference shows up in anything with structure: tables, images, footnotes, epigraphs and front matter.

Which is better to write in?

Atticus, because Vellum does not try.

Vellum is a formatter. You write somewhere else — Word, Scrivener, a plain-text editor — and import. It handles that import well and it is not pretending to be your drafting tool.

Atticus includes a writing environment with goals, chapter reordering and progress tracking, positioned fairly openly as a Scrivener replacement that also formats. It is not as strong a drafting tool as Scrivener, and for many people it does not need to be: one application, one file, no export step between writing and a finished book.

If drafting is the part you are trying to solve, the writing tools are their own comparison and leaving Scrivener is a separate question again.

What both of them get wrong

Neither is a complete pipeline, and the gaps are the same ones.

1. Neither designs your cover. Both take artwork you supply; the interior is their job. Get the dimensions and, for print, the spine and bleed right before you start.
2. Neither edits. They will set a typo in a beautiful face.
3. Neither uploads. You still meet KDP's requirements yourself.
4. Both keep your book in their format. The file is a Vellum document or an Atticus project, and the manuscript is inside it. Export is how you get it back.

That fourth one is the one people notice late. Two years on, wanting a second edition, you need the application that made it — which for Vellum means still owning a Mac.

The version with no application at all

Both of these exist because manuscripts arrive as Word files and Word files are a bad source for a book. If your manuscript is plain text instead, the whole category becomes a build step.

bukpress takes a Markdown manuscript and exports the typeset PDF and the reflowable EPUB from that one source. The book stays a text file you own, the design is saved once and reused, and a correction is one edit and one rebuild rather than reopening a project on a specific computer. That suits some people and not others — if you want to drag a chapter around and see it move, Vellum and Atticus are the right shape and this is not. Self-publishing from Markdown is the whole route if you want to judge it.

So which one?

• Mac, formatting only, want it right without learning anything — Vellum.
• Windows, Linux or Chromebook — Atticus. There is no second option.
• Want writing and formatting in one purchase — Atticus.
• Complex interiors and no patience for checking — Vellum.
• Already write in plain text — neither; export straight to PDF and EPUB.
• Cannot decide and own a Mac — use Vellum's trial on your real manuscript. It costs nothing and answers the question in an evening.

Frequently asked questions

Is Vellum worth the price? For a Mac owner publishing more than one book, usually yes — it is a one-off cost against an afternoon of formatting per title, and the output needs less checking than anything else in the category. For a single book you may never repeat, it is a lot against what self-publishing otherwise costs.

Can I run Vellum on Windows? Not natively, and the workarounds are a rented cloud Mac or a licence-violating virtual machine. Treat it as Mac-only and pick Atticus instead.

Does Atticus replace Scrivener? For many people, yes. It is weaker at restructuring a complicated manuscript and stronger at producing a finished book, which is the opposite trade to Scrivener's.

Can I switch from one to the other later? Yes, through your manuscript rather than your project file. Export to DOCX or EPUB and import that; you will redo the design, because neither reads the other's format.

Do either of them validate the EPUB? Not thoroughly. Both produce files that normally pass, and when one does not you are reading an EPUBCheck error yourself.