Where should I eat?
Pick two constraints before you look at a single restaurant — how far you'll travel, and whether you're eating out or ordering in. Then go down a short list of nearby places, give each one a plain yes or no, and take the first yes. You are almost never short of restaurants. You are short of constraints, and an unconstrained list has no natural stopping point.
Last updated: 2026-09-04
More options make this harder, not easier
Every restaurant app is built to show you more places, on the assumption that the problem is supply. It isn't. Open any of them and you are handed hundreds of results sorted by something that has nothing to do with what you want tonight, and the browsing itself becomes the task.
The trouble with an open list is that each new option quietly raises the bar for every option you already saw. A place you'd have been perfectly happy with ten minutes ago now has to beat everything you've scrolled past since. That's why the search can run twenty minutes and end at the restaurant you go to every week.
How to decide where to eat in about a minute
- Set a distance you'll actually travel. Before looking at a single restaurant, decide how far you're willing to go right now. Ten minutes on a weeknight is a different list than thirty on a Saturday. This one constraint removes more options than any amount of browsing.
- Decide whether you're going out or staying in. Eating out and ordering in are two different decisions wearing the same clothes. Pick one first. Trying to answer both at once is why the search feels endless.
- Stop reading reviews. Ratings are useful for ruling out somewhere bad, not for choosing between two places that are both fine. Past a 4.0 you are reading other people's opinions instead of forming your own, and it does not make the decision easier.
- Give each place a plain yes or no. Go down the list once and answer only "would I eat there tonight?" Don't rank, don't compare, don't hold anything in reserve. Ranking is what turns a one-minute decision into a twenty-minute one.
- Take the first yes. Not the best yes. The first one. You already applied your constraints, so everything still on the list is acceptable by definition, and picking between acceptable options is where the time goes.
When "where should I eat" is really a group decision
Plenty of people search this alone while the decision is not actually theirs alone. If someone is waiting on you to come back with an answer, the constraint method above still helps — but it solves the wrong half of the problem.
With two or more people, the difficulty stops being the number of options and becomes the order of opinions. Whoever names a place first sets the anchor, and everyone else is put in the position of agreeing or rejecting. Saying "I don't mind" is the usual escape, and it hands the decision straight back. That needs a different method: how two people can decide where to eat covers it.
If the sticking point is that nothing appeals rather than that too much does, the question underneath is usually what you're in the mood for, not where to go — see what to do when you can't decide what to eat.
Frequently asked questions
Where should I eat tonight?
Start by fixing two constraints rather than browsing: how far you'll travel, and whether you're eating out or ordering in. Then go down a short list of nearby places and give each a yes or no, and take the first yes. The problem is almost never a shortage of restaurants — it's that an unconstrained list has no natural stopping point.
How do I decide where to eat when nothing sounds good?
"Nothing sounds good" usually means you're browsing without constraints, so every option is being compared against every other one. Narrow by distance first, then answer one yes-or-no question per place. If genuinely nothing appeals after that, you're likely deciding what you're in the mood for rather than where to go — that's a different question worth answering first.
Is there an app that tells me where to eat?
Several will pick randomly for you. DinnerSwipe works differently: it builds a short deck of real restaurants near you and you swipe yes or no through it, so the result is something you actually chose rather than something a wheel landed on. It's free, works in a browser, and doesn't need an account.
Why do I spend so long deciding where to eat?
Because restaurant apps are built to show you more options, and more options make a decision slower, not easier. Every additional place you look at raises the bar for the ones you already saw. Capping the list before you start is the single change that shortens the decision most.
What if I'm deciding with someone else?
Then the problem changes shape. With two or more people the difficulty isn't the number of options — it's that whoever names a restaurant first sets the anchor, and everyone else can only agree or reject. That needs a different method, covered on our page about deciding where to eat together.
Decide it tonight
DinnerSwipe builds a short deck of real restaurants near you and you swipe through it once. Eating with someone? They swipe the same deck on their own phone and you match on a place you both want. Free, no account.
Start a room