Word Count Guidelines for Common Documents (Cover Letters, Emails, Resumes)

The common convention of keeping a cover letter to a single page, roughly 250-400 words, isn't arbitrary — hiring managers and recruiters reviewing dozens or hundreds of applications for a single role typically spend well under a minute on an initial cover-letter read, and a letter that runs well past 400 words risks losing the reader's attention before it makes its key points. The reasoning is about the reader's actual constraints (limited time, many applications to review), not an aesthetic preference for shortness.

Checking your draft against this range is straightforward with /word-counter/ — paste your letter in and check the live count against the 250-400 target before sending, adjusting down if you've included unnecessary background rather than focusing on your most relevant, specific qualifications for the role.

Business email conventions favor brevity even more than cover letters — a common guideline is keeping the substantive body of a professional email under roughly 150-200 words, because most recipients skim email rather than reading it closely, especially in a busy inbox context. An email that requires significant scrolling to read in full is more likely to be skimmed, misread, or deferred than one that fits in a single screen's view.

This convention differs meaningfully by context: a detailed project status update to a close collaborator can reasonably run longer than a first-contact outreach email to someone who doesn't know you, where brevity and a clear, single ask matter more. Adjust the general 150-200 word guideline based on your specific relationship with the recipient and how much genuinely necessary context the message requires.

A single resume bullet point conventionally runs somewhere around 15-25 words — long enough to convey a specific accomplishment with a concrete result, but short enough to be scanned quickly alongside several other bullets under the same job entry. This length convention exists because resumes are scanned, not read closely, in an initial screening pass — a wall of long, paragraph-like bullets works against the document's actual purpose of being quickly skimmable.

A useful practical check: paste a full resume section into /word-counter/ and divide the total word count by the number of bullets to get your average bullet length, then look specifically at any individual bullet that runs noticeably longer than the others, since that's usually the one worth trimming first.

LinkedIn's About section technically allows up to 2,600 characters (see /limits/linkedin/ in the platform-limits section for the full breakdown of LinkedIn's various character limits), but most effective, widely-read professional summaries use meaningfully less than the maximum — commonly somewhere in the 200-1,000 character range, front-loaded with the most compelling information first, since LinkedIn truncates the visible summary behind a 'see more' link well before the full 2,600-character maximum displays.

The gap between the platform's technical maximum and the practically effective length here mirrors a pattern seen across several platform limits covered in /limits/ pages on this site: the number you're allowed to write and the number that actually gets read in full are frequently two different figures, and writing to the practically effective length usually serves the reader (and by extension, your own goals) better than filling the maximum allowance.

Most academic journals specify an abstract length in the 150-250 word range, though the exact figure varies by publication and field, and a fair number of journals pin down one precise number (250 words flat, say) rather than leaving any range to interpret at all — worth checking your specific target journal's author guidelines directly rather than assuming a general convention applies. See /limits/essay-word-counts/ in the platform-limits section for this figure alongside other common academic-writing length conventions.

Every convention above traces back to the same underlying logic: match your document's length to how much attention and time its actual reader realistically has for it, in its actual reading context. A hiring manager skimming a stack of applications, a busy colleague scanning an inbox, and a peer reviewer assessing an abstract before deciding whether to read a full paper are all in fundamentally time-constrained reading situations, and each of the length conventions above reflects that constraint rather than an arbitrary stylistic rule. When you're unsure what length is appropriate for a document type not covered here, thinking through your actual reader's realistic attention budget is a more reliable guide than guessing at a round number.