Basil & Paprika.

I have a Paprika 3 license that I bought, on an iPad mini, in the spring of 2015. It is the longest continuous relationship I have ever had with a piece of consumer software. The library inside it now contains nine hundred and sixteen recipes, organized into thirty-four categories, with a meal plan that goes back, if I scroll, to the week my daughter was born. It is the closest thing I own to a kitchen diary.

I also have Basil, which I installed in late 2024, and which now holds two hundred and eighty-three recipes — almost all of them imported in the last eighteen months from places Paprika could not really see: an Instagram reel from a chef in Lisbon, a YouTube video from a Korean grandmother, a TikTok of a galette that I have now made four times. The two apps live next to each other on my second home screen. They do almost the same job. They are also, somehow, doing very different things.

§ I.What Paprika gets right

Paprika is, on its strongest dimension, the best web clipper in the category. The custom in-app browser is fast, and the recipe parser — refined over a decade of use against thousands of food blogs — is uncannily reliable. You navigate to a recipe page, you tap save, and you get clean ingredients, clean steps, a working photo. The number of edge cases the team has handled, quietly, over the years is the kind of thing you only notice if you have used a worse parser.

Paprika is also a serious meal planner. The week view is honest, the drag-and-drop works, and you can move a recipe from Tuesday to Thursday without three taps and a confirmation dialog. Sync, paid as a small annual subscription, is reliable across iPhone, iPad, Mac, and the web. The pricing model — a one-time per-platform purchase, plus that sync subscription — is unusual in 2026 and refreshingly transparent. You know exactly what you are paying for and exactly when you are paying for it.

And there is the matter of patina. A library that has lived through ten kitchens, two cities, and three pandemics is not a library you abandon lightly. Paprika has earned that gravity by being there.

§ II.Where Basil differs

Basil was designed against a different set of assumptions about where recipes come from. In 2015, the recipe lived on a food blog, with structured ingredients and a numbered method. In 2025, increasingly, it lives in a fifty-second video on a phone with a voice-over and a caption. Paprika's parser handles the first beautifully and the second uneasily. Basil is built, more deliberately, for the second world without giving up the first.

The practical effect is that one-tap import in Basil works on websites, on Instagram reels, on TikTok recipes, on YouTube cooking videos, and on the screenshot a friend airdrops you at brunch. The app pulls a structured recipe out of each of these — ingredients, steps, a photo — and files it in the same library as everything else. There is no separate clipper, no separate workflow.

The cooking experience is also where the two diverge. Basil's cooking mode keeps the screen awake, advances by swipe, holds timers in line with the steps, and is laid out for a phone propped against a salt cellar with one hand on a knife. Paprika has a cooking view; Basil has a cooking mode. The difference is the difference between a feature and a posture.

Basil is free. There is no ad layer, no upsell screen, no nag for sync. iCloud sync is included because iCloud is already there. Family Sharing works because the App Store already does that work. Allergens are tagged at the household level and flagged on every recipe automatically — a small thing, until it is your sister-in-law and the peanuts.

§ III.The deeper philosophy

Paprika treats a recipe as a record. The product is a database with a kitchen attached. Every interaction radiates outward from the idea that the recipe is the artefact, and the artefact deserves a place to live. This is not a criticism. It is the reason the app has lasted.

Basil treats a recipe as the thing about to happen. The product is a kitchen with a database underneath. Imports are fast because import is the friction; cooking mode is good because cooking is the point; the grocery list aggregates across the week because the question on Saturday morning is not what is in the library but what is missing from the fridge.

Both are coherent worldviews. Both produce good software. They produce different software.

§ IV.Who each is for

Paprika is for the cook who already has Paprika. That is not a tautology. It means: the value of an app of this kind compounds with the library, and a decade-old library is worth more than a switch can usually justify. It is also for the new user who prefers a long-running, deeply tested, web-first organizer with a parser that has seen every food blog there is, and who does not need their recipe app to handle a TikTok.

Basil is for the cook who is starting roughly now, or who is starting the next chapter — a new flat, a new family, a new way of cooking. It is for the cook whose recipes arrive from everywhere, who plans the week on Sunday and shops once, who would prefer one library across cooking and planning and shopping, and who does not want to think about a subscription in order to feed people.

Both apps are, on their own terms, doing the work. One has a decade of patina and the most reliable web clipper in the category. The other was built last year against the way recipes actually move on the internet now, and against the small physical reality of a phone on a counter at 7:14 on a Tuesday. The Paprika library on my iPad will outlive most of the appliances in my kitchen. The Basil library is the one I open when dinner is in eleven minutes. They are, in the end, the right answers to two different questions.