Defamation Risk for Podcasters: What You Can Say, What Gets You Sued, and What Insurance Covers

The Risk Most Podcasters Never Think About

You built your show to have opinions. You name names, you call out bad actors, you break down the story everyone else is too polite to touch. That instinct is what makes a podcast worth listening to — and it is also the exact instinct that creates legal exposure most independent creators never stop to consider. Every time you describe a real person, company, or event as a fact rather than an opinion, you are standing in the same legal territory as a national news network.

The headline cases make that territory look distant. In April 2023, Fox News settled Dominion Voting Systems' defamation claim for $787.5 million, the largest known media defamation settlement in U.S. history — with no apology required. A separate suit from Smartmatic, seeking $2.7 billion, is still moving forward after a New York appellate court refused to dismiss it in early 2025. Numbers like these belong to a world of national broadcasts and corporate plaintiffs, and no independent podcaster should read them as a forecast of their own risk.

But look one case over. Alex Jones — a broadcaster speaking directly to an audience, the closest analogue to what you do — was hit with roughly $1.5 billion in defamation judgments over his false claims about the Sandy Hook shooting, and the Supreme Court declined to intervene. He was not a newsroom. He was a guy with a microphone and an audience, which is the point worth sitting with.

That distinction is the whole point of this guide. Defamation is governed by state law, so the specifics shift depending on where you and your subject sit, but the core machinery is remarkably consistent. Understanding how it works is not about scaring you into silence — it is about giving you the confidence to say what you mean without handing someone a lawsuit.

The Five Elements — and the Opinion Defense

Defamation is state common law, so the exact wording of the test varies by jurisdiction — and so do the rules about which statements are so damaging they're presumed harmful (the "per se" categories). But nearly every state builds on the same skeleton, drawn from the Restatement (Second) of Torts. To win, a plaintiff generally has to prove the elements courts require:

• A false statement of fact — not opinion, not a true statement that merely embarrasses someone;
• Publication to a third party — someone other than the subject heard or read it, which a podcast obviously satisfies;
• Fault — at minimum negligence, and for public figures, actual malice;
• That the statement is of and concerning an identifiable person — the audience could tell who you meant;
• Harm or damages — reputational injury, though some categories are actionable without proof of special harm.

The first element is where most podcast disputes live, because it draws the line between fact and opinion. Pure opinion is protected — you can say a restaurant's food is overrated or a founder is a mediocre CEO, because those are judgments a reasonable listener understands as your take. The problem is that people assume the word "opinion" is a shield. It is not.

The Supreme Court settled this in Milkovich v. Lorain Journal Co. There is no wholesale exemption for anything labeled opinion; a statement dressed up as opinion is still actionable if it implies an assertion of objective, provably false fact. The operative question is whether the statement is "sufficiently factual to be susceptible of being proved true or false." Saying "in my opinion, Jones lied under oath" implies you know Jones perjured himself — a checkable fact — and the opinion framing won't save it. By contrast, statements that "cannot reasonably [be] interpreted as stating actual facts" — loose, figurative, or hyperbolic language nobody takes literally — stay protected. Calling a competitor "a total clown" is name-calling; claiming he "embezzled from his investors" is a factual charge you had better be able to prove.

Public Figures, Private Figures, and "Actual Malice"

Before you weigh whether a statement is false and damaging, ask a prior question: who is the person you're talking about? The identity of the plaintiff sets how hard it is for them to win. The same sentence about a sitting senator and about your neighbor down the street carries very different legal risk, because the two of them have to clear very different bars to hold you liable.

Public officials and public figures face the highest bar. Under New York Times Co. v. Sullivan, a public official cannot recover for a defamatory falsehood about official conduct unless he proves "actual malice" — "that is, with knowledge that it was false or with reckless disregard of whether it was false or not." That is a demanding standard. Honest mistakes, sloppy fact-checking, and reasonable-but-wrong reporting generally don't meet it; the plaintiff essentially has to show you knew or strongly suspected you were wrong and ran with it anyway.

Private figures have it much easier, which means commenting on a private individual is the higher-risk scenario for you. Under Gertz v. Robert Welch, Inc., states may set their own liability standard for defaming a private person, so long as they don't impose liability without fault — in practice, most require only negligence. A private figure need not prove actual malice to recover actual damages, though punitive and presumed damages still require it. Negligence is a far lighter burden than actual malice, so a careless episode about a private person is where podcasters get exposed.

Between those poles sits the limited-purpose public figure: someone who, in Gertz's words, "voluntarily injects himself or is drawn into a particular public controversy and thereby becomes a public figure for a limited range of issues." That status is narrow. It attaches only to the specific controversy the person entered — not to their private life generally. And it turns on the plaintiff's own conduct: Gertz himself had "achieved no general fame or notoriety" and hadn't "thrust himself into the vortex" of the controversy, so he remained a private figure despite being a lawyer involved in a high-profile case.

The trap to avoid: you cannot manufacture public-figure status by covering someone. Putting a private person on blast in an episode doesn't convert them into a public figure who has to prove actual malice — their own fame or voluntary entry into a controversy controls their status, not your coverage of them. Because this classification is fact-intensive and decided case by case, treat it as a risk-sorting tool rather than a guarantee.

The Republication Trap: Repeating a Guest's Claim

Here is the rule that catches podcasters off guard: you do not have to invent a false accusation to get sued for one. If you repeat it, you own it. Under the republication rule, "one who repeats or otherwise republishes defamatory matter is subject to liability as if he had originally published it." Your guest supplies the accusation; the law can still treat you as the publisher who put it into the world.

Play this out in the situations you actually face. A guest goes on your show and accuses a named person of fraud, and you nod along and let it stand. A listener sends in a juicy message about a local business and you read it on air. A clip from another creator makes a damaging claim and you repost it to your feed with a caption. In each case, the false statement passed through you to your audience — and that act of passing it along is what the law treats as your own publication. Being the microphone, not the mouth, does not get you out.

The instinct most people have here is to reach for attribution as a shield: "He said it, not me." That instinct is wrong. Under the republication rule, you can be liable even when you expressly attribute the statement to someone else — and even when you distance yourself from it, for example by noting that the accused person denied the claim. Framing it as someone else's accusation does not neutralize the harm to the person accused. The old maxim captures it bluntly: "tale bearers are as bad as the tale makers."

You may have heard about a privilege for reporting accusations, and it is worth naming so you understand its limits. Some jurisdictions recognize a narrow, limited privilege for accurately reporting newsworthy accusations made by responsible sources — variously called neutral reportage or a wire-service defense. It is jurisdiction-specific, applied inconsistently, and far narrower than most creators assume. Treat it as a caveat, not a strategy: the default rule is that repeating a false accusation exposes you, and you should not plan your show around a privilege that may not exist where you are. None of this is legal advice for your specific situation.

Does Section 230 Protect You? And What Insurance Actually Covers

A lot of creators assume Section 230 is a blanket shield — post a podcast, invoke the magic words, walk away immune. That is a misreading. Section 230 is a distributor immunity, not a speaker immunity, and the difference decides whether it helps you at all.

What Section 230 actually does

The core provision, 47 U.S.C. § 230(c)(1), says that "no provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider." Read that carefully: the protection attaches to content provided by another party. Section 230 shields the platform or host that merely carries someone else's speech — it was written to stop websites from being sued as the "publisher" of their users' posts.

Your own episode is not someone else's speech. The statute defines an "information content provider" as any entity "responsible, in whole or in part, for the creation or development of information," and when you write, record, and release an episode, that is you. On your own on-mic statements you are the content provider, so the words are yours to answer for. Case law squarely addressing a host's recorded audio under this exact framing is thin, so treat this as a reading of the statute rather than a settled rule — but the statutory logic is hard to escape: you cannot be a mere distributor of your own voice.

So the guest audio you host, the listener comments you display, the clip a fan submitted — those can fall on the protected side of the line. The monologue you recorded on Tuesday does not.

The backstop creators actually rely on

Because your own speech sits outside Section 230, the practical protection most working podcasters lean on is insurance — specifically media liability coverage, sometimes sold as media errors and omissions or media perils. This is the line of coverage built for exactly these claims: it responds to defamation, libel and slander, invasion of privacy, and intellectual property claims, and — the part that matters most in practice — it covers your defense costs, not just a final judgment. Defending even a meritless defamation suit can cost more than most independent shows earn in a year, so the defense obligation is often the real value.

Pricing varies widely, and the figures floating around online come from insurance marketers and aggregators rather than any authoritative benchmark — so treat them as illustrative, not a quote. Low-end policies get advertised in the range of $50 to $100 a month, while podcast-specific coverage is often cited around $3,000 to $7,000 a year, and broader estimates run from roughly $2,500 to $15,000 annually depending on your revenue, reach, and how provocative your content is. A representative podcast policy might carry limits like $1 million per occurrence and $3 million aggregate with a self-insured retention around $10,000. Your number will depend on your specifics — get an actual quote before you rely on any figure here.

None of this is legal advice or an insurance recommendation, and defamation itself is governed by state law that varies. What holds across the board is the structure: Section 230 is a shield for carrying others' words, insurance is the backstop for your own.

What Courts Protect — and a Pre-Publish Checklist

The point of everything above isn't to make you stop talking. It's to make sure that when you say something pointed, you're standing on solid ground. Courts protect a lot of what podcasters do every week: pure opinion, sharp criticism, and rhetorical hyperbole — heated language that no reasonable listener would take as a literal statement of fact. When you call a company's product "a scam" as shorthand for "I think it's overpriced and I wouldn't buy it," you're offering an opinion, not a provable factual charge.

The Supreme Court drew this line clearly. In Greenbelt Cooperative Publishing Ass'n v. Bresler, it held that describing a developer's hardball negotiating position as "blackmail" was "no more than rhetorical hyperbole" — vigorous name-calling, not a libelous accusation of an actual crime. The organizing question, from the Milkovich standard discussed earlier, is whether a statement is "sufficiently factual to be susceptible of being proved true or false." If it can be objectively proven false, it can be defamatory. If it's genuinely a matter of opinion, it generally can't.

Before you publish a segment that names names or makes a hard claim, run through this:

• Is it a provable fact or an opinion? If you're stating a fact, it has to be true.
• Can you actually back it up? Truth is a complete defense — but only if you can prove it, not just believe it.
• Is the subject a public or private figure? Private figures clear a lower bar to win, so the risk to you is higher.
• Are you repeating someone else's claim? Republishing a defamatory statement makes it your liability, too.
• Do you have a correction process? In many states, a prompt, prominent correction can reduce or limit the damages you'd owe.

Defamation is state law, and this is general information rather than legal advice — the specifics shift depending on where you and your subject are. But the through-line is simple: the goal isn't silence, it's saying what you mean on ground you can defend.