You want dinner ideas, not a lecture. So here they are first — sorted by what you probably already have. The reason this list is organised by ingredient and not by cuisine is that the useful question isn't "what do I feel like eating," it's "what can I actually make right now without going to the shop."
20 dinners, sorted by what's in your fridge
If you have eggs
- Frittata — whatever vegetables are wilting, plus eggs, in an oven-safe pan. Genuinely improves with sad vegetables.
- Fried rice — needs day-old rice; fresh rice goes gluey. Egg, whatever protein, whatever veg, soy.
- Shakshuka — tinned tomatoes, onion, garlic, eggs poached on top. Fifteen minutes, one pan.
- Egg-drop soup — stock, a beaten egg stirred in slowly, spring onion. Absurdly fast.
- A proper omelette and toast — allowed to be dinner. It's dinner.
If you have chicken
- Sheet-pan chicken and vegetables — everything on one tray, 200C, 35 minutes, no attention required.
- Stir-fry — chicken, any three vegetables, garlic, soy, a splash of vinegar. Eight minutes.
- Chicken and rice soup — the correct answer when it's cold and you're tired.
- Chicken thighs with whatever starch — thighs are forgiving; breasts punish inattention.
- Chicken tacos — shredded, with anything crunchy on top.
If you have mince (ground beef, pork, lamb, turkey)
- Chilli — mince, tinned tomatoes, tinned beans, cumin. Better the next day.
- Bolognese — worth the slow version if you have an hour, fine in twenty if you don't.
- Tacos — the lowest-effort way to make mince feel like a meal.
- Meatballs — mince, breadcrumbs, egg, whatever herbs. Freeze half.
- Rice bowl — browned mince, rice, a fried egg, chilli oil. Ten minutes.
If you have pasta and almost nothing else
- Cacio e pepe — pasta, hard cheese, black pepper, pasta water. Three ingredients, and it's very good.
- Aglio e olio — garlic, olive oil, chilli flakes. Store-cupboard dinner par excellence.
- Tuna pasta — tinned tuna, olive oil, lemon, whatever green thing survives in the drawer.
- Pasta with tinned tomatoes and butter — a tin, an onion halved, a lot of butter. Don't overthink it.
- Pasta bake — the correct destination for leftovers you're bored of.
Scan that list and you'll notice something: your fridge almost certainly already contains three or four complete dinners. It always did. The problem was never a shortage of options.
So why is this so hard?
Deciding what to make for dinner is structurally one of the hardest small decisions you make, and it's for two reasons that compound.
First, the option space has no edges. Most decisions arrive pre-narrowed — which of these two routes home, which of these three job offers. "What should I eat" technically admits every dish that has ever been cooked. Difficulty in choosing scales with the number of options, and it scales badly. It does not scale with how much the decision matters. That's the counterintuitive part, and it's why dinner can feel heavier than choices with genuine stakes: the stakes are trivial, but the search space is enormous, and it's the search space that does the damage.
It's also why "just cook something!" is such useless advice. It doesn't narrow anything. It's a restatement of the problem with an exclamation mark.
Second, you're asked at your worst moment. Dinner gets decided at the end of the day by a version of you who is hungry, tired, and has already spent the day's judgment elsewhere. Under those conditions two biases dominate: you'll favour whatever is fastest, and whatever requires no further thought. Both point at takeout. The takeout order isn't a willpower failure — it's the correct output of the conditions. If you want a different result, change the conditions, not the willpower.
Which means any system that works has to do one of two things: shrink the option space, or move the decision away from 6pm. The good ones do both.
The four systems that actually end the question
1. Theme nights
Best for: households with kids, or anyone who wants structure with zero setup.
Monday is pasta. Tuesday is tacos. Wednesday is a grain bowl. Thursday is soup or stir-fry. Friday is whatever's left.
This works because it collapses the option space from "every meal" to "every pasta" — a difference of several orders of magnitude. You're no longer deciding what to eat, only which version. That's a decision you can make while tired. The limitation: it has no idea what's in your fridge. If it's Monday and you have no pasta, the system has nothing to say. It's a good scaffold and a bad database.
2. Batch cooking
Best for: people who cook alone, or who like cooking but not on weeknights.
Cook two or three things in quantity at the weekend; eat them through the week. The decision gets made once, under good conditions, and then you coast. It genuinely works — and the catch is that it answers "what will I eat" without answering "what do I want to eat." By Thursday, the thing you enthusiastically cooked on Sunday is just a container. It solves the logistics of dinner and not the boredom of it.
3. Weekly meal planning (the popular one, and the one that fails)
Best for: a specific kind of person — and it's worth being honest about whether that's you.
Sit down Sunday, plan seven dinners, build a grocery list, shop once, execute. When it works it's the best system there is. But it asks you to predict, on Sunday, what a different version of you will want to eat on Thursday. That version had a bad meeting. That version is not in the mood for the salmon. And the plan has no fallback, so the first missed night tends to take the rest of the week with it.
It fails in a second, quieter way too: it's a system that depends on you continuing to run it, every Sunday, forever. Most people don't quit meal planning because it stopped working. They quit because they missed one Sunday, then two, and never restarted. If you've drifted away from it three times, the problem isn't your discipline — it's that you picked a system that requires discipline.
4. Don't make the decision at all
Best for: people who want the outcome of meal planning without the maintenance.
The newest option is to hand the decision to something else. Not a recipe search — a search is still a decision with extra steps — but an actual delegation, where something else decides and tells you the answer.
This is worth distinguishing carefully, because it's easy to confuse with the apps you've already tried. Ingredient-search apps like SuperCook are genuinely excellent, and if you enjoy picking your own meal from a list of matches, SuperCook has a far bigger recipe database than we do and you should use it. But it's still you, at 6pm, hungry, choosing from a list. The app narrowed the options. It didn't make the decision.
The delegated version looks like this: you tell it once what's in your kitchen and what you can't eat. Then at dinnertime it tells you what you're cooking. One meal. Not a list. You didn't open anything, and you didn't choose.
How to pick
| If you... | Use | Honest catch |
|---|---|---|
| Want structure with zero setup | Theme nights | Doesn't know what's in your fridge |
| Like cooking, hate weeknight cooking | Batch cooking | Boring by Thursday |
| Genuinely enjoy planning | Weekly meal plan | Collapses the first Sunday you skip |
| Enjoy browsing and picking yourself | SuperCook or similar | You're still deciding at 6pm |
| Want to stop thinking about it entirely | Delegate the decision | You give up the choice |
What we built, and who it isn't for
Mealody is the fourth option. You add what's in your fridge once — by hand, or by photographing the shelf — and set what time you eat. From then on your phone sends you one meal at breakfast, lunch, and dinner: something you can cook right now, from what you already have, filtered against your household's allergies, diet, and the things you simply don't like.
It draws from 1,248 recipes across 22 cuisines and it's free on iOS. You don't browse it. Most days you never open it — the notification is the product.
It is not for everyone, and it would be dishonest to pretend otherwise. If you like standing in the kitchen working it out, you'll find it bossy. If choosing dinner is one of the small pleasures of your day, don't hand it to a notification. But if "what's for dinner" is a small daily tax you'd rather stop paying, this is what it looks like to stop paying it.
Frequently Asked Questions
I don't know what to make for dinner. What should I cook?
Start from what you already have. Eggs: frittata, fried rice, shakshuka. Chicken: sheet-pan chicken and veg, stir-fry, chicken and rice soup. Pasta and little else: cacio e pepe, aglio e olio, tuna pasta. Mince: chilli, bolognese, tacos. Nearly every fridge already holds three or four complete dinners — the problem is trying to remember them at 6pm while hungry.
Why is deciding what to make for dinner so hard?
Two reasons compound. The option space has no edges — "what should I eat" admits every dish ever cooked, and choosing gets harder as options multiply regardless of how little the decision matters. And you're asked at the worst possible moment: hungry, tired, and already out of judgment for the day. Under those conditions, takeout is the predictable output, not a willpower failure.
How do I stop having to decide what's for dinner every night?
Pick a system that shrinks the options or moves the decision out of 6pm — the good ones do both. Theme nights, batch cooking, weekly planning, or delegating it entirely to an app that pushes you one meal at mealtime from only what you can actually cook tonight.