Can you transfer Paprika recipes to CookBook?
Yes. CookBook’s team can import your Paprika library with Pro. Send a Paprika HTML ZIP including images, or a .paprikarecipes file, to team@cookbookmanager.com with your CookBook email or username. Keep your original archive and check the imported recipes before retiring the old collection. See the official bulk-import guide.
You do not need to retype years of favourite meals. This guide covers the handover and the checks afterwards. For the export buttons on your device, use our separate Paprika export guide.
In this article
- Can you transfer Paprika recipes to CookBook?
- What makes CookBook a useful next step?
- Request your Paprika transfer
- Before you move: choose a few recipes to check
- Transfer your Paprika collection in four steps
- What should you check after importing?
- Is this the same as CookBook’s bulk-import button?
- Make the first imported recipe your next dinner
- Frequently asked questions
- Ready for your recipes to do more?
What makes CookBook a useful next step?
Moving is worthwhile when the new app fits the way you now discover and cook recipes. CookBook brings supported social saves and photographed written recipes into the same library as your existing favourites. You can plan from that collection and open it on iOS, Android or the web.
- Turn supported social recipe links into saved recipes, including finds from TikTok, Instagram and Facebook.
- Add family cards and cookbook pages with written-recipe scanning, then review the captured text.
- Plan meals from your collection and use editable shopping lists.
- Ask about a saved recipe or explore ideas with CookBook’s AI features; availability and limits depend on your plan.
For a full decision, read CookBook vs Paprika. Paprika’s native desktop apps and dedicated pantry remain meaningful reasons to stay if those are central to your routine. If the upcoming version prompted your search, our Paprika 4 subscription explainer separates the announcement from your current setup.
Request your Paprika transfer
Request my Paprika transfer. Your email opens with the details the team needs: CookBook username, recipe count, Paprika version, export format, Pro status and any existing CookBook recipes. Attach the archive or add its download link before sending. Do not send your password.
Standard transfers have no additional fee beyond CookBook Pro. During the 14-day trial, the team can usually import a sample of your collection. Once you continue on paid Pro, the team can migrate the full collection. Typical turnaround is 1 to 3 business days, depending on volume and complexity.
If you already have recipes in CookBook or previously imported part of this collection, mention it in your request. Agree how overlapping recipes should be handled before starting; do not assume that a repeated upload will merge duplicates automatically. See supported import files and the help instructions.
Before you move: choose a few recipes to check
Start with the food you actually cook. Pick one weeknight meal, a family recipe with personal notes, a recipe with several method sections and one with your own photo. These become your reference sample after the transfer.
Try CookBook on your preferred device and make sure you like finding, editing and cooking a recipe there. Check the current CookBook plans before arranging a full-library transfer.
Transfer your Paprika collection in four steps
1. Make a dated Paprika archive
Use the export instructions for iPhone, Android, Mac or Windows. Save an untouched original and a separate working copy. Note the number of recipes you expect to move and whether you exported the whole collection or a category.
2. Keep the file complete
For HTML, keep the recipe pages and their images together in one ZIP. Do not send just index.html or a screenshot of your recipe list. For the native archive, retain the .paprikarecipes extension. Paprika describes these formats in its export documentation.
3. Arrange the Pro import
With Pro active, email the team your CookBook account identifier, say you are moving from Paprika, and attach the archive or a download link. We queue the import and notify you when it is ready. For current requirements, use the bulk-import help page.
4. Check the imported collection
Open your reference recipes in CookBook and compare them with the originals. Check the collection count, then the fields you rely on. Keep Paprika and your backup until you are satisfied with the result. Report a specific example to the team if something needs attention.
What should you check after importing?
| Paprika information | Where to check in CookBook | What needs attention |
|---|---|---|
| Categories and nested categories | Recipe tags and filters | Check the names and grouping you use. Do not assume the original nested hierarchy will remain identical. |
| Notes and ratings | Recipe notes, description and rating | Compare personal notes and the rating with the original, including any information in the description. |
| Main and additional photos | Recipe photographs | Prefer the complete HTML ZIP with images for assistance. Ask the team to check every photo you need; do not rely on a remote picture link alone. |
| Ingredient groups and quantities | Ingredient list | Check group labels, fractions, units and serving count. |
| Method formatting | Recipe instructions | Check step order, line breaks and section headings, not just whether text exists. |
| Source URLs and links between recipes | Source field and linked text | Open the source link. Links that point into Paprika are not automatically CookBook recipe links. |
| Pantry records, menus and meal plans | Keep separate records | These are separate from recipe-file transfer. Agree any additional work with the team before moving. |
Is this the same as CookBook’s bulk-import button?
No. Self-service accepts a CookBook CSV template or a ZIP of .cookbook files, up to 250 recipes per file. A Paprika archive uses team assistance instead. Changing its extension will not make it a compatible self-service file.
If you already have a spreadsheet, check its structure against the template linked in the bulk-import guide. For an existing Paprika collection, keep the original export and use the supported transfer route above.
Make the first imported recipe your next dinner
Once the checks are complete, choose a familiar meal and put the new workflow to use:
- Find the imported recipe and add an easy-to-remember tag.
- Put it on your meal plan for a day you will actually cook.
- Add its ingredients to a shopping list and remove anything you already have.
- Open cooking mode when it is time to cook, then save any changes you want to remember.
That gives the move a practical payoff: the meals you already love, with room for the recipes you keep discovering.
After checking the move, make a CookBook backup and keep the original Paprika archive.
Frequently asked questions
Do I need CookBook Pro to move my Paprika library?
Yes. Standard assisted transfers are included with Pro. The 14-day trial typically qualifies for a sample; a full collection transfer follows when you continue on paid Pro.
What if my Paprika collection has more than 250 recipes?
The 250-recipe limit applies to self-service files. For Paprika, contact the team with your export and collection size.
Do I need to send my Paprika password?
No. Prepare an exported recipe archive. Keep your passwords private; an archive lets you share the recipe data without handing over your Paprika login.
Should I delete Paprika as soon as I request the transfer?
No. Keep the original app and a separate backup while the transfer is arranged and checked. Make any cleanup decision only after confirming the recipes and information you need are available.
Ready for your recipes to do more?
Get CookBook, choose the plan that fits your collection, then follow the transfer steps above. Your existing favourites can sit beside new social finds, handwritten recipes and the meals you want to cook next.
