Google Earth Pro's Desktop Sunset Is a Deadline for Linear Infrastructure
The announcement converts the industry's favorite free viewer from permanent fixture to legacy risk - and gives every land, construction, and operations team about a year to answer a question they've been avoiding.
On July 7, Google announced that the Google Earth Pro desktop application will no longer be available for download after June 25, 2027. The reaction across the geospatial world was immediate and mostly wrong. This is not a shutdown. Installed copies of Earth Pro will keep launching after the deadline. Google Earth continues on the web and mobile, where the company has been investing in cloud projects, data layers, and AI-assisted analysis.
But read the announcement the way an operator should, and it says something more important than “download it while you can.” It says the center of gravity has moved. The desktop app that thousands of linear infrastructure teams treat as standard equipment is now legacy software: no new downloads, no updates, and a permanent dependency on backend imagery and terrain services that Google can reshape at will. Meanwhile, the recommended path forward - Google Earth's web plans - arrives with per-user pricing of $75 to $150 per month at the professional tiers and plan-based limits on imported data.
For most industries, that's a footnote. For ours, it's a forcing function.
The universal viewer nobody chose on purpose
Ask how Google Earth Pro became critical to pipeline work and nobody can point to a decision. It simply accreted. It was free, it ran on anything, and it opened the one file format everyone on a corridor could produce: KMZ. Land agents exported tract exhibits to it. Survey passed centerline QC through it. Construction dropped daily progress over it. Inspectors flew patrol routes in it. Executives who had never opened a GIS application in their lives could spin the globe, find the corridor, and feel briefed.
That's a remarkable amount of operational weight resting on a consumer application with no user management, no audit trail, no access control, and no service commitment. The industry knew this. It was simply a tolerable risk while the tool was free and seemingly eternal. The July announcement changes the second variable. Free-and-eternal is now legacy-or-per-seat - and every project team inherits a question with a due date: what, exactly, is our corridor viewing strategy?
The real exposure isn't the app. It's the workflow.
Here's the uncomfortable part: for many teams, Google Earth Pro isn't just a viewer. It's the de facto system of record. The “current” version of the corridor lives in whoever's inbox received the newest KMZ. Ownership is unclear, versions proliferate, and the data that drives million-dollar field decisions travels as email attachments with no record of who changed what, when.
That workflow was fragile before Google touched anything. The sunset just puts a spotlight on it. Whether teams migrate to Google's web plans, to another desktop globe, or to nothing at all, the KMZ-over-email pattern fails the basic tests a regulated, capital-intensive industry should apply to its project data: Is there one authoritative version? Can we control who sees what? Can we trace an export back to its source? On most corridors today, the honest answer to all three is no.
A 12-month response plan
The good news is that the timeline is generous if you use it. A reasonable sequence looks like this:
- Inventory (now). Take stock of who actually uses Earth Pro on your projects, what data moves through it, and which workflows would degrade first if the desktop app or its backend services faltered.
- Stabilize (next quarter). Archive installers for machines that will need them, back up My Places files and shared KMZ libraries, and write down export standards - for most organizations, for the first time.
- Decide (this year). Determine where the authoritative version of your corridor data should live - and accept that the answer cannot be “a folder of KMZ files.” Tracts, centerline, construction progress, and inspection records need a governed home with role-based access.
- Migrate (before June 2027). Move the workflow, not just the files. Keep KMZ as what it always should have been - a convenience export from an authoritative source - and retire the processes where an emailed attachment is the record.
Where purpose-built platforms come in
This is, transparently, the problem Steel Shire was built for. Arpium exists to be the live common operating picture that teams were approximating with Google Earth - every tract, crew, hazard, and status update layered on one real-time map, with the rest of the ecosystem governing ROW, construction, material, and inspection data at the source. More than 15,000 miles of linear infrastructure already run this way. And yes: you can still export a KMZ any time you like. It just stops being your database.
One more difference worth noting, since pricing is suddenly part of this conversation: Google's professional path forward charges per user. We never have - Steel Shire is priced per mile, with unlimited users and contractor logins on every tier, because rationing access to project data is precisely how the KMZ problem started. But that's a big enough topic to deserve its own post. It's next in this series.
If the announcement has your team asking what a governed corridor looks like in practice, that's a 30-minute conversation. Book a demo and we'll walk your project through it.
