Sunday, November 22, 2026 Fresh recipes, tested in our kitchen — every day.

Contact Us

Got a question about a recipe? A substitution that worked brilliantly, or one that flopped? We want to hear about all of it. Messages from readers are how a lot of our recipes get better: a missing step gets clarified, a cook time gets adjusted, and more than a few brand-new recipes started life as someone asking, “Can you make a version of this?”

Use the form below for recipe questions, feedback, corrections, and recipe requests. If a recipe gave you trouble, tell us which one and what happened, the more detail the better. We read everything ourselves and reply as fast as a small, busy kitchen team can, usually within a couple of days. Business and collaboration inquiries are welcome through the same form.

One small favor: if you are writing about a specific recipe, include its name or the link. It saves a round of detective work on our end and gets you a useful answer much sooner.

Prefer email? Reach us directly at contact@foodrecipedaily.com — we read every message.


How to Write a Message That Gets a Good Answer

The form below takes any message, long or short, but a few details make a big difference to the quality of the reply. Start with the recipe name, if your message is about a recipe. Then say what happened, or what you want to know, in plain language. “The sauce was thin” is a start. “The sauce was thin after simmering for twenty minutes, and I used low-fat milk instead of cream” is something we can actually answer. Cooking is full of variables, and the more of them you name, the fewer guesses the reply has to contain.

Measurements help too. If you doubled a recipe, halved it, or swapped an ingredient, say by how much. A pinch of difference in salt is one thing. A doubled amount of baking soda is quite another. Pan size, oven type, and whether you used a gas or electric stove all matter for timing questions. None of this needs to be precise to the gram. Rough numbers and honest descriptions beat polished wording every time, because they describe a real kitchen, not an ideal one.

Questions About Substitutions

Substitution questions are among the most common messages here, and they are welcome. The best substitution messages name three things: the original ingredient, the ingredient you want to use instead, and why you are swapping. The reason matters because the best substitute for an allergy is not always the best substitute for a missing ingredient, and the best substitute for a dietary preference may differ again. A dairy-free swap for butter in a sauce is a different problem from a dairy-free swap for butter in a pastry crust, and the answer changes accordingly.

It also helps to know the role the ingredient plays. Is it providing moisture, structure, flavor, or all three? Eggs in a cake do several jobs at once, which is why egg substitutes are trickier than they look. Sugar in a jam is a preservative as well as a sweetener, which is why reducing it changes shelf life, not just taste. If you are unsure about the role, just say what the dish is and what you want to change. Figuring out the role is part of the answer, and it is often the most useful part, because it teaches you how to make the next substitution on your own.

Corrections and Reader Discoveries

If something on a recipe page looks wrong, tell us, even if you are not sure. A step that references an ingredient not in the list, a temperature that disagrees with the recipe card, a photo that shows a different result from the one described, or a link that leads nowhere, all of these are worth a message. Quote the line if you can, or describe where it appears. Corrections are checked against the recipe as it was tested, so a message that turns out to be a misunderstanding still helps, because it shows where the wording needs to be clearer.

Reader discoveries go in the same inbox. Maybe you found a faster way to prep an ingredient, a storage trick that kept leftovers fresh for days, or a variation that your family now prefers to the original. Those discoveries often become notes on the recipe page, credited in general terms to reader feedback, so that the next cook benefits. If you would rather your tip stayed private, say so in the message, and it will.

Recipe Requests and Topic Ideas

A recipe request with context is far more likely to become a real recipe than a bare dish name. Tell us the occasion, the time you have, the number of people you are feeding, and any constraints, like a missing piece of equipment or an ingredient to avoid. “A slow cooker dinner for six, no mushrooms, ready after work” gives a clear brief. “Something with beef” does not, and it will probably sit unanswered while clearer requests get cooked and tested first.

Topic ideas are welcome as well. Maybe a guide would serve you better than a single recipe, like how to choose a knife, how to store spices so they keep their flavor, or how to plan a week of meals without repeating the same dinner. Guides take more work than recipes, so they are chosen carefully, and reader demand is one of the main signals. If several readers ask for the same guide, it moves up the list, which is another reason to send the idea even if it feels small.

Business, Press, and Collaboration Messages

The same form handles business messages, and a clear proposal gets a clearer answer. Say who you are, what you are proposing, and what it would involve on both sides. A brand pitching a product should name the product and explain why it fits a home cooking audience, rather than sending a generic pitch that could have gone to any food site. A writer proposing a guest contribution should name the topic and explain the angle, not just ask whether guest posts are accepted.

There are a few things this site does not do, and stating them here saves everyone a round of messages. Paid links disguised as editorial recommendations are not accepted. Reviews are not promised in exchange for free products. Recipes are not published as advertisements. Those boundaries keep reader trust intact, which is the site’s main asset, and they apply evenly, whether the sender is a small producer or a large brand.

Website Problems Worth Reporting

If the site itself misbehaves, a report helps more than you might think. Note the page you were on, what you were trying to do, and what happened instead. A recipe that will not print, a page that loads without images, a form that erases your message on submit, or a link that goes to the wrong place, each of those has a different cause, and the description points to it. Your device type and browser, if you know them, narrow it down further.

You do not need technical language. “I tapped the print button on my phone and got a blank page” is a complete and useful report. If an error message appeared, its exact wording helps, but a plain description of what you saw is enough to start. Reports from readers often catch problems that never appear during testing, because real readers use a wider mix of devices, browsers, and connections than any test setup covers.

A Note on Privacy in Your Message

Only include personal details that are needed to answer your question. A name and an email address are enough for a reply. There is no need to include home addresses, phone numbers, or financial details in a recipe question, and you should never send passwords or account credentials through a contact form on any site, including this one. Messages are read privately and are not published. If a message leads to a correction or a new recipe, the published update will not identify you unless you have specifically asked to be mentioned.

If you are writing on behalf of someone else, like a family member who cooked a recipe and has a question, say so, and include the details as they experienced them. Second-hand cooking questions are harder to answer, because the person who was in the kitchen is not the person writing, but they are still welcome, and a few concrete details bridge most of the gap.