Nano Banana in Google Earth: Google Rolled It Back

Google has pulled this feature. On July 30, 2026 it switched on image generation inside Google Earth using Nano Banana, its image model, and called it "available globally today for Google Earth web users." Google has since added a notice to the top of that same post, labelled "Update, 7/31", while leaving the post's own byline date at Jul 30, 2026 and publishing nothing separate:

We know that people uniquely trust Google Earth for a reliable view of the world. We've seen geospatial professionals using this feature for a range of useful purposes, however we've also seen people sharing screenshots of generated imagery that appear to violate our policies. So we're rolling back this feature in Google Earth while we work on implementing stronger guardrails. It's important to note that generated images didn't appear in the main Google Earth experience for others to see and were watermarked as AI generated.

Key Takeaways

• It is gone. Google's own announcement now says it is "rolling back this feature in Google Earth while we work on implementing stronger guardrails."
• It lasted one day. Announced July 30, 2026; Google labels its own rollback notice "Update, 7/31" and the original text "Original post, 7/30", so the withdrawal came the next day.
• Google never announced the removal separately. No new blog post, no help-centre article, no release note. The notice was added to the launch post in place.
• The stated reason is misuse, not the technology. Google says it saw "people sharing screenshots of generated imagery that appear to violate our policies."
• The images were already labelled. Google says they "didn't appear in the main Google Earth experience for others to see and were watermarked as AI generated."
• No return date. "While we work on implementing stronger guardrails" is the whole commitment. Google has not said when, or whether, it comes back.
• Nano Banana elsewhere is unaffected. The Gemini app's image generation is a separate product and still runs, including on the free tier.

What It Did, While It Lasted

It turned any spot on the map into a starting image and then edited that image to your description. The model was not guessing what your street corner looked like; it worked from Google Earth's existing satellite, aerial and 3D imagery of that specific place. Google called this generating images "grounded in the real world," and said it was the first time Earth's imagery had been usable that way.

Google's five published examples were historical reconstructions of a real site, infographics about a place, real estate and urban planning renderings, previews of a building on an empty lot, and imaginative makeovers of somewhere you know. The genuinely useful one was the fourth: showing a builder or a partner what an extension would look like on a picture of your actual plot.

Why Google Pulled It

Read the notice closely, because Google is careful about what it does and does not blame.

That last pair is the interesting part, and it generalises well beyond Google Earth. The safeguards Google built worked inside the product: the images were private and they were watermarked. What defeated them was somebody taking a screenshot and posting it somewhere else, which strips a visible label's context and, depending on the method, the invisible one too. A watermark tells you what a file is. It does not stop a picture of that file travelling without it.

What Google Has Not Said

Google dates the rollback itself, in the post: the notice is headed "Update, 7/31" and the text below it "Original post, 7/30", so the feature ran for one day. Re-read live on November 2, 2026, the post still carries both labels and the rollback paragraph, and still says nothing about a return -- back in Google Earth, re-enabled and restored all return zero on the page. The Internet Archive has no capture before August 1, 2026 at 07:46:46 UTC, and every capture from that one through September 28, 2026 contains the notice.

What To Do Instead

If you wanted to visualise a build on your own land, this was the best free tool for it and there is no direct replacement. The closest thing is the Gemini app's Nano Banana image generation, which will edit a photo you upload -- including a screenshot of your plot from Google Earth. You lose the automatic grounding in Earth's 3D imagery, which was the whole point, but you keep the editing.

If you wanted it for teaching, the same workaround applies: screenshot the site in Google Earth, then ask Gemini to render it as it looked in another era.

Do not wait for it. Google has committed to guardrails, not to a date. If it returns, this page will say so.

Nothing you generated is at risk. Google says the images never entered the shared Google Earth experience, so there is nothing of yours sitting on the public map.

The bottom line: a good feature shipped, got screenshotted into a problem, and was withdrawn the next day, with the news carried only by a paragraph quietly added to the launch post. If you read about Nano Banana in Google Earth and went looking for it, that is why you could not find it. For where Google's image model is still worth your time, see the best free AI chatbot right now and which AI chatbot you should pay for.

Corrections and Updates

November 2, 2026: this page said Google's rollback notice "carries no date," and Google labels it "Update, 7/31". The label sits directly above the paragraph this page quotes, and a capture from September 28, 2026 at 01:05 UTC -- the day this page was last revised -- already contained it, so the date was there to be read and was not. That fixes the length of the feature's life at one day rather than "days at most", and the summary, Key Takeaways, two FAQ answers, the dating paragraph and the verdict were corrected to match. Re-read live today, the post still carries the notice and still names no return date.

September 28, 2026: this page said the feature was "live worldwide today," and it had not been live since roughly August 1, 2026. Google added a rollback notice to its own announcement in place, leaving the post's date, URL and article:published_time untouched, so the citation kept returning 200 and kept reading as a launch. The title, summary, Key Takeaways, all six FAQ answers, the availability table and the verdict were rewritten. The error was found by diffing the live post against its archived captures rather than by re-fetching the citation.