Table of Contents
If you’re on Windows and you’ve been eyeing Vellum, yeah… I get why it feels annoying. Vellum is Mac-only, so you can’t just install it like a normal app. Still, there are a few workable paths, and I’ve seen plenty of Windows authors make it happen without buying a Mac just for one piece of software.
In my experience, the “right” option depends on how often you’ll use Vellum, how big your manuscript is, and how picky you are about layout consistency. So instead of vague promises, I’m going to lay out the real workflows: cloud Mac (like MacInCloud), a virtual machine approach (with the practical gotchas), and then the alternatives if you’d rather not deal with any of that.
Key Takeaways
- Vellum won’t run natively on Windows. To use it, you need either a remote Mac service (cloud) or a macOS virtual machine.
- Cloud Mac is usually the easiest route. Services like MacInCloud let you log in from Windows and run Vellum in a browser/remote session. Pricing commonly starts around $1/hour, but your total cost depends on how long you format and export.
- Virtual machines are possible, but messy. You’ll need VirtualBox/VM tooling, enough RAM/storage, and you may run into performance issues—plus macOS licensing/legality considerations.
- Alternatives can be “good enough” (or better for some people). Atticus runs natively on Windows and is typically cheaper than cloud Mac usage for many authors.
- Think about export fidelity and automation. Vellum’s style automation and preview workflow are hard to fully replicate. Word is fine for basic formatting, but it won’t mimic Vellum’s chapter/style-driven setup.
- Don’t forget the hidden costs. Cloud time, internet reliability, and any extra software for VM/remote access can add up fast.
- Pick based on your workflow. If you’re formatting a short book once or twice a year, cloud might make sense. If you’re publishing often, a Windows-native tool usually wins.
Vellum only works on Mac, with no official Windows version. As of 2025, there’s still no native Windows or PC build. So if you want Vellum’s formatting and export workflow, you’re basically choosing between (1) running it on a Mac environment you access remotely, or (2) running a macOS virtual machine on your Windows PC.
8. Cost and Pricing Factors for Windows Users
Since Vellum is Mac-only, you’ll pay in one way or another. Either you pay for cloud Mac time, or you pay with hardware and setup effort if you try a VM.
Cloud Mac (example: MacInCloud) — what you’ll actually spend
Services like MacInCloud rent access to a Mac server. You log in from your Windows machine and run Vellum in that remote environment.
Pricing is often quoted as starting around $1 USD per hour, but here’s what matters: formatting and exports aren’t instant. If you’re doing a full workflow—import, style mapping, preview checks, table of contents, then EPUB/PDF/MOBI exports—you might burn 2–6 hours depending on how clean your manuscript is.
Quick budgeting example: If your plan averages $1.25/hour and you spend 4 hours total, that’s about $5 for that project (before any taxes/fees). If you spend 12 hours, it jumps to $15. Not crazy—but it can creep up if you’re constantly re-importing or troubleshooting.
Virtual machine — the “hidden” costs
Yes, you can set up a macOS virtual machine on Windows (commonly using tools like VirtualBox). But in my experience, this is where things slow down: drivers, graphics acceleration, storage space, and stability.
To make it usable for ebook formatting, you’ll want at least:
- RAM: 16GB minimum (32GB is nicer)
- CPU: a decent multi-core processor
- Storage: 60–100GB free for the VM disk (and room for exports)
- Time: expect setup to take hours, not minutes
Also, there’s the legal side: macOS licensing is generally intended for Apple hardware. I’m not here to give legal advice, but it’s something you should factor in before you commit to a VM setup.
What you’re comparing against (Atticus and other Windows tools)
Vellum is typically around $250 USD for a one-time purchase. If you’re only using it occasionally, cloud Mac may be cheaper than buying a Mac. But if you publish regularly, buying into a Windows-native workflow can be smarter.
For instance, Atticus is commonly priced around $147 USD (varies by promotions), and it runs on Windows without you needing cloud time or a VM. That alone can save you the hassle of remote sessions and file transfer friction.
And if you’re comparing day-to-day productivity: cloud Mac often adds friction around clipboard, drag-and-drop, and uploading/downloading files. You can work around it, but it’s still a tax on your workflow.
9. Recommendations for Windows Authors
If you’re on Windows, I’d pick based on how you work—not just what sounds “closest to Vellum.” Here’s how I’d decide.
If you really want Vellum: use cloud Mac (and plan your file transfers)
When I’ve seen authors succeed with Vellum from Windows, it’s usually because they treat it like a two-machine workflow: Windows for writing and prep, cloud Mac for formatting/export.
Here’s a simple workflow that reduces rework:
- Prep your manuscript in a consistent structure first. Use clear chapter headings (e.g., “Chapter 1”, “Chapter 2”) and keep formatting simple.
- Import once, then iterate carefully. Every extra import can cost you time (and cloud hours).
- Keep exports predictable. Decide your target files up front—EPUB and PDF are common—and don’t keep switching formats mid-process.
- Save versions. Name exports like BookTitle_v01_epub, v02_pdf, etc. Otherwise you’ll lose track fast when you’re downloading/uploading.
- Check TOC early. Table of contents problems are the #1 “why is this broken?” moment for ebook files.
Limitations to expect: USB passthrough and perfect clipboard behavior can be hit-or-miss in remote sessions. If you’re relying on copy/paste for formatting notes or style text, you may need to upload/download files instead.
If you want a smoother Windows experience: Atticus is the closest “no drama” option
I like Atticus for Windows because it’s built for the platform you’re already on. You don’t need remote access or VM troubleshooting.
In particular, Atticus covers a lot of the “ebook formatting” needs people go looking for Vellum for—chapter detection, style control, and multiple export formats—without the Mac-only hurdle.
Where you might still notice differences: Vellum’s preview workflow and some of its automation feel very “hands-off” once you set things up. With Atticus, you still get automation, but you may spend a bit more time matching your exact typography preferences.
If you want to see how that plays out, you can check Atticus directly.
Word vs InDesign vs Scrivener (and what you’ll miss)
Microsoft Word is the easiest entry point. But it’s also the most manual when you move beyond basic formatting. If your book needs consistent chapter styles, smart TOC behavior, and clean ebook-ready output, Word can start feeling like you’re fighting the tool.
On the other end, Adobe InDesign is powerful, and Scrivener is great for drafting and organizing. But neither is a perfect “Vellum replacement” for the specific style/preview/ebook automation people love.
Here’s the practical tradeoff:
- Word: quick edits, but you’ll do more manual formatting cleanup.
- InDesign: professional layout control, but it has a steeper learning curve and is a bigger toolchain.
- Scrivener: excellent writing workflow, but formatting/export often needs extra steps depending on your publishing target.
Cost break-even: when cloud Mac stops being “cheap”
Here’s a rule of thumb I use: if you can finish a book formatting pass in under 4–6 hours, cloud Mac can be a reasonable spend. If you’re expecting to iterate heavily—multiple style revisions, lots of TOC fixes, experimenting with cover/PDF tweaks—your total cloud time can climb quickly.
And once your cloud spend approaches the cost of a Windows-native tool, it’s usually not worth the extra friction.
Whatever path you choose, one tip that saves time: get your manuscript structure solid before you format. Clean headings and consistent chapter breaks reduce the amount of rework in any ebook formatter.
FAQs
Vellum is designed as a Mac application, so it doesn’t run directly on Windows. Most authors look for it because of the formatting automation and ebook export workflow, but the software itself is still Mac-exclusive—so you’ll need a workaround if you want it on a Windows machine.
You’ve got two realistic options: use a cloud Mac service (like MacInCloud) or set up a macOS virtual machine on your Windows PC. Cloud is usually simpler, while a VM can be more flexible—but it takes more setup and can be less stable.
For Windows, many authors start with Atticus because it’s native and includes ebook-focused formatting tools. Microsoft Word is fine for basic formatting, while Adobe InDesign and Scrivener can work well for more advanced workflows—just expect a different setup and less “Vellum-style” automation.
In cloud sessions, the usual issues are permissions, missing fonts, or unstable connection. If Vellum fails to open, I’d try: logging out and back in, confirming your internet is stable, and checking whether the remote environment has the fonts you’re using (or whether Vellum is substituting them). Also, avoid long idle times—some remote sessions drop or lock.
Most of the time, exports are consistent—but differences can happen if fonts aren’t available in the remote environment or if you rely on specific typographic settings. Before you export your final version, do a “quick sanity check” export (even just 5–10 pages) to confirm heading styles, page breaks, and your table of contents.
I can’t give legal advice, but it’s worth reading Apple’s macOS licensing terms. In general, Apple’s licensing is meant for Apple hardware. If you’re considering a VM approach, make sure you understand the rules before you invest time and money into the setup.
