Perspective API is shutting down: What happens on January 1

The Perspective API, the free toxicity-scoring service from Google’s Jigsaw that many publishers and platforms use to moderate comments, is shutting down at the end of 2026. Learn about paths for publishers to get off of Perspective before the end of this year, as well as what will happen on Jan 1st if you do nothing and your comments stop getting toxicity scores.

According to the official notice on perspectiveapi.com , the service will remain active until December 31, 2026. After that it will be shut down, and Google is not offering any migration support. They stopped accepting usage or increased-quota requests in February 2026.

If your moderation pipelines call the Perspective API today, then on January 1, 2027 those calls will stop returning scores.

What Perspective is (and why newsrooms used it)

The Perspective API launched in 2017 with a clear problem statement: hostile comment sections were driving readers and publishers away from conversation. To solve this problem, the team at Google’s Jigsaw created a developer tool that became widely used across publishers and platforms.

For almost a decade, a single free API became the default toxicity layer for a lot of conversation stacks — including Coral installs that wire Perspective into pre-moderation and toxicity threshold rules. Major newsrooms, online gaming platforms, and others are depending on this API to provide toxicity scores to their user’s comments across many languages.

The official timeline

From perspectiveapi.com :

  • New usage / increased quota requests stopped: February 2026
  • Service remains active until: December 31, 2026
  • Perspective API calls will stop working: January 1, 2027

The official reason

Jigsaw’s stated reason: AI capabilities have evolved, and there is less demand for a standalone tool in this area, and Jigsaw’s mission is moving on to new challenges.

What breaks on January 1 if you do nothing

Anything that depends on live scores from Perspective’s comments:analyze endpoint.

Expect the following failures:

  1. Failed API calls. Clients that call commentanalyzer.googleapis.com will stop getting toxicity (and related attribute) scores.
  2. Automated moderation stops. Pre-moderation pipelines/queues, auto-hide rules, and toxicity thresholds will all stop doing their job… some may even behave unpredictably depending on how your moderation tooling handles a failed call if it doesn’t just default back to “not toxic.”
  3. Comment sections turn into dumpster fires. Discourse, Coral, custom Node/Python clients, and internal trust & safety pipelines that assumed Perspective would keep answering will surface production errors or allow toxic comments to be posted during the worst week of the year for comment volume: right after the holidays.

The exact blast radius depends on how your specific moderation tool handles errors, but the result is the same: upstream service you rely on is going away, and there is no official migration solution.

Why waiting until December is a bad plan

  • Cutover during holiday traffic is painful. Comment volume and staffing are both challenging between Christmas and New Year. You need time to identify your chosen new solution as well as implement it before the ball drops on NYE.
  • You might need to recalibrate. Any replacement tool will not match Perspective’s scores one-for-one. For example, taking time to shadow-score a sample of your real historical comment data against a new model would let you compare scores and update your score thresholds accordingly.

Paths off of Perspective

You DO NOT have to rip out your whole moderation stack. Most integrations just point directly to Perspective’s comments:analyze endpoint.

You DO need to decide what model will do the scoring, and where to send your comment text:

  1. Self-host — Run an open-source toxicity classifier model in your own infrastructure so that comment text never leaves your network. CoastWeb built an MIT licensed open-source perspective-replacement that uses @tensorflow-models/toxicity 1.2.2 (Apache-2.0) with model weights already baked into the container image. It supports English-only (version 0), and never writes comment text to disk, a database, or application logs, and is cheaper than you might think to run.
  2. Hosted drop-in — Point your existing client at a Perspective-compatible replacement endpoint and pay someone else to run it. This will send your comment data to their servers, just like you are doing now with Perspective. How that host uses your comment data will depend on which hosting provider you select.

Remove the Perspective Dependency — If you’re thinking that you are ready for a full moderation pipeline migration, that might be a better long-term solution, but you don’t have to take on that massive task before the API sunsets. Replacing the API with a self-hosted or a paid-hosting option can buy you time to inventory which of your tools is making API calls to Perspective, and let you compare replacements to implement an entirely new moderation workflow to replace your existing T&S stack.

What you can do before Dec 31 to prepare

If you are running Coral for comments

  1. Check Coral’s Perspective integration settings in Configure > Moderation and confirm the Toxic comment filter is enabled and still sending data to Perspective. (If Coral’s Toxicity filtering is not enabled, you don’t need to worry about the API going away.)
  2. Determine the attributes you actually use (TOXICITY, SEVERE_TOXICITY, INSULT, and so on) and which language. (Coral supports toxicity filtering in English (en), Spanish (es), French (fr), German (de), and Portuguese (pt).
  3. Decide whether data residency / self-hosting is a hard requirement for your newsroom or if sending your data to a new toxicity score provider is acceptable.

If you have other tools that call Perspective

  1. Search your repos and config for commentanalyzer.googleapis.com, or env variables that set Perspective API keys.
  2. Determine which attributes you use (TOXICITY, SEVERE_TOXICITY, INSULT, and so on) and in which languages.
  3. Make a plan to replace calls to Perspective in your app, such as:

Get help from CoastWeb

We are very familiar with this particular API.

As a former member of the Coral team at Vox Media, and still an active contributor to Coral's open source repository, CoastWeb’s founder Jessie Rushing has been working with Coral’s Perspective API integration since 2018.

CoastWeb needed a perspective-replacement (MIT licensed) solution for our own instances of Coral, so we developed one.

Book an intro call — quick consultation with Jessie to learn which of the available paths off of Perspective is right for you.

Join our free Dec 10th Webinar

It's possible to keep your existing moderation pipeline working after the sunset.

In this live webinar Jessie will cover how to deploy and run your own open-source model for toxicity scoring, how its results compare with Perspective’s, and how doing so can cost as little as $20/month & might even save you money on network egress since the comments stay inside of your network.

Click here to join our free webinar on Thursday, December 10th, 2026, at 10:15 am Pacific Time

CoastWeb is an independent engineering & web development agency. We are not affiliated with Google or Jigsaw.

We develop and host CMS, commenting & other cloud solutions for web publishers of all sizes. We can provide architecture support & infrastructure solutions for challenging use cases. We are happy to help newsrooms and site-runners figure out a path off Perspective that makes sense for your organization.

Resources

No comments yet