The press release is dead. You have read that headline on a marketing blog, probably more than once, usually written by someone selling the thing that supposedly replaced it. It is a confident claim, it gets clicks, and it is wrong. Not partly wrong. Wrong in a way that costs companies real coverage when they believe it and stop writing releases.
Here is the more accurate version. The press release as a hype document, blasted to a thousand journalists who never asked for it, hoping a few bite, has been dead for years. Good. It deserved to die. But the press release as a structured, factual, citable source document is doing more work in 2026 than it did a decade ago, because two different audiences now depend on exactly that kind of document. So is the press release dead? No. It changed jobs. This piece walks through three concrete signals that prove the format is alive, where it still earns coverage, and how to write one that does its job.
Where the “press release is dead” idea came from
The “press release is dead” idea is not pure invention. It grew from a real failure. For two decades, the dominant way companies used releases was volume. Write a release for any event, push it through a wire service, blast a contact list, and measure success by how many outlets republished it verbatim. That model produced enormous quantities of low-value content, journalists learned to ignore the flood, and pickup rates fell. The people declaring the format dead were watching that specific model fail, and that model did fail.
The error is in the conclusion. They saw one use of the press release stop working and announced the document itself was finished. That is like watching fax-based ordering die and announcing the purchase order is dead. The delivery method and the marketing strategy collapsed. The artifact, a clear written statement of who did what, when, and why, with quotes and verifiable facts, did not. It just needed new jobs, and it found them.
There is also a measurement error baked into the death narrative. The old model was easy to measure badly: count the outlets that republished your release word for word. By that metric, the press release did collapse, because verbatim republication fell hard. But verbatim pickup was never the point, and it was always a weak goal anyway, a hundred identical copies of your text scattered across low-quality sites. The jobs that actually matter, confirming facts for a reporter, ranking as a search asset, feeding an AI answer, were never captured by the old pickup metric at all. So the metric died, the strategy died, and people mistook the death of a bad scoreboard for the death of the game.
The three jobs a press release still does
A modern press release earns its place by doing three jobs, and each one is a data point against the claim that the format is dead. Think of them as the three jobs framework: source document, search asset, and AI input. A release that does all three is alive and working. A release that does none of them really is dead, and the format gets blamed for the writing.
Job one is the source document. A release is a reference a journalist consults to confirm a fact: the correct spelling of a name, an exact title, a date, a dollar figure, an approved quote. The reporter is not republishing the release. They are using it the way anyone uses a reference document, to get the details right fast.
Job two is the search asset. A release published on your own site and on a reputable wire is an indexed page that can rank for the specific, low-competition queries around your announcement, your funding round, your new hire, your product launch. Months later, someone searching that exact event finds your account of it.
Job three is the AI input. Answer engines build responses from text they can read and trust, and a press release is unusually well suited to be read: it is structured, factual, dated, and explicit about who and what. The format that journalists found too dry is the format an AI engine finds easy to parse.
Job three is the newest reason the format matters, and the one most people miss. A decade ago, a dry, structured release was a liability: it was tedious to a human reader, and human readers were the only audience that existed. Today that same dryness is an asset, because a second kind of reader has arrived. An answer engine assembling a response about your company, your funding, or your launch is looking for exactly what a good release provides, a clear, dated, factual account it can parse and cite. The release did not change. The audience expanded, and the format turned out to suit the new reader better than the old one. Newsrooms increasingly run on automated feeds and AI-assisted research too, which means the structured release is often read by software before any journalist sees it, and software rewards the structure that humans once found dull.
Each job is a reason the release survives. The first one deserves a closer look.
Job one: the press release as a source document
To see why the source-document job matters, picture how a reporter actually handles a story that mentions your company. They are not building the story from your release. They have an angle, other sources, a deadline. What they need from you is fast, reliable confirmation of specifics, and they need it without a phone call.
A well-built release gives them that. The chief executive’s name spelled correctly and titled correctly. The funding amount and the lead investor. The launch date. A quote that is already approved, already on the record, ready to use without a follow-up email. When a reporter has that document open in a tab, you have removed friction from their job, and reporters reward removed friction with accuracy and inclusion. When they do not have it, they guess, or they leave you out, or they get a detail wrong that you then spend a day correcting.
This is the job that proves the format is not dead, because it does not depend on the reporter loving your release or republishing a word of it. It depends only on the release existing, being accurate, and being easy to find. Wire services such as PR Newswire and Business Wire still exist and still carry releases for exactly this reason: they make the source document discoverable and timestamped. The Associated Press and other newsrooms still ingest wire feeds. The plumbing that the “press release is dead” crowd declared obsolete is still running, because the source-document job never went away. So when you ask is the press release dead, the honest test is whether your release can do this one job. If a reporter could confirm every key fact of your story from it in thirty seconds, it is alive.
Where the press release actually fails
Defending the format is not the same as defending most releases. Plenty of releases genuinely fail, and pretending otherwise helps no one. The format is alive. The average release is not, and the gap between the two is craft.
A release fails when it leads with hype instead of fact. “Industry-leading,” “best-in-class,” “thrilled to announce” are not information. A reporter scanning for the source document skips straight past them, and an AI engine cannot extract a fact from an adjective. A release fails when the actual news is buried in paragraph four, under a wind-up nobody asked for. It fails when it has no real quote, only a manufactured line of marketing copy with an executive’s name attached. It fails when the basic facts, the who, the what, the when, the number, are vague or missing, which means it cannot do job one at all.
A release also fails when it is written for an event that is not news. A company rebrands a feature, hires a mid-level manager, or wins a minor award, and someone writes a release because writing releases is the habit. No reader, human or machine, has a reason to care, so the release does nothing, and its failure gets counted as evidence that releases do not work. They worked fine. There was simply no story for them to carry. The format cannot manufacture significance that the underlying event does not have, and asking it to is the most common way teams set a release up to fail before a single word is written.
Notice that every one of these failures is a writing failure, not a format failure. The release is dead in those cases because the writing killed it. This is the sleight of hand in the “press release is dead” argument: it takes the predictable result of bad writing and blames the document type. Fix the writing and the same format does all three jobs. The question is the press release dead has an answer, and the answer depends on the writer, not the format.
Write fewer, write them as documents
The practical move for 2026 is not to abandon the press release. It is to change how you treat it. Write fewer of them, and write each one as a source document rather than a marketing broadcast.
Writing fewer means raising the bar for what earns a release. Not every internal milestone is news. A release should mark something a journalist or a searcher would plausibly care about: funding, a launch, a major hire, a partnership, a result. When you stop producing releases for non-events, the ones you do produce carry more weight and get more attention.
Writing each as a document means leading with the fact, putting the real news in the first sentence, including a quote a human actually said, and stating every key detail in plain, verifiable language. Publish it on your own newsroom page so it becomes a permanent search asset, and use a reputable wire when timestamped, discoverable distribution genuinely helps the story.
It also helps to think about the release as a permanent record rather than a one-day event. A release blasted out, picked up or not, and forgotten by Tuesday is using maybe a tenth of the document’s value. The same release, published on your own newsroom page, kept accurate, and written so a human or an engine can extract the facts months later, keeps working long after the news cycle moves on. Someone researching your funding round next year, or an AI engine answering a question about your category, can still find your clear account of what happened. That long tail is the part of the press release that was never dead, and the part most companies throw away by treating the release as disposable. Then judge it by the three jobs framework: can a reporter confirm the story from it, can it rank for the event, can an AI engine read and cite it. A release that passes all three is not a relic. It is one of the most efficient documents in your communications toolkit, doing three jobs at once. The press release is not dead. The lazy press release is, and that was always the one worth burying.