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.
The morning light came through the archive windows at an angle that made the dust visible above the maps.
Clara unfolded the survey sheet along its oldest crease.
Fresh product demonstration matched to the job behind this search.
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 manuscript, design system, edition decisions, validation, and generated files stay connected so a correction never requires rebuilding the production chain.
Start in the book-aware editor or bring in an existing DOCX, then keep the complete manuscript editable in the production project.
Shape volumes, parts, chapters, sections, front matter, back matter, notes, images, tables, poetry, letters, and special blocks.
Apply professional edition defaults, refine element types, and reserve local overrides for genuine exceptions.
Judge real composed print pages and deliberate ebook behavior while the source remains editable.
Resolve blockers and reviews before producing print PDF, EPUB 3, or an editable DOCX handoff.
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. The working project remains local, the core workflow does not depend on a browser editor, and the retained source stays available for later corrections and editions.
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.