What should I eat? Save your meals once and let a picker decide dinner

"What do you want for dinner?" "I don't know, what do you want?" — that loop is one of the most reliable arguments in any household, and it has almost nothing to do with food. By the time dinner rolls around you've already spent your good judgment on work, errands, and a hundred tiny calls nobody thanked you for. The last thing you have energy for is generating, weighing, and defending a list of options from memory. The fix isn't a recipe — it's removing the decision. Save the meals your household actually eats once, and then let a picker draw one for you.

Build the list once, reuse it forever

The whole idea behind the what should I eat meal picker is that you do the thinking exactly once. Sit down for five minutes and type out the meals you genuinely rotate through — one per line — and they're saved for next time. You're not staring at a blank page at 6pm trying to remember that you like fajitas; you're choosing from a list your calmer, earlier self already wrote. The list lives in your browser, so the next evening you just open the tool and click. Add a meal whenever you discover one, delete the ones that never get picked, and the list slowly becomes an honest map of what your household actually eats rather than an aspirational one.

That single step quietly solves the real problem. Decision fatigue isn't about lacking options — it's about having to summon and rank them under pressure. A saved list converts "what could we possibly eat" into "pick one of these," which is a far smaller question, and one a tool can answer for you instantly.

Tag meals so one list serves every mood

A flat list works, but moods vary. Some nights you have an hour to cook; some nights you want takeout on the table in twenty minutes; some nights you're trying to eat lighter. So you can add #tags after any meal — Stir fry #cook #quick, Pizza #takeout, Salad #healthy #quick — and then filter by them at pick time. There's an Include tag box and an Exclude tag box, and the meal's name is just the line with the tags stripped off, so your results stay clean.

The behaviour of those two boxes is worth getting right, because they're not symmetric. The Include filter is strict: if you list more than one tag there, a meal has to carry all of them to qualify. Asking for quick, healthy keeps only meals tagged both quick and healthy — not either-or. The Exclude filter is the opposite: a meal is dropped if it has any of the tags you list, so excluding spicy, takeout removes everything tagged spicy or takeout. Once that clicks, you can narrow a single big list down to exactly tonight's mood — "something quick that isn't takeout" — without keeping five separate lists.

Don't eat the same thing twice in a row

The objection people raise about random meal pickers is "won't it just give me tacos three nights running?" Genuine randomness has no memory, so left alone it absolutely can. That's what the Avoid last N days option is for. Set it to 7 — the default — and any meal the picker has handed you in the past week is temporarily taken out of the running, so you get variety without babysitting it. The tool remembers each pick by name with the date it happened, right there in your browser, and quietly keeps about three months of that history so the "avoid" window always has something to work from.

It's worth knowing the one edge this creates: if you tighten the filters and the avoid window far enough that nothing is left eligible, the picker won't invent a meal — it'll tell you no meals match and suggest loosening a constraint or clearing the recent history. That's the honest behaviour. A picker that silently relaxed your rules to produce something would be worse than one that admits you've boxed it in.

A fair pick, not your usual three favourites

Left to our own devices, we don't pick randomly — we drift back to the same handful of comfortable meals and the rest of the list gathers dust. Among the meals that survive your filters, the picker draws using the browser's cryptographic random source rather than the quick-and-dirty randomness most web pages reach for, so every eligible meal has a genuinely equal shot. The practical payoff is that the dishes you wrote down months ago and forgot about actually resurface, instead of losing every silent tiebreak to whatever you cooked last week.

Private, offline, and yours

Your meal list is personal, and it stays that way. Everything you save lives in your own browser and is never uploaded to a server, which has a pleasant side effect: the tool keeps working with no connection at all. You can stand in a kitchen with patchy signal, open the page, and still get a pick. Nothing nags you, nothing emails you, and no account is involved — picks happen only when you click.

When a different tool fits better

A meal picker is purpose-built for the dinner question, but it's part of a family. If the choice tonight is really "cook or order" rather than "which dish," a random decision maker settles a this-or-that faster. If you're picking from any old list — not meals — a random single picker is the general-purpose version of the same draw. And for the after-dinner sequel — "okay, what do we watch now?" — a random movie picker runs the exact same save-once, tag, and pick routine over your watchlist.

Hand dinner to the picker tonight

The point isn't that a computer chooses better meals than you do — it's that the choosing is the part that drains you, and it doesn't have to. Spend five minutes writing down what you actually eat, tag a few of them, set the avoid window to a week, and from then on let the meal picker end the nightly negotiation in a single click — and click again if tonight's draw isn't the one.