Ulysses vs Catalpas Atelier Scribe: Markdown Writing and the Full Publishing Pipeline

Ulysses vs Catalpas Atelier Scribe: From Pure Writing in the Apple Ecosystem to Cross-Platform and Publishing

Among the many Markdown writing tools, Ulysses has always occupied a particular position. It does not have Scrivener’s vast source-management apparatus, nor Notion’s treasure-chest of features, but it has perfected “one person sitting in front of a screen writing in peace” with a clarity few others match. Many long-time writers in the Apple ecosystem—bloggers, columnists, nonfiction authors, even novelists—use Ulysses as their main day-to-day tool.

Scribe focused writing environment — Catalpas Atelier Scribe · Writing environment

That position is not accidental. Ulysses’s Library structure lets authors keep every project, note, and snippet in a unified view, sorted automatically by Smart Folders, with Goals tracking daily word counts and deadlines. Its editor interface is exceptionally restrained, keeping anything inessential out of view. Over many years, Ulysses’s sync among Mac, iPad, and iPhone has almost never failed—that stability is itself the kind of quality indie authors value most.

But Ulysses’s design center has always been “the writing stretch of the road.” It makes the manuscript comfortable to write and the library well organized, but when the manuscript matures and needs to move toward final e-book or printed-book form, Ulysses leaves that work to the next runner. It exports PDF, DOCX, EPUB, and HTML, but those exports are closer to “good enough to hand to an editor or a blog” than to “ready to ship to KDP or into a press.” What if you write in Chinese or Japanese and need vertical typesetting or annotation? What if a Windows laptop or Linux workstation sits among your work devices? What if you want to see, while writing, what the manuscript will look like printed, rather than shuttle it into a second piece of software afterward?

These are the questions Catalpas Atelier Scribe sets out to fill in. It does not propose to compete with Ulysses on the purity of the writing experience—that is the result of Ulysses’s years of polish—but it extends the same Markdown-centered writing experience to platforms beyond Apple, and puts e-book and print-ready PDF export inside the same application.

This article moves across four dimensions—platform and data ownership, coverage of finished output, the coupling between writing and layout, and pricing—to help you decide which tool or combination fits your project. The two tools share quite a bit in writing experience, so the real differences usually land in “what happens after writing.”

Platform and Data Ownership: Apple Ecosystem vs Native Three-Platform

Ulysses is an Apple-ecosystem application, covering macOS, iPadOS, and iOS. This is not a meaningless restriction but an extension of its product philosophy—concentrate engineering resources on Apple platforms so that Mac-to-iPad sync, iOS input-method cooperation, and Apple Pencil integration are all polished to a high level. Many long-time Ulysses users draft on iPad, revise on Mac, and add a sentence or two on iPhone whenever it occurs to them—that all-Apple device continuity is one of Ulysses’s core values.

But that focus also means a rigid boundary. If you use Windows, if your writing laptop is Linux, if Mac is only a backup or not present at all in your work environment, Ulysses is not on your option list. For authors outside the Apple ecosystem, that boundary removes Ulysses from the shortlist entirely.

Catalpas Atelier Scribe took a three-platform native route—Windows, macOS, and Linux all have native desktop applications, not an Electron-wrapped web page but software that runs natively on each platform. All tiers are uniform across the three, and file formats are cross-platform compatible. You can draft on a company-issued Windows laptop, continue editing at home on a Mac, and finish print export on a Linux workstation—no format conversion at any point.

On data ownership, the two tools are philosophically close: “default to your machine.” Ulysses puts the library on iCloud by default for sync but supports External Folders to save your manuscript directly into Dropbox, a local folder, or elsewhere; Scribe by default saves Markdown files in any local directory, with an optional cloud sync entry point (Google Drive, etc.). Neither locks the author into a proprietary cloud.

There is one file-format difference worth noting. Although Ulysses is internally Markdown-based, its library uses its own extensions (Markdown XL) that encode chapters, tags, and notes as metadata into the text. If you export a manuscript to a standard .md file and open it in another editor, some of the extension syntax needs cleanup. Scribe uses standard Markdown files directly—each chapter is a .md, openable in any editor, committable to Git. This is not an oversight in Ulysses but a trade-off of its library structure.

The meaning of this distinction varies. For authors whose entire device setup is settled in the Apple ecosystem and who don’t plan to switch, Ulysses’s completeness may be the optimal answer; for authors with mixed device setups or those who want their manuscript preserved as open-standard plain text, cross-platform and format openness are design choices with real impact.

Finished Output: Good Enough to Send vs Ready to Ship to Print

Ulysses’s export capability is competitive among Markdown writing tools. It supports PDF, DOCX, EPUB, HTML, and other formats, with a set of Styles letting authors adjust fonts, colors, and layout. For handing manuscripts to editors, posting to a blog, or making a relatively simple e-book, Ulysses’s export is basically sufficient—which is why it serves a wide range from bloggers to nonfiction authors.

That said, Ulysses’s design trade-off is clear: it does not try to be a print layout tool. Its PDF output is not specifically optimized for the traditional print details of text frame, tracking, chapter opening pages, or facing-page binding, and its EPUB layout control leans toward Markdown’s automatic rendering rather than fine typesetting. This is not an oversight but a scope Ulysses drew from the start—take the author to the moment the manuscript matures, and the export capability is meant to “ship the manuscript out,” not “finish final layout inside Ulysses.”

Scribe chooses to fill in that pipeline. Plus offers EPUB 3 and grayscale/RGB print PDF export, covering most standard novel projects; Pro adds CMYK color space, ICC color profiles, custom print masters (facing-page setup, binding side, bleed toggles), custom font import and page templates, and full-page image backgrounds. The whole set has a single goal: after you finish writing, you don’t need to switch to another layout tool—Scribe itself can produce a print file you can send directly to KDP, IngramSpark, or a commercial printer.

The more striking gap is in CJK typesetting. Chinese and Japanese novels commonly require vertical layout; Japanese textbooks need furigana; Chinese classical works need pinyin and bopomofo—these are structural language requirements, not decorative extras. Ulysses’s support for CJK characters is character-level—it can let you enter and display these characters, but vertical typesetting and annotation are not built in. Scribe supports CJK vertical typesetting across all tiers; Pro additionally provides Ruby annotation (pinyin, furigana, bopomofo) across e-book, document, image, and print PDF export formats.

This is not a criticism of Ulysses—it is a description of the two tools’ coverage. Ulysses puts its resources into a pure Markdown writing experience, which is its core value; Scribe puts its resources into the full pipeline of writing + print + CJK, which is its core value. They resonate strongly in writing but extend in different directions in “what happens after writing.”

Coupling Between Writing and Layout: Are the Writing Tool and the Layout Tool the Same?

Ulysses’s workflow is classic “write → export → lay out elsewhere.” Inside Ulysses you write with focus; when you need to, you switch to Smart Folders to check progress and use Goals to check word count—nothing about fonts, tracking, or pagination intrudes on the writing process. At export time, Ulysses converts the manuscript to a finished format, a clear stage switch from “creation” to “publication preparation.”

This staged design has its benefits. While writing, your view contains only the text, undistracted by layout details; subsequent layout work happens in Vellum, Atticus, InDesign, or another specialized tool. Two things, each handled with full attention, undisturbed by the other.

Scribe takes an integrated coupling path. It writes natively in standard Markdown, with text editing on the left and a live preview of the final e-book and print layout on the right. Every keystroke, every chapter heading adjustment, reflects instantly in the layout view on the right—what you write is what gets printed.

For some authors, that immediacy is a creative aid. When you write a key dialogue, you can immediately see its breathing rhythm on the page; when you rearrange a chapter, the layout of the whole book reflows. You sense what the reader will experience when they turn to that page, and that sense feeds back into your prose rhythm and paragraph composition. For other authors, that instant feedback is a distraction—they prefer to finish the story first and worry about how it looks later.

Neither workflow is absolutely better; what matters is which one suits you. Ulysses’s separated workflow fits creators who say “writing is just text—layout is another matter”; Scribe’s integrated workflow fits creators who say “I need to sense the final page while I’m writing.”

It is worth mentioning that Scribe also integrates reference management and LaTeX math support on top of the writing environment. Scribe Pro includes built-in integration with reference managers like Zotero, allowing citations from research notes to be inserted into the body and the bibliography automatically maintained; LaTeX equations come with live preview, suitable for nonfiction, textbook, or hardcore sci-fi authors. Ulysses, given its focus on general-purpose Markdown writing, does not specifically cover these scenarios—again a difference of trade-offs, not better or worse.

Pricing: Subscription vs Subscription Plus a Free Tier

Ulysses uses a subscription model: about US$5.99/month or US$49.99/year. Setapp subscribers can use Ulysses inside that subscription (along with several other Apple-platform tools). Ulysses’s subscription pricing has been broadly accepted by long-time Apple-ecosystem authors—steady updates, reliable sync, restrained feature evolution—all of which make authors willing to treat it as a long-term partner tool.

Catalpas Atelier Scribe also uses a tiered subscription model, but with a functional free tier. The Free tier offers the full basic Markdown writing and layout capability, sufficient to complete a project end to end; Plus unlocks EPUB and grayscale/RGB PDF export; Pro provides the full professional set—CMYK, ICC, custom print masters, ruby annotation, references, LaTeX, and more. Pro is currently US$79.99/year at early-bird pricing, with a regular price of US$129.99/year.

The main difference between the two models is coverage. Ulysses’s subscription serves the “pure writing” stretch—if your project ultimately needs professional layout capability, you’ll still pay for Vellum, Atticus, or another layout tool. Scribe’s subscription lets a single tool cover the full pipeline from writing to print, and you can start from Free to verify fit first.

Concretely: using Ulysses alone purely as a writing tool, three years total about US$150, averaging US$50 per year; if your actual workflow is Ulysses + Vellum full package, three years total about US$150 + US$250 = US$400, averaging about US$133 per year. Scribe Pro at early-bird pricing over three years averages US$80 per year—a single tool covering the full pipeline.

The right choice depends on whether you need a professional layout tool on top of the writing tool, whether your project needs CJK or color print capability, and whether you want to validate the tool’s fit from a Free tier first.

How to Choose

Ulysses and Scribe actually share quite a bit philosophically—both treat Markdown as the foundation of writing, both respect the author’s preference for a clean writing environment, neither tries to stuff the author into a treasure-chest of features. Their divergence is not about aesthetics or writing experience but about what happens “after writing.”

Ulysses may be the better fit if:

All your work devices are in the Apple ecosystem—Mac, iPad, iPhone
You need to keep a full library and sync available during lightweight writing on iPad or iPhone
You have already built years of library structure and writing habits on Ulysses and don’t want to migrate
Your project ultimately hands the manuscript to an editor or external layout designer, and you don’t take part in page work
You value the pure writing experience Ulysses has polished over many years

Catalpas Atelier Scribe may be the better fit if:

Your device combination includes Windows or Linux, or you expect to switch primary machines
You want your writing tool and your layout tool to be the same one, without shuttling to a second piece of software
Your project involves CJK languages and needs vertical typesetting or ruby annotation
Your project needs color print, hardcover, or commercial offset, with CMYK and ICC color management
You want to see, while writing, what the manuscript will look like when printed as a book
You need built-in support for reference management or LaTeX math
You want the manuscript preserved as standard .md files, committable to Git or openable in any editor
You want to start from the Free tier and confirm the tool fits your workflow before upgrading

Ulysses has established its own standard for Markdown writing in the Apple ecosystem, built on years of product refinement and word-of-mouth in the author community; that standard should not be lightly dismissed by any newcomer. Scribe’s goal is not to replace it—it is to offer an option in a similar spirit on the platforms and back half of the pipeline Ulysses chose not to enter: equally restrained in writing experience, equally respectful of the author’s attention, equally hopeful that “publish your own book” should not require relaying across multiple tools, only extending that spirit beyond the Apple ecosystem.

The best tool is not the one with the strongest spec sheet but the one that fits your project. If all your devices and workflow are settled inside the Apple ecosystem, Ulysses is worth trying first; if your project crosses some boundary of platform, language, or print scenario, Scribe is worth a serious look. Start from the Free tier, write a few chapters, and see whether it slips into your rhythm.

Further reading:

Try the same workflow in Scribe — start Free, Pro early-bird pricing locked for a limited time →