A launch release keeps growing as every feature and statistic gets added. So how long should a press release be? About one page, or 300 to 500 words, with the news up top and the rest cut or moved.
That limit holds for any tech press release format. The sections below give a length target for each part of the release, the misreadings that inflate drafts, and where overflow detail belongs.
The one-page limit and why it holds
A press release works best at one page, and Davis advises treating that as a maximum because most recipients won’t have the time or patience to read past that. Read the upper end as a ceiling for releases with a lot of substance. It is not a target to grow into.
The length rule only works if the structure supports it. Presscloud puts the news in the headline and the lead, depth in the middle and background at the bottom, so a release can be cut from the end without losing the announcement. That is the inverted pyramid in practice: any paragraph can be dropped from the bottom without breaking the story above it.
| Common assumption | What the guidance supports | Planning use |
|---|---|---|
| More detail makes a release more convincing | One page maximum; a longer release is rarely read in full | Cut to the news and move supporting material elsewhere |
| Word count is one number for the whole release | 300 to 500 words overall, with limits per section: a one-sentence headline, a lead of three to five sentences, a body of five paragraphs at most, and a boilerplate of two to four sentences | Budget each section before drafting rather than trimming at the end |
| Background can open the release to set the scene | News in the headline and lead, depth in the middle, background at the bottom | Order the draft so cuts always come from the bottom |
Length ranges and section limits here come from Presscloud’s press release guide, and the one-page ceiling comes from Davis’s dos and don’ts.
Length targets by section
Each part of a release has its own job and its own limit. Planning them separately stops any one section from eating the page.
Headline and subheadline
The headline carries the news in one sentence, factual and compelling, according to Presscloud. Davis notes that the headline is the first thing readers will notice, so a sprawling headline costs more than the extra words suggest. If a subheadline is used, EasyPR keeps it no longer than one sentence. Use it for the one detail that sharpens the headline, not to repeat it.
Lead paragraph
Presscloud sets the lead at three to five sentences answering who, what, where, when and why, often complemented by how. A tech lead that needs more than that is usually carrying background, such as architecture or company history, that belongs lower down or elsewhere. EasyPR makes the same point from the reader’s side: be concise, because journalists often skim this section first.
Body and quotes
Presscloud caps the body at five paragraphs with depth, numbers and quotes. Quotes therefore share the body budget rather than sitting on top of it. A quote that only repeats the lead takes space a number or a specific detail could use better. Pick the quote that adds a view or a consequence the facts cannot carry.
Boilerplate
The boilerplate is a concise paragraph at the end of the release, per EasyPR, and Presscloud puts it at two to four sentences about the company under its own heading. Treat it as fixed text that is written once and kept short. When a release runs long, cut the body first and leave the boilerplate untouched.
Misreadings of the word count
Most overlong drafts come from a few predictable assumptions rather than from the announcement itself.
- A range is not a quota. The 300 to 500 word range is described as a maximum, so a release that makes its point in fewer words has nothing to make up.
- Short does not mean thin. The body is meant to hold depth, numbers and quotes within its five paragraphs. Specific figures and a pointed quote give a short release substance without adding bulk.
- Length is not the only variable. A tight release still fails if the opening is vague, because the headline is noticed first and the lead is skimmed first. Write the headline and lead as if they might be the only text read.
- Technical depth does not require technical volume. A complex product still has to fit the page limit, so the release states what the product does and why it matters, while explanation of how it works belongs in supporting material. For wording that stays readable, see how to write about technical products for journalists.
When a draft still overshoots after those corrections, something has to leave the page, and the next question is where it should go.
Moving overflow to a fact sheet
Background that does not strengthen the story is the first thing to move. EasyPR advises avoiding overwhelming the reader with unnecessary details, and a linked fact sheet or media kit lets that detail remain available without lengthening the release. Reporters who want depth can follow the link, while everyone else gets the announcement in a page.
- Mark the news. Identify what the headline and lead must say, and leave those untouched.
- Cut from the bottom. Because background sits at the end of a well-built release, trim there before touching the middle.
- Move supporting detail. Company history, technical specifications and other reference material that explains but does not announce are the best candidates for the fact sheet.
- Keep one pointer. Reference the fact sheet once, near the end of the body, rather than summarising its contents in the release.
- Re-read the lead. After cutting, check that the lead still answers who, what, where, when and why on its own.
Checking length before sending
Run a word count on the finished draft and compare each section against its limit, not just the total. A release that lands inside the overall range can still have a five-sentence headline or an oversized boilerplate. Check any limits shown on the form if the release goes through a distribution service, since those can shape the headline before the copy is final.
A trimmed release still needs a good delivery. The practical steps are covered in how to email a press release to journalists.
Frequently asked questions
| Question | Answer |
|---|---|
| Does length affect whether journalists read the release? | Yes. Presscloud notes that journalists receive dozens to hundreds of releases daily and that a longer release is rarely read in full. Davis likewise advises one page because most recipients will not read past it. |
| Is a one-page press release enough for a tech announcement? | Yes, for most announcements. The guidance allows one page to a page and a half at most, or 300 to 500 words, and anything beyond that is better placed in a linked fact sheet or media kit. |
| What should the first sentence do? | Davis says the first sentence should tell what the entire press release will be about, so a reader who stops there still has the subject. |
