# Scrivener alternatives: 7 picks, by why you're leaving

> The right replacement depends on what drove you out: Compile, the learning curve, the sync, or the Windows version. Seven options mapped to those four reasons.

Canonical: https://buk.press/blog/scrivener-alternatives

18 September 2026 · 6 min read

If Compile is what broke you, move to a plain-text editor and export from the file instead (iA Writer, Obsidian or VS Code). If the complexity is the problem, Ulysses or iA Writer. If you want writing and formatting in one purchase, Atticus. If sync is the problem, anything that stores plain files in a folder. Scrivener's corkboard has no real equivalent, so if that is why you stayed, no alternative will feel right.

"Scrivener alternatives" is usually answered with a list of seven writing apps and no acknowledgement that people leave Scrivener for four quite different reasons. The tool that fixes one of them is often the tool that makes another worse.

So: work out which one you are, then read only that section. If you have not committed to Scrivener at all and are still choosing, [the writing tools compared](https://buk.press/blog/best-book-writing-software) is the post you actually want.

## Why do people leave Scrivener?

| Reason | What it feels like | What fixes it |
|---|---|---|
| Compile | Two hours to get a readable PDF | Leave export to a separate tool |
| Complexity | Nine panes, you use two | A minimal plain-text editor |
| Sync | Dropbox conflicts, iOS out of date | Plain files in a folder |
| Windows parity | Features arrive on Mac first | Anything cross-platform |

The fifth reason, "it feels dated", is real and is not a reason on its own. Every alternative below trades away something Scrivener does well, and an interface you dislike is a poor price to pay for losing the binder.

## If Compile is the problem

This is the most common one, and the most misdiagnosed. Compile is hard because it is trying to be a page-layout engine inside a writing tool, and the fix is to stop asking one application to do both jobs.

The move is to keep your manuscript as plain text and treat the finished book as a build output:

- **iA Writer**: one-off, every platform, writes Markdown, gets out of the way.
- **Obsidian**: free, plain Markdown in a folder you own, strong if the book grew out of notes. [Obsidian to PDF](https://buk.press/blog/obsidian-to-pdf) is the route.
- **VS Code**: free, real find-and-replace across the whole book, and version control, so you can recover the paragraph you cut on Tuesday. [Writing a book in VS Code](https://buk.press/blog/writing-a-book-in-vs-code).

All three write the same format, so the choice between them is taste rather than capability. The export then happens once, from the files, and it behaves the same way every time, which is the thing Compile never quite does. [Self-publishing from Markdown](https://buk.press/blog/self-publish-from-markdown) is the full path.

You do not have to leave Scrivener to stop using Compile. Compile to plain Markdown, and do the typesetting elsewhere. That keeps the binder and removes the part you hate, and it is worth trying before you migrate anything.

## If the complexity is the problem

You opened Scrivener for the corkboard, used a text pane and a folder list, and paid a learning curve for the rest.

- **Ulysses**: Apple only, subscription, a library rather than a file system, goals and a clean editor. The closest thing to "Scrivener without the parts you don't use".
- **iA Writer**: one-off, everywhere, deliberately fewer features. The floor is lower and so is the ceiling.

Both store Markdown, which matters more than it sounds: the file is readable in fifty years and every export tool understands it.

What you lose is the binder: the ability to see forty scenes as cards and drag them into a new order. Ulysses has groups and sheets, which is close; iA Writer has folders, which is not. If you restructure heavily, read the corkboard section below before you move.

## If you want writing and formatting in one place

**Atticus** is positioned fairly openly as the answer to this question: a writing environment plus a formatter, one purchase, runs in a browser on any operating system. It is a weaker drafting tool than Scrivener and a much better export, which is exactly the trade Compile refugees are looking for.

It is also the only option here that replaces both halves of what you are doing today. [Atticus versus Vellum](https://buk.press/blog/atticus-vs-vellum) covers it against the other formatting tool; [Vellum alternatives](https://buk.press/blog/vellum-alternatives) covers the formatting category on its own.

## If sync is the problem

Scrivener's iOS sync runs through Dropbox and produces conflicted copies when two devices disagree. The tools that never do this are the ones storing ordinary files:

1. **Obsidian**: a folder of Markdown, synced by whatever you already use.
2. **iA Writer**: iCloud or a folder, your choice.
3. **Google Docs**: nothing to sync, and [it labours past fifty thousand words](https://buk.press/blog/google-docs-vs-markdown).
4. **Notion**: fine for the raw material, awkward as a manuscript. [Notion to book](https://buk.press/blog/notion-to-book).

A book in one file per chapter, in a folder, in any sync service, has no proprietary format to conflict. That is the whole trick.

## If you are on Windows

Scrivener for Windows exists and trails the Mac version. Everything in this post runs on Windows except Ulysses, so the list is: iA Writer, Obsidian, VS Code, Atticus, Word.

Worth knowing: **Vellum does not run on Windows either**, so if you were planning to leave Scrivener for the Mac formatting tool everyone recommends, that door is closed too.

## What no alternative replaces

The corkboard, honestly.

Scrivener's binder plus corkboard (scenes as cards, drag to reorder, see the whole shape at once, split-screen against research) has no real equivalent outside it. Obsidian's canvas is close for notes and poor for a manuscript. Atticus reorders chapters and does not do cards.

If restructuring is central to how you work, the sober answer is to keep Scrivener for drafting and remove only the part that hurts. Compile to Markdown, or export to DOCX and [convert](https://buk.press/blog/word-to-markdown), then typeset from that.

## Getting your book out

Whatever you pick, migrate through a format both ends understand.

1. **Compile to Markdown or DOCX**, whole manuscript, one file per chapter if offered.
2. **Check the things that break**: [chapter headings](https://buk.press/blog/markdown-headings-book-structure), italics, scene-break markers, [front and back matter](https://buk.press/blog/front-matter-and-back-matter), footnotes.
3. **Keep the Scrivener project.** Archive it. It costs nothing and it is the only copy of your research pane.
4. **Recombine if you want one file**: [combining Markdown files](https://buk.press/blog/combine-markdown-files).

Then the export is a separate step that you own. [bukpress](https://buk.press/) is one way to run it: a Markdown manuscript in, a typeset PDF and a reflowable EPUB out, with the design saved once and reused, so a correction is one edit and one rebuild instead of another session with Compile.

## Frequently asked questions

**What is the closest thing to Scrivener?** Atticus for the writing-plus-export combination, Ulysses for the calm-library version of the same idea. Nothing matches the binder and corkboard together.

**Is there a free Scrivener alternative?** Obsidian and VS Code, both free and both plain Markdown. Neither is a book tool; both are used as one, and the export is a separate step either way.

**Can I import a Scrivener project into another app?** Not the project. The manuscript. Compile to DOCX or Markdown and import that. Your research, labels and snapshots stay behind, which is the argument for archiving the project rather than deleting it.

**Is Scrivener still worth using in 2026?** For a book you will genuinely restructure, yes. Nothing has replaced the binder. The common mistake is paying that learning curve for a book written straight through, where a plain-text editor would do.

**Do I still need a formatting tool after switching?** Unless you write in Markdown and export straight to PDF and EPUB, yes. [What a print-ready PDF requires](https://buk.press/blog/print-ready-pdf) is the part none of the writing tools finish.

**About this article.** Written by the team that builds bukpress, which turns Markdown into print-ready PDF and EPUB books. Spotted something wrong or out of date? Write to [support@buk.press](mailto:support@buk.press).

## Read next

Tools 17 September 2026 · 5 min read

## [Best book writing software: 7 picks, honestly](https://buk.press/blog/best-book-writing-software)

Scrivener if the book has a complicated structure you need to move around; Ulysses or iA Writer if you want to write in plain text and be left alone; Word if your editor works in Word; Obsidian if the book comes out of notes you already keep. All of them are for writing, none of them make a finished book, and choosing between them matters far less than finishing a draft.

[Read it](https://buk.press/blog/best-book-writing-software)

Tools 18 September 2026 · 6 min read

## [Atticus vs Vellum: which one, and why Mac decides it](https://buk.press/blog/atticus-vs-vellum)

If you own a Mac and only need formatting, Vellum: its defaults are better and its output needs less checking. If you are on Windows or Linux, Atticus, because Vellum will not run at all. Atticus also costs less and puts the writing and the formatting in one place, at the price of a rougher tool. Both are one-off purchases, and neither is an editor, a store or a printer.

[Read it](https://buk.press/blog/atticus-vs-vellum)

Tools 8 September 2026 · 6 min read

## [Scrivener to PDF: getting a book out of Compile](https://buk.press/blog/scrivener-to-pdf)

Compile to PDF directly when the book is plain prose and the default layouts are close enough; set the page size and margins in the Page Settings pane before anything else. When you need control over page breaks, running heads or an image-heavy interior, compile to Markdown or DOCX instead and typeset from there: Scrivener is a superb drafting environment and a blunt typesetter.

[Read it](https://buk.press/blog/scrivener-to-pdf)

## Write it in Markdown. Ship a book.

bukpress turns the file you are already writing into a typeset PDF and EPUB: your type, your covers, no watermark, ever.

[Get Lifetime, $27 once](https://app.buk.press/signup)