Export recipes from apps: what to check first

If you've saved dozens of videos, screenshots and recipes found online, you know the panic: one day the app changes, raises prices or shuts down. You end up with recipes scattered and hard to export.

You don't need to be alarmist. You need a simple plan to make sure your recipes don't get trapped. Here are concrete criteria to use when evaluating any app, three quick tests to do right away, and a practical way to make backups on your computer or in the cloud.

What to ask the app before uploading everything

When you evaluate an app for saving recipes, focus on measurable facts, not vague promises. Here are concrete questions to ask or look for in the documentation:

• What export formats does it offer? (PDF is readable, but look for open formats like JSON, Markdown or CSV as well). Open formats are easier to reload or transform.
• Can you export in bulk or only one recipe at a time? You should be able to extract your entire library without repeating the operation hundreds of times.
• Do exports include images, notes, tags and links to the original source? If the video source or original link is missing, you lose context.
• Can I download a file that is readable with normal programs? A JSON or Markdown file opens on any computer: that's a good sign.
• Does the app state who owns the data and how it is deleted? Check the data ownership and deletion policy.
• Do saved recipes work offline? If the service stops functioning, you at least want to be able to read what you saved.
• Is there an automatic backup feature to a personal cloud (Google Drive, iCloud, Dropbox) or only internally managed backups? The former is preferable.
• What happens if I stop paying? Some apps lock important functions behind a subscription; verify that access to your data is not restricted.

These questions tell you whether the app gives you control or keeps you locked in.

Three quick tests to do in 10 minutes

Try the app before moving all your recipes. Run these practical tests.

1. Export a single recipe
   • Choose a recipe with ingredients, steps and an image.
   • Export and open the file on your computer or phone. Check that ingredients and steps are readable and that the image is included.
2. Export a small group (5–10) or test bulk export
   • If the app doesn't offer bulk export, try to find out if it has an API or tools to automate. If not, estimate the time needed to migrate manually.
3. Try to reuse the exported file
   • Import it into another app that reads JSON/Markdown or open it in an editor. If the file is open and structured, you can rebuild the library elsewhere.

During the tests, pay attention to these things:

• Are tags, cooking time, or personal notes missing from the export?
• Are images low resolution or absent?
• Do links to the video source remain active?

If you find problems, save a manual copy immediately (see section below) before moving the rest.

For those who use videos as a source, you might find it useful to read how to extract recipes from videos and which methods work best: How to extract a recipe from a video: 3 practical methods.

What to save right away on your computer or cloud

Don't rely only on the app's export. Keep a copy that is easy to consult. Here's a practical procedure to create a useful backup.

1. Create a main folder: "Recipes-Backup".
2. For each recipe save three separate items:
   • a Markdown or HTML file with title, ingredients, quantities and steps (example name: 2026-08-olive-pasta.md)
   • the main image in JPG/PNG (same prefix as the Markdown file)
   • a meta.json file with origin, link to the video, save date, tags and personal notes
3. Create an index.csv or index.xlsx with one row per recipe: title, Markdown file, tags, time, link to the source. This lets you search and filter with Excel or a simple script.
4. Save the folder in at least two different places: an external drive and a personal cloud (Google Drive, iCloud, Dropbox).

Example structure:

• Recipes-Backup/
  • 2026-08-olive-pasta.md
  • 2026-08-olive-pasta.jpg
  • 2026-08-olive-pasta.json
  • index.csv

If you're only interested in organising what you've already saved in apps, read the practical tips in Organise saved recipes in 3 practical steps.

When it's worth using an app and when it's not

An app is useful if it saves you time in saving, searching and using recipes. But it must not become a prison.

Mark the app as acceptable if it meets at least these conditions:

• Exports to a readable format (preferably JSON/Markdown in addition to PDF).
• Allows bulk export or has a documented way to download the entire library.
• Keeps images and links to the source.
• Gives you offline access to saved content.

If the app doesn't meet these points, use it only as a temporary tool: make regular backups and move the files elsewhere.

One option that meets many of these needs is Cucinario: you can share a link (or use the share button) and get a structured recipe in seconds; it reads links from Instagram, TikTok, YouTube and websites; and it can also read photos of handwritten recipes. Bear in mind, however, that like many apps it has a limited free tier and a paid plan beyond which new imports may require a connection. Always run the quick tests above before entrusting your entire library.

If you find yourself rewatching the same reel several times to figure out quantities, there's also an article explaining why that happens and how to avoid it: Why you rewatch the same reel four times for the quantities.

An easy action to take now

Open the app where you keep your recipes. Do the first test: export one recipe and open the file on your computer or phone. If everything appears (ingredients, steps, image, link), immediately copy it into the "Recipes-Backup" folder. If it doesn't, don't move the rest until you have a backup plan.