How to make money from your recipes (without a food blog)

Disclosure first: we make Drry, which is software for running a paid community, so we are not a neutral party on the question of whether you should run one. Read the arithmetic below and decide for yourself. The argument is that the two default ways to make money from recipes, display ads and a one-off ebook, both pay badly for the work involved, and that a small monthly membership pays better with a smaller audience, as long as you understand that people are not paying for the recipes.

Why the default paths pay so badly

Start with display ads, because that is what most food creators are told to do. Ad networks pay on a per-thousand basis, and the number swings wildly: by season (food traffic and advertiser spend both collapse in January and spike in November), by where your readers live, by whether they are on mobile, and by which network you are on. A rough working range for a food site is somewhere between $5 and $25 per thousand sessions, and you should check your own numbers rather than trust anyone else's, including ours.

Now do the arithmetic. To earn $900 in a month at a $15 rate you need roughly 60,000 sessions. At $5 you need 180,000. Those are not beginner numbers. They are the output of years of SEO work in one of the most brutally competitive niches on the internet, where you are fighting national publishers with staffed test kitchens for the phrase "banana bread". And the ground has moved under that game: AI answers now lift the ingredient list and the method straight out of the page and show them without the visit, which means the same ranking produces fewer sessions than it did, and sessions are the only thing ads pay for.

The other default is the ebook. Someone likes you enough to hand over $19, they get a PDF, and then the relationship ends. You have to find a new person to earn the next $19. It is not that ebooks are bad, it is that you have converted the warmest thing you own, somebody's trust, into a single transaction and then thrown away the receipt.

Nobody pays monthly for a file

Here is the part people get wrong when they try to charge. They put fifty recipes behind a paywall, price it at $9 a month, and are surprised when members leave in month two. Of course they do. The member downloaded the fifty recipes. What are they paying for in month three?

Be honest about this: recipes are commoditised. There are millions of free ones, and a decent AI will now write you a passable weeknight dinner on demand. If your entire offer is "access to recipes", you are selling something with an infinite free supply, and the market prices that at zero.

What is not commoditised is you. The recipes are the spine of the product, not the product. The product is:

• The collection being kept current. New recipes on a rhythm, seasonal swaps, the summer set and the winter set. A membership is a subscription to your ongoing attention, not to an archive.
• Cooking alongside you. A monthly live cook-along where forty people make the same thing at the same time, on whatever video tool you already use, is worth more than forty people making it alone, and the people who show up to it are usually the ones who stay subscribed.
• The room where the questions get answered. "Can I swap the yoghurt for coconut milk?" is a question with no good free answer. Google gives you eight contradictory forum threads. You give one answer, from the person who wrote the recipe, in ten seconds. That is the thing people actually pay for, and it is the thing no file and no search result can supply.

If you take one idea from this guide, take that one. Price the access to you. Let the recipes be the reason people believe the access is worth having.

The pricing math, done properly

Membership numbers look small until you compound them. Work an example at $9 a month, which is a comfortable impulse price for a recipe membership and low enough that nobody has to think hard.

Now the part nobody wants to look at, which is churn. Some percentage of your members cancel each month. For a small membership, 5% to 10% monthly is a realistic band, and it improves as you get better at the first two weeks. The useful shortcut is that the average member stays roughly 1 divided by your monthly churn rate. At 5% that is 20 months, so each $9 member is worth about $180 over their life. At 10% it is 10 months and about $90.

The second useful shortcut is that a membership settles at new members per month divided by churn rate. Add 5 members a month with 5% churn and you level off at 100 members, which is that $900. Add 10 a month at the same churn and you level off at 200, which is $1,800. That is the entire growth model on one line, and it tells you where to spend your effort: either bring in more people, or keep the ones you have for longer. Most creators obsess over the first and ignore the second, even though halving churn does the same thing as doubling signups and is usually far cheaper.

One more number worth naming: the fee. If a platform takes 10% of member payments, your $900 month is $810, and the cut grows exactly as you do while doing nothing more for you at $9,000 than it did at $900. We are not neutral here, so state it plainly and check it yourself: Drrytakes 0% of member payments on every plan, the money runs through your own Stripe account and only Stripe's standard processing fee applies, and the plans are free, $29 a month and $99 a month (the pricing page has the detail). Whichever tool you choose, read the fee line before the feature list.

What to give away, and what to keep in

The instinct once you start charging is to lock everything. Resist it. Your free recipes are not lost revenue, they are the entire marketing function, and they work in a way ads and posts do not: somebody cooks your food, it turns out well, and now they trust you. That is a far shorter path to a paid member than any amount of promotion.

So publish your best recipes publicly. Not your leftovers, your best ones, the ones people screenshot and send to their group chat. Then make sure each one carries an invitation at the bottom: what the membership is, who it is for, and a link. A free recipe that recruits is worth more than a paid recipe that sits behind a wall nobody knows is there.

This is worth setting up properly rather than by hand. In Drry, any single guide can be flipped public, which gives you one shareable link a search engine can index, that carries your own call to action and can capture an email address with an optional form (here is how the guide builder works). So the same recipe you wrote for members doubles as the page that recruits them, and you are not maintaining two copies of anything.

Publish the recipe as a page, not a PDF

The format is not a detail. Watch how a recipe is actually used: somebody is standing in a kitchen holding a phone with one greasy hand, scrolling with a knuckle, checking whether they already added the baking powder. A PDF is miserable in that situation. It zooms wrong, it does not remember where you were, and you cannot tick anything off.

A recipe that respects the kitchen has:

• Ingredients with real quantities, tickable. People shop from this list on their phone and cook from it an hour later. Being able to check items off as you go is the difference between a document and a tool.
• Steps that stand on their own. One action per step, in the order it happens, so a person glancing down mid-task finds their place immediately.
• A photo or a short video on the tricky ones. "Knead until smooth" means nothing to a beginner. Ten seconds of footage of what the dough should look like removes the single most common reason a recipe fails at home.
• Times and servings at the top. Prep time, cook time, how many it feeds. This is the information people use to decide whether to start, so it cannot be buried at the bottom.

This is the shape of Drry's guides: ingredient lists with quantities that members can check off, steps that carry photos or native video, and times and servings up top. They are included free on every plan with no cap on how many you publish, which matters because a recipe collection only gets more valuable as it grows and you should never be counting.

The first thirty days

A concrete sequence, in order, with the thing most people get wrong at each step named.

• Pick one promise.Weeknight dinners in 30 minutes. Batch-cook Sundays. Gluten-free baking that actually works. Not "my recipes", which is a topic, and topics are free. One promise tells a stranger in four seconds whether this is for them, and it tells you what to cook next.
• Put in 8 to 12 recipes, not 60. Enough that day one feels like a real collection, few enough that you can ship this week. Sixty recipes is six months of unpaid work and it makes the collection harder to browse, not easier.
• Price it and charge from day one. $7 to $15 a month is the honest band for a recipe membership. Do not open free with a plan to charge later: converting a free group to paid reliably goes badly, and free sets a culture of lurking. If you want help with the number, we wrote a whole guide on what to charge.
• Invite the audience you already have. Not ads. The people on your email list, the people who reply to your stories, and above all the people who have ever messaged you a cooking question. Message those individually. A warm personal ask converts several times better than anything else you will do.
• Add a live cook-along once it feels like a room. Around 30 or 40 members, a monthly live session stops feeling awkward and starts being the reason people renew. Before that, focus on replying to everyone by name, which does the same job at a smaller scale.

If you want the fuller version of the launch mechanics, including how to run the first week, the paid community playbook covers it step by step.

The short version

Ads need traffic you probably cannot get in a niche this competitive, and AI answers are quietly taking a slice of the traffic you do get. An ebook earns you one payment from someone who liked you enough to buy, and then the relationship is over. A small monthly membership, with the recipes as the spine and you as the product, gets to $900 a month at 100 members and $9, which is reachable from an audience of a few thousand engaged people. Keep the free recipes free and make each one an invitation. Publish them as pages you can cook from, not files. Watch churn as closely as you watch signups, because keeping a member twice as long is worth exactly as much as finding twice as many. And read the fee line before you pick where to build it.