Vellum Review: The Book Formatting Software Serious Authors Actually Use

Why Serious Authors Choose Vellum: Practical Reasons Beyond "It Looks Pretty"

Vellum is not simply a shortcut to attractive interiors; it is a production tool that eliminates recurring friction in an author's release cycle. Consider three operational benefits that separate it from the alternatives and make it a professional choice:

• Predictable output: when you master Vellum's workflow, you can deliver retailer-ready files without last-minute fiddling or device-specific debugging. That predictability reduces launch-day risk.
• Repeatable branding: series-wide style templates and front-matter controls let you create a replicable brand identity across multiple titles with minimal effort.
• Time leverage: the hours saved per book compound across a catalog. Time saved equals more revisions, marketing, or new writing.

Below are advanced, actionable practices that experienced authors use when they incorporate Vellum into a serious publishing pipeline.

Advanced Vellum Techniques for Series Branding and Metadata (Actionable)

1. Establish a style master file

   • Create a dedicated Vellum project that contains only your series-level front matter, epigraph style, and preferred ornamental breaks. Export one book from that project as a "reference" and keep the Vellum project file as the style master.
   • Action: For each new book, import your manuscript into the master project (File > Import Manuscript). Immediately save-as with the book title, then replace placeholder front matter with the new manuscript. This preserves series consistency.

2. Embed metadata and series order correctly before export

   • Vellum allows you to set title, series name, and series number in the Book Info panel. Use consistent series-name casing and a numeric series number (not words) to ensure retailers display correct ordering.
   • Action: Before exporting, run a quick consistency check: open Book Info for each book in the series and verify exact string matches for series name.

3. Create a canonical chapter opener pattern

   • Choose one approach to chapter openers (e.g., drop cap + extra leading line, or none). Avoid mixing styles across a series. Vellum applies your choice globally, so set it once in Styles and leave it.
   • Action: Use "Styles > Chapter" and adjust Drop Cap and ornamental break settings. Export a device preview (iPhone + Kindle) to validate how drop caps wrap on small screens.

4. Use consistent front/back matter blocks

   • Create reusable blocks for author bio, newsletter sign-up, and author websites. Insert these as template pages into every book; Vellum can duplicate them so revisions propagate easily.
   • Action: Save these as files in a "Templates" folder of your writing project. Drag-and-drop into Vellum's Book Contents to add and reorder.

5. Automated cross-links for series bundles and boxed sets

   • For boxed sets or bundles, export the individual EPUBs first and then create a new Vellum project for the boxed set that includes extracted front matter promoting the series. This guarantees the boxed set has its own ISBN/metadata while reusing content.
   • Action: Export all singles, then in the boxed-set project create a consolidated Table of Contents and ensure front matter references the single titles with exact retailer URLs where available.

Real example: an indie thriller author I coached used a Vellum master file to format three books in a year. Initial setup took 90 minutes. Subsequent books were formatted in 30–45 minutes. The author reported consistent retailer displays and a 40% reduction in post-upload correction emails from readers about formatting inconsistencies.

Optimizing Print Exports: A Technical Checklist for POD Accuracy (Actionable)

1. Select the correct trim size first

   • Vellum offers presets for common trim sizes. Choose your target (e.g., 5.5" x 8.5") and don't change it after layout, or you will need to reflow images and check page counts.
   • Action: Match the trim size to your intended POD service (KDP Print or IngramSpark) before finalizing header/footer settings.

2. Check pagination for catchwords and widows/orphans

   • While Vellum does a good job with typographic defaults, run a quick manual pass on the generated PDF for widows/orphans near chapter breaks and critical paragraph transitions.
   • Action: Export the print PDF and use a PDF viewer's two-page spread to scan chapter starts and ends. Flag any orphan/widow issues, then adjust by adding a one-line tweak in the manuscript (extra line break before a heading) to influence pagination.

3. Embed fonts only when necessary and permitted

   • Vellum embeds fonts that are licensed and available on your Mac, but POD services sometimes reject embedded fonts that aren't licensed for embedding. Use standard book typefaces if you need guaranteed acceptance.
   • Action: Verify your font license and, when in doubt, switch to a common book font (e.g., Georgia or Times) for print exports to avoid KDP/Ingram font issues.

4. Image resolution and bleed

   • For interior images, export PNG/JPEG at 300 dpi at final print size. For bleed images, extend artwork 0.125" beyond trim edges and ensure filename clarity.
   • Action: In your image editor, set document size to final inches at 300 dpi, save using a filename that includes dimensions, then insert into the manuscript. Verify in Vellum's print preview.

5. Final file naming and version control

   • Use semantic versioning for outputs: BookTitle_v1_print.pdf and BookTitle_v1_epub.epub. Track ISBNs in a single metadata spreadsheet to avoid duplicates.
   • Action: After export maintain a "Releases" folder with dated subfolders and the export files. Keep one-line release notes for each export describing the purpose (proof, pre-order, wide retail).

Case study: a nonfiction author exporting a 250-page illustrated manual used the checklist above and caught two costly problems before upload: the cover bleed was insufficient for the selected spine width, and a proprietary display font lacked embedding rights. Fixing both pre-upload avoided a week-long reprint delay with IngramSpark.

The Problem With Formatting Your Own Books\\n\\nIf you have ever tried to format a manuscript in Microsoft Word and export it as an ebook, you already know the particular misery involved. Paragraph indents that disappear. Chapter headings that render differently on every device. Drop caps that look fine on your screen and catastrophic on a Kindle Paperwhite. The process is technically possible, but it is the kind of technically possible that makes you question your life choices.\\n\\nFor years, self-publishing authors had two options: pay a professional formatter several hundred dollars per book, or spend days learning the arcane rules of ebook CSS and print PDF production. Neither option was especially appealing.\\n\\nThen Vellum arrived, and for a significant portion of the author community, the formatting problem essentially went away.\\n\\n## What Vellum Actually Does\\n\\n[Vellum](https://store.vellum.pub?via=curt43) is a Mac-only application that takes your manuscript — typically a Word document or a plain text file — and converts it into beautifully formatted ebooks and print-ready PDFs. The interface is clean and intuitive: you import your manuscript, choose a style from Vellum's curated collection of book designs, preview the result on simulated device screens, and export.\\n\\nThe output formats include EPUB (for Apple Books, Kobo, Barnes & Noble, and most other retailers), MOBI (for Kindle, though Amazon now prefers EPUB), and PDF files sized for various print-on-demand trim sizes through services like KDP Print and IngramSpark.\\n\\nWhat sets Vellum apart from every other formatting tool is the quality of the output. The typography is genuinely beautiful — the kind of interior design you would expect from a traditionally published book. Ornamental chapter breaks, elegant drop caps, properly formatted front matter, running headers and footers: all of it handled automatically, and all of it adjustable if you want to customize.\\n\\n## The Learning Curve (Or Lack of One)\\n\\nOne of the most common things authors say about Vellum is that they were up and running within an hour of downloading it. That is not marketing copy — it is an accurate description of the onboarding experience.\\n\\nThe application is designed around a single workflow: import, style, preview, export. There are no hidden menus, no cryptic settings panels, no need to understand what an OPF file is or why your NCX is malformed. You make choices from clearly labeled options, and you see the results immediately in the preview pane.\\n\\nFor authors who are not technically inclined — which describes most authors — this is transformative. The software does not require you to think like a designer or a developer. It requires you to think like an author, which is exactly what you are.\\n\\n## Pricing: One-Time Purchase, Not a Subscription\\n\\nVellum uses a one-time purchase model rather than a subscription, which is increasingly rare in software and genuinely appreciated by authors who produce books over many years.\\n\\nThere are two tiers. The ebook-only license allows you to produce unlimited ebooks. The complete license adds print book production. Both licenses cover unlimited books — you pay once and use the software indefinitely, including all future updates.\\n\\nFor authors who produce multiple books per year, the math is straightforward. A single professional formatting job typically costs between $150 and $400. Vellum's complete license pays for itself within the first book or two, and then every subsequent book is formatted for free.\\n\\nThe one significant limitation is that Vellum is Mac-only. Windows users are out of luck, and there is no web-based version or Windows port on the roadmap. If you work primarily on a PC, you will need to look at alternatives like Atticus, which offers similar functionality on both platforms.\\n\\n## What Vellum Does Exceptionally Well\\n\\n**Ebook formatting** is where Vellum genuinely excels. The EPUB files it produces are clean, valid, and render beautifully across every major reading device and app. The reflowable text handles font size changes gracefully. Images are handled correctly. Tables of contents are properly structured. This is harder to achieve than it sounds — many ebook formatting tools produce technically valid files that still look wrong on certain devices.\\n\\n**Style consistency** is another strength. Once you have chosen a style for a series, every book in that series will have a matching interior design. For authors building a brand across multiple titles, this kind of consistency matters.\\n\\n**Speed** is perhaps the most practically significant advantage. A manuscript that would take a professional formatter two to three days to produce can be exported from Vellum in under an hour, including time to review the preview and make adjustments.\\n\\n## The Honest Limitations\\n\\nVellum is not the right tool for every book. **Complex nonfiction** with heavy use of tables, footnotes, sidebars, and custom layouts will push against the software's constraints. Academic books, textbooks, and heavily illustrated titles are better served by InDesign or a professional formatter.\\n\\n**Print interiors** are good but not quite at the level of Vellum's ebook output. The print PDF files are clean and professional, but authors with very specific typographic requirements — custom fonts, unusual trim sizes, complex page layouts — may find the options limiting.\\n\\nAnd again: **Mac only**. This is a real constraint for a significant portion of the author community.\\n\\n## How It Fits Into a Self-Publishing Workflow\\n\\nFor most independent authors, Vellum fits naturally into a workflow that looks something like this: write in Scrivener or Word, edit with a professional editor, format in Vellum, distribute through KDP and Draft2Digital. The tools complement each other well.\\n\\n[Draft2Digital](https://www.draft2digital.com/taciturnstudios), for instance, handles distribution to Apple Books, Kobo, Barnes & Noble, and dozens of other retailers from a single upload — which pairs naturally with Vellum's ability to export retailer-specific EPUB files in one click.\\n\\n## The Bottom Line\\n\\nVellum is the best book formatting software available for Mac users, and it is not particularly close. The output quality is exceptional, the interface is genuinely pleasant to use, and the one-time pricing model means it gets more economical with every book you produce.\\n\\nIf you are a Mac user who self-publishes, or who is considering self-publishing, [Vellum](https://store.vellum.pub?via=curt43) is one of the few tools in the author's toolkit that genuinely delivers on its promise. Download the free trial, import your manuscript, and see what your book could look like.\\n\\n## Further Reading\\n\\nFor authors interested in the craft and business of writing, C.V. Wooster's books offer a range of perspectives — from the philosophical questions that underpin creative work to the practical realities of navigating institutions and systems. [The Chinese Room Argument: Decoding AI Consciousness & Understanding](/blog/the-chinese-room-argument-decoding-ai-consciousness-understanding) examines questions of mind and meaning that any writer grappling with AI tools will find relevant. *The Chinese Room* examines questions of mind and meaning that any writer grappling with AI tools will find relevant. *Middle-Finger Management* offers a wry look at the organizational dynamics that writers navigating traditional publishing will recognize immediately. For a dive into the ethical considerations that might arise with increasingly sophisticated AI in creative fields, consider reading about the [Trolley Problem & Self-Driving Cars: Real-Life Ethics Unpacked](/blog/trolley-problem-self-driving-cars-real-life-ethics-unpacked).\\n\\n## Tools & Hardware That Complement a Vellum Workflow (Practical Recommendations)\\n\\n- For Mac hardware: aim for a recent MacBook or iMac with an SSD and at least 16 GB of RAM if you publish frequently and work with large image files. Faster export times and responsive previews reduce friction.\\n- For reading-device QA: I recommend keeping at least one physical test device. A Kindle Paperwhite is inexpensive, ubiquitous among readers, and useful for quick checks. Buy here (affiliate): https://www.amazon.com/dp/B08N36XNTT/?tag=seperts-20\\n- For distribution and retail copies: maintain accounts on KDP and Draft2Digital and a spreadsheet that records ASINs, ISBNs, and upload dates. This single source of truth will save you headaches during promotions and box-set assembly.\\n\\nInternal note: if you buy author merchandise or resources from the site's store, visit /shop. For more essays and technical guides, browse the /blog.\\n\\n## QA and Release Checklist — Pre-Upload (Actionable)\\n\\n1. Export EPUB and open in multiple readers: Apple Books, Kobo Previewer, and Kindle Previewer (use Amazon's new EPUB support).\\n2. Validate EPUB with epubcheck or an online validator to catch structural errors.\\n3. Check the Table of Contents links: click each entry on two devices.\\n4. Validate image resolution and bleed in the print PDF.\\n5. Confirm metadata: author name spelling, series title, series number, ISBNs, keywords, and categories.\\n6. Run a small sample: upload the EPUB to a private distributor account (Draft2Digital allows pre-publication uploads) and use their preview to simulate retailer rendering.\\n7. Finalize filenames and update the release spreadsheet.\\n\\nActionable tip: build an automated “post-export” folder script (a simple shell or Automator workflow on Mac) that renames files to your semantic versioning scheme and moves them into a dated release folder. This reduces human error at the upload stage.\\n\\n## Integrating Vellum With Professional Services (Expert Guidance)\\n\\n- When to hire a formatter anyway: if your book requires complex tables, appendices, endnotes with cross-references, or unusual visual layouts, export from Vellum but consider a final pass by a formatter experienced with InDesign.\\n- Collaborating with cover designers: request spine width from your final Vellum print PDF page count and specific font metrics before the cover is designed. This avoids iterative cover reflows.\\n- Using beta readers for format feedback: include a formatting pass in your beta round. Ask beta readers to report on things like orphaned lines, chapter heading breaks, and image placement across devices.\\n\\nCase study: a memoirist used Vellum for ebook formatting but contracted a formatter to produce an InDesign version for a limited-edition print run with coated paper and heavy image pages. The hybrid approach saved money while ensuring the special edition met high production standards.\\n\\n## Frequently Asked Questions\\n\\n### Is Vellum worth it for an author with only one book?\\nYes — if you plan to publish that book in multiple formats (ebook and print) and value control and speed, Vellum can pay for itself relative to a one-time formatter fee. The time savings and reliable output matter: you can iterate layouts and re-export quickly without paying per-change fees. If the single book is complex (many tables, footnotes), evaluate a professional formatter for the print edition, but use Vellum for the ebook to get a clean EPUB quickly.\\n\\n### Can I use Vellum files with KDP and IngramSpark without additional edits?\\nTypically yes for standard fiction and trade nonfiction. Vellum exports PDF files formatted to common trim sizes that upload directly to KDP Print and IngramSpark. However, for titles with strict typographic requirements, specialty trim sizes, or chapter-based image bleed, you should proof the print PDF and order a physical proof before approving wide release.\\n\\n### I use Windows. Are there recommended alternatives that match Vellum’s quality?\\nWindows users should evaluate Atticus (cross-platform web app) and professional formatting services. Atticus provides many Vellum-like features and a browser-based workflow. For maximum control or highly bespoke interiors, InDesign is the industry standard but has a steeper learning curve.\\n\\n### How do I handle version control and backups of Vellum projects?\\nUse the macOS file system the same way you would for manuscripts: keep Vellum projects in a versioned "Releases" folder, use dated subfolders, and back up to a cloud service (iCloud, Dropbox, or a dedicated backup). For more robust version history, use Time Machine locally or a Git-based approach for plain-text manuscripts; exported Vellum project files can then be archived after each release.\\n\\n### Are there common pitfalls authors should avoid when using Vellum?\\nYes. Avoid importing poorly cleaned Word files — stray styles, manual tabs, and inconsistent use of Heading styles create odd edge cases. Also, do not rely on a single device preview; test on at least two different readers. Finally, be cautious about fonts and licensing for print: confirm embedding rights before final print exports.\\n\\n---\\n\\nIf you'd like, I can prepare a downloadable pre-export checklist tailored to your next manuscript (Word/Scrivener source) and a sample Vellum master project structure you can import. Also available: curated guides and signed copies in the store at /shop, and more in-depth essays in the /blog.

Automating Vellum Workflows on macOS (Actionable, Expert-Level)

Automation reduces repetitive manual steps and removes human-error points during formatting and release. Below are concrete, reproducible Automator / shell / Keyboard Maestro patterns used by professional indie publishers.

1. Automator Folder Action: Post-export file normalization

• Purpose: Automatically rename and move Vellum export files into your Releases folder and append semantic versioning.
• Steps:
  1. Open Automator -> New -> Folder Action. Choose the folder where you export files from Vellum (e.g., ~/Desktop/VellumExports).
  2. Add "Run Shell Script" (pass input as arguments) with this script:

     for f in "$@"; do
       base=$(basename "$f")
       dir=~/Documents/Publishing/Releases/$(date +%Y-%m-%d)
       mkdir -p "$dir"
       # Normalize spaces, append timestamp
       new="${base%.*}_v1_$(date +%s).${base##*.}"
       mv "$f" "$dir/$new"
     done
     

  3. Save. Any EPUB/PDF you export to the watched folder will be moved and renamed automatically.
• Example: A paperback PDF exported as "MyBook.pdf" becomes "MyBook_v1_1627554321.pdf" in ~/Documents/Publishing/Releases/2026-07-28/.

2. Keyboard Maestro Macro: Batch-validate EPUBs with epubcheck and open previews

• Purpose: Run epubcheck, open the file in Apple Books and Kindle Previewer, and copy the file path to clipboard.
• Components:
  • Trigger: Hotkey (Ctrl + Option + Cmd + E).
  • Actions:
    • Prompt for file or folder.
    • For each EPUB: run shell action: /usr/local/bin/epubcheck "$KMVAR_File"
    • If output contains "ERROR", show notification and open the HTML report.
    • Otherwise, open with "open -a 'Books' "$KMVAR_File"" and "open -a 'Kindle Previewer' "$KMVAR_File"".
• Why: This saves the cycle of running validation, waiting, and manually opening multiple readers.

3. Hazel rules for cover/version control

• Hazel (Noodlesoft) monitors folders and applies rules. Add a rule:
  • If Kind is PDF and Name contains "cover", then:
    • Run shell script to extract PDF dimensions (using pdfinfo) and write a small text file that you can reference when ordering proofs from IngramSpark or KDP.
• Real-world benefit: When your designer sends multiple cover variants, Hazel standardizes filenames to include spine width and ISBN automatically, avoiding a common cover/orientation mismatch.

4. Example macro + Automator integration for boxed sets

• Workflow:
  1. Export all single-title EPUBs from Vellum into a folder.
  2. Run a Keyboard Maestro macro that zips them into a folder and creates a CSV of titles/ASINs.
  3. Automator picks up the CSV and uses a short Python script to generate simple HTML landing pages for your boxed set marketing (title, blurbs, retailer links).
• Why: The boxed-set project often needs exact retailer links and an export manifest. Automating this reduces copy errors and assures consistency between Vellum metadata and marketing pages.

Tools to install

• epubcheck (Java-based): https://github.com/w3c/epubcheck — run locally for strict validation.
• Kindle Previewer: Amazon's official preview tool (for checking Kindle-specific quirks).
• Keyboard Maestro and Hazel: paid Mac utilities but widely used by professional authors and small presses.

External resources:

• EPUB standards & validation: epubcheck on GitHub (industry tool) — https://github.com/w3c/epubcheck
• Practical guidance on file naming and metadata best practices: Library of Congress metadata basics — https://www.loc.gov/ (see their guidance on bibliographic metadata for reference)

Advanced EPUB Validation and Retailer-Specific Tweaks (Actionable)

Ebook distribution isn't one-size-fits-all. Retailers have subtle expectations: Amazon tolerates certain CSS overrides differently than Apple Books. The following checklist and tweaks are used by small presses to reduce post-upload issues.

1. Run epubcheck and interpret the most common errors

• Output categories: ERROR, WARNING, INFO.
• Common errors to fix immediately:
  • Missing/incorrect manifest entries (fix by ensuring images are referenced exactly).
  • Broken internal links in the ToC (fix by repairing anchors in source manuscript).
• Action: Always keep a copy of the epubcheck HTML report alongside the EPUB in your release folder.

2. Retailer-specific preflight

• Apple Books:
  • Use Apple Books Preview or send the EPUB via iTunes Producer if you're using the Apple pipeline. Check for fixed-layout issues if your book contains complex imagery.
• Amazon (KDP):
  • Use Kindle Previewer (latest) and upload an EPUB directly; check the "look inside" output. Amazon's handling of cover images and first-page break sometimes differs. For series with back-matter links, verify that Amazon's annotated "also by" and "Look Inside" places don't disrupt your intended sequence.
• Kobo/B&N:
  • Use their provided previews or Draft2Digital's preview if publishing wide. Kobo's epub engine has historically been more forgiving of CSS but tests differently on the Kobo Clara vs. Kobo Libra.

3. CSS and font fallbacks

• Action: Avoid embedding decorative fonts that don't have explicit embedding rights. Instead:
  • Set font-family fallbacks in the EPUB's CSS (Vellum handles this internally, but confirm for print exports).
  • For EPUB: rely on user-agent fonts for body text; use embedded fonts only for small ornamentals (chapter drops, headers) where licensing is confirmed.

4. Accessibility checks

• Why: Retailers increasingly expose accessibility metadata and features. Accessible EPUBs expand marketplaces (libraries, educational channels).
• Actionable steps:
  • Ensure images have alt text in your manuscript source; Vellum will carry alt text into the EPUB manifest.
  • Run EPUB Accessibility tools (Ace by DAISY Consortium) if you plan to distribute to library markets. More info at https://daisy.org/ (industry org).

5. Example: How a launch went smoother because of retailer tweaks

• Context: A midlist nonfiction author used Vellum for ebook and PDF and initially uploaded to KDP without checking Kindle Previewer. Amazon's internal processing changed the cover sizing and the first chapter break. The team re-ran the EPUB through Kindle Previewer, identified a missing empty page before the table of contents, and re-exported. The re-upload avoided inconsistent "Look Inside" appearance and prevented early negative reader feedback.
• Practical tip: Always upload to the retailer and use their preview tool prior to the release date even if you validated locally.

Authoritative references:

• EPUB validation and standards: epubcheck (GitHub) — https://github.com/w3c/epubcheck
• Accessibility guidance for publications: DAISY Consortium — https://daisy.org/

Vellum in Hybrid Publishing: InDesign, Professional Formatters, and Special Editions

Vellum is excellent for standard trade fiction and many nonfiction titles, but hybrid publishing (mix of mass-market ebook, trade print, and premium special editions) often demands mixed toolchains. Here's an expert guide for integrating Vellum into a hybrid pipeline.

1. Split responsibilities and use each tool where it’s strongest

• Vellum: Ideal for ebooks and straightforward print-ready PDFs.
• InDesign: Necessary for heavy typographic control, advanced image placement, multi-column layouts, and premium paperback/hardcover editions.
• Professional formatter: Use when you need precise control over endnotes, cross-references, or long tables that Vellum cannot manage elegantly.

2. Concrete workflow for a hybrid release

• Step 1: Finalize manuscript in Word or Scrivener. Use styles consistently (Heading 1 for chapters, Heading 2 for major subheads).
• Step 2: Edit and proofread; create a copy labelled "For Formatting".
• Step 3: Import into Vellum for ebook export; perform EPUB validation and retailer previews. Export EPUBs and basic print PDF proofs for KDP/Ingram.
• Step 4: If a premium print edition is planned (hardcover, special paper, footnotes with margin references), hand off the "For Formatting" file to an InDesign pro. Include a Vellum-generated PDF as a reference for chapter flow and ornamentation preferences.
• Step 5: Use the InDesign master to produce the limited-run print files; use Vellum outputs for ebook distribution and regular POD versions.

3. Communication checklist for working with a formatter/designer

• Provide:
  • Vellum print PDF (for page-count reference and ornamental style).
  • Exact trim size and paper type.
  • Final page count from Vellum (to determine spine width).
  • Licensing info for fonts (copy of purchase or license text).
  • A brief style guide: drop-cap policy, chapter opener choice, epigraph treatment.
• Example: When commissioning a small press to produce a cloth-bound edition in Seattle at a boutique bindery, the designer required the Vellum print PDF to confirm decorative chapter-start art; the InDesign version then expanded the decorative elements into higher-resolution artwork suitable for letterpress embossing.

4. Cost control and decision criteria

• Do not use InDesign for formats that Vellum handles well unless there's a clear visual or functional requirement.
• Spend budget on design and binding only when the premium edition will have a market (collectors, signed copies, bookstore placements). For most backlist titles, Vellum plus a POD service suffices.

References and industry reading:

• Practical industry perspective on indie tools and publishing economics: Publishers Weekly — https://www.publishersweekly.com/
• Copyright, ISBN, and deposit guidance: U.S. Copyright Office — https://www.copyright.gov/
• University library resources on digital publishing and metadata (useful for metadata best practices): Purdue OWL for style and manuscript prep — https://owl.purdue.edu/

Internal resources

• For production assets or special editions, see /shop and consult the consult page in /blog for deeper essays on print production and marketing strategy.

Frequently Asked Questions

How do I prepare a Word document to import cleanly into Vellum?

Start by stripping free formatting: remove manual tabs and multiple spaces, use paragraph styles rather than manual bold/italic calls for headings, convert special characters to standard Unicode (curly quotes are fine), and ensure images are inline (not floating). Use Heading styles consistently: Heading 1 for chapter starts, Heading 2 for subsections. Export as .docx from Word or as plain .rtf if issues persist. If your Word file contains tracked changes, accept/reject them before importing.

Can Vellum handle books with endnotes and academic citation needs?

Vellum supports endnotes and basic footnote functionality for ebooks, and endnotes are exported into the EPUB manifest correctly. However, for academic books that require complex cross-references, numbering schemes, bibliographies with strict citation formatting (Chicago with specific local rules), or footnotes placed as sidebars, InDesign or LaTeX workflows are preferable. A common hybrid is: use Vellum for the ebook and a professional InDesign formatter for the print academic edition.

What are the best practices for fonts when planning both ebook and print?

For ebooks: keep body text in user-agent/readers' default fonts (they allow reader size adjustments), and reserve embedded fonts for headers/ornamentation only if licensing allows. For print: choose embedding-friendly fonts or confirm license permissions from your font vendor. If uncertain, use common book fonts (Georgia, Times) for print PDFs to avoid embedding-rejection issues with KDP and Ingram. Always keep a font license file in your release folder.

How do I handle translations or international editions with Vellum?

Create a separate Vellum project per language. Keep a shared style master (covering ornamentation, chapter opener policy, and front/back matter structure) and import the translated manuscript into that master. Be careful with metadata: use localized series titles, and keep a language-specific release spreadsheet (ISBN per language). Example: an author released English, Spanish, and German editions; each Vellum project had identical style choices but different front matter and localized author bios.

What proofing regimen do you recommend before sending files to a distributor?

1. Internal proof: export EPUB and open in Apple Books and Kindle Previewer.
2. Validation: run epubcheck and fix all ERRORs; be conservative about WARNINGs.
3. Retailer preview: upload to Draft2Digital (or your chosen aggregator) for a retailer-level preview.
4. Print proof: order a physical proof from KDP Print and/or IngramSpark and review actual paper, gutters, and spine calculations.
5. Beta reader formatting pass: give early readers the EPUB and a print proof (PDF) and request explicit feedback on typography, orphan/widow lines, and image placement.
6. Keep release notes and version numbers documented.

If you want, I can bundle the Automator scripts, a Keyboard Maestro macro template, and a Vellum master project structure as downloadable files to jump-start your setup. For production-ready templates and signed copies, visit /shop; for further technical essays and case studies, the /blog contains step-by-step guides and real-world author interviews.