Generate ebook chapters
How chapter generation works, how credits are consumed, and how to avoid wasting generation on a weak outline.
Generate after the structure is stable
Chapter generation is where most writing credits are spent, so review the outline first. If a chapter title is vague, the generated chapter is likely to be vague too.
The Write action targets the remaining chapters in one run. If the current credit balance covers only part of them, Scribora writes the affordable subset, preserves those chapters, and leaves the rest of the outline waiting for you to continue later.
Credit use
Scribora uses operation-based credits. The exact cost model is defined centrally by the product and exposed in the current pricing experience. Do not rely on old screenshots or third-party descriptions for credit values.
How a Write run behaves when credits are limited
Write normally targets all remaining chapters. Before dispatch, the product computes how many of those chapters the current balance can afford. A partially affordable run is allowed: the CTA and displayed credit cost are reduced to the affordable subset, the generated chapters stay in the project, and the remaining chapters wait behind the credit wall.
If no remaining chapter is affordable, the Write step becomes the finish-book purchase path instead of starting a job that cannot complete any work.
Generation runs in the background
The project records the active generation job and chapter progress while writing is running. The workflow explicitly tells the user that the job continues in the background, so a long chapter run is not tied to keeping the project page in the foreground.
Ready to use the workflow?
Start with a real source set. Scribora is most useful when you already have material worth turning into a book.