How to Digitize Handwritten Family Recipes

Lay each card flat, light it from one side, shoot it against a plain background, and fill the frame with the page: that is what makes pale ink readable. Cookfolio transcribes without translating or rewriting, leaves blank anything it cannot make out, and shows the whole result for checking before saving. Vague quantities like a glass of milk or a knob of butter stay exactly as written. And you can keep a photo of the original card as the recipe image.

What you are actually trying to save

This is narrower than choosing a system for your recipes in general, which the five methods for digitizing recipes covers. The material here is specific: stained index cards, spiral notebooks, annotated clippings, biro gone brown, pencil half rubbed away.

What disappears when someone tidies a recipe into clean prose is the part that mattered: the approximate quantities, the turns of phrase (“you will see when it is ready”), the margin notes, the personal spelling.

So sort before you shoot. Group by person and by source, and decide now that a dish surviving in three versions stays three recipes, not one negotiated compromise. And keep the paper: digitizing is a copy, not a replacement.

Photographing faded handwriting so the AI can read it

Light from the side, never a flash. Raking light catches the groove the pen left in the paper and lifts pale ink off the background. A frontal flash flattens contrast and burns out glossy paper.

Shoot flat and square, on a plain contrasting surface. Angled shots skew the lines and swallow words at the edge; a cream card on a dark worktop keeps edges clean.

Fill the frame with the page. This matters most. Every image is resized to 2048 px on its longest side before analysis, so a double page shot from a distance keeps almost no pixels on the writing. One recipe per photo, tightly framed, at full resolution, though nothing is gained beyond 2048 px.

Accepted: JPEG, PNG, WEBP (10 MB), PDF and Word DOCX (20 MB), plain text TXT (5 MB).

For handwriting, a photo beats a PDF. A PDF is read through its text layer, and only its first page is rendered as an image, at roughly 108 DPI. A multi-page scan loses everything after page one, and a handwritten scan with no text layer gives only a low-resolution render. Word is the same: an image pasted into a DOCX is ignored. So: handwritten cards mean photos, one per recipe.

What the AI transcribes, and what it will not invent

The model is instructed as a transcriber, not a cook. It extracts only what is explicitly written and adds no implied step: it will not insert “preheat the oven” if the card never says so, never estimates a missing prep time, cooking time or calorie count, and leaves the field empty whenever there is doubt.

It never translates: a French card stays in French, title, ingredients, steps and headings included. It does normalize units into a fixed list of codes (g, kg, ml, cl, dl, L, tsp, tbsp, cup, fl oz, oz, lb, piece, pinch, clove, slice, sprig, handful), so “tbs” comes back as tbsp: unit normalization, not rewriting. If the image is not a recipe, the import fails cleanly instead of improvising.

Nothing is saved until you confirm: a review screen shows every field, editable. A very cursive hand or stained card can give a partial transcription, so read it back line by line.

Free covers 5 recipes and 5 lifetime AI imports across all sources, one file being one credit. A family collection passes that fast, hence Pro (4.99 EUR monthly, 39.99 EUR yearly).

Vague quantities and “cook until golden”

An ingredient with no numeric quantity is kept as written and untouched when you change the servings: only numbers are recalculated, rounded to one decimal, as the guide on adjusting recipe portions explains. Leaving “a knob of butter” unnumbered is safe, not a gap.

So put the original wording in the ingredient name and leave the quantity blank: “butter, a generous knob”, “milk, one tumbler”. Do not invent 25 g; for an equivalence, add a recipe note instead.

Pinch, piece, clove, slice, sprig and handful exist as units but convert into nothing. Conversion works only within the same nature, volume to volume or mass to mass: a cup into grams is impossible, since it depends on the ingredient’s density.

Cooking mode timers are detected in the text of the steps and need a number plus a time unit. “1h30”, “15 min” and “20 minutes” give a timer; “cook until golden”, “half an hour” spelled out and “1.5 hours” give none, decimals and fractions being ignored deliberately. So do not rewrite “until golden” as “12 min”: add a second, numbered sentence and keep the original phrase in front.

Keeping the voice, not just the data

Keep the phrasing and the order of the gestures, the household names (“Aunt Marie’s cake”, not “yoghurt cake”), and the domestic measures. For what the structure cannot hold, use the fields that exist: the description carries context (“served every 15 August since 1974”), the notes carry provenance and variants (“Renée’s notebook, 1978, she always used more butter than it says”), and section titles respect the original split when the card itself separates pastry, filling, assembly.

Date and source each recipe in the notes while the document is in front of you: that is what nobody can reconstruct in ten years. And resist correcting: an obvious slip, 250 where 25 was meant, belongs in a note, not a silent rewrite.

Keeping a photo of the original card

On a photo import, the review screen gives you the full source image. If the card holds no picture of a finished dish, the photo slot offers a crop of that original, so the handwritten card itself, writing visible, becomes the illustration. You can crop, replace or remove it. A real photo of the dish in the source can be detected and offered automatically, and stays replaceable.

One honest limit: a recipe carries a single photo, so you choose between the document and the dish. No gallery, no attachments. For handwritten cards, where the writing is the heirloom, keep the document as the recipe photo, and the original in your own photo library too. A recipe spread over two cards is best shot side by side in one frame, since one import handles one file.

Passing it on, and what “backed up” really means

Within your household, the Family plan (6.99 EUR per month or 59.99 EUR per year) opens a shared space for up to 4 accounts: recipes, planning and shopping list in common, in real time, each with their own login. When you join, you choose which personal recipes to copy across, with duplicate detection; the rest are not deleted, just set aside, and they come back if you leave. The Family setup guide walks through it.

Outside the household, sharing goes through a web link, and the recipient can import the recipe into their own account, which counts against their 5 free recipes but spends none of their import credits.

Recipes are hosted in Europe and synced across web, iOS and Android, reachable from any connected device, though a connection is required: there is no offline mode. Settings offer a JSON export of your data: a personal data export, not a restore file, since it excludes photos and is not designed to be re-imported. So keep the paper, keep your original photos, and keep the recipes in the app for daily use.

The point is not storage. It is finding Aunt Marie’s gratin in three seconds on a Sunday, then cooking it full-screen, step by step, screen awake, hands in the flour.