Family Recipe Books & Cookbook Compilation

The "I want a real, printed cookbook of my grandmother's recipes" page. For digitizing the source material see Food Costing & Recipe Digitization; for OCR engines see OCR & Vision; for the design tools used see Design; for photo book / print-on-demand more broadly see Photo Book Printing; for self-host archive of the originals see Self-Hosted Files & Cloud; for self-host document management see Self-Hosted Document Management; for the recipe sources / managers feeding this see Self-Hosted Recipe Managers.

Hosted "do it for me" platforms

• ★ Family Cookbook Project — paid (~$8/mo subscription + book printing); the long-running default; web-based; easy for non-technical family members; print-on-demand. Has been doing this since 2002.
  • https://www.familycookbookproject.com
• Heritage Cookbook — paid; smaller; cleaner UI than Family Cookbook Project; one-time per book.
• Cookbook Create / Bookemon — paid; generic photo-book platforms with cookbook templates.
• Mixbook — paid; photo-book service; cookbook templates.
• TasteBook — sunset; ignore.

DIY (the right call if you have any layout chops)

• ★ ★ Affinity Publisher 2 — paid one-time (~$70); InDesign-grade desktop publishing without a subscription. The right pick for a serious one-off cookbook. See Design.
• ★ Scribus — FOSS; mature desktop publishing; the OSS-only path.
  • https://www.scribus.net
• InDesign — paid sub; industry standard; overkill for one cookbook.
• Pages / Word / Google Docs — works; binder-shape rather than book-shape; OK if the goal is "spiral-bound at Kinko's."
• Canva — paid + free; templates; surprisingly capable; weak on long-document layout.
• LaTeX + cuisine.cls / cookbook.cls — for the I love TeX crowd; produces beautiful results; high learning curve.

Generators / static-site shapes

• ★ Chowdown — Jekyll-based; "recipes as a static site"; charming. Doubles as a blog. See Self-Hosted Recipe Managers.
  • https://github.com/clarklab/chowdown
• Cooklang + a Hugo / Astro theme — recipes-as-text → static site → printable PDF. The git-tracked path.
• Bookdown / Quarto books — for the R / Quarto crowd; gorgeous PDF output.
• Pandoc + a custom template — Markdown recipes → printable PDF; ~50 lines; the engineer's path.

Print-on-demand printers

• ★ Lulu — POD; hardcover + softcover; books from $15; the default for self-published cookbooks.
• Blurb — POD; photo-book-flavored; better paper for color photography.
• Mixam — POD; UK / EU; cheaper for color.
• Ingram Spark / KDP Print — POD; Amazon-distribution-flavored; thinner paper.
• Local print shop with spiral binding — for "kitchen-counter usable" shape; under-rated.

What "good cookbook design" needs

• ★ Spiral binding lays flat in the kitchen. Hardcover looks better; spiral cooks better.
• Generous margins, big ingredient list font. Most heirloom cookbooks fail here; readable-while-cooking matters.
• Photo per recipe (or every 2–3). Photos drive use; text-only family books gather dust.
• Index by main ingredient. Not just title; "chicken" / "lamb" / "almonds."
• Reserve a blank "notes" page next to each recipe. Future cooks scribble.
• Cover the heritage stories. A paragraph from the contributor under each recipe transforms the book.

Photography for the cookbook

• ★ Even daylight, white-bounce board, food on a neutral surface. Beats any equipment.
• iPhone 14 Pro / Pixel 9 Pro food photos are good enough.
• Edit lightly; over-saturated food photos look like stock photography.
• For mobile editing see Photo Mobile Editing; for print-quality color see Photo Color Management; for the broader photo-book pipeline see Photo Book Printing.

Workflow (the family-cookbook playbook)

1. Collect: emails / text photos / scanned cards from family. Use a shared folder (Self-Hosted Files & Cloud) or a Mealie / Tandoor instance.
2. Digitize: OCR or Vision-API'd into structured recipes. See Food Costing & Recipe Digitization.
3. Edit / standardize: ingredient lists in consistent format, instructions in consistent voice; this is the work.
4. Test-cook each recipe at least once. Recipes-from-memory contain errors; test-cooking finds them.
5. Photograph each recipe. Two-day session; batch.
6. Layout in Affinity Publisher / Scribus / Family Cookbook Project.
7. Proof PDF, hand-check pagination + index.
8. Print one proof copy before doing the family run.
9. Distribute / give as a holiday gift.

Honest pricing landscape (mid-2026)

Practical guidance

• ★ A spiral-bound "kitchen edition" + a hardcover "shelf edition" is the right move; one to cook with, one to display.
• Make a digital copy too. Mealie / Tandoor / a PDF on Nextcloud — survives a flood, lets future generations cook from it.
• Family recipe books take longer than expected. Plan 6 months; deliver in 9.
• Make 5+ extra copies. Family expands; lost copies replace.
• Color profiles matter for print. Blurb wants ICC-tagged sRGB or AdobeRGB; check before final upload. See Photo Color Management.
• The story is the book. A recipe without context is a webpage. The grandmother / aunt / dad voice is what makes the book.

Pick this if…

• Easiest, family-friendly, hands-off: Family Cookbook Project.
• Cleaner output, willing to learn layout: Affinity Publisher + Lulu.
• OSS-only: Scribus + Lulu.
• Tech-flavored / git'd: Cooklang + Pandoc → PDF.
• Recipes online for the wider family: Chowdown or Mealie public link.
• One quick proof for grandparents: Word + spiral bind at Kinko's.