How long do leftovers last in the fridge?

The short version, and roughly where food-safety guidance converges: most cooked leftovers are best eaten within about three to four days of going into the fridge. Not because day five is instantly dangerous, but because that is the conservative line drawn for food that gets reheated once and eaten, not tested in a lab first. Cooking does not reset your food to a blank, indefinitely safe state. It resets the population of what was living in it, and a new one starts growing the moment the dish begins to cool.

Why cooking is not a safety switch

Heat kills most of what was in the raw ingredients, which is why a dish tastes and smells fine straight off the stove. But the kitchen it lands in is not sterile, and neither is the spoon, the air, or the container. A few bacterial spores survive normal cooking temperatures without much trouble, and anything introduced afterward — a spoon that touched raw chicken earlier, a lid that sat on the counter — gets a running start the moment the food starts to cool. "It was cooked" answers whether it was safe an hour ago. It does not answer whether it is safe now.

The part that matters more than the fridge itself: cooling

Bacteria multiply fastest in what food-safety guidance calls the danger zone, roughly 4–60°C (40–140°F) — body temperature and stove temperature are both well inside it, room temperature sits right in the middle. A large pot of stew left to cool on the counter can spend an hour or more drifting through that entire range before it is cold enough for bacteria to slow down again. The fix is almost embarrassingly simple: split a big batch into smaller, shallower containers before it goes in the fridge. Shallow means it cools in the time it takes to sit down and eat, not in the time it takes to reheat a full pot. Refrigerating within about two hours of cooking — sooner in a hot kitchen — matters more than any decision you make later.

The window, and why it is a range and not a promise

Three to four days is a default, not a universal constant, and it moves in both directions depending on what is actually in the container. Moist, protein-heavy dishes — a meat stew, a curry, plain cooked chicken — sit at the shorter end, because that is exactly the environment bacteria like best. Drier or more acidic food, and anything with a lot of sugar, tends to hold a little longer, but treating the conservative range as your default is the simpler habit, and the one that does not depend on correctly judging your own dish each time.

A few foods that deserve extra care

Cooked rice is the one that catches people out most often, because the organism involved, Bacillus cereus, produces spores that survive cooking and a toxin that survives reheating — so "it's piping hot now" does not undo time spent warm earlier. Rice that sat out on the counter for an afternoon is a different food, safety-wise, from rice that went into the fridge within the hour, even though they look identical in the container. The same cooling logic applies double to anything with rice in it: cool it fast, refrigerate it promptly, and do not let it linger at room temperature "to cool down first" for longer than necessary.

Why your nose is the wrong test here

With milk, smell is a genuinely useful instrument — sour milk announces itself. Cooked leftovers are a different category, closer to the use-by foods described elsewhere on this site: the organisms that matter most in reheated food do not reliably change the smell, taste or appearance before they matter. A container that looks and smells completely normal on day six is not evidence that day six was fine; it is evidence that your nose was not tested against the right thing. This is the one place where time and temperature history genuinely outrank a sniff test, and where "when in doubt, throw it out" is the boring but correct default rather than an overreaction.

What actually makes this easy

• Write the date on the container. The same trick that works for an opened carton of milk works here, and for the same reason: nobody reliably remembers which Tuesday a stew was made, especially in a shared kitchen where the person eating it is not the person who cooked it.
• Split, don't stack. A few shallow containers cool faster and more evenly than one deep one, and they make the three-to-four-day window easier to track, because each one can carry its own date.
• Freeze what you will not get to. If four days is realistically not enough time, freezing on day one or two is a legitimate way to move the goalposts — the clock genuinely stops, rather than just slowing down.
• Reheat once, thoroughly. Repeated cooling and reheating gives bacteria another lap around the danger zone each time. Portion before freezing so you are only reheating what you will actually eat.

None of this requires memorising a table of exceptions. It requires one date written where you can see it, and the same habit that helps with everything else in the fridge: something you already have, tracked well enough that using it up is the easy choice rather than the thing you meant to get to. That is the gap Munch is built to close — a shared, per-batch record of what is in the fridge and how old it is, so the oldest container is the one that surfaces first, not the one at the back.