Ask a room of PR practitioners how long should a press release be, and most will give you a number before they ask what the release is about. Four hundred words. One page. Six hundred at the outside. The numbers are quoted with confidence, as if length were a specification the document has to meet, like a form with a fixed number of boxes. It is not. A press release has exactly one obligation: to carry the news it announces, completely and without waste. Length is what that obligation happens to measure once the news is written down — no more a target than the length of a letter is a target before you know what the letter has to say.

That said, the numbers are not arbitrary. The one-page convention — roughly 400 to 600 words for a standard announcement — is a real working norm with real history behind it, and a writer who ignores it entirely will produce releases that newsrooms handle badly. The skill lies in knowing what the convention is for, what actually determines the right length for a given announcement, and how to tell a release that is long because its news is substantial from one that is long because nobody edited it.

The Short Answer: Length Follows the News

A press release should be as long as its news requires and not one sentence longer. Every announcement carries a set of facts a journalist needs in order to write the story without coming back for basics: what happened, who is responsible, when and where it takes effect, why it matters, and what happens next. When those facts are present — supported by the one or two quotations that add a human voice and any figures the claim depends on — the release is finished, whether it finished at 350 words or at 900.

Judged that way, length is a result, not a decision. The decision is what belongs in the document. A simple announcement — a new appointment, a changed date, an opened office — has few facts to carry and should be short. A dense one — annual results, a research report, a multi-party agreement — has many, and will run longer without being bloated. Writers get into trouble when they reverse the order: choosing a length first and then stretching or squeezing the news to fit it. The stretched release pads; the squeezed one omits. Both fail the reader, in opposite ways.

Where the One-Page Convention Comes From

The one-page norm is an inheritance from the wire era. Releases were typed, faxed, and later moved across wire services as plain text, and newsrooms worked to physical constraints: a page on the desk, a screen of copy on the terminal. A release that fit on one page could be read at a glance, assessed in seconds, and filed or spiked without a second thought. Editors built a scanning habit around that size, and the habit survived the technology that created it.

Two other forces keep the convention alive. The first is newsroom time: journalists triage far more material than they can use, and a document that visibly respects their time gets a fairer reading than one that sprawls. The second is the discipline of the single story. A press release is supposed to announce one thing, and most announcements, honestly told, need a few hundred words — a lead, some development, a quote, a closing paragraph of background. The 400-to-600-word range is simply what one story, fully told, usually weighs. It is a description of typical practice, not a studied optimum, and it should never be quoted as a rule with a source nobody can name.

Treat the convention as a default, then. If a draft lands far outside it, that is a prompt to ask questions — is a second story hiding in here? is half of this background the reader does not need? — rather than an instruction to cut or pad until the number looks right. The questions are the point; the number is only what triggers them.

What Actually Determines Length

Four things set the real length of a release. The first is the amount of verifiable news. Count the facts that are genuinely new and checkable: a launch date, a price, a named partner, a figure that can be sourced. A release built on three facts will be short however it is dressed up; a release built on thirty will not fit a page however tightly it is written. Padding cannot manufacture news, and compression cannot repeal it.

The second is the quotation load. Quotes are the most expensive words in a release, because they repeat, in a voice, what the prose should already have established. One quote that adds judgement, reaction, or commitment earns its length. Three quotes saying the same thing in three job titles do not. Most releases need one voice — occasionally two, where two parties genuinely speak, as in a partnership or a joint appointment — and the length should follow that arithmetic.

The third is the data the reader must be given rather than pointed to. Some announcements rest on numbers: results, measures of the organisation’s own performance, findings from its own research. The headline figures belong in the release itself, because a journalist should not have to open a second document to learn what the story is. Supporting tables, methods, and full datasets do not belong — they are what linked documents and attachments are for. The line between the two is the line between a release that is usefully long and one that is swollen.

The fourth is background obligation. An organisation announcing something its audience already follows needs little context. One announcing itself to a new sector, a new country, or a new kind of reader owes more: what it is, why it is the one announcing this, what came before. Background is legitimate length, but it is also the easiest length to over-serve, because it is the part the writer knows best. It should be the first place to look when a draft runs long.

How Length Distributes Across a Release

Length discipline is mostly proportion. In a well-made release the parts stand in a rough relationship to one another, and a part that swells out of proportion is usually where the trouble is. The parts themselves — what belongs in each and how they are formatted — are covered in full by the complete guide to formatting a press release; what follows here is only about the share of the whole each part should claim.

The headline should be the shortest hardworking text in the document: a single line that carries the news, typically well under fifteen words. If the headline needs a second sentence to make sense, the announcement itself may not yet be clear in the writer’s mind. A summary line or deck, where the format uses one, buys a little more room — a sentence, not a paragraph — and should add a fact rather than repeat the headline in other words.

The opening paragraph carries the whole story in miniature, and it should be tight enough to stand alone if everything after it were cut — because for many readers, in effect, it is. Fifty to eighty words is the natural weight of a lead that answers who, what, when, where, and why without decoration. A lead that runs to twice that is usually smuggling in background, or a second story.

The body is where length legitimately lives: the development of the facts, the evidence, the sequence of events, the detail a journalist needs to write with confidence. It should be the largest share of the release, and the only share allowed to grow without suspicion. Quotations sit inside it, rationed as described above. The boilerplate, by contrast, is fixed weight — a short standard paragraph, roughly fifty to a hundred words, that identifies the organisation. It should be the same in every release, and never the place where new material is parked; a boilerplate that keeps growing is a sign that the release above it has leaked.

When Longer Is Right

Some announcements are honestly long. Financial results are the clearest case: the figures are the story, the comparison periods matter, and the statement from management carries formal weight. A results release that omitted the numbers to hit a word target would be useless. Research reports are similar — the finding, the method in outline, and the basis of the research in brief all belong in the release, with the full report carried in a linked document the release points to.

Complex technical announcements also earn their length: a platform change that alters how customers work, a safety recall with instructions, a regulatory decision with conditions. In each, the cost of a missing detail falls on the reader. Even then the discipline holds — the release carries everything needed to understand and act on the news, while the deep material, specifications, full terms, and extended data, moves to documents the release links to or attaches. A long release should feel dense, not padded: every paragraph carrying a fact the story needs.

When Shorter Is Right

At the other end, some of the best releases are barely a page’s first half. A single-fact announcement — a date confirmed, a price changed, a venue moved, an appointment made — needs its fact, one line of context, a sentence of consequence, and the contact details. Written honestly, that is 150 to 250 words, and there is no virtue in inflating it. Journalists trust senders who can be brief when the news is brief; it buys attention for the day the news is not.

The extreme case is the release that is only a quotation and a fact: a short statement responding to an event, confirming a position, or correcting the record. Such statements are a recognised form, and their brevity is their credibility — they say the one thing and stop. The mistake is to feel that a short release looks insubstantial and to bulk it out with background the reader did not ask for. Thin is a fault; short is not. Thin means the necessary facts are missing. Short means only the necessary facts are present.

The Costs at Both Ends

An over-long release fails in predictable ways. The news gets buried: the actual announcement sits in paragraph four, while the first three rehearse the organisation’s history and market. Padding announces itself — stock phrases, throat-clearing openings, quotations that applaud rather than inform — and experienced readers discount the whole document when they detect it, including the parts that deserved better. Worst of all, length hides the story from the writer: many a bloated draft contains a sharper, shorter release that nobody stopped to find.

An under-written release fails just as surely, in the opposite direction. Missing facts force the journalist to choose between chasing the sender for basics — which, on a deadline, usually means dropping the story — and writing around the gaps. A release too thin to write from is not concise; it is unfinished. The test is whether a competent stranger could produce an accurate short news item from the document alone. If they would have to guess at the date, the place, the spelling of a name, or what happens next, the release is too short, whatever its word count says.

Length Across Channels

Length interacts with channel less than writers fear, because republication keeps the text whole. A release sent over a wire service arrives at newsrooms at its full length; a release emailed directly does the same; a release posted to a company newsroom is read at whatever length it was published. Nobody downstream is trimming your release to fit a smaller box. If it is cut, it is cut by an editor making a judgement — and editors cut from the end, which is why front-loading the news matters more than the total count.

The channel does change the reading conditions, and that argues for one adjustment. An emailed release is often first met in a preview pane or on a phone, which argues for a lead that does its work immediately. A release that will be posted and searched for later argues for completeness, since it becomes the standing record of the announcement. Neither argues for a different total length in itself. They argue for the same length, spent in the right places.

Editing Down Is the Real Skill

Almost every release improves by getting shorter in the edit, and the order in which you cut matters. Cut background first: it is the most expendable layer, the reader can be pointed to it elsewhere, and drafts accumulate it fastest. Merge quotations next — if two voices say overlapping things, keep the stronger and let the other go; the release loses words and gains authority. Then move detail sideways: anything a reader might want but does not need in order to understand the news — full specifications, extended timelines, complete tables — belongs in a linked document or an attachment, named clearly in the release so it can be found.

What should survive every edit is the factual spine: the announcement itself, the names spelled right, the dates and figures the claim depends on, the one quotation that adds a human judgement, and the route to a human being for questions. A useful discipline is to read the draft asking one question of each paragraph — what would the story lose if this went? Paragraphs with no answer are length without function. Cut them, and the release does not get poorer; it gets clearer, which is the entire point.

A Final Self-Check

Before a release goes out, five questions settle its length better than any word count. Is the news in the first paragraph, complete enough to stand alone? Is every fact a journalist needs present, and checkable? Is there exactly one story here, or is a second announcement hiding in the middle? Does every quotation say something the prose has not already said? And is everything that is merely background either earning its place, or moved to where background belongs?

If the answers hold, the release is the right length — whether the count says 220 words or 880. The one-page convention will be there in the background, doing its quiet work as a sense of proportion. But it is the news that decides. Writers who learn to let it decide stop asking how long a press release should be, because they can see the answer in front of them: as long as the story needs, and not a sentence more.