What to cook tonight when you don't know what to make

It's 6pm. You're standing in front of the fridge. You have half a head of cabbage, some leftover rice, two eggs, and a vague sense of dread. You open a recipe app, get served a list of trending dishes that require ingredients you don't have, and eventually order takeout.

This happens to almost everyone, almost every night. And it's not a motivation problem — it's a search problem. The right recipe for what's in your fridge already exists. You just can't find it.

The fridge stare is a search failure

Most recipe apps are built for discovery — they show you what's popular, what's trending, what's in season. That's useful when you're meal planning on a Sunday afternoon. It's useless at 6pm on a Tuesday when you need to cook what you have.

The recipes that solve tonight's dinner aren't the ones on the front page of a cooking website. They're the ones that work with cabbage and rice and eggs. The ones your mother made when the fridge was almost empty. The ones you've cooked before and know actually work.

Start with what you have, not what you want

The most reliable way to answer "what's for dinner" is to reverse the question. Instead of finding a recipe and buying ingredients, start with the ingredients and find the recipe.

This sounds obvious, but it requires a different kind of search. You need to be able to say: "I have chicken, garlic, and half a lemon — what can I make?" and get a real answer, not a list of dishes that happen to contain chicken.

A few approaches that actually work:

• Search your own recipe collection first — the dishes you already know how to make are faster and more reliable than anything new
• Think in techniques, not recipes — if you can sauté, roast, or make a quick sauce, you can cook almost anything in your fridge
• Keep a short mental list of 5–6 "fridge-clearing" dishes you can always fall back on — a frittata, a stir-fry, a grain bowl, a simple pasta

The best source is your own recipe collection

Generic recipe websites don't know what you like, what you're good at, or what you've cooked successfully before. Your own recipe collection does.

If you've been saving recipes — from family members, from cookbooks, from dishes you've made and want to make again — that collection is the most valuable cooking resource you have. It's curated by you, for you. Every recipe in it is one you've already decided is worth making.

The problem is that most people can't search their own collection by ingredient. Recipes are scattered across bookmarks, screenshots, recipe cards, and half-remembered conversations. So the collection exists, but it's not usable at 6pm.

Make your collection searchable

Whatever system you use to store recipes, the goal is to be able to answer one question quickly: "Given what I have right now, what can I make?"

If your recipes are in a notebook, a quick index by main ingredient on the first page goes a long way. If they're digital, any system that lets you search by ingredient is better than one that doesn't.

The payoff is significant. When you can search your own recipes by what's in your fridge, the "what's for dinner" question stops being stressful. The answer is already there — you just needed a way to find it.

The simplest rule for tonight

Look at what you have. Think of one protein, one vegetable, one starch. Search for a recipe that uses all three. If you find one you've made before, make that. If you don't, make the simplest version you can imagine — seasoned, cooked through, served warm.

Dinner doesn't always have to be inspired. Sometimes it just has to happen.