Quick answer: Edge doesn’t have a native CookBook add-on, but you can install our Chrome extension in Edge in under a minute, then click the CB icon on any recipe page, sign in, and hit Edit recipe to save it.

Install the extension in Edge

1. Open Microsoft Edge and visit the CookBook extension on the Chrome webstore[](https://chrome.google.com/webstore/detail/cookbook-app-recipe-impor/pehlnokhmjhnlghjkjbepjimjbcnjnlb) here.
2. At the top, Edge shows a banner: “Allow extensions from other stores.” Click Allow → Add extension.
3. Review the permission pop-up and click Add extension again.
4. Edge confirms the CookBook icon has been added to your toolbar.

(Need visuals? See Microsoft’s official guide here.)

First-time sign-in and permissions

• Click the CookBook icon in the toolbar.
• A new tab opens to the CookBook Web App, sign in once.
• Edge may ask “CookBook wants to store files on this device.” Choose Allow (the clipper caches recipe text and photos locally for faster loading).

Import a recipe

1. Browse to any recipe page.
2. Click the CookBook icon in the toolbar.
3. The clipper scans the page. If successful, you’ll see the recipe title, photo, servings, and counts of ingredients and steps.
4. Choose either:

• Save to CookBook: Saves the recipe immediately without opening the CookBook app.
• Edit recipe: opens CookBook so you can add tags, change servings, or upload photos before saving.

If the clipper can’t read the recipe

You might see:

• “We could not read the recipe data from this page.”
• “Website must support structured recipe data…”

Why?

Many sites don’t label their recipe data with standard formats (hRecipe, Microdata, Recipe Schema, or JSON-LD), so the clipper can’t parse it, even if the ingredients are visible on-screen.

What you can do

• Hit retry
• Copy–paste the recipe into CookBook manually.
• Think the site does use a standard format? Tap Submit a request with the URL and a screenshot - we’ll investigate.

Updated on: 14/06/2026