Last Updated on October 4, 2026 by Umar Farooq
The number on the display is an estimate, and when it goes up the machine is correcting that estimate rather than failing to keep to it.
Every washer has to show you a time before it knows anything about your laundry. So the first number you see is a default: the length that cycle takes with the load the manufacturer assumed you would put in it. Then the machine weighs what you actually gave it, measures how fast water arrives, notices how much foam is in the drum and checks whether the load will balance — and each of those measurements is a chance to discover that the default was wrong. A time that moves is a machine that has learned something.
This page is about that number and what makes it change, because a washer that adds time mid-cycle is usually doing arithmetic, not failing. It is not a troubleshooting page, because for most people reading this there is nothing to troubleshoot. If your cycle genuinely never ends rather than simply running long, that is a different situation, covered in washing machine stops mid cycle. If it never gets past the sensing stage at the start, see washing machine stuck on sensing. And if you want the weighing stage itself explained, that is washer load sensing explained.
Where the first number on the display comes from
The estimate you see when you press Start was calculated before a single measurement was taken. The control board looks up the program you selected, applies the assumptions built into it — a mid-sized load of ordinary cotton, mains water at a typical temperature, a drain that clears at the expected rate — and prints the resulting figure. It is closer to a menu price than a stopwatch. Nothing about your particular load has been consulted yet, because at that moment the machine has no way to consult it.
What follows is a sequence of reality checks. Load sensing gives it a weight, which sets water level, wash duration and how many rinses are worth running. The fill valve opens and the pressure sensor watches how quickly the level rises, which quietly reveals whether the laundry is absorbing more than the weight predicted. If the cycle heats, the machine times how long the water takes to reach temperature. Before every spin it tests whether the drum is loaded evenly. Each check either confirms the default or replaces it.
That is why the display sits still and then jumps. The number is not ticking down toward a fixed endpoint; it is republished every time a measurement completes. A washer that never revised its estimate would not be more accurate, only more confident.
Why a washer adds time mid-cycle instead of taking it away
Corrections add work. That asymmetry is why people search for this and almost never for the opposite. When the machine discovers something it did not expect, the response is nearly always another action — one more rinse, another redistribution attempt, a longer fill, a second heating stage. There is no equivalent move in the other direction, because a washer cannot un-rinse a load or take back a tumble it has run. Downward revisions exist, but they happen once, early, when sensing finds a lighter load than the default assumed.
Four discoveries account for nearly all of the upward movement, and they arrive at different points in the cycle.
- The load weighs more than it looks. The weight sensor assumes it is weighing dry laundry, because that is the only assumption available to it. Load something already damp and the water weight reads as extra laundry. LG’s documented example: dry towels estimated at 30 minutes jump to an estimated 1 hour 52 minutes once the machine detects the laundry is already wet (LG frontload washer — wash time keeps extending).
- There is too much foam. Excess suds stop the machine rinsing properly and can escape the door seal at spin speed, so it adds rinses until the foam clears. LG puts a figure on the cost: when too many suds are detected during spinning, the machine stops to help prevent leaking, and “this adds about 2 hours to the cycle time” (LG front load washer error code list).
- The load will not balance. Before spinning, the machine checks distribution. If one side is heavy it adds a little water, tumbles to redistribute, drains and tries again — a loop that costs several minutes each pass and often runs more than once.
- Water is slower than assumed. A partly closed tap, low mains pressure or a sluggish drain stretches stages the estimate had budgeted a fixed time for.
Which of these are your doing, and which aren’t
Two of the four are load decisions, and they are the ones worth changing. Damp items and an over-dose of detergent are both under your control, both free to fix, and both produce time penalties out of all proportion to the mistake. Detergent is the under-diagnosed one: the same over-dose that adds hours also causes poor rinsing and white residue on dark clothes, so people treat it as three separate problems instead of one cause with three symptoms.
The other two are mostly not your fault. Balance retries are the machine solving a physics problem that a duvet or a single pair of jeans has handed it, and there is a limit to how well that load can be balanced at all. Slow fill and slow drain are plumbing rather than laundry. In all four cases the extra time is the machine protecting the wash result, or itself — spending minutes to avoid handing you back a soapy, half-spun load.
Refining the estimate, or actually going wrong
Here is the line almost nobody draws. A revised estimate and a broken cycle look identical for the first ten minutes. What separates them is whether the number ever settles.
| What you saw | Normal — the estimate is being refined | A real fault — worth investigating |
|---|---|---|
| Time jumped once, near the start | Sensing found a heavier load than the default | It jumps every cycle, on dry, ordinary loads |
| Foam visible, extra rinses added | Time climbs once, then counts down steadily | Rinses keep repeating and the foam never clears |
| Slow tumbling, no spin yet | Two or three balance retries, then it spins | It retries indefinitely and never reaches spin speed |
| Time stalls on one number | The machine is filling, heating or draining | It stalls on the same number every cycle and stops there |
| Time resets upward again and again | — | The machine is looping, not estimating |
The test that tells you which one you have
Run one cycle and do not touch it. Note the number at the start, note it again after ten minutes, and note the wall-clock time it actually finishes.
- Normal: one or two upward revisions, then the number counts down without further jumps and the cycle ends. It can finish 40 minutes late and still be normal.
- A fault: the number climbs, drops, then climbs back to roughly where it was, more than twice — or the machine returns to a stage it had already completed and never ends.
Use dry laundry, an ordinary mixed load at roughly two-thirds of the drum, and a correct detergent dose. Testing with the load that caused the problem tells you nothing.
One thing not to do: don’t cancel and restart because the number went up. Restarting re-runs sensing and repeats any rinses already completed, which genuinely does make the cycle longer.
When a washer adds time mid-cycle and it is a real fault
The threshold is completion. A cycle that runs long and then finishes has done its job, however irritating the display was along the way. A cycle that stops finishing is a fault, and the fix is not on this page.
- It stops finishing — whether it halts at the same point every time, or loops on suds, balance or drain without ever completing: washing machine stops mid cycle.
- It never leaves the sensing stage: washing machine stuck on sensing.
- The cycle ends but the laundry is soaked: full spin never ran — clothes soaking wet after wash.
- Every stage is slow, on every cycle: start with the water — washing machine fills too slowly and washing machine drains too slowly.
FAQ
Is it normal for the time to go up instead of down?
Yes. The number is an estimate recalculated from what the machine measures, and most of what it discovers adds work rather than removing it.
How much extra time is too much?
It depends on what was corrected — foam alone can add around two hours on an LG. The question is whether the cycle finishes, not by how much it overran.
Why did it add an hour the moment I pressed Start?
Sensing weighed the load and found it heavier than the program’s default, most often because the laundry was already damp. See washer load sensing explained.
Does using less detergent actually shorten the cycle?
It removes the extra rinses that over-sudsing triggers, which is the largest avoidable time cost here. On a Samsung it shows as a Sud or 5d code — see Samsung washer Sud or 5d error.
Would a smaller load be faster?
Not necessarily. Very small loads cluster on one side of the drum and trigger balance retries of their own. Around two-thirds full is the range that senses and spins cleanly — see washer load size: how full.
