Local working files
Offline mode is not meaningful if the authoritative manuscript still lives in a vendor account. A local-first project gives the author a file that can be copied, backed up, versioned, and retained independently.
Cambric is offline-capable desktop book software for Windows and Mac. The working manuscript stays on your machine, the core writing and formatting workflow remains local, and print PDF and EPUB 3 come from a project you control.
One manuscript project stays editable while Cambric composes the print interior.
Offline capability matters most when it is paired with local ownership and useful output. A plain text editor works without internet but does not produce a book. Cambric combines the resilience of a local project with book-aware editing, live typeset pages, and final print and ebook export.
A buying-intent search should end in a decision framework. These are the tests that determine whether software will survive a real manuscript and remain useful after launch.
Offline mode is not meaningful if the authoritative manuscript still lives in a vendor account. A local-first project gives the author a file that can be copied, backed up, versioned, and retained independently.
Drafting, revision, formatting, preview, and export should not require a steady internet connection. Purchase validation and downloads may involve an online service, but producing the book should not feel like editing a website.
Collaboration sync is useful when you need it. For a solo author’s production master, it can also introduce duplicate versions, merge uncertainty, and account dependence. Local-first lets you decide which sync tool, if any, touches the project.
A book may need corrections years after release. The author should be able to open the source and regenerate files without reconstructing a browser workspace or discovering that an old online product changed direction.
The working project stays editable from first import through every later correction. Each output is generated from that source rather than becoming a new master.
Start chapters in Cambric or import a DOCX from Word, Google Docs, or a Scrivener compile. Preserve the manuscript you already have rather than rebuilding it for the software.
Review chapter boundaries, front matter, back matter, scene breaks, headings, emphasis, images, and other meaningful parts before they become layout problems.
Select a professional design direction and book settings. The template coordinates typography and recurring page rules across the complete manuscript.
Read the real composition, not a generic sample. Resolve manuscript-specific exceptions while the source remains editable and every later page can reflow safely.
Create the print-ready PDF and EPUB, inspect the artifacts, upload to the chosen retailers, and return to the same project whenever the book needs a revision.
The obvious use cases are travel, rural connectivity, and focused writing away from notifications. The deeper issue is dependency. When the only authoritative manuscript lives behind a login, access to your own book depends on authentication, service uptime, account status, product policy, and the company continuing to operate the workspace you chose.
A local project does not eliminate risk; it moves responsibility back to the author. You need backups. But those backups can use tools and locations you choose, and they remain legible as files you control. For a commercial creative asset, that is a meaningful distinction.
Keep the active Cambric project on your computer, then maintain at least two backups with one copy away from the machine. That can mean an external drive plus an encrypted cloud folder, a versioned backup service, or a private repository appropriate to your technical comfort. Local-first does not mean “stored in exactly one place.” It means you choose the replication system.
Use clear release folders for exported PDF and EPUB files, cover assets, retailer metadata, and the exact files uploaded. The Cambric project remains the editable source of truth; exports are release artifacts. That separation makes future corrections far less confusing.
Cambric is sold and licensed online, and the protected download page validates a license key before providing current installers. Those commercial steps necessarily involve a network service. The important boundary is the creative and production work: the manuscript project lives locally and the desktop app is designed around your machine rather than a browser document.
If real-time multi-author collaboration is the primary need, a cloud editor may be a better fit. If you are the person responsible for preserving, formatting, and reissuing the book, Cambric’s local-first model gives that responsibility a durable home.
Cambric is a desktop application for Windows and macOS. Your working files remain local, the core workflow does not depend on a cloud editor, and a one-time license keeps the production path available for the next title and the backlist after that.
Several products can appear for the same search while solving different stages of a book. This map keeps the comparison honest.
| Software category | Best at | Main trade-off | Use it when… |
|---|---|---|---|
| Cambric | Writing through professional PDF + EPUB | Focused on text-led book interiors, not every publishing job | You want a local, repeatable manuscript-to-book workflow on Windows or Mac |
| Specialist drafting apps | Planning, research, nonlinear composition | Final book production usually moves elsewhere | The difficult part is organizing and completing the draft |
| Word processors | Familiar editing and tracked-change collaboration | Manual, fragile print layout and inconsistent conversions | Editorial exchange matters more than final production |
| Browser formatters | Access on many devices and fast standard output | Cloud or account dependence and varying control | Convenience across devices is the first priority |
| Professional layout tools | Freeform control over every page and asset | Steep learning curve and more manual production | The book is illustrated, complex, or designed spread by spread |
Cambric does not replace developmental editing, cover design, ISBNs, retailer accounts, distribution, or marketing. It owns the interior-production layer and makes that layer reusable.
Cambric’s core writing, formatting, preview, and export workflow is local. Purchasing, downloading installers, and license-related services require internet access.
Cambric projects are local files on your machine. You choose where they live and how they are backed up.
No. You can place backups wherever you choose, including a cloud storage provider. The distinction is that Cambric does not require its own browser workspace to be the owner of the manuscript.
It reduces dependence on account and service availability, but safety still depends on good backups and device security. A local file with no backup is not resilient.
Yes. Cambric has desktop builds for 64-bit Windows, Apple Silicon Macs, and Intel Macs.