Open the camera roll on the phone of any home cook under the age of fifty and search the word menu. Then search recipe. Then search food. The app will return — depending on how long the phone has been in service and how often its owner has lingered on cooking content — somewhere between two hundred and twelve hundred screenshots. They are not in a folder. They are not titled. They sit, in chronological order, between a screenshot of a friend's apartment listing and one of a confirmation number from an airline. They are saved. They are unfindable.
I counted mine, on a Sunday in Menton, the lemons in season on the windowsill and nothing pressing in the afternoon. Eight hundred and forty-seven. A pasta from a chef in Rome whose handle I no longer remember. A fish stew from a friend's stories. A galette I had wanted to make for perhaps eleven months. A TikTok of a woman in a beige kitchen turning out something with eggplant that had stopped me at one in the morning. None of them ingredient-listed. None of them step-listed. None of them connected to anything that could be cooked from. The screenshot, as a category, is the user telling the system I want to remember this — and the system, in response, doing nothing with that intent at all.
§ I.How the Folder Fills
The mechanism is well-rehearsed. You are scrolling — Instagram in the morning, TikTok at night, the cooking-adjacent corner of the group chat at any hour — and a recipe arrives. The video is forty seconds long. The caption has the ingredients, sometimes. The voiceover has the method, mostly. The comments have the corrections. You are not in your kitchen. You are on the train, or in bed, or three glasses into a Tuesday evening, and you intend to make this — not now, but soon, certainly within the week — and so you do the thing your phone is built to do, which is screenshot it. The image is captured. The intent is captured. Both go into the camera roll.
And there they stay. Friday arrives. You have decided to cook. You stand in the kitchen and cannot remember the dish, much less the handle, much less the date you saved it. You scroll. You give up. You order in. The screenshot was a vote — a small private declaration that this thing was worth keeping — and the vote is uncounted, because the system that received it has no mechanism for counting.
§ II.Why Screenshots Fail at Being Recipes
A screenshot is a picture of a recipe. A recipe is a structured document — a list of ingredients with quantities and units, a sequence of steps with timings, a yield, often a note on equipment. The picture contains some of this information, sometimes. The picture cannot be searched by ingredient. The picture cannot be filtered by tag. The picture cannot be added to a shopping list, because no system has parsed it into the components a shopping list requires. The picture cannot be scaled, because no system knows that the number two in the image refers to two cups and not two tablespoons. The picture is a flat artefact in a stack of flat artefacts, and the stack grows daily, and the stack defeats search by sheer volume.
What makes this particularly painful is that the cook's intent was never to save a picture. The cook's intent was to save the dish. The picture was the only available container. The phone offered no other verb — no save as recipe, no parse and file, no make this cookable later. There was screenshot. So screenshot it was.
And the folder, in the months and years that follow, becomes a graveyard of intentions — eight hundred small declarations of we should make this, none of which becomes dinner, all of which still take up space.
§ III.What the Verb Should Have Been
The verb should have been: paste this URL, or share this post, or hand this screenshot over, and I, the app, will read it — caption, on-screen text, voiceover transcript, visible ingredients — and turn it into a recipe with structured fields. Not a picture. A recipe. Searchable. Scalable. Connectable to a shopping list. Cookable from.
Basil's import is built on this premise. You see the eggplant TikTok. You tap the share sheet. You send it to Basil. The app fetches the post, parses the caption, transcribes the audio, identifies the ingredients mentioned in either, and builds a recipe card — title, ingredient list with quantities, ordered steps, source link back to the original. The whole thing takes perhaps twelve seconds. The result lives in your library, alongside the recipe from your mother and the one you typed up last March. It can be searched by the word eggplant. It can be scaled. It can be added to next Wednesday's plan. The screenshot was never necessary.
The same works for an Instagram reel, a YouTube video, a website, a recipe pasted as text into a group chat, or — and this matters, because the folder is full of them — an existing screenshot. You can hand Basil the picture. The OCR reads it. The parser structures it. The recipe arrives in your library. The image, having served its purpose, can be deleted.
The screenshot was a vote — a small private declaration that this thing was worth keeping — and the vote is uncounted, because the system that received it has no mechanism for counting.
§ IV.Halving the Folder
I spent a Sunday on this. The lemons were on the sill, the kettle was on, and I worked through the camera roll in reverse chronological order — the most recent saves first, on the theory that I would still remember why I had captured them. I sent each one to Basil. Some came in cleanly: a fully captioned reel from a Roman pasta account, parsed perfectly, ingredients in grams, steps numbered. Some came in messily: a TikTok with no caption, only voiceover, where the parser had heard half a tablespoon as half a teaspoon and I had to correct it. A few — the ones that were screenshots of screenshots, twice-degraded — came in as titles only, with a note that the source could not be fully read, and I either typed the missing pieces in or let the recipe go.
Three hours in, the folder was at four hundred. By evening, two hundred. The library, meanwhile, had grown by perhaps a hundred and twenty new recipes — the actual signal extracted from the noise, the dishes I had really meant to cook, now searchable by ingredient, scalable to two or to eight, droppable into the meal plan for the coming week. The remaining screenshots — the duplicates, the food I had photographed at a restaurant rather than saved as a recipe, the things I no longer remembered wanting — went into the trash. The folder, halved, finally felt like something other than a haunting.
The folder is at one hundred and ninety-four. The kettle is off. The eggplant TikTok — the one from the woman in the beige kitchen, the one I saved at one in the morning eleven months ago — is now a recipe in the library, scaled for two, added to Thursday. The lemons on the sill are still in season. The afternoon is still long. The eight hundred small votes I had cast and forgotten have, most of them, been counted at last. Some of them were not, in the end, votes I would have stood by; the screenshot is generous that way, and the cook, scrolling at midnight, more so. But the ones that mattered are now in a place where they can become dinner. The folder, for the first time in years, is no longer a problem. It is just a folder.
