Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Google Cloud can surface low-usage resources and projects that deserve investigation, but its recommendations do not prove that nobody depends on them. Start with Cloud Billing Reports to find where spending is concentrated, use FinOps Hub’s Utilization insights to identify supported resource-level candidates, then verify each workload’s owner and purpose before changing or deleting anything.
What “unused” means in Google Cloud
Google Cloud’s tools identify signals such as low activity, idle resources, or configurations that may be larger or more expensive than a workload needs. They do not establish that a resource is safe to remove: it could support failover, recovery, seasonal demand, development, or a scheduled job. Treat “potentially wasted usage” as a product label for an investigation lead, not a verdict.
Keep five distinctions in view as you investigate: resource-level versus project-level scope; billed cost versus estimated possible savings; which services are covered; the period measured; and the permissions that shape what you can see.
Find where Google Cloud spending is concentrated
Cloud Billing Reports provide the broad cost context. In the Google Cloud console, open Billing > Reports, select a useful date range, and group costs by project, service, SKU, or location. Reports can also show trends over time and forecasts based on historical trends. Google documents historical usage and cost data back to January 2017; data filtered by billing period goes back to January 2019.
#1 Best Overall
Use the report to answer practical questions such as which project or service cost the most last month, and how daily service costs compare over time. What appears depends on access: a user may see a single project, authorized projects, or the projects linked to a billing account. For billing-account-wide reports, Google lists Billing Account Viewer, Billing Account Costs Manager, and Billing Account Administrator among the documented roles. Project cost views require billing cost-view access on the project; a multi-project view also depends on the relevant project and billing-account permissions.
Inspect resource candidates in Utilization insights
In the console, open FinOps Hub and review the Utilization insights view. It can be examined by service or by App Hub application. Service coverage is specific rather than universal: the documented services and signals include the following.
Rank #2
| Service or view | Documented insight categories |
|---|---|
| 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 configuration recommendation related to CPU allocation |
| App Hub applications | Application-level cost and recommendation context; coverage can be partial when an application spans billing accounts |
These insights use service-specific utilization metrics and activity, so do not assume that every resource type is scanned or that every candidate has a recommendation. Google says the dashboard refreshes daily, shows up to 1,000 resources in its recommendations table ordered by last-30-day cost, and may omit insights when no optimization recommendation is available. In service view, it handles one service at a time and supports granular filtering across up to ten projects. The dashboard is scoped to one billing account at a time; an App Hub application spanning multiple billing accounts may therefore appear only partially.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Understand the two cost figures
“Estimated cost of wasted usage” is the estimated cost over the previous 30 days for resources that have utilization metrics. It is a retrospective cost measure for the covered resources, not a forecast of what you will save by acting. “Potential savings” is a separate estimate of what might be saved if recommendations are applied. The two figures are not interchangeable.
Rank #3
Check for unattended projects
For projects assigned to a Google Cloud organization, review the unattended project recommender. It analyzes project activity over the prior 30 days and can recommend reviewing or deleting projects it identifies as low-usage. Its signals can include networking, API activity, project owner, and service activity. This is a project-level lead, not proof that the project is dispensable; the recommender is not available for projects outside Google Cloud organizations.
Interpret potential savings as estimates, not invoice reductions
Google describes recommendation savings as estimated amounts if the proposed action is taken. Depending on the contract and the user’s permissions, an estimate may use list prices or custom contract pricing based on historical costs. Google’s cost recommendation methodology says estimates are based on past usage and do not account for credits or additional discounts. FinOps Hub also cautions that estimates do not account for existing committed use discounts (CUDs) that might apply to a resource. Some dashboard totals deduplicate overlapping opportunities by presenting the higher-savings recommendation.
Rank #4
Consequently, a displayed amount is useful for ranking opportunities, not a promise that the same amount will disappear from the bill. Workload changes, contract terms, discounts, credits, and the recommendation’s assumptions all affect the outcome. For custom-contract estimates, Google documents billing.resourceCosts.get for project-scoped recommendations and billing.accounts.getSpendingInformation for billing-account-scoped recommendations.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate candidates before changing or deleting them
Use recommendations to decide what to investigate first, then make an operational decision with the people responsible for the workload. Google’s cost optimization guidance emphasizes workload requirements and load patterns; a low recent-usage signal alone cannot reveal every dependency or business need.
Quick Recap
Best Value
- Identify the owner and purpose. Check project ownership, service activity, deployment records, and the team responsible for the application. Ask whether the resource supports production, recovery, failover, development, seasonal work, or a scheduled task.
- Check dependencies and timing. Find out what calls, stores data in, or relies on the resource, and whether a quiet period is expected to end. Confirm the effect on reliability, compliance, and recovery plans.
- Validate the cost basis. Compare the recommendation with billing reports and establish whether the estimate uses list or custom pricing. Account for credits, discounts, and applicable CUDs rather than treating potential savings as a guaranteed bill reduction.
- Choose the least risky action that answers the question. Where suitable, try a reversible pause or right-sizing change and monitor the workload before deletion. Preserve required data and backups; delete only after the owner confirms that the resource and its dependencies are no longer needed.
What these tools can—and cannot—tell you
- They can: show billing trends and cost groupings, surface utilization signals for documented services, and flag low-activity organization projects for review.
- They cannot: prove that nobody uses a resource, inventory every possible source of waste, or guarantee that applying a recommendation will reduce an invoice by the displayed estimate.
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.

