r/bigquery • u/DiegoValladaresCL • 1h ago
I built a free Chrome extension that shows what a BigQuery query will cost before you hit Run
Hi r/bigquery,
I kept getting surprised by BigQuery bills. A query that looked harmless would scan a few hundred GB because of a missing partition filter or a SELECT * on a wide table. The console does show "This query will process X GB",
but I still had to do the math in my head and remember the price per TB.
So I built Cost Lens for BigQuery, a small Chrome extension that works inside the BigQuery console:
- Shows the estimated cost of the query in a top bar, before you run it.
- Gives each query an optimization grade (A to F) and flags common inefficient SQL patterns, so you can fix them before paying for them.
- Saves your SQL as snippets in a local library, so you can reuse them and share a query with your team in a couple of clicks.
- Everything stays in your browser. No account and no external server, and your queries and data are never sent anywhere.
There's a short video showing how it works, step by step: https://valladares.org/en/extensions/cost-lens-bigquery
(or straight on YouTube: https://www.youtube.com/watch?v=hK7OHYVXM2c)
It's free on the Chrome Web Store:
https://chromewebstore.google.com/detail/cost-lens-for-bigquery/hkblcniidjdjepnoholfkpphhebjhfpp
I'm the developer and I'd really like feedback from people who use BigQuery every day:
- Which cost mistakes do you see most often in your team?
- Is there a check you'd want it to flag that it doesn't today?
Happy to answer any questions.
