What is CrumbKit?
CrumbKit is a browser-based recipe collector. You can add recipes from the web, keep them in your browser, browse them later, and export them as JSON.
Paste a recipe URL, copy a structured extraction prompt for your AI tool, then paste the returned JSON back into CrumbKit. Recipes stay saved in this browser until you clear them.
Build your browser catalog here. If you clear this browser data before exporting, your catalog will be lost.
Search by title, ingredient, category, or tags.
Answers to the questions people usually ask once they start collecting recipes in CrumbKit.
CrumbKit is a browser-based recipe collector. You can add recipes from the web, keep them in your browser, browse them later, and export them as JSON.
No. CrumbKit does not require an account to use the catalog features.
Your recipes are stored in this browser using browser storage. They stay here until you clear them or clear your browser data.
Yes. Clear Session removes the saved catalog from this browser. Export your catalog first if you want to keep a backup.
It downloads your full CrumbKit catalog as a JSON file that you can import later or keep as a backup.
It loads a previously exported CrumbKit JSON file back into the app and merges or replaces matching recipes by id.
Open Add Recipe, paste a recipe URL, copy the AI prompt, run it in your AI tool, then paste the returned JSON back into CrumbKit.
Open Add Recipe, switch to Manual Form, and paste the title, ingredients, steps, image URLs, and notes yourself.
Yes. Open the recipe, click Edit Recipe, update the fields, and save the changes.
Some sites hide images behind JavaScript or anti-bot systems. In those cases the AI may miss them, and manual correction or a pasted image URL list works better.
Different AI tools follow instructions with different reliability. Stronger models usually do better, while weaker ones may simplify the schema or miss images.
Use the ingredient rows in Manual Form. Each row has its own quantity field, unit dropdown, and ingredient name field.
Use one step card per cooking step. Each step can contain multiple lines of instructions and its own list of linked ingredients with quantity, unit, and free text.
It helps protect the app and server-side integrations from automated abuse.
The catalog itself is stored in your browser. Some configured server-side actions can still run when recipes are added, such as archiving or webhook delivery, depending on your setup.
Yes. The UI is responsive and the core catalog workflow works on both desktop and mobile browsers.
The Catalog page gives you a cleaner full-library view with search, category filter, and sorting, without the homepage hero section.
Because models differ in browsing ability, schema obedience, and image extraction quality. Some infer, some hallucinate, and some extract more faithfully.
Not completely. CrumbKit works best when you quickly sanity-check ingredients, servings, steps, and image URLs before relying on a recipe.
Try the AI prompt first. If that fails, use Manual Form. For difficult sites, copy the website text manually and clean it up into the form.
Yes. Export as often as you want and keep several JSON files for backup, organization, or testing.
No. It only clears the recipes stored in this browser. Files you already exported stay on your device.
Use Add Recipe, paste a URL, copy the prompt, paste the AI JSON back in, then open Catalog to browse everything in one place.