What to Eat for Dinner When You Don't Know What You Want
·9 min read
You open the fridge. You stare into it. You close the fridge. You open the pantry. You stare into that. You close it and walk away, only to circle back ninety seconds later and repeat the whole thing. This is not cooking. This is a diagnostic loop, and it runs until something breaks the cycle or you give up and order Thai food again.
The thing about not knowing what you want for dinner is that it feels like a preference problem — like if you just searched your brain hard enough, you'd find the answer sitting there. But most of the time it's not a preference problem at all. It's a decision architecture problem. Your brain has too many options, too little energy to evaluate them, and no framework for narrowing things down. So it just spins.
Here are several frameworks that actually work when you're stuck. Pick whichever one matches how your brain is working tonight.
Narrow by Format, Not by Dish
Instead of asking yourself what specific meal you want — which requires you to mentally search through hundreds of possibilities — ask a few binary questions about format.
Hot or cold?
Heavy or light?
Eat with your hands or with a fork?
Something crunchy or something soft?
Something you cook or something you assemble?
Each question cuts your option space roughly in half. After three or four of these, you're usually in a specific-enough zone that a meal presents itself. If you answered hot, heavy, fork, and soft, you're in pasta or stew territory. If you answered cold, light, hands, and crunchy, you're looking at wraps or salads with lots of texture. The format narrows the field without requiring you to generate ideas from scratch.
This works because the part of your brain that can answer simple either/or questions is different from the part that generates creative dinner ideas. The first one is still working fine at 6 PM. The second one clocked out at 4.
The Pantry Scan Method
Open the fridge and pantry. Instead of looking for inspiration, look for ingredients. Pull out three to five things that need to be used soon or that catch your eye. Then apply the formula: protein + starch + vegetable + some kind of flavor = dinner.
That's genuinely it. You don't need a recipe. You need a formula.
The pantry scan works because it replaces the blank-slate problem with a constraint problem, and constraint problems are dramatically easier for tired brains to solve. You're not asking 'what should I make out of all possible meals?' You're asking 'what can I make with these five things?' That question has a small, manageable answer.
Here's a trick that sounds silly but works with surprising reliability: pretend you're looking at a restaurant menu in your head. Not a specific restaurant — just the general categories.
Would you order Italian? Mexican? Chinese? Thai? American comfort food? Japanese? Indian? Mediterranean?
Most people can answer this question even when they can't answer 'what do you want for dinner.' Something about the restaurant framing activates a different decision pathway. Once you've picked a cuisine, the specific dish usually follows pretty quickly. Italian means pasta or pizza. Mexican means tacos or burritos. Thai means curry or stir-fry. You've gone from infinity options to two or three.
If even this feels like too much, try the elimination version: would you definitely NOT want Italian tonight? Cross it off. Keep going until only two or three cuisines remain, then pick from those.
Default Meals Everyone Should Have
One of the best investments you can make in your future dinner sanity is building a list of default meals — dinners you can make more or less on autopilot, with ingredients you usually have around, that you know your household will eat without complaint. Not exciting meals. Not new meals. Reliable meals.
Here are some strong candidates for your default list:
Pasta with garlic, olive oil, and parmesan (aglio e olio)
Fried rice with eggs and whatever vegetables are around
Tacos with ground beef or turkey and simple toppings
Quesadillas with beans and cheese
Sheet pan chicken thighs with roasted vegetables
Grilled cheese and tomato soup
Stir-fry with rice (any protein, any vegetable)
Scrambled eggs, toast, and fruit
Black bean burritos
Baked potatoes with whatever toppings are in the fridge
The key feature of a default meal isn't that it's perfect — it's that it requires zero inspiration. You don't need to want it. You just need to be willing to eat it. That's a much lower bar, and on most nights, it's the right bar.
For more ideas like this, our post on what should I eat tonight has a list of twenty-five meals organized by energy level.
The Mood-Based Approach
Your mood affects what you want to eat more than you probably realize. Instead of asking 'what do I want for dinner,' try asking 'how am I feeling right now?' and let the answer guide you.
Stressed or overwhelmed: You want comfort food. Mac and cheese, soup, grilled cheese, pasta with butter. Things that are warm, soft, and familiar. Don't fight it.
Tired but not stressed: You want minimum effort. Scrambled eggs, a grain bowl, quesadillas, anything that's done in under fifteen minutes.
Actually energized: This is the night to try something new. Make that recipe you bookmarked, cook with someone, experiment with a cuisine you don't usually make.
Bored or restless: You want novelty. Spin a random dinner generator, try a new takeout place, or cook something from a cuisine you've never attempted.
Neutral, no particular feeling: Default meal. Go to your list, pick one, don't overthink it.
When you can make anything, you can't decide. But when you add constraints, decisions get easier. This is counterintuitive but extremely well-supported — people make better and faster decisions when their options are limited.
Try adding one constraint and watching how fast the decision resolves:
Time constraint: 'It has to be done in 20 minutes.' Suddenly most recipes are eliminated and you're down to a manageable list.
Ingredient constraint: 'I'm not going to the store.' Now you're working with what's in the kitchen, which is a much smaller set of possibilities.
Equipment constraint: 'One pan only.' Eliminates multi-step recipes and focuses you on sheet pan meals, one-pot pastas, and stir-fries.
Leftover constraint: 'I need to use the chicken from yesterday.' Now the question isn't 'what should I make' but 'what goes with leftover chicken' — wraps, fried rice, quesadillas, chicken salad. Much easier.
Crave works well here because you can type in your constraints directly — 'I have 20 minutes, chicken thighs, and rice' — and it generates something specific. It's basically the constraint-based approach with the final step automated. No scrolling, no browsing, just an answer.
15 Dinners That Work When You Have No Plan
If frameworks aren't doing it for you tonight and you just need someone to hand you an answer, here's a list. These all use common ingredients, take 30 minutes or less, and require minimal decision-making beyond 'which one.'
Fried rice with eggs and whatever vegetables are in the fridge. Ten minutes, one pan, endlessly variable.
Pasta aglio e olio: garlic, olive oil, chili flakes, parmesan. Five ingredients, twenty minutes, tastes like a restaurant made it.
Quesadillas with cheese, beans, and salsa. Press in a dry pan until crispy. Five minutes per quesadilla.
Sheet pan sausage and peppers: slice kielbasa or Italian sausage, toss with peppers and onions, roast at 425°F for 20 minutes.
Scrambled eggs on toast. Add cheese if you want. Takes four minutes and it's a complete meal.
Stir-fry: whatever protein is in the fridge plus whatever vegetables plus soy sauce plus garlic. Serve over rice.
Loaded nachos: chips, canned beans, cheese melted in the oven, topped with sour cream and salsa. Fifteen minutes.
Peanut butter noodles: cook any noodle, toss with peanut butter thinned with soy sauce and a splash of rice vinegar. Warm or cold.
BLT wraps: bacon, lettuce, tomato, and mayo in a tortilla. No cooking beyond the bacon.
Shakshuka: eggs poached in a spiced canned-tomato sauce. Serve with bread. Twenty-five minutes, one pan.
Grilled cheese and canned soup, upgraded with a squeeze of lemon and fresh herbs.
Smash burgers: ground beef pressed thin on a hot skillet. Three minutes per side. Better than most restaurant burgers.
One-pot pasta: dry pasta cooked directly in broth with garlic and cherry tomatoes. The starch thickens everything into a sauce.
Grain bowl: microwave a pre-cooked grain pouch, top with canned chickpeas, avocado, and any dressing you have.
Breakfast for dinner: pancakes, eggs, and bacon. Zero dinner-decision energy required because it's not even dinner. It's breakfast that happens to occur at 7 PM.
When You're Stuck Because You're Cooking for Others
A lot of the 'I don't know what to eat' problem gets worse when you're deciding for multiple people. Your partner is ambivalent, the kids want pizza every night, and you're trying to find something everyone will eat without making three separate dinners.
A few approaches that work:
The 5-3-1 method: One person names five options. The other narrows to three. First person picks the final one. Done in two minutes.
Rotating chooser: Monday is your night to pick, Tuesday is your partner's, and so on. Whoever isn't choosing doesn't get veto power (within reason).
Build-your-own nights: Tacos, baked potatoes, grain bowls, pizza on naan — any meal where everyone assembles their own plate from shared components. Solves the picky eater problem without cooking multiple meals.
Sometimes the best dinner decision is no decision at all. Write your ten default meals on slips of paper, put them in a jar, and draw one. Or use an app like Crave to generate a suggestion — you describe what you're vaguely in the mood for (or just say 'I don't know') and it picks something specific. The commitment to eat whatever comes up is part of what makes this work. You're not deciding anymore. You're just following instructions.
The freedom of not having to choose is underrated. Your brain gets decision fatigue. Offloading the dinner choice to randomness or an algorithm isn't lazy — it's efficient. You eat something reasonable, you don't spend thirty minutes deliberating, and you get your evening back.
If you want more techniques for breaking through dinner indecision, our post on what to do when nothing sounds good covers the 'I'm hungry but nothing appeals to me' version of this problem. And for the deeper psychology of why this keeps happening, why is deciding what to eat so hard is worth a read.
Crave is a free iOS app that picks dinner for you. Type a craving, get a full recipe with ingredients and step-by-step instructions. Download on the App Store.
What should I eat for dinner when nothing sounds good?
Go to your default list — meals you've made before that you know are fine, even when you're not excited about food. If you don't have a list yet, start with eggs on toast, pasta with butter and parmesan, or quesadillas. The goal isn't an exciting dinner; it's getting fed without a 30-minute deliberation.
How do I decide what to eat quickly?
Use the format method: ask yourself hot or cold, heavy or light, hands or fork. Three binary questions usually land you in a specific enough zone that a meal presents itself. Alternatively, add a single constraint (must be done in 20 minutes, must use what's in the fridge) and watch how fast the decision resolves.
What's the easiest dinner to make with no plan?
Fried rice with eggs, pasta aglio e olio, or quesadillas. All three use pantry staples, take under 20 minutes, and require zero advance planning. The formula is simple: protein plus starch plus a vegetable plus some kind of seasoning equals dinner.
Why can't I ever figure out what I want for dinner?
It's usually decision fatigue. By evening, you've made hundreds of choices and your brain's decision-making capacity is depleted. The fix isn't trying harder — it's using frameworks that reduce the number of decisions: binary questions, default meal lists, or letting an app decide for you.
Let Crave pick dinner tonight
Type a craving, get a full recipe with ingredients and step-by-step instructions. Free to try on iOS.