Are Recipes Intellectual Property? (2026 Updated)

You’ve spent months (maybe years) perfecting a recipe. It might be your signature hot sauce, a spice blend your customers rave about, or a plant-based dessert that finally tastes right. So it’s completely normal to ask: “Is my recipe protected by law?”

This is one of the most common questions we hear from food and beverage founders - and for good reason. Recipes can be a real competitive advantage, and once they’re out in the world, it can feel like anyone could copy them.

This guide is updated for 2026 and reflects current New Zealand intellectual property (IP) and consumer law basics, including the practical reality of how recipes are protected (and where the gaps usually are).

Let’s break it down in plain English: what “intellectual property” actually means for recipes, what you can protect, what you usually can’t, and the best legal steps to protect your business from day one.

What Does “Intellectual Property” Mean For A Recipe?

Intellectual property is a broad term for legal rights that protect valuable intangible assets - things like brand names, logos, product designs, written content, inventions, and confidential know-how.

When you’re talking about recipes, you’re usually dealing with a mix of different “assets”, for example:

• The written recipe (your specific wording, layout, instructions, photos, notes)
• The underlying method/formula (the combination of ingredients, proportions, technique)
• The product brand (name, logo, packaging look and feel)
• Your business systems (supplier details, prep processes, shelf-life testing, batch sheets)
• Your marketing content (web copy, product descriptions, videos)

The tricky part is that different IP rights protect different parts of that overall package - and recipes are rarely protected the way people expect.

The Key Idea

In New Zealand, a recipe is usually protected best as a trade secret (confidential information), supported by strong contracts and internal processes. Some parts of your recipe materials may also be protected by copyright, and your brand can be protected by a trade mark.

Are Recipes Protected By Copyright In New Zealand?

Sometimes - but usually not in the way that stops someone cooking the same thing.

Copyright protects original “expressions” of ideas, not the ideas themselves. In a recipe context, copyright is more likely to protect:

• the exact wording of your written recipe and instructions (if they’re original)
• original photos, videos, and recipe book layouts
• blog posts, product descriptions, and other written content you create

However, copyright generally does not protect the underlying concept of the recipe - like “a spicy mango chutney” - or a basic list of ingredients and simple steps that are purely functional.

So What Does That Mean In Practice?

If someone copies and pastes your recipe text from your website into their own cookbook or online store, you may have a copyright issue to pursue.

But if they read your recipe and then rewrite it in their own words (or reverse engineer the product and create their own version), copyright often won’t stop that.

This is why recipe businesses usually need to think beyond copyright and focus on confidentiality and brand protection.

Can You Patent A Recipe Or Food Product?

Occasionally - but for most food businesses, patents aren’t the main protection.

A patent protects a new invention (like a novel process, composition, or technical solution). In theory, certain food innovations can be patentable, especially where there’s:

• a genuinely new product composition (not just a twist on an existing recipe)
• a technical benefit (e.g. shelf stability, improved texture, reduced allergens)
• a novel manufacturing method or process

In practice, many recipes don’t meet the threshold for patent protection because they’re considered:

• too obvious (in a legal sense)
• not new (someone else has done something similar)
• too difficult to define as a technical “invention” rather than culinary creativity

The Big Trade-Off With Patents

If you apply for a patent, you generally need to disclose the invention publicly in the patent specification.

For many businesses, that’s the opposite of what you want - especially if the recipe’s value comes from secrecy.

So, while patents can be powerful in the right circumstances, most recipe-based businesses in NZ focus on:

• confidential information protections (trade secrets)
• trade marks (brand protection)
• tight contracts with manufacturers, staff, and partners

How Do You Protect A Recipe As A Trade Secret?

For most food and beverage founders, the most effective approach is treating your recipe as confidential information - meaning you protect it as a trade secret.

Trade secrets aren’t “registered” like trade marks. They’re protected through a combination of:

• keeping the information genuinely confidential
• only disclosing it when necessary
• using the right legal documents and practical controls

What Counts As A Trade Secret?

A trade secret can include:

• ingredient quantities and ratios
• specific technique (timing, temperature, sequence, curing process)
• supplier lists and sourcing details
• batch production records and quality control metrics
• product testing results (shelf life, allergen testing, stability testing)

The more effort you take to treat it as confidential, the easier it is to argue later that it was confidential and shouldn’t have been misused.

Practical Steps To Keep Your Recipe Confidential

If you want your recipe protected as a trade secret, you’ll usually need to build confidentiality into how your business operates. For example:

• Limit access to the full recipe (not everyone needs to know everything).
• Split knowledge across team members (one person measures spice blend, another handles final assembly).
• Keep version control and document who accessed the recipe and when.
• Secure storage (password-protected systems, restricted folders, physical lockbox for printed formulas).
• Mark documents as confidential and ensure people understand what that means.

These steps aren’t just “nice to have” - they’re often what determines whether you can realistically take action if someone walks away with your formula.

The Contracts That Usually Matter Most

Strong legal foundations are what turn “please don’t share this” into something enforceable. Depending on your setup, that might include:

• a Non-Disclosure Agreement before you share the recipe with a potential manufacturer, investor, collaborator, or staff member
• well-drafted clauses in your Employment Contract covering confidentiality and IP created during employment
• a proper manufacturing agreement (especially if you’re using a co-manufacturer)
• clear service or supply terms for people involved in production

It can feel awkward asking someone to sign an NDA early on - but it’s one of the cleanest ways to show that you take confidentiality seriously.

What About Trade Marks, Branding, And Packaging?

Even if the recipe itself is hard to “own” legally, your brand is usually much easier to protect - and it’s often what customers actually recognise and trust.

Brand protection is especially important when:

• you’re selling packaged products (retail or online)
• you’re building a following on social media
• you’re expanding into new regions or exporting
• you’re working with distributors, resellers, or franchise partners

Trade Marks Can Protect Names And Logos (Not The Recipe)

A trade mark can help protect things like:

• your product name
• your business name
• your logo
• sometimes slogans and distinctive brand elements

If a competitor starts selling a similar product and uses a confusingly similar name, a trade mark can give you stronger options to stop them.

This matters because even if someone can lawfully make “something similar”, they generally shouldn’t be able to ride on your reputation by copying your branding.

Don’t Forget Consumer Law Around Claims And Labelling

If you’re selling food products, what you say on your packaging and ads matters. In NZ, businesses need to comply with the Fair Trading Act 1986 (misleading or deceptive conduct and false claims) and the Consumer Guarantees Act 1993 (certain guarantees to consumers).

From an IP perspective, this also comes up when people use “copycat” branding - packaging that’s designed to mislead customers into thinking they’re buying your product.

If you’re building a direct-to-consumer brand online, it’s also worth having a fit-for-purpose Privacy Policy, because even a simple mailing list or online store can involve collecting personal information.

Common Scenarios Where Recipe Protection Goes Wrong

Most recipe disputes don’t start with strangers on the internet. They usually start with someone who was close to the business - a staff member, co-founder, contractor, or manufacturer.

Here are a few common situations where founders get caught off guard.

1. A Co-Founder Or Collaborator Leaves With The Recipe

Early stage businesses often build recipes collaboratively. If the relationship breaks down and there’s no clear agreement, it can be hard to prove who owns what - or what someone can do after they leave.

This is why a tailored Founders Agreement (or a proper collaboration agreement) can be critical, even if you’re still “testing the concept”.

2. A Contractor Creates The Product Development Work

Maybe you hired a food technologist, a chef consultant, or a product developer to help you finalise the formula. A key question is: who owns the IP created during that engagement?

Ownership doesn’t always automatically transfer just because you paid for the work. You typically need clear written terms that assign IP rights to your business and lock in confidentiality.

If you’re engaging external help, a well-scoped Consulting Agreement can help set expectations around IP ownership, confidentiality, and deliverables.

3. A Manufacturer “Reuses” Your Formula

If you use a third-party manufacturer (including a co-packer), they may have access to:

• full ingredient ratios
• process steps
• batch records
• packaging specs and supplier details

Without a proper manufacturing agreement (and confidentiality obligations), you can end up in an uncomfortable grey area if they later produce a “similar” product for another customer - or launch something themselves.

This is where NDAs help, but a broader agreement often needs to cover things like:

• who owns improvements or variations
• what happens to your data and documents after termination
• non-use / non-supply restrictions (where appropriate)
• quality control and product specifications

4. You Accidentally Make The Recipe Public

Posting “the full recipe” online (or sharing detailed percentages and steps in marketing) can undermine your ability to argue it’s confidential later.

If your competitive edge depends on secrecy, you’ll want to decide early what your “public-facing” version looks like - and what stays internal.

Key Takeaways

• Recipes can be intellectual property, but not always in the way people expect - copyright may protect your written recipe content, but it usually won’t stop someone making the same dish.
• Most recipe businesses protect the formula as a trade secret by keeping it confidential and using strong contracts and access controls.
• Patents are possible in limited cases, but they’re often expensive and require public disclosure, so they’re not the default option for most recipes.
• Your brand is often your strongest protectable asset - trade marks and consistent branding can help stop confusing copycats even if your recipe can be replicated.
• Strong agreements prevent common disputes, especially when working with co-founders, contractors, staff, and manufacturers (think NDAs, consulting terms, and employment clauses).
• Consumer law still matters - especially around product claims, advertising, and packaging, which must comply with the Fair Trading Act 1986 and Consumer Guarantees Act 1993.

If you’d like help protecting your recipe, your brand, or your commercial arrangements with staff, manufacturers, or collaborators, you can reach us at 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.