Why this site exists
You’ve got a recipe that promises a pot of beans so rich it’ll make your neighbors knock on the door—but the first bite tastes like a can of beans that sat too long in a cupboard, or the texture is wrong: mushy, or too thick, or just *off*.
The instructions assume you own a pressure cooker or a slow cooker that doesn’t leak, or that you can eyeball ‘a pinch of salt’ without ending up with a bowl of soup.
This site exists to fix that. Every recipe here is cooked at least three times—once by me, once by someone who doesn’t own a fancy gadget, and once by someone who’s never made beans from scratch.
We adjust until it works in a real kitchen, with real tools, and real time. No shortcuts, no guesswork.
Who writes this site
Dwight Hutchins is the founder and editor of Bean Recipes Stew.
How many times do you test a recipe before publishing it?
At least three. Once by me, once by someone who doesn’t own a pressure cooker, and once by someone who’s never made beans from scratch. If it fails any of those tests, we go back to the drawing board.
What’s the worst mistake you’ve made in a recipe?
A batch of refried beans that turned out so thick you needed a spatula to spread it. The instructions said ‘mash until smooth,’ but I mashed until it was glue. Fixed it by adding broth one tablespoon at a time.
Why are there no recipes for lentils here?
Because I refuse to cook them. I’ve tried. They turn to mush or taste like dirt. I’ll write about beans until I can figure out lentils—or until someone else sends me a recipe that actually works.
I keep a jar of dried beans on the counter. Not for cooking—just to look at. The colors, the shapes, the way they rattle when you shake them. It’s the only thing in the kitchen that doesn’t get used every day.
How a recipe is built
A recipe starts with a question: *What’s the one thing that always goes wrong with this dish?* For beans, it’s usually texture—too thick, too thin, or just *wrong*. So we start there.
The first test
The first batch goes in my kitchen with my tools: a heavy pot, a wooden spoon, and a timer. I write down every step, every misstep, and every time I second-guess myself. If the beans split open or the broth turns cloudy, I note why. No excuses. Just facts.
I never skip the tasting. Even if it’s terrible. That’s how we find what’s missing—a pinch more salt, a splash of vinegar, or an extra hour of soaking.
The fixes
The second test happens in a kitchen with half the tools. No fancy gadgets, no shortcuts. If the recipe relies on a blender or a food processor, we do it by hand—even if it takes twice as long.
The third test is the brutal one: someone who’s never cooked beans before tries it. If they can’t follow the steps without guessing, we rewrite them.
We keep adjusting until it works for all three. No exceptions.
What we will not do
We won’t publish a recipe that hasn’t been tested in three different kitchens. We won’t use ingredients you can’t find at a regular grocery store. We won’t write instructions that assume you own a pressure cooker or a slow cooker that doesn’t leak.
And we won’t pretend a recipe is ‘foolproof’ if it isn’t.
Things you will never find here
- Recipes that require specialty equipment you don’t own.
- Ingredients you can’t find outside a gourmet store.
- Instructions that say ‘season to taste’ without telling you what ‘taste’ means.
- Photos that look nothing like the final dish.
Where to start
If you’re new here, start with the ‘Beginner’s Guide to Cooking Beans.’ It’s not just a recipe—it’s a list of the most common mistakes and how to avoid them. If you’re looking for something specific, use the search bar.
If you can’t find what you need, the contact page is where to ask.
Say hello
I love hearing about the beans you’ve made—or the ones you’ve burned. Send me a message on the contact page. Tell me what worked, what didn’t, or what you’d like to see next.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.