The short answer
Export the collection as one self-contained HTML file and send that — it opens on any phone or computer with no app and no account, and it keeps working offline forever. Email it, AirDrop it, or drop it in a shared folder so relatives always have the current version. For a keepsake, print the same 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
Send one file, not a link and not an invitation
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. A single file has none of that: they tap it and the cookbook opens. In Culinary Card, "Send collection" produces exactly that — one .html file with a cover, a contents page, and every recipe including photos, all embedded inside it.
- 2
Know why the file works when the link does not
That file is self-contained: the photos are inside it rather than loaded from the internet. 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. Nobody needs an account, and nothing expires. It is the closest a digital thing gets to handing someone a book.
- 3
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.
- 4
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 it has a search box — typing "paprika" or "Grandma" finds the recipe without scrolling — because that is the feature that turns it from an attachment into something they use on a Tuesday.
- 5
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.
- 6
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.
- 7
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.
- 8
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
- ✕
Sharing an app account instead of a file
Every signup screen between a relative and a recipe loses a percentage of them, and the loss is heaviest among exactly the people who hold the oldest recipes. Share something that opens on tap. Keep the account for yourself, as the place you maintain the master copy.
- ✕
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.
- ✕
Assuming everyone will find the file again
An attachment opened once in Mail is effectively gone a month later. Tell people how to save it, and put a copy in a shared folder as the version of record so there is always somewhere to point them back to.
Why Culinary Card works for this
Culinary Card treats sharing as the point rather than an afterthought. One button turns your whole collection into a single file — cover, contents, photos and all — that opens on anything, works offline, needs no account, and has search built into it. The same button prints the collection one recipe per page for a binder, or saves every recipe as its own image so you can drop them straight into a photo book service. You arrange the order once — alphabetically, by course, or by who each recipe came from — and that arrangement carries through every format. Your collection stays the living master copy that 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 search box and the tappable checkboxes.
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, and that is the whole idea. The exported file has no login, no tracking and no connection back to anything. It is a document. Only you, as the person maintaining the collection, need an account.