Who owns a recipe? Ethics, attribution, and your private kitchen

Most home cooks assume one of three things about recipes and copyright:

If I bought the cookbook, I can do whatever I want with it.
If it’s on the internet, it’s free to use.
If I rewrite it slightly, it’s mine.

All three are incomplete. Recipes exist in a strange legal middle ground — part functional instruction, part creative expression, part cultural inheritance. The law offers some clarity. The ethics offer more.

This article is not legal advice. We are not lawyers. What follows is an overview of how copyright law generally treats recipes, what major voices in food writing say about attribution and respect, and how those principles inform the way Sharp Cooking operates.

What the law protects (and what it doesn’t)

In most legal systems — including the United States, the United Kingdom, the European Union, and countries that follow the Berne Convention — copyright law distinguishes between ideas and expression.

Ideas are not protected. That includes:

Lists of ingredients
Functional procedures (“bake at 350°F”)
Methods and techniques

Expression is protected. That includes:

The specific words used to describe the process
Headnotes, stories, and commentary
Photographs and layout
The overall creative presentation

The U.S. Copyright Office Circular 33 states this explicitly: “Mere listings of ingredients as in recipes, formulas, compounds, or prescriptions are not subject to copyright protection.”

The legal reasoning is straightforward. You cannot own the fact that combining flour, butter, sugar, and eggs in certain proportions produces a cookie. That’s chemistry. What you can own is the particular way you describe that process — the narrative voice, the explanatory detail, the creative structure of the instructions.

In the European Union, a 2018 ruling by the Court of Justice confirmed that even the taste of a food product cannot be copyrighted, because taste is not “precise and objective” enough to qualify as a protected work. If taste itself isn’t protected, the functional instructions for achieving that taste are even less so.

The UK Copyright, Designs and Patents Act 1988 follows similar principles, though British law is somewhat stricter about protecting the typographical arrangement of a recipe on the page — meaning the layout and design may be protected even when the ingredient list is not.

The general international consensus: recipes as functional procedures are not owned. Recipes as literary works can be.

The merger doctrine and the limits of protection

There’s a concept in copyright law called the “merger doctrine.” It holds that if there is only one way — or very few ways — to express an idea, then the idea and the expression have “merged,” and neither can be protected.

Applied to recipes, this means: if the only reasonable way to describe a step is “whisk the eggs,” that phrase is not protectable. There’s no creative variation available. The instruction is essentially the idea itself.

This is why most recipe instructions, standing alone, are difficult to protect. Functional cooking steps tend to merge with the ideas they describe.

What remains protectable is everything around the recipe: the introduction, the story about where it came from, the chef’s notes about substitutions, the photographs, the design. That material is where creativity lives.

What the food world’s authorities say

Legal rules tell you what you can do. Ethical norms tell you what you should do. In food writing and professional cooking, those norms are well established — and they matter more than most home cooks realize.

Mark Bittman: Recipes as shared heritage

Mark Bittman, author of How to Cook Everything and longtime food columnist, has often described recipes as “the software of human life” — fundamental techniques and knowledge that belong to culture, not individuals.

In his view, recipes are meant to be shared, adapted, and passed down. But that doesn’t mean attribution is irrelevant. Quite the opposite. Bittman emphasizes what he calls “reciprocity”: if you use someone’s recipe, cite the inspiration. Not because the law requires it — because respect for the lineage of the dish requires it.

His broader argument: recipes are not property in the legal sense, but they are part of a collective inheritance that should be honored.

David Lebovitz: The gold standard for attribution

Paris-based pastry chef and food writer David Lebovitz has written what many consider the definitive guide to recipe attribution ethics.

Lebovitz breaks down the etiquette clearly:

“Adapted from”: You made significant changes to ingredients or method.
“Inspired by”: You saw an idea and built something new from it.
“Via”: You are republishing with permission or directing readers to the source.

He also draws a critical distinction: the ingredient list may be legally unprotectable, but the headnote — the story or context before the recipe — is the author’s voice. Never copy that.

Lebovitz’s stance, widely adopted across the food blogging and publishing world: Legal permissibility does not equal ethical best practice. Just because you can copy a recipe doesn’t mean you should, especially if doing so undermines the creator’s livelihood or misrepresents the origin of the work.

Diana Henry: Recipes as memory and labor

British food writer Diana Henry, author of more than a dozen acclaimed cookbooks, has spoken about recipes as “culminations of years of testing.” While a recipe writer may not legally own the chemistry of a cake, they do own the labor — the work that went into perfecting it.

Her framing is useful: respecting the creator means respecting their time, even when the law offers no protection.

In a world where recipe websites and apps make copying trivially easy, the ethical obligation to acknowledge sources becomes even more important, not less.

Samin Nosrat: Cooking as functional science

Samin Nosrat’s Salt, Fat, Acid, Heat approaches cooking not as a collection of recipes but as a system of elements and techniques. Her framework treats recipes as expressions of chemistry and physics — reinforcing the idea that no one can “own” the fact that salt enhances flavor or heat denatures protein.

This view supports the legal consensus: recipes are functional. The presentation of recipes is creative.

The ethics of attribution: a shared standard

The Food Blogger Alliance and similar organizations have developed shared guidelines for how to attribute recipes ethically. The core principles:

If you republish a recipe verbatim, always credit the source and link back.
If you adapt a recipe significantly, state that clearly: “Adapted from [source].”
If a recipe inspires you to create something new, acknowledge the inspiration: “Inspired by [source].”
Never copy headnotes, stories, or personal commentary. That is the author’s voice, not functional instruction.
When in doubt, over-attribute rather than under-attribute.

These are not legal requirements. They are professional norms. They reflect a shared understanding in the food world that recipes are not created in a vacuum — and that acknowledging influence is a sign of respect, not weakness.

Private storage vs. public publishing

Here is where the ethical and legal landscape intersects with how you use recipes at home.

There is a meaningful distinction between:

Public publishing: Making a recipe available to the world via a blog, social media, or a public-facing platform. This is where copyright and attribution rules apply most strictly.

Private storage: Keeping a recipe in your own collection — digitally or on paper — for personal use. This has always been understood as lawful, whether the medium is a handwritten index card or a digital note.

When you buy a cookbook, you own the physical book and the right to cook from it. You also have the right to make personal copies for your own use — typing a recipe into a document, photographing a page for reference, or transcribing it onto a card.

What you do not have is the right to republish that recipe publicly, to distribute it at scale, or to profit from someone else’s creative work without permission.

This distinction is not new. It has existed as long as cookbooks have. What has changed is the ease with which digital tools allow both private archiving and public redistribution — and the risk that people confuse the two.

Digitizing as format shifting, not republishing

The concept of “format shifting” — moving content you own from one medium to another for personal use — is well established in copyright discussions. Ripping a CD you purchased to play on an MP3 player is a common example.

Digitizing recipes from cookbooks you own operates on similar logic. You are not creating new public copies. You are translating a format you already have access to into a more convenient, searchable, and durable form for your own household.

This is not redistribution. It is preservation.

The ethical standard here is straightforward: digitizing for personal use respects the creator’s work by ensuring it survives longer and remains accessible. Digitizing for public republishing — especially without attribution — does the opposite.

How Sharp Cooking approaches copyright and ethics

Sharp Cooking is built on the principle that your recipe collection is private — a digital equivalent of the recipe box your grandmother kept on the counter.

That architectural choice shapes everything:

Recipes are private by default. Nothing you save is indexed by search engines.
Shared recipes require explicit permission. Sharing is opt-in, not automatic.
We block bots and crawlers. Your collection is not training data for AI or content for aggregators.
We do not build a public recipe directory. We are not a publishing platform. We are a storage tool.
AI extraction is a formatting assistant, not a republishing engine. When you use AI to digitize a recipe from a photo or URL, that content stays in your private collection. It is not redistributed, indexed, or monetized by us.

These are not just technical features. They are ethical commitments.

We do not monetize user-generated recipe content. We do not treat your personal archive as a dataset to scrape or a catalog to index. We do not assume that because a recipe exists on the internet, it is free to redistribute.

You remain responsible for storing content you have lawful access to. We provide the infrastructure. You decide what belongs in your collection and how you use it.

What this means for you

If you are a home cook building a personal recipe archive, the principles are simple:

Recipes you collect for personal use — from cookbooks, blogs, handwritten cards, or family emails — can be digitized and stored privately. This has always been permissible.
If you share a recipe with someone else, especially publicly, attribute the source. Even when the law doesn’t require it, respect does.
Do not copy headnotes, stories, or creative commentary. Those belong to the author. The ingredient list and functional instructions are what you store.
Understand the difference between a private kitchen archive and a public publishing platform. One is a tool for your household. The other is a distribution channel. They are not the same thing.
When in doubt, give credit. Attribution costs nothing and preserves the culinary lineage that makes cooking meaningful.

FAQ

Are recipes copyrighted?

In most jurisdictions, ingredient lists and basic procedural instructions are not copyrightable. They are treated as facts or functional procedures. What is copyrightable is the creative expression around the recipe: the narrative, the headnotes, the specific language used to describe the process, and the photographs or layout. Legal permissibility to copy a recipe’s functional parts does not mean it is ethical to do so without attribution.

Can I digitize a recipe from a cookbook I own?

Yes. Digitizing recipes from books you own for personal use — what copyright experts call “format shifting” — is generally understood to be lawful. You are not creating new public copies; you are converting content you already have access to into a more convenient format for your household. This is comparable to ripping a CD you own to play on a digital device.

What does “adapted from” mean?

“Adapted from [source]” means you started with someone else’s recipe and made significant changes — altering ingredients, modifying the method, or adjusting proportions. It signals that the original recipe informed your version, but your version is not identical. This is the standard attribution format recommended by food writers like David Lebovitz and organizations like the Food Blogger Alliance.

That depends on how you share it and what you share. Sharing a link to a recipe is always fine — you are directing someone to the original source. Copying the full text of a recipe and republishing it, especially on a public platform, is ethically questionable and may be legally problematic depending on how much creative expression (headnotes, commentary, photos) you include. When in doubt, link to the source or share only the ingredient list with attribution.

What is the difference between private storage and public publishing?

Private storage means keeping a recipe in your own collection — whether on paper or digitally — for personal use in your household. Public publishing means making a recipe available to others via a blog, social media, or public-facing app. The ethical and legal standards are very different. Private storage has always been understood as permissible. Public publishing requires attribution and, depending on the content, may require permission.

Does Sharp Cooking scrape or republish recipes?

No. Sharp Cooking is a private storage tool, not a publishing platform. When you use AI to digitize a recipe from a photo or URL, that content is added to your private collection. It is not indexed by search engines, shared with third parties, or used to build a public recipe directory. Your collection remains yours.

Recipes are meant to be cooked, adapted, and passed down. Sharp Cooking helps you preserve the ones you love — privately, respectfully, and securely.