---
title: "The Google Graveyard and Why Google Keeps Killing Products — Cloud Changelog"
description: "Google Reader, Google+, Inbox, Stadia and Google Podcasts: the products Google launched and shut down, why it keeps happening, and what it cost in trust."
url: "https://cloudchangelog.com/articles/google-graveyard"
updated: "2026-11-19"
---

# The Google Graveyard and Why Google Keeps Killing Products

Google has shut down more than 300 products, and each closure has made people a little slower to trust the next launch.

November 19, 2026

In the mid-2000s, the team behind Google Reader kept a sign in their workspace at Google's headquarters. It read "Days Since Cancellation," and the number under it was always zero.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

It was a joke, and it was also accurate. Reader was loved by its users, and for years someone inside the company was trying to close it. In 2013, someone finally did.

## Google Reader, 2013

Reader was a simple idea. You told it which websites you liked, and it gathered every new article from all of them into one tidy list. No more checking twenty sites a day. At its peak it had a little over 30 million users, many of them opening it every day.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

On a March day in 2013, Google said it would switch Reader off on July 1. The news sat fifth in a list of otherwise dull updates in a post by senior executive Urs Hölzle.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1) "While the product has a loyal following, over the years usage has declined," he wrote.[\[2\]](https://cloudchangelog.com/articles/google-graveyard#source-2)

The post went up on the same day Pope Francis was elected. Mihai Parparita, one of Reader's last engineers, later said the plan inside Google was that the Pope would dominate the news. It did not work. The people who cared about Reader, he said, did not much care about the Pope.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

By the next day, a petition started by a fan named Daniel Lewis had more than 30,000 signatures.[\[3\]](https://cloudchangelog.com/articles/google-graveyard#source-3) Google did not change its mind.

Former team members later told The Verge their side of it. Reader was never big enough by Google's standards, where success means hundreds of millions of users. Jason Shellen, one of its founders, said executive Marissa Mayer once told him he was wasting his engineers' careers on it. When Google decided to rebuild itself around Google+, its answer to Facebook, many of Reader's best people were pulled onto that project or left. By 2011, Reader was in maintenance mode, kept running mostly by one engineer.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

"Literally, it felt like the entire time I was on the project, various people were trying to kill it," said Dolapo Falola, a former Reader engineer.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

In the years after it closed, much of the web's reading moved into feeds run by Facebook and Twitter, which decided for you what you saw.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

## Google+ and Inbox, 2019

Google+ was the project that swallowed Reader. Started in 2011, it was run by Vic Gundotra, who reported directly to the chief executive, Larry Page. Ron Amadeo of Ars Technica later wrote that for a while, every Google employee was effectively paid to work on it.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

It never caught on. In October 2018, Google admitted that a bug had let outside apps see profile details that people had shared privately, possibly affecting up to 500,000 accounts. In the same post, Google announced it would close the consumer version of Google+, and it offered a remarkable statistic about its own product: 90 percent of visits lasted less than five seconds.[\[5\]](https://cloudchangelog.com/articles/google-graveyard#source-5)

Consumer Google+ shut down on April 2, 2019. So did Inbox, on the same day.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

Inbox was a newer, smarter take on email from the Gmail team. It sorted your mail into bundles, like all the messages about one trip. Google said it wanted to focus only on Gmail, which by then had most of Inbox's features.[\[6\]](https://cloudchangelog.com/articles/google-graveyard#source-6) Fans had to go back to the old app.

Google's messaging apps had it worse. Amadeo counted Hangouts, Hangouts Chat, Allo, Duo, Google Voice and Android Messages, all from one company, and concluded that its messaging team had pretty much no credibility left. Allo, one of them, closed in March 2019.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

## Stadia, 2023

Stadia was Google's attempt to replace the games console. You played big new games over the internet, on a TV or laptop, with Google's computers doing the heavy work.

Even before it went on sale, people asked whether it would last. In an interview, the gaming site Kotaku asked Phil Harrison, the head of Stadia, how players could know Google would stick with it, given how many projects it had started and then dropped. Harrison began: "I understand the concern."[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

In September 2022, Harrison announced that Stadia would close on January 18, 2023. It had not gained the following Google expected.[\[7\]](https://cloudchangelog.com/articles/google-graveyard#source-7)

Google refunded everyone. Controllers and other hardware bought from Google's store were paid back, and so was every game and add-on bought in the Stadia store.[\[7\]](https://cloudchangelog.com/articles/google-graveyard#source-7)

Losing the games themselves still stung. Some publishers helped. Ubisoft offered free copies of its games on PC to people who had bought them on Stadia, and other games let players carry their progress to other systems. Google promised an update so the controller could work with other devices over Bluetooth, and it put out one last free game, a version of Snake called Worm Game.[\[8\]](https://cloudchangelog.com/articles/google-graveyard#source-8)

Writing in TechCrunch, Devin Coldewey argued that the technology had worked well. People simply had not trusted Google to keep it running for more than a year or two.[\[9\]](https://cloudchangelog.com/articles/google-graveyard#source-9)

## Google Podcasts, 2024

Not every closure involves a failed product. Google Podcasts had been installed more than 500 million times on Android phones.[\[10\]](https://cloudchangelog.com/articles/google-graveyard#source-10)

Google closed it anyway, in stages through 2024, because it wanted all its audio in one place: YouTube Music. In the United States, the app stopped playing shows in early April. Listeners were told to move their subscriptions to YouTube Music, or export them for another app by July.[\[10\]](https://cloudchangelog.com/articles/google-graveyard#source-10)

## The running tally

All of this is tracked by a website called Killed by Google, a project by Cody Ogden. It lists every product, app and gadget Google has shut down, each with its dates and a short epitaph. It now has a little over 300 entries.[\[11\]](https://cloudchangelog.com/articles/google-graveyard#source-11)

The pace was at its worst in 2019. Amadeo counted that in the first three months of that year, a Google product, feature or service died on average about every nine days.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

## Why it keeps happening

Part of the answer is how Google is organized. Amadeo described a company made of independent teams that launch things on their own schedules, often without talking to each other. That is how Google ends up with several apps doing the same job, and then closes most of them.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4) A product can also lose its home when the executive who championed it leaves, as Google+ did after Gundotra departed in 2014.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

The other part is scale. A product with tens of millions of users would be a hit for most companies. At Google, the Reader team found, it counted as a rounding error. Almost nothing reaches the size Google wants, and so almost everything is eventually at risk.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

Shellen's story points to a third pressure. The Verge found that the people who built Reader did it because they loved it, since a small, steady product was not seen as a smart career move.[\[1\]](https://cloudchangelog.com/articles/google-graveyard#source-1)

## What it cost in trust

Amadeo argued in 2019 that every closure made Google look less stable, and that this mattered most for products that ask people to commit something: their photos, their money, months of a developer's work.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

Google's cloud business, which rents computing power to companies, felt this most. In 2021, two of its vice presidents, Kripa Krishnan and John Jester, promised at least a year's notice before any change to its main business services that could affect customers. Customers need trust and stability, they wrote, before making long-term investments.[\[12\]](https://cloudchangelog.com/articles/google-graveyard#source-12)

To be fair, every big tech company closes products, and most never get a website keeping score. Google's biggest products, like Search, Gmail, Maps and YouTube, have been around for a very long time and are still here.

It is the smaller ones people remember. Six years after Reader closed, Amadeo noted that he still saw people bringing it up all the time.[\[4\]](https://cloudchangelog.com/articles/google-graveyard#source-4)

## Sources

1. The Verge — “[Who killed Google Reader?](https://www.theverge.com/23778253/google-reader-death-2013-rss-social)” (June 2023). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-1-1)[↩2](https://cloudchangelog.com/articles/google-graveyard#cite-1-2)[↩3](https://cloudchangelog.com/articles/google-graveyard#cite-1-3)[↩4](https://cloudchangelog.com/articles/google-graveyard#cite-1-4)[↩5](https://cloudchangelog.com/articles/google-graveyard#cite-1-5)[↩6](https://cloudchangelog.com/articles/google-graveyard#cite-1-6)[↩7](https://cloudchangelog.com/articles/google-graveyard#cite-1-7)[↩8](https://cloudchangelog.com/articles/google-graveyard#cite-1-8)[↩9](https://cloudchangelog.com/articles/google-graveyard#cite-1-9)
2. Google — “[A second spring of cleaning](https://blog.google/topics/inside-google/a-second-spring-of-cleaning/)” (March 2013). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-2-1)
3. TechCrunch — “[The Death Of Google Reader Sparks A Petition 30,000 Signatures Strong](https://techcrunch.com/2013/03/14/the-death-of-google-reader-sparks-a-petition-30000-signatures-strong/)” (March 2013). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-3-1)
4. Ars Technica — “[Google's constant product shutdowns are damaging its brand](https://arstechnica.com/gadgets/2019/04/googles-constant-product-shutdowns-are-damaging-its-brand/)” (April 2019). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-4-1)[↩2](https://cloudchangelog.com/articles/google-graveyard#cite-4-2)[↩3](https://cloudchangelog.com/articles/google-graveyard#cite-4-3)[↩4](https://cloudchangelog.com/articles/google-graveyard#cite-4-4)[↩5](https://cloudchangelog.com/articles/google-graveyard#cite-4-5)[↩6](https://cloudchangelog.com/articles/google-graveyard#cite-4-6)[↩7](https://cloudchangelog.com/articles/google-graveyard#cite-4-7)[↩8](https://cloudchangelog.com/articles/google-graveyard#cite-4-8)[↩9](https://cloudchangelog.com/articles/google-graveyard#cite-4-9)
5. Google — “[Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+](https://blog.google/technology/safety-security/project-strobe/)” (October 2018). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-5-1)
6. TechCrunch — “[Say goodbye to Inbox by Gmail](https://techcrunch.com/2018/09/12/say-goodbye-to-inbox-by-gmail/)” (September 2018). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-6-1)
7. Google — “[A message about Stadia and our long term streaming strategy](https://blog.google/products/stadia/message-on-stadia-streaming-strategy/)” (September 2022). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-7-1)[↩2](https://cloudchangelog.com/articles/google-graveyard#cite-7-2)
8. Engadget — “[Your Google Stadia controller won't be a paperweight after the service shuts down](https://www.engadget.com/google-stadia-controller-bluetooth-unlock-214830717.html)” (January 2023). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-8-1)
9. TechCrunch — “[Stadia died because no one trusts Google](https://techcrunch.com/2022/10/01/stadia-died-because-no-one-trusts-google/)” (October 2022). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-9-1)
10. TechCrunch — “[Google pushes Podcasts users in U.S. to move to YouTube Music by April 2](https://techcrunch.com/2024/03/29/google-pushes-podcasts-users-in-u-s-to-move-to-youtube-music-by-april-2/)” (March 2024). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-10-1)[↩2](https://cloudchangelog.com/articles/google-graveyard#cite-10-2)
11. Killed by Google — “[Killed by Google](https://killedbygoogle.com/)” (accessed November 2026). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-11-1)
12. Google Cloud — “[Delivering API stability with Google Enterprise APIs](https://cloud.google.com/blog/topics/inside-google-cloud/new-api-stability-tenets-govern-google-enterprise-apis)” (July 2021). [↩](https://cloudchangelog.com/articles/google-graveyard#cite-12-1)

## More articles

- [Pentium FDIV Bug: The Chip That Got Division Wrong](https://cloudchangelog.com/articles/pentium-fdiv-bug)

  A math professor found that Intel's Pentium chip got some division wrong, and Intel's first answer made things worse.
- [Mars Climate Orbiter: How a Unit Mix-Up Lost a Spacecraft](https://cloudchangelog.com/articles/mars-climate-orbiter-unit-mix-up)

  A NASA spacecraft flew for nine months, then was lost within minutes of reaching Mars, because one file used pounds where everyone expected metric units.
- [A Short History of the Changelog](https://cloudchangelog.com/articles/history-of-the-changelog)

  How a plain list of software changes went from a programmer's private diary to app store jokes and pages that investors follow.

Get a free daily, weekly or monthly summary by email.

## Contact

- [YouTube](https://www.youtube.com/@cloudchangelog)

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "author": {
    "@type": "Organization",
    "name": "Cloud Changelog"
  },
  "citation": [
    {
      "@type": "CreativeWork",
      "name": "Who killed Google Reader?",
      "publisher": {
        "@type": "Organization",
        "name": "The Verge"
      },
      "url": "https://www.theverge.com/23778253/google-reader-death-2013-rss-social"
    },
    {
      "@type": "CreativeWork",
      "name": "A second spring of cleaning",
      "publisher": {
        "@type": "Organization",
        "name": "Google"
      },
      "url": "https://blog.google/topics/inside-google/a-second-spring-of-cleaning/"
    },
    {
      "@type": "CreativeWork",
      "name": "The Death Of Google Reader Sparks A Petition 30,000 Signatures Strong",
      "publisher": {
        "@type": "Organization",
        "name": "TechCrunch"
      },
      "url": "https://techcrunch.com/2013/03/14/the-death-of-google-reader-sparks-a-petition-30000-signatures-strong/"
    },
    {
      "@type": "CreativeWork",
      "name": "Google's constant product shutdowns are damaging its brand",
      "publisher": {
        "@type": "Organization",
        "name": "Ars Technica"
      },
      "url": "https://arstechnica.com/gadgets/2019/04/googles-constant-product-shutdowns-are-damaging-its-brand/"
    },
    {
      "@type": "CreativeWork",
      "name": "Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+",
      "publisher": {
        "@type": "Organization",
        "name": "Google"
      },
      "url": "https://blog.google/technology/safety-security/project-strobe/"
    },
    {
      "@type": "CreativeWork",
      "name": "Say goodbye to Inbox by Gmail",
      "publisher": {
        "@type": "Organization",
        "name": "TechCrunch"
      },
      "url": "https://techcrunch.com/2018/09/12/say-goodbye-to-inbox-by-gmail/"
    },
    {
      "@type": "CreativeWork",
      "name": "A message about Stadia and our long term streaming strategy",
      "publisher": {
        "@type": "Organization",
        "name": "Google"
      },
      "url": "https://blog.google/products/stadia/message-on-stadia-streaming-strategy/"
    },
    {
      "@type": "CreativeWork",
      "name": "Your Google Stadia controller won't be a paperweight after the service shuts down",
      "publisher": {
        "@type": "Organization",
        "name": "Engadget"
      },
      "url": "https://www.engadget.com/google-stadia-controller-bluetooth-unlock-214830717.html"
    },
    {
      "@type": "CreativeWork",
      "name": "Stadia died because no one trusts Google",
      "publisher": {
        "@type": "Organization",
        "name": "TechCrunch"
      },
      "url": "https://techcrunch.com/2022/10/01/stadia-died-because-no-one-trusts-google/"
    },
    {
      "@type": "CreativeWork",
      "name": "Google pushes Podcasts users in U.S. to move to YouTube Music by April 2",
      "publisher": {
        "@type": "Organization",
        "name": "TechCrunch"
      },
      "url": "https://techcrunch.com/2024/03/29/google-pushes-podcasts-users-in-u-s-to-move-to-youtube-music-by-april-2/"
    },
    {
      "@type": "CreativeWork",
      "name": "Killed by Google",
      "publisher": {
        "@type": "Organization",
        "name": "Killed by Google"
      },
      "url": "https://killedbygoogle.com/"
    },
    {
      "@type": "CreativeWork",
      "name": "Delivering API stability with Google Enterprise APIs",
      "publisher": {
        "@type": "Organization",
        "name": "Google Cloud"
      },
      "url": "https://cloud.google.com/blog/topics/inside-google-cloud/new-api-stability-tenets-govern-google-enterprise-apis"
    }
  ],
  "dateModified": "2026-11-19T14:03:00.000Z",
  "datePublished": "2026-11-19T14:03:00.000Z",
  "description": "Google Reader, Google+, Inbox, Stadia and Google Podcasts: the products Google launched and shut down, why it keeps happening, and what it cost in trust.",
  "headline": "The Google Graveyard and Why Google Keeps Killing Products",
  "image": "https://cloudchangelog.com/_files/3LKjxEzy7iiSV3FYehOlOemjcXv/pAZHsLj9yLzkjKpNwDT0Bw/original.png",
  "mainEntityOfPage": "https://cloudchangelog.com/articles/google-graveyard",
  "publisher": {
    "@type": "Organization",
    "name": "Cloud Changelog"
  }
}
```
