Blog · Guide
How to prepare a cookbook manuscript for formatting
Prepare recipes, images, measurements, front matter, and page features so a cookbook formatter can build a consistent interior.
Prepare a cookbook for formatting by making every recipe structurally consistent, separating high-resolution image files, deciding the print size and color approach, and marking every special page feature. The formatter should receive a stable manuscript and an asset map, not a folder of ingredients that still requires editorial decisions.
Why do cookbooks need extra preparation?
A text-heavy nonfiction book can often flow from headings and paragraphs into a standard template. A cookbook combines repeated recipe components, tables or lists, photographs, callouts, indexes, and pages readers may use with messy hands on a kitchen counter. Small inconsistencies become obvious once recipes sit side by side.
Formatting is also distinct from editing. A formatter arranges approved content into usable pages. They should not have to decide whether “tsp” means teaspoon in one chapter, repair missing oven temperatures, or guess which photo belongs to which recipe. If you are unsure which production stage comes next, compare editing, proofreading, and formatting.
Before handing off the book, settle four layers:
| Layer | Decisions to finish |
|---|---|
| Content | Recipe text, introductions, notes, and front/back matter |
| Consistency | Units, ingredient order, temperatures, timings, and labels |
| Assets | Images, captions, credits, and placement references |
| Production | Trim size, print color, ebook needs, and special page features |
Step 1: Freeze the recipe template
Choose one standard sequence and apply it throughout. A practical template might contain:
- Recipe title
- Short introduction
- Yield or servings
- Preparation and cooking time
- Ingredients in order of use
- Numbered method
- Storage, substitution, or serving notes
- Image reference
That list is an example. Your book may need equipment, allergen notes, difficulty, nutrition information, or regional measurement alternatives. The point is to decide once, label fields consistently, and avoid inventing a new structure for every recipe.
Optional fields should still have rules. For example, decide whether a missing storage note means “not applicable” or “not yet supplied.” Blank uncertainty tends to survive into proofs.
Step 2: Run a recipe completeness check
Read each recipe as an instruction set, not as prose. A useful check follows the order in which a cook will act.
- Confirm every ingredient used in the method appears in the ingredient list.
- Confirm every listed ingredient is used or explicitly marked for serving.
- Check quantities, units, temperatures, pan sizes, and timings.
- Check that steps are in chronological order.
- Define ambiguous cues. “Cook until done” is less useful than a visible or tactile sign.
- Check cross-references, such as “use the sauce on page X.” Leave page numbers for the formatter if pagination is not final.
- Standardize spelling and terminology.
Do not ask layout to conceal incomplete instructions. If a recipe needs substantive correction, return it to editing before formatting.
Step 3: Standardize measurements and style
Create a one-page style sheet. It can be simple, but it should answer recurring questions:
- Are measurements US customary, metric, or both?
- Will units be abbreviated?
- How will ranges, fractions, and temperatures appear?
- Do ingredient names use sentence case or lowercase?
- Are steps numbered?
- Which words appear in bold or italics?
- How are optional ingredients labeled?
- How are substitutions distinguished from required ingredients?
Apply the style rather than merely documenting it. Search the manuscript for common variants such as “tablespoon,” “tbsp,” and “Tbsp.” Decide which form wins. A final proofreader can catch stray inconsistencies, but a coherent source file gives the formatter a much better starting point.
Step 4: Organize photographs and illustrations
Keep original image files in a dedicated folder. Give them stable, descriptive filenames such as chapter-03-roast-tomatoes-01. In the manuscript, use an unmistakable placeholder such as [IMAGE: chapter-03-roast-tomatoes-01] and add the caption separately.
For every image, record:
| Item | What to provide |
|---|---|
| Filename | Exact match to the supplied file |
| Placement | Recipe opening, full page, step image, or flexible |
| Caption | Final approved wording or “no caption” |
| Credit | Required credit wording, if any |
| Crop concern | Anything important near an edge |
| Color priority | Whether color is essential to understanding |
Only use images you have the right to publish. Formatting cannot establish rights or repair an unsuitable source image. Avoid copying images into a word-processing file and then discarding the originals; embedded versions may be compressed.
Step 5: Choose the physical reading experience
Decide the intended trim size before design begins. A compact recipe book, a large photographic cookbook, and a workbook-style kitchen planner place very different demands on a page. Also decide whether the print edition is color or black and white, whether recipes may cross a page turn, and whether you want space for notes.
Amazon's official print preparation guidance explains trim, margins, and bleed, and recommends PDF for print. Your formatter needs the relevant production choices to create the correct file.
Do not choose a size only because another cookbook uses it. Consider ingredient-list length, typical method length, image orientation, and how the book will be held. Long recipes may need a different grid or type scale from short recipes.
Step 6: Plan navigation and reference pages
Cookbooks are rarely read only from front to back. Decide how readers will retrieve recipes. Possibilities include a contents page, recipe index, ingredient index, dietary labels, chapter dividers, and running heads.
Build the source list for any index before handoff, even if page numbers will be generated later. For an ingredient index, decide whether “bell pepper” and “red pepper” should be combined. For dietary markers, define exactly what each icon or label means and verify every assignment.
Front and back matter may include a title page, copyright page, introduction, equipment notes, measurement guide, acknowledgments, sources, and author information. Supply final wording and put the sections in the intended order.
Step 7: Treat print and ebook as separate outputs
A print PDF preserves a designed page. A reflowable ebook allows text to adapt to a device and reader settings. KDP lists EPUB and KPF among supported ebook formats. Do not rely on the old MOBI workflow.
Ask these questions for the ebook:
- Can every recipe be understood without a fixed two-page spread?
- Will tables remain readable on a small screen?
- Does navigation link to chapters or individual recipes?
- Are image captions attached to the right images?
- Do callout boxes make sense when linearized?
A design can share a visual identity across formats without forcing the ebook to imitate a printed page.
Step 8: Package the handoff clearly
Create one delivery folder containing the final manuscript, image folder, style sheet, asset map, production brief, and any permissions or credit text the formatter needs. Mark older drafts clearly or remove them from the handoff folder so nobody formats the wrong version.
Include a short list of known exceptions. For example: “Recipe 24 has no photograph by design,” or “The conversion table must appear before Chapter 1.” Explicit exceptions prevent well-meaning normalization from changing an intentional feature.
Breakthrough Publishing offers Custom Formatting for cookbooks and other designed interiors. Its stated scope includes a print PDF and an editable source when applicable. That service is separate from proofreading and content editing, so the preparation steps above still matter.
Step 9: Review the proof as a reader
When the first proof arrives, inspect it systematically rather than reading only for typos.
- Check the contents and every navigation link.
- Compare image placements against the asset map.
- Check recipes that run longer or shorter than average.
- Look for stranded headings and awkward page turns.
- Confirm units, fractions, symbols, and accented characters survived.
- Inspect pages at actual printed size.
- Test the ebook on more than one screen size if you are producing one.
Record corrections by page and heading, with one instruction per issue. Avoid vague notes such as “make this nicer.” State the problem and desired result.
A clean cookbook handoff does not mean the project can never change. It means editorial decisions are visible, assets are traceable, and the formatter can concentrate on hierarchy, readability, and production quality.
Questions people ask
Should cookbook photos be placed inside the manuscript?
Use clear placeholders in the manuscript and provide organized original image files unless your formatter requests another method.
Do all recipes need the same structure?
A consistent structure makes the book easier to format and use, even when some recipes need optional fields.
Should I choose trim size before formatting?
Yes. Trim size and intended print features affect the page design, image space, and final page count.
Can an ordinary reflowable ebook preserve a complex cookbook layout?
Not always. Reflowable ebooks adapt to readers' screens, so design print and ebook experiences around their different constraints.
More from the blog
- Question
How to check a manuscript for missing chapters and repetition
Audit a manuscript against its promise, outline, cross-references, and repeated ideas before editing and formatting.
- Comparison
Free KDP ISBN vs your own ISBN when using a second printer
Choose an ISBN before adding a second print service, with checks for imprint details, edition identity, and an already-published KDP paperback.
- Question
Do I need to tell KDP my book uses AI-generated content?
Learn when KDP asks you to disclose AI-generated text, images, or translations and how to audit a mixed-origin book.