biti by bit beta

A book made by everyone

Recipe book gift ideas

A collected recipe book is one of the few gifts that costs almost nothing and gets kept for forty years. The hard part isn't the printing — it's getting the recipes out of the people who never wrote them down.

Who it suits as a gift

A recipe book works when the group giving it has a shared kitchen history, or when the person receiving it is about to start their own. In practice that means:

Decide the shape before you ask anyone

Three decisions, and they take two minutes: how many recipes per person (one is right — "as many as you like" produces either none or nine), who's in, and the deadline, which should be a fortnight before you actually need it. Say all three in the first message. Vagueness is why these books stall.

Twelve to twenty recipes makes a proper little book. Six is a lovely card. Forty needs an index and a real deadline.

Getting a recipe out of someone who cooks by feel

This is the whole job. Ask a good cook for their recipe and you get "oh, a bit of this, until it looks right" — not because they're withholding, but because they genuinely don't hold it as a list. You have to reconstruct it.

Two practical notes. If they hedge on quantities, write the hedge: "about half a cup — she says you'll know" is a better line in a family book than a false precision. And if two people in the family make the same dish differently, print both. That argument is part of the recipe.

Start a recipe book →

Share one link, everyone adds their own recipe, and you print the finished book. Run one free, no signup, nothing to pay.

What to ask for beyond the method

The ingredients and steps are the least interesting part of a family recipe book, and the part most easily replaced by the internet. The rest is why the book gets kept. Ask for these — they're short enough that people will actually answer:

  1. What do you call it? The real name, not the proper one. "Nan's brown biscuits" beats "Anzac slice".
  2. Who taught you? And, if they know, who taught them.
  3. When do you make it? The occasion, the season, the weather, the person who always asks for it.
  4. What does it go with? Half the point of a dish is the rest of the table.
  5. One memory, three lines max. The first time you made it, or the time it went wrong.
  6. Anything you cheat on now? The shop-bought shortcut people take once they've made it two hundred times is genuinely useful information.
  7. A photo — of the dish if you have one, but better still of the handwritten card or the stained page it lives on.
  8. How you'd like your name to appear. "Aunty Fay", "Faye Nguyen", "Mum". It's their byline.

A scan of someone's actual handwriting, printed facing the typed version, is the single best design decision in most of these books. It costs nothing and it's the page people stop on.

Bridal shower recipe cards

The traditional version puts a blank recipe card in each invitation and asks guests to bring it filled in. It's charming, and it half-fails every time: a third of people forget, some cards are illegible, and one goes missing between the venue and the car. The hybrid works better — send a link ahead of time so the recipes are collected and legible, and put a blank card on the table on the day for the handwriting. Guests who forgot can add theirs from their phone.

Wording for the invitation insert, if you'd like it:

Please bring a recipe. Something you're known for, something easy, or something you wish someone had given you at twenty-five — we're collecting them into a book for the kitchen.

How to present it

Collect it without the email thread

The recipe collection tool does the gathering part: name the book, share one link, and everyone adds their recipe, their name and the story behind it in their own words. No accounts, no chasing attachments, and when it's full you hit print and get a clean keepsake to bind. Run one free, no signup — it's a small tool, not a platform. Pairs well with the group card for the message that goes with it, and the hens and shower planner if the book is for a kitchen tea.

FAQ

How many recipes do you need for a recipe book gift?

Twelve to twenty makes a proper little book. Six is closer to a lovely card, and beyond about forty you'll want a contents page and an index. Ask for one recipe per person — "as many as you like" reliably produces either none or nine.

How do you get a recipe from someone who cooks by feel?

Don't ask them to write it down. Watch them cook it, hold measuring cups under their hand as they throw things in, ask "how do you know it's done?" rather than "how long?", and ask what people get wrong when they try it. Then write it up and read it back — people who can't recite a recipe can correct one precisely.

What should you ask for besides the ingredients and method?

The name they actually call it, who taught them, when it gets made, what it's served with, one short memory, any shortcut they take now, a photo of the handwritten card, and how they'd like their name to appear in the book.

What do you write on bridal shower recipe cards?

Keep the ask simple on the invitation insert — something you're known for, something easy, or something you wish someone had given you at twenty-five. Collecting recipes by link beforehand and putting blank cards on the table at the shower gets you both a legible book and everyone's handwriting.

How should a memory cookbook be printed and bound?

Comb or spiral binding at a copy shop, so it lies flat on a bench, on paper heavier than office stock. A5 is a good kitchen size. Add a dedication and contents page, and leave a few blank pages at the back for recipes added later.

Is a recipe book a good gift for a milestone birthday?

Yes — particularly a book of the recipes that person taught everyone else, compiled by the people they taught. It costs very little, reflects them back, and tends to be kept far longer than an object.