This is a short post because the answer is short: cover letters in 2026 should run 250-300 words across four short paragraphs on a single page. The data behind that range is consistent across multiple recent studies, the structure that produces this length is simple, and going over 400 words actively reduces your callback rate.
If you're looking for the studies, the structure, the per-paragraph word budget, or what to cut when you're over the target — keep reading. If you only need the answer, you've already got it.
The data: industry consensus + recruiter behavior
There's an honesty point worth making upfront: there is no widely-cited peer-reviewed academic study on optimal cover letter length. A lot of resume blogs cite a "Journal of Applied Psychology 2022 study of 6,000 applications" — that citation propagates across the resume-content ecosystem but I cannot independently verify it at the primary source. The references trace back to a single promotional blog post. We're not going to repeat that chain here.
What is verifiable is two things: industry-publisher consensus on the recommended range, and recruiter survey data on attention budgets.
| Source | Type | Recommendation / finding |
|---|---|---|
| ResumeGenius hiring manager survey (Pollfish, n=625 US hiring managers) | Survey of hiring managers | 67% say cover letters are "important" when deciding whether to invite an applicant for an interview; 83% read the majority of cover letters they receive |
| ResumeGenius cover letter guide | Industry guidance | 250-400 words |
| Indeed Career Guide | Industry guidance | 250-400 words, half a page to one page |
| Kickresume length guide | Industry guidance | 250-400 words |
| Resume.io length guide | Industry guidance | 250-400 words |
Four major industry publishers converging on the same range is the most-defensible signal we have. The lower end (250-300) is where career coaches consistently recommend entry-level and internship applicants land — because the proof paragraph for an early-career candidate has less work history to summarize.
The recruiter-attention data is the practical reason. If 66% of recruiters spend under 30 seconds on a cover letter, the document needs to do its work in roughly 250-300 words at normal reading speed. Anything longer doesn't get fully read.
Why 250-300 specifically? Four discrete jobs.
A cover letter has to do four things, and each takes a defined amount of space:
- Hook (40-60 words) — name the role, name the company, give one specific reason you want to work there that you couldn't paste into 50 other letters.
- Proof (80-120 words) — pick one project or experience and explain it with the detail your resume couldn't fit.
- Fit (30-50 words) — one line connecting your trajectory to the role's trajectory.
- Close (20-40 words) — a specific, low-pressure next step.
Add the ranges: minimum 170, maximum 270. Most letters land at 220-260 once written naturally, leaving a little headroom for a transitional sentence between paragraphs. The 250-300 target is a description of the natural length, not an arbitrary constraint.
The page test
The visual rule of thumb that does almost the same work: your cover letter should fit on one page with normal margins (1 inch all around) and 11-12pt body text, with white space between paragraphs. If it spills onto a second page, it's too long regardless of the exact word count.
This rule is generous — at 11pt with single-spacing, one page holds roughly 500 words. If you're filling the page, you're probably over the data-backed sweet spot. The page test is a ceiling check; the 250-300 target is the actual goal.
What to cut when you're over
Most cover letters that run long do so for predictable reasons. The order to trim:
Cut the fit paragraph first. It's the most common bloat point. Many writers turn the trajectory connection into three sentences when one works. "My experience in X has prepared me for Y, which has built my interest in Z, and I see this role as the natural progression" — replace with "I've been moving from full-stack feature work toward systems engineering, and this role is the next step I want."
Trim the hook second. "I am writing to express my interest in the position of [Role] at [Company]" is 13-14 words of preamble that signals nothing. Cut it. Open with the specific reason: "I'm applying for the Software Engineering Internship at Stripe because of the engineering blog post on the Black Friday capacity surge..." The role and company are still named, but the opening word is doing real work.
Don't touch the proof paragraph. It's the load-bearing one — the part of the letter that the recruiter actually wants to read. Cutting proof to save words is the wrong move. If proof itself is too long, it usually means you're covering two projects instead of one. Pick the stronger project and drop the other; don't compress both.
Cut the close last. A good close is 1-2 sentences and barely costs anything. Common bloat in the close: "Please don't hesitate to contact me at your earliest convenience to discuss how my qualifications align with your needs" (24 words of corporate boilerplate). Replace with: "I'd welcome the chance to walk through the project at a 20-minute call next week. Thanks for reading." (22 words doing actual work.)
What to add when you're under
If you're at 180 words and feel you're done, the proof paragraph is almost certainly under-developed. The fixes:
- Add the why. Why was the project worth doing? What problem was the team trying to solve before you got there?
- Add the how. Which specific technical decision did you make and why? "I chose Postgres over Redis for the flag store because we needed audit history, not just lookup speed."
- Add the unexpected finding. What did you not know going in? What's the part that would interest someone in the new role?
The unexpected-finding move is the most underused. It does two things at once: signals depth (you actually thought about the work, not just executed) and gives the interviewer something specific to ask about.
A worked length example
Here's the same internship cover letter at three lengths. Same content, different word counts.
150 words — too short, reads generic:
I'm applying for the Software Engineering Internship at Stripe. Last summer at Acme I built a feature flag service in TypeScript that 4 product teams adopted. The work taught me a lot about backend systems and I'd want to bring that experience to Stripe.
I'd welcome the chance to talk. Thanks.
265 words — the data-backed sweet spot:
I'm applying for the Backend Software Engineering Internship at Stripe because of the engineering blog post on how the team handled the Black Friday capacity surge — the cursor-pagination work on the charges API was exactly the systems-thinking I want to learn.
Last summer at Acme, I built the company's first feature flag service. The team had been editing a YAML file in the repo and waiting for the next deploy — sometimes 3 days for a flag flip. I shipped a Postgres-backed service in TypeScript with a small admin UI, and four product teams adopted it in the first month. Rollout time dropped from 2-3 days to under an hour. The interesting failure mode I didn't anticipate was webhook delivery races during deploys — that's the part of the work I'd want to dig deeper on at Stripe.
I've been shifting from full-stack feature work toward systems and infrastructure over the past two years, and Stripe's mix of payments-domain depth and capacity engineering is the next step I want.
I'd welcome the chance to walk through the feature flag service at a 20-minute call next week. Thanks for reading.
540 words — over the threshold:
(Imagine the 265-word version above plus: an opening "I am writing to express my interest in the position of Backend Software Engineering Intern at your esteemed company"; a second project example that dilutes attention from the first; a three-sentence "fit" paragraph explaining your career trajectory; and a corporate close like "Please don't hesitate to contact me at your earliest convenience to discuss how my qualifications align with your needs.")
The 265-word version reads as crafted and specific. The 150-word version reads as low-effort. The 540-word version reads as bloated and unfocused — and given that 66% of recruiters spend under 30 seconds reviewing a cover letter, the back half of a 540-word letter will not be read in time to influence the decision.
The single-most-useful test
After you've drafted the cover letter, paste it into a word counter. If you're between 220 and 320 words, ship it. If you're over 350, cut. If you're under 200, expand the proof paragraph.
This is the boring rule, but the converging industry guidance and the recruiter-attention math line up cleanly. The cover letter length question has a defensible answer — even without a flagship academic study to point at.
Related reading
- How to write a cover letter for an internship (template + 6 industry examples)
- Cover letter examples by industry: 8 templates that actually worked
- How long should a resume be in 2026? — same kind of data-backed length question
- How to tailor your resume to a job description
If you've drafted the bullets but want help compressing the proof paragraph into the data-backed length, Laxu Resume generates a 250-word cover letter alongside the tailored resume on every run. First one is free.