You have read a hundred of these
We get it. The internet is drowning in recipes that sound great in theory but fall apart in practice. The ones that work are usually hidden behind paywalls or buried under layers of ads. Here, we don’t do that.
Every recipe here is built to survive the chaos of a real kitchen—not just the one in a stock photo.
That means no vague ‘taste as you go’ advice when precision matters. No ‘adjust to your liking’ when what you like might ruin the dish.
And no pretending a recipe is ‘easy’ if it’s not—we’ll tell you upfront if you need a slow cooker, a blender you don’t already own, or three hours to let flavors marry. The goal isn’t to impress you with our cooking skills.
It’s to give you a recipe that actually works the first time.
You’re right—most of them are just repackaged instructions with no skin in the game.
Anyone can write that they test things
Every recipe here is made at least three times: once by me, once by a friend who’s never cooked it before, and once under conditions that would make a professional chef groan (burners set too high, ingredients measured with a tablespoon instead of a scale, no pre-soaking).
If it fails even once, we rewrite it. That’s why some recipes have steps like ‘let the broth cool for 10 minutes before blending’—not because it sounds fancy, but because we’ve seen what happens when you skip it.
We also keep a ‘failure log’ for each recipe. If a soup separates after sitting overnight, if a broth tastes flat the next day, or if a blender can’t handle the texture, we fix it.
No recipe here is ‘done’ until it works in a rushed weeknight kitchen, a college dorm, or a pot left to simmer while you’re at work. And yes, that means some recipes take longer to write than to cook.
We don’t just taste once and call it a day—we cook until something breaks.
About the author
Nolan Whitaker is the founder and editor of *Soup Recipes Spoon*, and the reason you’ll find more cloves of garlic in these recipes than you’d expect.
The rules we work by
- 1We never use ‘adjust to taste’
Every spice, salt, and acid measurement is tested and locked in. ‘Season generously’ isn’t a rule—it’s a cop-out. If a recipe says ‘½ teaspoon chili flakes,’ that’s what it takes to balance the dish without overpowering it. No guesswork.
- 2We prioritize ‘day-after’ flavor
A great soup should taste better reheated than it does fresh off the stove. That means longer simmer times, specific starches for thickening, and sometimes even a splash of vinegar to cut through richness. It costs time, but it saves you from scraping the pot later.
- 3We assume your tools are basic
No recipe here requires a mandoline, a sous-vide machine, or a chef’s knife you’ve never sharpened. If we ask for a ‘sharp knife,’ we mean the one you already own—not the one you’ll buy and never use again. The only exception? A good pot. A bad pot ruins everything.
- 4We lie about ingredients sometimes
Not the *real* ones—just the ones you might already have. ‘Fresh herbs’ might mean ‘dried oregano,’ and ‘aromatic vegetables’ could be ‘the leftover onion and carrot from last night’s stir-fry.’ We’d rather you use what’s in your fridge than skip the recipe entirely.
- 5We delete recipes that don’t work
If a dish fails three tests in a row—even if it’s ‘interesting’—it gets archived. No ‘here’s how to fix it if you’re feeling ambitious.’ If it’s not foolproof, it doesn’t belong here. That means some of your favorite soups might be missing, but every one left is worth making.
Breaking the rules happens. Last winter, we published a miso-butternut squash soup that turned out to be too sweet for its own good—even after four revisions. The issue? The squash was roasted too long, caramelizing into syrup.
The fix wasn’t more sugar; it was less time in the oven and a splash of rice vinegar to cut through the sweetness. Now that recipe has a warning: *‘Do not roast the squash past golden brown.’* Rules exist to be tested, not worshipped.
This will not be right for everyone
If you’re looking for ‘quick’ soups that take less time than boiling water, this isn’t the place. If you want recipes that sound like they’re from a food blogger’s Pinterest board but were never actually cooked, look elsewhere.
And if you’re the kind of cook who measures spices by smell and salt by ‘how it feels,’ you’ll probably want to skip the exact measurements here—though we’d argue those recipes might not taste as good the next day.
This site is for people who’ve burned a broth, over-salted a stew, or spent an hour stirring a pot only to realize they forgot the main ingredient. It’s for anyone who’s ever Googled ‘why does my soup taste bland’ at 11 PM on a Tuesday.
If that’s not you, that’s fine. But if it is, you’ll find what you’re looking for here.
You could just be told what you want to hear
We could tell you every recipe here is ‘comfort food for modern life’ or that we ‘believe in the power of a well-seasoned broth.’ But that’s not how we work.
Instead, we’ll tell you when a recipe needs a high-speed blender, when you can substitute a can of beans without noticing, and when a soup tastes better the third day than the first.
We’ll also tell you when a dish is overrated, when a shortcut saves time but ruins texture, and when you’re better off buying the jarred version.
Worth telling us
- The one ingredient you *must* buy fresh (and why the canned version won’t cut it)
- How we fix a soup that’s too thin, too thick, or just ‘off’ after sitting overnight
- The dishes we’ve tried—and failed—to recreate from scratch (and what we learned from the disaster)
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.