Google has announced the discontinuation of the Tenor API, requiring all partners holding API or Ads Distribution Agreements with Tenor to terminate those agreements and fully decommission their existing integrations, according to Google's official Tenor support documentation.

The directive is unambiguous: any application or service currently pulling GIFs, stickers, or related content through the Tenor API must remove that integration. There is no deprecation-lite path where read-only access persists in a degraded state. The API goes away, and anything built on it must be rebuilt or retired.

For developers, the practical blast radius depends heavily on how tightly Tenor was woven into their stack. Tenor has been a quietly ubiquitous dependency across messaging apps, social platforms, mobile keyboards, and productivity tools since Google acquired it in 2018. Its API was attractive precisely because it was free at reasonable call volumes, well-documented, and backed by Google's CDN infrastructure — the kind of integration engineers reach for when they need animated content without negotiating a custom content deal. Partners who treated it as a first-class dependency rather than a swappable module are now facing a non-trivial migration.

The alternatives are limited but real. Giphy — itself acquired by Shutterstock in 2023 after Meta's attempted purchase was blocked by the UK's Competition and Markets Authority — operates a comparable API and already serves as the default GIF backbone for Slack, Discord, and others. Tenor's own content library was also notable for its search quality and localization breadth, so partners migrating to Giphy or other providers will want to audit their search result fidelity, particularly for non-English markets. Smaller players like Gfycat effectively exited the market years ago, so the competitive landscape for drop-in replacements is narrower than it was even five years back.

Google has not publicly disclosed a timeline for when the Tenor API will go fully dark, which is a meaningful gap in the announcement. Migration planning for any production integration requires at minimum a sunset date; without one, engineering teams are left choosing between starting work immediately at unknown urgency or waiting for clarity at the risk of a hard cutoff. Worth flagging: the absence of a published deadline in the support documentation is unusual for a Google product wind-down of this visibility — the company has generally been explicit about deprecation windows following sustained criticism of abrupt shutdowns in earlier years.

The broader context here is Google's ongoing rationalisation of products that sit outside its core revenue lines. Tenor generated value primarily as a user-experience enhancement inside Google's own surfaces — Search, Gboard, Messages — rather than as a standalone API business. Maintaining a public API with CDN costs, rate-limit enforcement, abuse mitigation, and partner support is non-trivial operational work. When the strategic calculus shifts, the API becomes a cost centre with limited upside, and that is a familiar endpoint for Google ancillary services.

For engineering teams: the immediate action is an audit of any service that issues calls to the Tenor API endpoints or relies on Tenor's content delivery URLs. Check third-party SDKs and libraries too — Tenor integration is occasionally bundled into emoji or GIF picker components that teams may have pulled in transitively without flagging as a direct dependency. Prioritise identifying any contractual obligations under an Ads Distribution Agreement, since those carry additional compliance steps beyond simply removing API calls.

The animated GIF itself is, of course, going nowhere. The format turned 39 years old in 2026 and has survived repeated predictions of its obsolescence. What changes is the infrastructure layer underneath — and for the developers who built on Tenor's convenience, finding a replacement that matches its combination of content breadth, search relevance, and operational simplicity will take real work.