The short answer
Two good options, and they solve different problems. Share the book as a link or QR code and relatives open it in a browser with no app, no account and no signup wall, always seeing the current version as you add recipes. Or export the collection as one self-contained HTML file and send that — it needs no internet, nothing can switch it off, and it still opens in ten years. Send the link for a living collection; send the file for something permanent. For a keepsake, print the collection one recipe per page, or save every recipe as an image and upload those into a photo book service like Shutterfly, Mixbook or Blurb to get a bound cookbook.
Step-by-step
- 1
Whatever you send, make sure it has no signup wall
The instinct is to share an account or a folder, and it is the reason most family cookbooks never get read. Every person you share with hits a signup wall, and the ones who most want the recipes are the least likely to get past it. That is the thing to avoid, not links as such. Culinary Card gives you two ways around it: a share link and QR code for the book that opens straight into the recipes without an account, or "Send collection", which produces one .html file with a cover, a contents page, and every recipe including photos embedded inside it.
- 2
Send the link when the collection is still growing
Open the book, hit Share, and you get a link plus a QR code you can save as an image. Anyone who opens it reads the book in their browser — no app, no account, nothing to install. The part that matters for a family collection is that it stays current: add eleven more recipes next month and everyone who kept the link already has them, with nothing to resend. By default it is read-only, so nobody can rearrange your book by accident, and you can switch the link off later if you want it back. Print the QR code onto a card in a Christmas envelope and you have handed someone a cookbook.
- 3
Let the family add their own recipes to it
The other half of a family cookbook is everyone else's recipes, and chasing them by text is how the project dies. On the Share panel you can switch the link from "Just read it" to "Add their recipes". Anyone who opens that link and signs in can put their own recipes into the book — Aunt Chad adds his chili himself, in his words, and it appears in your book without you retyping anything. They can only add and take back their own; nobody can change or delete a recipe of yours, which is the part that makes this safe to send to a family group chat. Treat that link like a house key all the same: anyone who has it can add, so send it to people rather than posting it, and switch it back to read-only when the collecting is done.
- 4
Send the file when you want it to outlast everything
A link needs the internet and needs Culinary Card to still be here. A file needs neither. The exported file is self-contained — the photos are inside it rather than loaded from the internet — so it opens on an iPhone, an Android, a Windows laptop, a ten-year-old iPad. It works on a plane, in a basement kitchen with no signal, and in ten years when whatever service you used has shut down. Nothing expires and nobody can turn it off. It is the closest a digital thing gets to handing someone a book. Most families want both: the link for everyday cooking, the file tucked in a drive somewhere as the copy that cannot be taken away.
- 5
Pick the way each relative actually receives things
Email the file as an attachment for anyone over about sixty — it lands in the place they already look. AirDrop or text it to people in the room. For the family group, put it in a shared Google Drive, Dropbox or iCloud folder and send the link there, so when you add twelve more recipes next year you replace one file and everyone has the update. Mail providers usually cap attachments around 20–25MB, so if your collection is large, use the smaller-photos option in the export panel or share via a folder link instead.
- 6
Tell them how to keep it
This is the step people skip, and it is why the file gets lost. Two sentences in your message are enough: on an iPhone, tap the attachment, then Share and "Save to Files"; on a computer, download it and put it somewhere real rather than leaving it in Downloads. Mention that tapping a title in the contents opens that recipe and the section buttons narrow it down, because that is what turns it from an attachment into something they use on a Tuesday. On a phone that tapping is the fastest way around a long book; on a computer there is a search box as well, for finding a dish by an ingredient.
- 7
Print a copy for the kitchen
Some cooks will never use a phone at the stove, and they are not wrong. The same export prints one recipe per page, which is what you want: a page you can splatter, replace, and slide into a binder. Choose "Save as PDF" in the print dialog instead of a printer and you have a PDF to email or take to a print shop. A three-ring binder with sheet protectors costs a few dollars and is genuinely the most-used format in most families.
- 8
Turn it into a real photo book for gifts
For a wedding, a milestone birthday, or a memorial, a bound book is worth the effort. The trick is that photo book services want images, not documents — so export every recipe as its own image rather than fighting with a PDF. Culinary Card's "Save every card as an image" gives you a zip of one clean, numbered image per recipe. Unzip it, then upload the images into Shutterfly, Mixbook, Blurb, Artifact Uprising or Lulu and place one per page. The numbering matches your collection's order, so the book comes out in the order you arranged it rather than in whatever order the uploader felt like.
- 9
Arrange the order before you export, not after
Rearranging forty pages inside a photo book editor is miserable. Decide the order first: alphabetically, in chapters by course the way a printed cookbook reads, or grouped by who each recipe came from — all of Grandma Lois' together, then Uncle Chad's. The by-person arrangement is the one that makes people cry at the gift table, and it is the same click as the others. Whatever you pick flows through to the contents page, the printed pages, and the image filenames.
- 10
Send it before it is finished
A family cookbook is never done, and waiting for done is how it stays on your hard drive. Send the first twenty recipes now. Two things happen: people start cooking from it, and they start correcting you — "that's not how Mom made it, she used the whole can" — which is exactly the material you were trying to collect. Re-export and resend whenever you have added enough to be worth it.
Common mistakes to avoid
- ✕
Naming the file something only you would recognise
A tiny thing that decides whether anybody ever finds it again. "collection.html" sitting in a downloads folder is invisible; "Robinson Family Cookbook 2026.html" is findable by search in three years by somebody who has forgotten where it came from. Put the family name and the year in it before you send.
- ✕
Sending a giant attachment that bounces
A collection with a hundred photos can exceed what a mail provider will carry, and the bounce message is cryptic enough that most people assume the export failed. Either use the smaller-photos setting when you export, or put the file in a shared folder and send the link.
- ✕
Making the printed book the only version
Print is a keepsake, not a system. The moment it is bound it stops accepting new recipes, and the recipes keep coming. Keep the digital collection as the living master and treat every printed book as a snapshot of it.
- ✕
Sending it only to the people who cook
It is a natural filter to apply and it is the wrong one. The relatives who never cook are frequently the ones who sit and read the whole thing, because for them it is not a set of instructions at all, it is a book about people they miss. Send it to everybody.
Why Culinary Card works for this
Culinary Card treats sharing as the point rather than an afterthought. Group your recipes into books, then share a book by link or QR code — it opens in anyone's browser with no account, and it keeps showing your latest recipes without you resending anything. When you want something permanent instead, one button turns the collection into a single file, with the cover, the contents and every photo embedded inside it, that opens on anything and works offline. The same button prints the collection one recipe per page for a binder, or saves every recipe as its own image for a photo book service. You arrange the order once and that arrangement carries through, so your collection stays the living master copy you keep adding to.
Frequently asked questions
What file should I send so everyone can open it?
A single self-contained HTML file. It opens in the browser that is already on every phone, tablet and computer, needs no app or account, and keeps its photos inside it so it still works with no internet. PDFs work too and are better for printing, but they lose the tappable contents, the section filters and the checkboxes.
I downloaded the file on my phone — now what?
Tap it and it opens straight away, and to keep it rather than lose it in Downloads, use Share then "Save to Files" on an iPhone. One thing worth knowing: a phone often shows the file in a preview that does not run scripts, so the search box will not appear there. Tapping titles and sections still works, because that part is built not to need scripting. Open the file in a browser instead if you want search.
How do I make a printed cookbook from my recipes?
Two routes. For a simple keepsake, print the collection one recipe per page and put it in a binder with sheet protectors. For a bound book, export every recipe as its own image and upload those images into Shutterfly, Mixbook, Blurb or Lulu, one per page — photo book services handle images far more predictably than documents.
My email says the file is too large. What now?
Photos are almost all of the weight. Re-export with the smaller-photos option, which cuts the file to roughly a quarter with no visible difference on a screen. If it is still large, put the file in Google Drive, Dropbox or iCloud and send the link — which is better anyway, since you can replace it as the collection grows.
How do I send an update when I add more recipes?
Export again and replace the file. If you shared through a folder link, everyone gets the new version with no action from you. If you emailed it, send the new file and say which one it replaces — people keep the newest thing in their inbox.
Can relatives use it without creating an account?
Yes, either way, and that is the whole idea. A share link opens the book in their browser with no login and nothing to install. The exported file goes further — no login, no tracking and no connection back to anything, because it is just a document. Only you, as the person maintaining the collection, need an account.
Should I send the link or the file?
Send the link if the collection is still growing, because everyone keeps seeing your additions without you resending anything, and a QR code is easy to put on a card. Send the file if you want a copy that works with no internet and that nothing can switch off. They are not in competition — most people share the link for everyday use and keep the file as the archive copy.
Can other people add their recipes to my book?
Yes, if you want them to. Open Share and switch the link from "Just read it" to "Add their recipes". Anyone who opens it while signed in can then add their own recipes to the book and remove ones they added. They cannot change, delete or take out anything of yours. Because the link itself is the permission, only send it to people you trust — and you can switch it back to read-only, or turn it off, at any time.
Can I stop sharing a book later?
Yes. Open the book, hit Share, and turn the link off — it stops working for everyone who has it. Sharing again creates a fresh link, so the old one stays dead. A file you already sent is a different matter: once it is on someone's phone it is theirs, the same as a printed copy would be.