How long should a resume be in 2026? One page, two, or more

If you have under five years of experience, one page is correct. Between five and fifteen years, two pages is standard and expected. Beyond that, or in academic contexts, a resume can run longer, because the content that justifies the length actually exists. No ATS or hiring platform enforces a hard page limit. The limit that matters is how much of your content is actually relevant to the role.

The one-page rule most people repeat as gospel was never really a rule about pages. It was a proxy for signal density, and somewhere along the way the proxy replaced the thing it was standing in for.

Key takeaways

• Length follows experience, not a fixed rule. One page under five years, two pages from roughly five to fifteen, longer only when academic or research content genuinely requires it.
• No parser scores page count. ATS software extracts structured data, it does not have a field for "number of pages," and there is no penalty for a well-structured two-page resume.
• Recruiters scan for density, not brevity. A one-page resume padded with vague lines loses to a two-page resume where every line carries a specific, checkable claim.
• UK CVs and US resumes are converging, but UK hiring has historically tolerated slightly longer documents even at junior levels, and the terminology gap still trips people up.
• Three or more pages is correct for academic CVs and some structured public-sector applications, where the format itself demands it, never for a standard corporate resume.
• The honest way to shorten a resume is to tailor it per job, cutting what is irrelevant to this specific role rather than shrinking font size to force a fit.

The short answer by experience level

The table holds for most applications, but it breaks at the edges: a candidate with eight years at one employer in a narrow role can honestly fit one page, and a candidate with three years across two demanding startup roles might need slightly more than one page. Treat it as a default, not a ceiling to engineer your way to.

Where the one-page rule came from and why it calcified

The one-page rule predates applicant tracking systems, email applications, and the internet as most people use it for job hunting. It comes from an era when a resume was a physical sheet of paper, handed to a hiring manager or mailed with a stamp, and read by someone flipping through a stack of dozens on a desk. A single page was easy to file, easy to scan, cheap to photocopy. The constraint was physical.

That constraint stopped applying somewhere between the rise of the PDF attachment and the online application portal, both of which predate most job seekers active today. A resume now is a digital file, opened on a screen, scrolled rather than flipped. The cost of a second page dropped to functionally zero.

The rule survived anyway, because it became shorthand for a virtue rather than a physical constraint. "Keep it to one page" got repeated by career coaches and career centres as a stand-in for "be concise, do not waste the reader's time," which is genuinely good advice. But it got flattened into a literal page count, a much blunter instrument than the principle it was meant to represent, and blunt rules are what calcify: they are easy to repeat and hard to argue with in a five-minute conversation.

The cost shows up most for candidates in the five-to-fifteen-year range. Someone with nine years across three roles, each with real scope and outcomes, who forces that history onto one page is not being concise. They are deleting the information a recruiter would use to shortlist them, in service of a rule built for a different medium and a different candidate profile.

What ATS parsers do with length

Nothing. This is worth stating plainly, because the fear that a two-page resume gets scored down, or read only to the bottom of page one, is one of the most common anxieties candidates carry into the length decision.

An ATS parser works by extracting structured data, contact details, work history entries, skills, education, from the document you submit. Its output is a set of fields, not a page count. There is no scoring dimension in the standard ATS pipeline for "length" as such. A two-page resume with clean section headers, consistent formatting, and month-and-year dates parses exactly as reliably as a one-page version of the same content, because the parser reads text and structure, not sheets.

What can go wrong with a longer resume is not length itself, it is what tends to accompany length done badly: inconsistent formatting added without revisiting the structure, or a skills list growing into an unorganised wall of keywords. Those are formatting failures that correlate with length, not consequences of it. A badly structured one-pager will score worse than a well-structured two-pager every time.

The one place length genuinely touches scoring runs opposite to what people assume: more relevant content gives you more surface area to match the job description's language. Cutting content to hit an arbitrary page target can mean cutting the exact bullet that would have matched a required keyword.

How recruiters actually scan and why density beats length

Once a resume clears the ATS and reaches a human, the read is fast and pattern-based. A recruiter working through a stack of applications is not reading each one start to finish like a short story. The first pass scans for orientation: current title, recognisable company names, date ranges that suggest tenure and trajectory. Only resumes that pass that scan get a closer read, hunting for specifics, scope, outcomes, tools, the details that separate a plausible candidate from a strong one.

This is why density matters more than length in either direction. A one-page resume where every line is vague ("responsible for various projects") gives the recruiter nothing to anchor a closer read on, no matter how fast it scans. A two-page resume where every line names a specific responsibility or measurable outcome gives the recruiter exactly what the closer read is hunting for, even though it takes longer to get through.

Length becomes a liability only when it is length without density, a third page of padding or repeated phrasing that does not differentiate one role from the next. The fix for that is cutting the low-density lines, not capping the page count and hoping the right lines survive.

UK CV norms vs US resume norms

The UK and US have historically diverged on this more than most candidates realise, which is part of why the "right" length feels like a moving target when applying across both markets. US resume culture, particularly at startups and in tech, has enforced the one-page rule more strictly and for longer, especially under ten years of experience. UK CV culture has been comparatively relaxed, a two-page CV has long been normal even for candidates with five or six years of experience, without the same social pressure to compress everything onto a single sheet.

Some of that gap is closing as remote hiring and shared ATS platforms pull the norms closer together, but it has not disappeared, and the terminology confusion, CV versus resume, compounds it. The full breakdown of where the formats diverge beyond length is in CV vs resume: UK vs US differences explained. When in doubt, default to the stricter US convention for roles labelled "resume" and the more generous UK convention for roles labelled "CV," matching whichever the posting's own language suggests.

When three or more pages is correct

Three pages is wrong for a standard corporate resume, full stop. But two contexts genuinely call for more, and it is worth treating them as distinct categories rather than loopholes.

Academic CVs. In academic and research hiring, the document is called a CV because it functions differently from a job-market resume. It is expected to list every publication, conference presentation, grant secured, and course taught, in full. A postdoctoral researcher with five years of publication history will routinely submit a CV running four or five pages, and a shorter document reads as an incomplete record, not a concise one. Length here is the content, not padding around it.

Structured public-sector applications. Some government hiring processes, UK civil service competency frameworks are a common example, use formats built around structured responses to specific criteria rather than a free-form work history. The employer's own form dictates how much space each section gets, and a thorough, well-evidenced response can run well past what a corporate resume would allow. Follow the form's guidance here rather than importing resume conventions.

Outside those two contexts, more than two pages is a signal the document needs editing, not that the candidate has unusually extensive experience.

How to cut length without losing signal

The honest way to shorten a resume is not to reduce font size, tighten margins, or delete the newest bullet on each role until it fits a target page count. All three cut length at random with respect to what actually matters for the job in front of you. The honest way is to tailor: decide what is relevant to this specific role, and leave out what is not.

That is a genuinely different move from "make it shorter." A resume with fifteen years across four employers has, realistically, forty or fifty potential bullets once you count every project, tool, and outcome. No single job description needs all fifty. A role focused on technical leadership needs the eight or ten bullets that demonstrate it, and the rest, real and legitimate as it is, is noise for that application. Cut it, and the resume gets shorter without losing anything this reader wanted.

This is the model RecastCV is built around: keep a complete master CV and project library as the source record, then generate a tailored version per job description that pulls only what is relevant. The output is shorter than the master record because the selection was deliberate, not because anything was compressed. Run the result through the ATS CV checker afterward, since cutting the wrong bullet can remove a keyword match along with the padding.