Google Cloud can surface low-usage resources and projects, but its recommendations do not prove that nobody depends on them. Use FinOps Hub to find utilization-based candidates, Cloud Billing Reports to see where spending sits, and ownership and workload checks to decide whether any change is safe. The cost shown for a recommendation is an estimate—not a guaranteed reduction in your bill.
What does “unused” mean in Google Cloud?
There is no single Google Cloud report that certifies a resource is unnecessary. The available tools provide different signals: utilization insights flag service-specific patterns, an unattended-project recommendation identifies projects with little recent activity, and billing reports show charges and trends. A quiet resource may still support failover, recovery, seasonal work, development, or a scheduled job.
As an Amazon Associate I earn from qualifying purchases.
Keep the scope clear as you investigate: resource-level utilization is not the same as project-level activity; billed cost is not the same as modeled savings; and neither view is a complete inventory of every service. Google’s Utilization insights documentation describes the feature as identifying “potentially wasted usage,” a useful signal to investigate rather than a verdict.
Free tools Windows power users keep installed
One-click scans. No signup required.
Find resource-level candidates in FinOps Hub
- In the Google Cloud console, open FinOps Hub and go to Utilization insights. Select the billing account you want to examine.
- Choose a service view to inspect supported resources, or an App Hub application view to see application-level cost and recommendation context.
- Review the category and the resource’s utilization and cost information. Prioritize plausible opportunities with meaningful recent cost, but verify the workload before acting.
- Open the relevant recommendation, if one is available, and read its proposed change and assumptions. Treat the displayed savings as a lead for validation, not a bill reduction promise.
What the insights cover
| Service or view | Documented signals |
|---|---|
| Compute Engine | Idle, overprovisioned, or underprovisioned VMs; idle disks; and certain suboptimal configurations. |
| Google Kubernetes Engine (GKE) | Idle, overprovisioned, or underprovisioned clusters. |
| Cloud SQL | Idle, overprovisioned, or underprovisioned instances. |
| Cloud Run | A recommendation related to CPU allocation configuration. |
| App Hub applications | Application-level cost and recommendation context; the view may be partial if an application spans billing accounts. |
These are documented categories, not a promise that every resource or configuration is evaluated. The service view handles one service at a time; granular filtering supports up to ten projects. The resource recommendations table displays up to 1,000 resources, ordered by last-30-day cost, and some insights may not have an optimization recommendation. The dashboard refreshes daily. Its estimated cost of wasted usage covers the prior 30 days for resources with utilization metrics; it is not the same measure as potential savings from applying recommendations. See Google’s Utilization insights documentation for scope and display details.
#1 Best Overall
Check whether an entire project is unattended
For projects assigned to a Google Cloud organization, review the unattended-project recommendation. It analyzes activity over the prior 30 days and can suggest reviewing or deleting projects with low usage. Insights can include networking, API activity, project owner, and service activity. The recommendation is a project-level lead, not proof that the project is disposable; this recommender is not available for projects outside Google Cloud organizations. Google documents its scope in the unattended project recommender guide.
Before changing a project, identify its owner and ask what it supports. Check dependent services, APIs, networking, scheduled tasks, retained data, and recovery or compliance needs. A low-activity development or seasonal project can still be intentional.
See which projects and services cost the most
Use Cloud Billing Reports to put a candidate in the context of actual charges. In the Google Cloud console, open Billing, select the billing account, then open Reports. Choose a time range and group or filter the report to answer questions such as “Which Google Cloud project cost the most last month?” or “Which Google Cloud service cost me the most?” You can examine trends by project, service, SKU, and location, and compare daily service costs over time. The reports can also show forecasts based on historical trends. Consult Cloud Billing Reports for the available report controls and data history.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe view you can see depends on your permissions. A project-level view requires cost-view access on that project; multi-project and whole-billing-account views require the relevant project and billing-account permissions. Google lists Billing Account Viewer, Billing Account Costs Manager, and Billing Account Administrator among the roles for billing-account reports. Historical usage and cost data in Reports reaches back to January 2017; data filtered by billing period reaches back to January 2019, according to Google’s documentation. That history can help distinguish an ongoing expense from a temporary spike, but it does not establish whether a workload is safe to remove.
Understand what estimated savings do—and do not—mean
Google’s recommendation savings are modeled amounts if the suggested action is taken. Depending on pricing arrangements and access, an estimate may use custom contract pricing or list prices. Google says estimates are based on past usage and do not include credits or additional discounts; FinOps Hub also cautions that estimates do not account for existing committed use discounts (CUDs) that might apply. Some dashboard totals deduplicate overlapping opportunities by showing the recommendation with the higher estimated savings. Read the cost optimization savings methodology and FinOps Hub documentation alongside the recommendation.
For custom-pricing estimates, Google documents the permission billing.resourceCosts.get for project-scoped recommendations and billing.accounts.getSpendingInformation for billing-account-scoped recommendations. Without the required access, the estimate may use list pricing rather than your contract rate. Confirm the pricing basis and account for credits, discounts, CUDs, and any workload changes before treating an estimate as a business case.
Validate a candidate before resizing, stopping, or deleting it
Use recommendations to prioritize investigation, not to automate destructive changes. Google’s architecture guidance says resource decisions should reflect workload requirements and load patterns; see its cost optimization framework. For each candidate:
Recommended Free Tools
- Confirm ownership and purpose: contact the project or service owner and establish whether the resource supports production, testing, recovery, seasonal work, or a scheduled workload.
- Check dependencies and timing: review callers, APIs, network links, monitoring, automation, and workload schedules. A quiet period may be normal for the service.
- Protect data and obligations: verify backups, retention, recovery, and compliance requirements before changing storage or deleting a project.
- Model the real economics: compare the billed cost with the recommendation’s pricing basis and account-specific discounts or credits; assess whether the proposed change alters service capacity or reliability.
- Prefer a reversible test where appropriate: right-size or pause only after owner approval and with a way to restore service. Monitor the workload before considering deletion.
Cloud Billing Reports show where money went; utilization and project recommendations point to what may merit review. The safe decision comes from connecting those signals to the people, dependencies, and requirements behind the workload.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
