How to Import Recipes from Crouton to CookClip

What this migration supports

CookClip’s Crouton migration is designed for an exported recipe library, not a screenshot or a PDF printout. Use Crouton’s recipe export so CookClip can read structured data instead of asking you to rebuild every ingredient and step by hand. For a full library, choose the ZIP export. For a one-off recipe, a single .crumb file is enough.

The importer can preserve recipe titles, ingredient and step sections, servings, cooking times, source links, nutrition, tags, and embedded photos when those fields are present in the Crouton file. The result is still worth checking: exports can contain incomplete or unusual entries, and your source app may have details that need a small cleanup after migration.

Step 1: Export the recipes from Crouton

In Crouton, use its recipe export or backup option and save the export somewhere the iPhone or iPad can access through the Files picker. A ZIP export is the right choice when you want to move several recipes. If you are testing the workflow or moving one favorite, save that recipe as a .crumb file instead.

Keep the original Crouton library until you have checked the CookClip result. Do not use a PDF export when your goal is a structured migration; PDFs are useful for reading, but they do not carry the same recipe fields as Crouton’s .crumb data.

• Use a ZIP for a batch migration.
• Use a .crumb file for one recipe.
• Save the export in Files and keep the original library as a backup.

Step 2: Start the Crouton import in CookClip

Open CookClip and go to Settings → Import Recipes → Import from Crouton. Tap Choose Crouton Export, select the ZIP or .crumb file from Files, and leave CookClip open while it reads the archive and imports the recipes.

A ZIP can contain many .crumb recipes, so the import may take a moment. CookClip continues past individual malformed entries when it can, rather than making one bad file stop the whole batch. Migration imports are local and do not use the Smart Import quota.

Step 3: Read the migration summary

When the import completes, check the counts for imported, duplicate, and failed recipes. Existing matching recipes are skipped so you can safely retry an export without creating another copy of every recipe. A failed entry is a prompt to open the original Crouton recipe and decide whether to export it again, repair it manually, or leave it behind.

Open a few representative recipes from the beginning, middle, and end of the batch. Check the title, ingredient sections, step order, servings, cooking time, source link, tags, nutrition, and photos. Once the sample looks right, browse the rest of the library and start organizing only the recipes you actually plan to cook.

What to do after the migration

Keep CookClip as the working copy only after you are comfortable with the result. Add the recipes you want to cook soon to a practical collection, use search to find them by title or ingredient, and add a few meals to your plan before building a grocery list. The migration is the first step; the useful payoff is being able to find and cook the recipes without returning to the old app every time.

Because migrated recipes do not count toward the Free recipe-library limit, you can bring over the library you need and then decide which CookClip workflow fits your cooking habits. You do not need to delete Crouton immediately—keep it until your spot checks and any important backups are complete.

FAQ

Common questions