Google kills Tenor GIF API, forcing changes at X, Discord, and more 46%

By Ryan Whitwam0%

6/30/2026, 8:38:51 PM

Keywords: Gifs, Google 2

BS Summary: This article contains 24 faulty reasoning types, including Appeal to Emotion, Negativity Bias, and Biased Writer Voice, with Hasty Generalization as the most egregious example at 23.5% saturation with 116 hits. Analysis detected 863 faulty-reasoning hits from 493 analyzed words, generating a BS Score of 48% and a BS Rank of 46% (11,915 of 21,886 articles). This article is better (less manipulative) than 54.40% of the article peer group.

Google is so famous for killing products that there’s a whole virtual graveyard you can explore. 
Google’s latest shutdown now has a headstone of its own. 
Effective today, Google has discontinued the Tenor API, which you may not be familiar with by name. 
You’ve probably used it, though. 
Tenor is a database of searchable GIFs, which used to serve animated images to sites like X/Twitter, Discord, and more. 
Now, it only serves Google—maybe the headstone is a bit premature. 
Like many Google products, Tenor started as an independent company. 
Google came along and bought Tenor in 2018, and it continued running it largely unchanged in the intervening years. 
Tenor was integrated into Google products like Gboard and Google Messages, but the API also gave other platforms a way to help users find, share, and save GIFs. 
It’s similar to services like Giphy and Klipy. 
In January, Google announced it was going to start winding down that API access. 
It stopped accepting new integrations at that time, and the end date has now arrived: As of June 30, the Tenor API is no more. 
Google, a company with nearly 200,000 employees and more than $130 billion in 2025 profit, says it decided to stop supporting the image API so it could better focus its resources. 
The real problem was probably that Tenor was free, and Google didn’t see a way it could make money from a GIF API. 
“As part of an ongoing effort to focus resources on enhancing our core products, we’ve made the decision to sunset the Tenor API on June 30, 2026,” the company explained. 
To be clear, Tenor still exists. 
You can go to the Tenor website to search for GIFs, and Google’s apps will still source animated images from Tenor (for now). 
You may not have realized if you were using Tenor through Twitter or Discord, but any favorite GIFs you’ve saved there are gone. 
Most users didn’t understand easy GIF access was provided by a third-party API and have directed their resulting anger at the platforms themselves. 
Websites that relied on Tenor have been shifting to alternatives over the last several weeks, so you can still get your GIF fix without tedious manual uploading. 
X’s Nikita Bier confirmed on June 20 that the site had migrated away from Tenor. 
Discord, meanwhile, has tested both Giphy and Klipy, but it looks like most users are seeing Klipy integration now. 
WhatsApp and Bluesky also appear to be moving to Klipy integration for GIFs. 
Users of these websites will see a different selection of GIFs going forward, and not everyone is happy with the selection. 
Things could improve as more people use Tenor alternatives. 
Frank Nawabi, who founded Tenor and sold it to Google, is one of the folks behind Klipy. 
The startup recently raised $3.8 million in funding, and one of the investors was, you guessed it, Google. 
Article reasoning-pattern comparisonThis article: 3.7%Ryan Whitwam: 3.0%Ars Technica: 2.8%Confirmation Bias3.7%This article: 1.6%Ryan Whitwam: 0.4%Ars Technica: 1.2%Anchoring Bias1.6%This article: 7.9%Ryan Whitwam: 3.5%Ars Technica: 2.4%Availability Heuristic7.9%This article: 4.7%Ryan Whitwam: 1.2%Ars Technica: 1.0%Representativeness Heuristic4.7%This article: 0.0%Ryan Whitwam: 1.2%Ars Technica: 0.6%Hindsight Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 2.1%Overconfidence Bias0.0%This article: 3.7%Ryan Whitwam: 8.0%Ars Technica: 3.4%Framing Effect3.7%This article: 4.7%Ryan Whitwam: 2.3%Ars Technica: 0.5%Loss Aversion4.7%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.5%Status Quo Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Sunk Cost Effect0.0%This article: 9.5%Ryan Whitwam: 5.1%Ars Technica: 4.2%Optimism Bias9.5%This article: 4.7%Ryan Whitwam: 1.2%Ars Technica: 1.7%Pessimism Bias4.7%This article: 16.6%Ryan Whitwam: 13.8%Ars Technica: 6.2%Negativity Bias16.6%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 1.2%Self-Serving Bias0.0%This article: 9.3%Ryan Whitwam: 3.5%Ars Technica: 0.6%Fundamental Attribution Error9.3%This article: 4.7%Ryan Whitwam: 1.2%Ars Technica: 0.1%Actor-Observer Bias4.7%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.6%In-Group Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Out-Group Homogeneity Bias0.0%This article: 0.0%Ryan Whitwam: 0.8%Ars Technica: 2.0%Halo Effect0.0%This article: 0.0%Ryan Whitwam: 0.8%Ars Technica: 0.1%Horn Effect0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.0%Dunning-Kruger Effect0.0%This article: 8.5%Ryan Whitwam: 2.1%Ars Technica: 1.0%Recency Bias8.5%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.3%Primacy Effect0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Blind-Spot Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.5%Ad Hominem0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Straw Man0.0%This article: 6.3%Ryan Whitwam: 1.6%Ars Technica: 4.1%Appeal to Authority6.3%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 1.1%False Dilemma0.0%This article: 1.8%Ryan Whitwam: 0.5%Ars Technica: 0.7%Slippery Slope1.8%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Circular Reasoning0.0%This article: 23.5%Ryan Whitwam: 14.2%Ars Technica: 3.8%Hasty Generalization23.5%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Red Herring0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.6%Bandwagon0.0%This article: 17.8%Ryan Whitwam: 4.5%Ars Technica: 2.7%Appeal to Emotion17.8%This article: 4.7%Ryan Whitwam: 1.2%Ars Technica: 0.6%Begging the Question4.7%This article: 4.7%Ryan Whitwam: 2.3%Ars Technica: 2.3%Post Hoc (False Cause)4.7%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Tu Quoque0.0%This article: 4.7%Ryan Whitwam: 1.2%Ars Technica: 0.5%Burden of Proof4.7%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Appeal to Nature0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Composition/Division0.0%This article: 3.7%Ryan Whitwam: 0.9%Ars Technica: 1.5%Anecdotal3.7%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%No True Scotsman0.0%This article: 2.2%Ryan Whitwam: 0.6%Ars Technica: 1.7%Ambiguity (Equivocation)2.2%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.0%Gambler’s Fallacy0.0%This article: 1.6%Ryan Whitwam: 0.4%Ars Technica: 0.1%Middle Ground1.6%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Personal Incredulity0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Special Pleading0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.1%Genetic Fallacy0.0%This article: 0.0%Ryan Whitwam: 1.5%Ars Technica: 1.5%Unattributed Quote0.0%This article: 9.7%Ryan Whitwam: 2.4%Ars Technica: 1.0%Quote-first Misdirection9.7%This article: 14.8%Ryan Whitwam: 12.9%Ars Technica: 4.5%Biased Writer Voice14.8%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 1.0%Indoctrination0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.7%Politically Left Leaning Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 0.2%Politically Right Leaning Bias0.0%This article: 0.0%Ryan Whitwam: 0.0%Ars Technica: 1.3%Attempt to Sell a Product or S…0.0%

493 words analyzed.

Speakers

2speakers15%attributed speech417writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 12 words • 0.0% coverageWriter's voice • 16 words • 100.0% coverageWriter's voice • 10 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 5 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 11 words • 100.0% coverageWriter's voice • 10 words • 0.0% coverageWriter's voice • 19 words • 0.0% coverageWriter's voice • 28 words • 0.0% coverageWriter's voice • 8 words • 0.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 25 words • 0.0% coverageGoogle • 31 words • 0.0% coverageWriter's voice • 23 words • 100.0% coverageGoogle • 30 words • 100.0% coverageWriter's voice • 6 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 23 words • 100.0% coverageWriter's voice • 27 words • 0.0% coverageNikita Bier • 15 words • 0.0% coverageWriter's voice • 19 words • 0.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 21 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 18 words • 100.0% coverage
Selected voice

Google

100%flagged-word coverage
61 attributed words80% of attributed speech72% writer coverage
0%25.0%50.0%Quote-first Misdirection+44.9 ptsWriter: 4.3%Google: 49.2%49.2%Biased Writer Voice-17.5 ptsWriter: 17.5%Google: 0.0%0.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.