Last year, as an experiment, I baked cakes from recipes<\/a> generated by ChatGPT and Bard. It went better than I expected<\/a> \u2014 because much of each recipe didn\u2019t seem created by AI at all.\u00a0<\/p>\n<\/div>\n The recipes I got were eerily familiar to recipes I\u2019ve seen on food blogs or Instagram. They\u2019d been slightly changed, and only Bard (now called Gemini) bothered offering attribution, linking to a recipe from Sally\u2019s Baking Addiction. In some ways, this isn\u2019t a new problem; I\u2019ve seen far too many copied non<\/em>-AI recipes floating around the internet. AI, though, makes the ethics of recipe copying more fraught. Its sheer scale threatens to create a world where human recipe developers are crowded out by semi-randomized AI-generated competition, but while there have been hints of this world arriving, we\u2019re not in it yet.<\/p>\n<\/div>\n Even without AI\u2019s involvement, recipe similarities are a very touchy subject in the food world. Some influencers find themselves in a firestorm if another food blogger or cookbook author claims they stole their recipes. The New York Times <\/em>reported several<\/a> instances of alleged recipe copying, including the 2021 case when author Sharon Wee accused British chef Elizabeth Haigh of copying passages and recipes from her cookbook. Then, there\u2019s the online hate against popular food blogger Half Baked Harvest<\/a>, who\u2019s been accused several times of copying from two other popular food bloggers.<\/p>\n<\/div>\n But food creators have very little legal recourse if they feel someone took their work. A simple list of ingredients and instructions is treated as an idea that cannot be protected by a copyright. Many recipes have an element of oral tradition; many are passed down through family members. While some include lengthy personal preambles that are<\/em> copyrightable, the biggest pushback for \u201cstealing\u201d recipes is often the daily snark threads on Foodsnark Reddit, and the recipe world is largely governed by etiquette \u2014 not law.<\/p>\n<\/div>\n And like musical chords, there are a limited number of ingredients you can put together for a passable recipe. Take a pie crust. How many permutations of sugar, butter, and flour can one write out before someone claims they just repeated the same recipe?<\/p>\n<\/div>\n Large language models, like those that power ChatGPT and Gemini, can take those permutations, parse through them faster than a human could, and come up with a pretty solid recipe very quickly. As a result, finding recipes that meet a particular diet is often touted as a good potential use of chatbots. On the other hand, to make an obvious point, AI tools can\u2019t actually prepare or eat food. They don\u2019t really \u201cknow\u201d if a recipe will work, just that it fits the pattern of one that does.<\/p>\n<\/div>\n Cookbook author and recipe developer Abi Balingit, who runs the blog The Dusky Kitchen, said she doesn\u2019t think about AI when she creates recipes. But she worries that it may impact where food writers and developers can feature their work.\u00a0<\/p>\n<\/div>\n \u201cThere are gradients of what is fine and not, AI isn\u2019t making recipe development worse because there\u2019s no guarantee that what it puts out works well,\u201d Balingit said. \u201cBut the nature of media is transient and unstable, so I\u2019m worried that there might be a point where publications might turn to an AI rather than recipe developers or cooks.\u201d<\/p>\n<\/div>\n Generative AI still occasionally hallucinates and makes up things that are physically impossible to do, as many companies found out the hard way. Grocery delivery platform Instacart partnered with OpenAI, which runs ChatGPT, for recipe images. The results ranged from hot dogs with the interior of a tomato to a salmon Caesar salad that somehow created a lemon-lettuce hybrid. Proportions were off \u2014 as The Washington Post<\/em> pointed out<\/a>, the steak size in Instacart\u2019s recipe easily feeds more people than planned. BuzzFeed<\/em> also came out<\/a> with an AI tool that recommended recipes from its Tasty brand.\u00a0<\/p>\n<\/div>\n Balingit added that people have a certain level of trust when they read someone\u2019s recipe or watch them make a dish. There\u2019s the expertise of having made the food and actually tasted it.\u00a0<\/p>\n<\/div>\n That explained why I instantly felt the need to double-check the recipes from chatbots. AI models can still hallucinate and wildly misjudge how the volumes of ingredients impact taste. Google\u2019s chatbot, for example, inexplicably doubled the eggs, which made the cake moist but also dense and gummy in a way that I didn\u2019t like.\u00a0\u00a0<\/p>\n<\/div>\n Balingit maintains that one advantage recipe creators have is the human connection. Her cookbook Mayumu<\/em> is filled with dishes that take an imaginative trip through her parents\u2019 migration to the US from the Philippines, her childhood in California, and her current life in New York. She said AI doesn\u2019t have cultural or nostalgic connections to food and eating, a historically personal thing people share with others.\u00a0<\/p>\n<\/div>\n I felt the same. Though I never truly cared who first devised the idea to poach chicken in a ginger broth, it\u2019s still my favorite Filipino dish, tinola. When I first started learning how to cook it (thanks largely to my dad kicking me out of the kitchen for being a nuisance), I scoured the internet for \u201cauthentic\u201d recipes. I chose to follow the work of people whose personal connection to the dish was strong, and it made me want to make the food they wrote passionately about.\u00a0<\/p>\n<\/div>\n ChatGPT and Bard can generate functional recipes. I know that because I followed them. But I knew, as the person who baked those cakes, that it was dispassionate and generic. My editor, Adi Robertson, compared one to a boxed cake mix, and another reminded me of sad cafeteria cakes. Sure, it hits the spot. Yes, it\u2019s chocolate cake. But cakes can be so much more.\u00a0<\/p>\n<\/div>\n<\/div>\n