How do I use my leftovers instead of throwing them out?
Tuesday's chili ends up at the back of the fridge and you buy lunch anyway. Here is how to plan leftovers in advance, so you cook once and eat twice.
In this article
Tuesday night, you make a chili. The recipe serves six, there are two of you. The rest goes into a container, the container goes into the fridge, and the fridge does what it always does: it pushes it to the back, behind the milk and the cucumbers.
Thursday at noon, at the office, you buy a sandwich. Friday night, you open the container, you look at the chili for three seconds, and you throw it out.
The problem is not that you cook too much. It is that the leftovers existed nowhere in the plan. Nobody was counting on them, so nobody ate them.
Planning leftovers means deciding before you cook
Leftovers become a meal the moment somebody decides they are one. Not when you open the fridge already hungry: two days earlier, while building the week.
It is a simple idea and it changes two things at once. You cook fewer evenings, because one dinner also feeds tomorrow’s lunch. And you buy less, because a meal that gets eaten twice only gets bought once.
It is batch cooking’s smaller cousin, without the Sunday prep session. You are not cooking ahead: you are cooking as usual, knowing in advance who eats the rest.
Planners can put a recipe on two days
The market is not empty. Paprika is a very good recipe manager with a monthly calendar where you drag each meal in yourself. Plan to Eat is strong on planning. In both cases, nothing stops you from dropping the same recipe on Tuesday and on Wednesday.
But two copies of a recipe in a grid are two meals. Nothing says which of the two days does the cooking, and nothing says it is the same pot.
Origano makes the distinction:
- The link knows which day cooks. You mark Tuesday’s dinner as the one that produces the leftovers, and the next day’s meal as the one that eats them. Both slots carry the same meal, but they do not have the same role.
- The grocery list counts the pot once. That follows directly from the sentence above, and it is the half you see on the receipt.
- The generator picks a real dinner recipe. Even if you start from tomorrow’s lunch slot, the meal that cooks is what decides the type: you do not get handed a salad because the grid happened to be read the other way round.
A detailed comparison with the six main competitors sits on the alternatives page.
How to do it, in the week grid
1. Open the meal that cooks
In the weekly menu, every slot carries a small blue arrow walking into tomorrow, labelled “Eat the leftovers tomorrow…”. Click it on the dinner that will produce the leftovers, not on the meal that will eat them.
2. Pick tomorrow’s meal
A dialog asks “Which meal tomorrow should the leftovers fill?”, with two answers: Tomorrow lunch or Tomorrow dinner. You pick one, and that is it.
If tomorrow did not have that slot yet, it gets created. There is no groundwork to lay first.
The two slots then share a dashed border, and the one that eats carries a “Leftovers” tag. The evening that cooks stays an ordinary dinner, simply made in a larger quantity.
3. Or let the generator fill both at once
You can link two empty slots. The generator treats them as a single meal and draws one recipe for the pair.
It is the fastest way to build a week with four cooking evenings instead of seven: link Monday to Tuesday lunch, Wednesday to Thursday lunch, then generate. The grid fills from your own recipe books, and the pairs arrive already matched.
4. Undo the link when the week changes
The same arrow, red this time, cancels the link. It sits on both slots.
The meal that cooks keeps its recipe: you are still eating your chili on Tuesday. Only the next day’s lunch is cleared. Cancelling leftovers cancels the packed lunch, not the dinner.
What it changes once the week is built
The grocery list stops inflating. The shared meal’s ingredients are added up once. Two slots carrying the same recipe without being linked count twice, and that is on purpose: there, you really are cooking twice.
Tomorrow’s lunch is decided the night before. When you fill the container on Tuesday evening, you already know it is Wednesday’s lunch. It is not a leftover any more, it is a meal with a date on it.
You cook fewer evenings without eating worse. One dinner covering two meals, twice in a week, is two evenings back. You spend them cooking something longer on the nights that remain, or you do not spend them at all and you go and sit down.
The fridge empties itself. There is no orphan container left, because there is no leftover without a destination.
What about a household?
This is where planning leftovers stops being a private matter. If your partner does not know that Tuesday’s chili is their Wednesday lunch, they will buy a sandwich and the container will stay in the fridge. The decision has to be visible to the household, not just to the person who built the week.
The Pro plan adds permanent sharing: the weekly menu visible to everyone, the leftover pairs on it, and the grocery list following automatically. Whoever opens the fridge sees the same plan as whoever made it.
What it costs
Leftovers are in the free plan. The link, the week grid, the generator and the grocery list are not gated: free goes up to 50 recipes, with no credit card.
Past that, Pro is $30 USD a year, about $2.50 a month, or $4 USD a month.
No advertising, on either plan.
Where to start
- Create a free account, it takes a minute.
- Import five recipes that make big quantities: a chili, a pasta sauce, a roast, a hearty soup, a baked macaroni.
- Build the week and link two dinners to the next day’s lunch before you generate.
Then look at the grocery list that comes out. That is the moment the arithmetic gets concrete: five dinners cooked, seven meals eaten, one grocery run.