Picture a 61-year-old engineer who has spent her career at or near the Social Security wage cap. Her statement shows a benefit close to the program’s ceiling, and now she is staring at three numbers: what she could claim next year, what she could claim at her full retirement age, and what she could claim if she waits until 70. The gap between those three figures is bigger than most people realize, and the decision is largely permanent.
For 2026, the Social Security Administration sets the maximum monthly retired-worker benefit at $2,969 at age 62, $4,207 at the full retirement age of 67, and $5,181 at age 70. The average retired worker receives about $2,076 a month, so these maximums describe a narrow slice of claimants. One recent online thread captured the dilemma well: a soon-to-be retiree with a pension and healthy savings asked whether waiting until 70 was worth losing eight years of checks. The honest answer depends on three things, and only one of them is math.
What it actually takes to hit the maximum
The maximum rewards earning at or above the taxable wage base for a long stretch, not patience at the claiming window. In 2026, $184,500 in earnings are taxed for Social Security, and that cap rises most years. To approach the top benefit, you need roughly 35 years of earnings at or above that moving ceiling. Social Security averages your 35 highest-earning years, wage-indexed, so a single zero year pulls the average down meaningfully. Someone with 32 strong years and three zeros is not maxing out, period.
That is why high earners who retire in their late 50s sometimes pick up a 36th or 37th year of work: each additional high-wage year displaces an older, lower-indexed year in the calculation. The marginal lift can be modest, but for someone chasing the ceiling it is the only lever left other than timing.
The timing lever, in plain dollars
Claiming age does the rest of the work. Claiming at 62 instead of the full retirement age of 67 imposes a 30% reduction. Waiting from 67 to 70 adds 8% per year in delayed retirement credits, a 24% boost. For a maximum earner in 2026, that is the difference between an early-claim check and the delayed-claim check, every month, for life, with cost-of-living adjustments layered on top of the higher base. The 2026 COLA came in at 2.5%, which compounds on whatever number you lock in.
A useful back-of-napkin comparison: claiming at 70 versus 62 delivers a materially larger monthly check, $2,200 more per month, indexed for inflation. The break-even is typically in the early 80s. As one longtime financial commentator put it, “once you’ve hit like 82 years of age, if you live longer than that, you are better off taking your Social Security at 70.” Live to 85 after claiming at 70 and you collect roughly $701,000 in lifetime benefits, compared with about $641,000 if you claimed at 62.
How this fits with the rest of the picture
For a high earner, the bigger Social Security check at 70 is essentially cheap longevity insurance. The cost is drawing more from your portfolio in your 60s to bridge the gap. If you have a spouse who earned less, the calculation tilts further toward delaying: survivor benefits are based on the higher earner’s claimed amount, so locking in the maximum protects the surviving spouse for the rest of their life, not just yours.
Taxes deserve a glance too. Bridging to 70 with traditional 401(k) or IRA withdrawals can fill lower brackets in your 60s before required minimum distributions arrive, which often softens the lifetime tax bill more than people expect.
What to think through before you file
Two things matter more than the rest. First, the claim is close to irreversible once a year passes, so the real question is which check you want arriving when you are 85. Second, if you are the higher earner in a marriage, your claiming age sets the floor for your spouse’s survivor benefit, and that consequence outlives you.
Personal health, family longevity, and cash flow all shift the answer, so the right age for your neighbor may not be the right age for you. Run your own numbers against your own statement before you commit.