Cooking for One Without Eating the Same Thing Five Nights

Cooking for one is not cooking for four with smaller numbers. It is a different problem, and almost nothing written about home cooking acknowledges that.

The recipe serves four. The chicken thighs come in a pack of six. The bunch of coriander is enough for three meals and goes slimy in four days. So you either cook the full recipe and eat it until you resent it, or you buy carefully and still throw away half a cabbage. Most people living alone oscillate between those two failures and conclude they're bad at cooking. They aren't. The system is built for a family.

The real problem isn't portions, it's the tail

Halving a recipe is the easy part, and it's mostly a maths problem — we've written about the bits that don't halve cleanly, like pan size, baking time and a single egg.

The hard part is what's left over from the ingredients, not the meal. Half a tin of tomatoes. Two-thirds of a block of feta. The rest of the coriander. That tail is where the money and the guilt actually go, and no amount of careful portioning fixes it, because supermarkets do not sell in one-person units.

So the working approach isn't "cook smaller". It's "buy for a shape, then cook three different things out of that shape."

Cook once, eat differently

Batch cooking gets a bad reputation with solo cooks because it's usually taught as batch eating: make a vat of chilli on Sunday, eat chilli until Thursday, never want chilli again.

The version that actually survives contact with a real week is to batch a component, not a meal. Roast a tray of vegetables, cook a pot of grains, poach or roast a protein — then assemble differently each night. The same roast squash is a grain bowl on Monday, folded through pasta with chilli and lemon on Tuesday, and blitzed into soup on Thursday. You cooked once. You did not eat the same dinner three times.

The trick is that the component should be seasoned lightly. Anything you season decisively on Sunday — heavy on cumin, say — locks itself into one cuisine and you've recreated the vat problem.

Shop for a tail you've already planned

Before you buy the herbs, know the second thing they're for. That single habit does more for a one-person kitchen than any amount of meal planning software.

In practice it means picking recipes in overlapping pairs: two that both want half a bunch of parsley, two that both want half a tin of chickpeas. You're not planning a week of meals. You're planning that nothing gets opened without a second use already lined up.

It also means being realistic about the fresh things. Herbs, leaves and berries are the fastest to die. Root vegetables, cabbage, carrots, onions and hard cheese will forgive an unplanned week, which is why a solo kitchen leans on them.

Freeze in portions, not in blocks

The freezer is the single biggest advantage a solo cook has, and most people use it wrong by freezing one large container. A frozen litre of soup is a commitment; four frozen portions are options.

Bread, cooked grains, stock, half-tins of tomato paste, the second half of that block of feta's brine — these all freeze in usable amounts. The rule is simply that it should thaw into one meal, not into a decision about what to do with the rest.

Where an app helps

Two moments in the above are genuinely tedious, and both are where we can save you time.

The first is the "what can I make from this tail" question, standing in front of a fridge holding half a cabbage and some feta. Photographing what you have and getting a set of real options is faster than searching for recipes by ingredient and hoping one matches what you own. We wrote about that in cooking from what's already in the fridge.

The second is scaling. Halving a recipe to one or two servings, and having the grocery list scale with it, removes the arithmetic that makes people give up and cook the full four portions "just this once".

Where it doesn't

An app can't make a supermarket sell you a third of a cabbage, and it can't tell you whether you'll actually feel like eating a grain bowl on Wednesday. If you already cook confidently for yourself, the habits above are the whole article and you don't need software for them.

And if the honest answer is that you don't want to cook five nights a week, that's fine. Cooking for one badly on Tuesday and eating toast on Wednesday is a normal week, not a failure of planning.