How to Format a Cookbook for Print and Kindle (2026)

Cookbook formatting is a different animal from formatting a novel or memoir. A cookbook has to survive splattered fingers, greasy thumbs, and a reader standing three feet from the stove. Every recipe needs a predictable structure, scannable ingredients, and method steps that never leave the cook guessing. Get it wrong and readers leave one-star reviews about typos in the oven temperatures. Get it right and your cookbook becomes the stained, dog-eared copy they reach for every week.

A well-formatted cookbook has to work twice: once as a physical object with margins, bleed, and photographs you can almost smell, and once as a Kindle eBook where the layout reflows and every image earns its place. This guide covers both, from recipe anatomy to print specs, food photography, Kindle pitfalls, and the recipe index serious cooks demand. If you already understand print vs. eBook formatting, cookbook formatting is that same discipline applied to a far more visual, far more fiddly kind of book.

Quick answer: Format every recipe with the same elements in the same order — title, headnote, yield, prep and cook times, ingredients in a clean list, and numbered method steps. Use 300 DPI images with bleed for print, and choose between fixed-layout and reflowable carefully for Kindle. Keep units consistent, add a recipe index, and always proof a printed copy by cooking from it.

The anatomy of a perfectly formatted recipe

Every great cookbook reads the same way from recipe to recipe, and that sameness is the point. A cook mid-recipe should never hunt for the oven temperature or wonder whether the serving count hides in a paragraph of prose. The standard professional structure is: recipe title, an optional short headnote, yield, prep and cook times, an ingredient list, and numbered method steps.

Titles should be descriptive and findable. “Weeknight Chicken and Rice” beats “Chicken Surprise” in a recipe index and in Amazon search alike. Use one consistent heading style for every recipe title.

The headnote is the sentence or two before the ingredients where you say why the recipe matters: a memory, a tip about where you first ate the dish, a warning that the dough needs an overnight rest. Keep headnotes short and set them in a distinct style, often italic, so the eye can skip them when the cook just wants the facts.

Yield, prep time, and cook time belong in a consistent spot, usually directly under the headnote. Format them identically every time: “Makes 4 servings”, “Prep: 15 minutes”, “Cook: 40 minutes”. Readers scan this block before committing, so never bury total time in the instructions. State resting, chilling, or proofing time separately: “Plus 2 hours chilling.”

The ingredient list is the heart of cookbook formatting. List ingredients in the order used, one per line, quantities first. Use consistent abbreviations — “tsp”, “tbsp”, “g”, “ml”, “oz”, “cup” — and never mix “1 cup” with “one cup” in the same book. Group ingredients under subheads when a recipe has components: “For the cake”, “For the frosting”. A well-set list lets the eye run straight down the amounts without the words getting in the way.

Number every method step, keep each step to one action, and always put the oven temperature and pan size in the step where the reader needs them. End each step where the reader can see progress: “Bake until golden, 25 to 30 minutes.”

Units, measurements, and conversions that never confuse

Few things destroy reader trust faster than inconsistent measurements. Decide at the start whether you use US customary, metric, or both, then enforce it on every page. Books for American home cooks usually use cups, tablespoons, and teaspoons with Fahrenheit. Books with an international audience increasingly give both — “1 cup (240 ml)” — though dual units lengthen ingredient lists and add pages and print cost.

Pick one abbreviation set and stick to it: tsp, tbsp, oz, lb, g, kg, ml, L. Tablespoon is “tbsp”, never “T” or “tbs”. Use true fraction characters (½, ¼, ¾) rather than slashed numbers, because “1 1/2” in bad light can be misread as “11/2”.

Follow the same pattern inside every ingredient entry: quantity, unit, ingredient, preparation note. “2 tbsp olive oil, divided” reads better than “Olive oil, 2 tbsp, some of it”. When every recipe follows this pattern, readers absorb amounts in a glance and spend their attention on the cooking.

A one-page conversion table — volume equivalents, weight equivalents, and an oven temperature chart (Fahrenheit, Celsius, Gas Mark) — turns your book into a reference readers keep. Place it in the front matter or an appendix and mention it in your introduction.

Food photography specs for print and Kindle

Food photography sells cookbooks, and the technical specs are non-negotiable. For print, every photo must be at least 300 DPI at its final printed size. A phone photo that looks crisp on your screen is usually 72 DPI, and it will print as a blurry mess. A full-page 8.5 x 11 inch hero shot needs at least 2550 x 3300 pixels — larger is always safe, smaller is never fine.

Color management is where amateur cookbooks quietly fail: your camera, screen, and printer all use different color spaces. Work in RGB while editing, but export print files in CMYK or use your printer’s conversion profile — food reds and greens shift dramatically between the two. Proof one physical copy before approving the run.

Any photo touching the page edge must extend 0.125 inches past the trim line on every bleeding side — without this bleed, trimming leaves a white sliver of unprinted paper. Keep text and important details at least 0.5 inches inside the trim line.

For Kindle the rules flip. Reflowable eBooks want screen-sized images — roughly 1200 pixels maximum width and modest file sizes — so the eBook does not balloon past Amazon’s delivery-cost thresholds. Oversized images trigger delivery fees that eat your royalty on every sale. Photos must also survive reflow: a caption must never detach from its photo, and a photo must never land in the middle of an ingredient list after the reader changes font size.

Choose either a single-column or a two-column grid and apply it consistently. Two-column layouts set the ingredient list in a narrow left column and the method in a wider right column — a classic magazine look that keeps everything for one recipe in view at once. Single-column layouts are calmer and better for recipes with long headnotes. Never mix both styles in the same book without a professional designer enforcing the rules.

A full-page chapter opener — “Mains”, “Baking”, “Desserts” — gives readers a breather and prime real estate for a full-bleed photograph. Add a short introduction: three or four sentences about the chapter and any equipment the reader should know about first.

A running head showing the chapter title on every page helps a cook with sticky fingers flip to the right section fast. Page numbers should be readable at arm’s length from the counter, and cross-references must use generated page numbers, never typed ones.

White space is an ingredient. Crowded pages are hard to cook from: fingers smudge, eyes lose their place, and a wall of text turns readers off before they start. Generous line spacing in the method steps, clear space around photographs, and margins wide enough for the book to open flat separate a professional cookbook from a cramped one. Consider a lay-flat binding, because a cookbook that will not stay open on the counter does not get used.

Kindle formatting: reflowable vs fixed-layout

Most cookbooks work best as reflowable eBooks. Text flows like any other eBook, readers can resize the font, and content adapts to phones, tablets, and e-ink Kindles, with photographs inline between recipes. It works on every Kindle device and is the format Kindle Create handles best.

Fixed-layout eBooks preserve your exact page design like a PDF, but only display properly on tablets and the Kindle app — on basic e-ink Kindles they are a poor experience. Reserve fixed-layout for photography-driven books where the page design IS the product.

Kindle Create is Amazon’s free tool for building both formats. Import your formatted document, assign each recipe part to its text styles, and generate the eBook — but clean up the manuscript first, because the tool inherits every formatting sin in your source file.

Image-heavy eBooks carry three pitfalls. First, file size: Amazon charges a delivery cost per megabyte on eBooks priced $2.99 to $9.99, and full-resolution photos can dent your royalty on every sale. Compress images to the smallest size that still looks good on a tablet. Second, placement: anchor each image to the paragraph it illustrates so it never floats into an unrelated recipe after reflow. Third, e-ink: basic Kindles display in grayscale, so test that photos still read well in black and white.

SpecificationPrint cookbookKindle cookbook
LayoutFixed page design; full control over columns and spreadsReflowable text adapts to every screen size
Images300 DPI, CMYK, 0.125-inch bleedApprox. 1200px max width, compressed to control delivery costs
ColorCMYK conversion, proofed on paperRGB; test in grayscale for e-ink devices
NavigationPage numbers, running heads, printed indexLogical TOC, searchable text, linked index
ProofingPhysical proof copy; cook-it-yourself testPreview on e-ink, tablet, and phone

A detailed look at eBook formats compared helps you decide which file types to produce for Kindle, Kobo, and other stores, since each retailer has its own quirks with image-heavy books. And if Kindle is your main market, a dedicated Kindle eBook formatting guide covers the Kindle-specific requirements — from the Kindle Create workflow to Amazon’s image quality checks — in far more depth than this overview.

Recipe TOCs, indexes, and cross-references

A cookbook without a proper index does not get cooked from. Readers remember a recipe was chicken, or used coconut milk, or was fast — not that it was on page 87. Index every recipe by name, plus by main ingredient, course, and dietary tag. Tag each recipe’s categories in your manuscript from the start, then generate the index from those tags during layout.

The table of contents usually lists chapters and, in thorough books, every recipe within each chapter. A recipe-level TOC is enormously useful in an eBook, where it becomes the navigation spine. In print, chapter-level entries are often enough. For Kindle, make every recipe title a styled heading so it lands in the eBook’s logical TOC — the pop-up navigation readers use to jump around.

Cross-references are the quiet glue of a professional cookbook. When a recipe says “serve with the Roasted Garlic Aioli on page 112,” that page number should be a live cross-reference, not typed text. In InDesign or Affinity Publisher, cross-references update automatically when pagination shifts during proofing. In Word workflows, use bookmarks and cross-reference fields. If a number can change, it should be generated, never typed. Verify every cross-reference in your final proof — a broken “see page 0” is the kind of error readers photograph and post in reviews.

Get the print specifications right the first time, because reprints are expensive and one-star reviews are forever. The two most popular cookbook trim sizes are 8.5 x 11 inches and 7 x 10 inches. The larger size gives photographs and two-column layouts room to breathe and reads like a proper coffee-table cookbook; 7 x 10 is more economical, feels like a working kitchen manual, and costs less to print and ship. Either way, budget for premium color printing — standard black-and-white interiors turn food photography into gray mush.

If you print through Kindle Direct Publishing, follow their exact template: correct page size, 0.125-inch bleed where elements touch the edge, text inside safe margins, and a print-ready PDF with embedded fonts. KDP color printing is serviceable but not gallery-grade — order a physical proof and examine it under kitchen lighting before approving.

Glossy or coated stock makes photography pop and wipes clean when sauce splatters on it — a real consideration for a book living on a counter. Matte stock feels more premium and reduces glare. Either way, use paper heavy enough that photos do not show through.

Then comes the most important quality check in cookbook publishing: cook from the printed proof yourself. Make several recipes from the proof copy in a real kitchen under real time pressure. You will catch the missing “preheat the oven”, the ingredient in the method but never in the list, and the font size unreadable from three feet away. Fix everything, regenerate, and proof once more.

Frequently Asked Questions

Can I format my cookbook in Word or Google Docs?

Yes, for a straightforward cookbook — especially if you use paragraph styles rigorously for titles, headnotes, ingredients, and steps. Complex print layouts (two-column spreads, full-bleed dividers, auto-generated indexes) are much easier in InDesign or Affinity Publisher. A practical middle path: draft in Word, then hand a clean manuscript to a professional for print layout.

Should my cookbook be fixed-layout or reflowable on Kindle?

Choose reflowable for almost every cookbook: it works on all Kindle devices, lets readers resize text, and is simpler to build in Kindle Create. Fixed-layout preserves your exact page design but only works well on tablets and the Kindle app. Go fixed-layout only for photography showcases where page design is the selling point.

What resolution do cookbook photos need for print?

300 DPI at final printed size, without exception — roughly 2550 x 3300 pixels for a full page in an 8.5 x 11 inch book. Phone images at 72 DPI will print blurry no matter how sharp they look on screen. Use your largest original and scale down; scaling up never adds detail.

How many recipes should a cookbook have?

Most successful self-published cookbooks land between 60 and 120 recipes. Fewer than 50 can feel thin for the price; more than 150 makes testing, photography, and proofing dramatically harder. Quality beats quantity: 75 tested recipes with great photos outsell 150 sloppy ones.

Do I need an index in my cookbook?

Yes — readers rank a good index among a cookbook’s most important features. Index by recipe name at minimum, ideally also by ingredient, course, and dietary tags, so readers can search by what is in the fridge. Generate it from tagged styles during production.

How do I handle metric and US measurements?

Pick a primary system and add the other in parentheses for key quantities, or include a conversion table in the front matter. For US audiences, US customary in the lists plus a metric and oven-temperature chart up front is most common. Apply your choice identically to every recipe.

Conclusion: a cookbook is a kitchen tool, so format it like one

Formatting a cookbook is empathy for a distracted, flour-dusted reader. Consistent recipe structure, scannable ingredient lists, numbered steps, photographs that survive press and Kindle, a real index, and a proof copy you have cooked from — these separate professional cookbooks from amateur ones.

If the technical side — bleed settings, Kindle image compression, cross-references, index generation — is more than you want to handle alongside testing and photography, that is what a formatting professional is for. Your job is the food; let someone else sweat the trim sizes.

A cookbook worth cooking from

Get a print-ready cookbook PDF and a Kindle edition with crisp food photography — professionally formatted, proofed, and ready to publish.

Basic Formatting — $97 per book

Professional Formatting — $147 per book

Premium Formatting — custom quote

Request cookbook formatting from ArrowUpz.

Leave a Comment

Your email address will not be published. Required fields are marked *