Google Cloud Free Tier Explained: What Is Really Free
What you build: a tour of the Always Free products (VM, bucket, BigQuery, Cloud Run, Pub/Sub, Secret Manager) with a real price-list cost check, the bigger-VM trap and a budget alert.

✍️ Translate this blog into Hindi, Tamil or Telugu
"Is it free?" is the first question every beginner asks about Google Cloud, and the honest answer is: some things are always free, within limits, in certain places. In this lab you use the main Always Free products for real (a VM, a storage bucket, BigQuery, Cloud Run, Pub/Sub and Secret Manager), check what each would cost without the free tier using Google's own price list, fall into the classic trap (a slightly bigger VM that is not free), and set the safety net every account should have: a budget alert.
Who it is for: students and beginners who want to practise on Google Cloud without surprise bills. Time: about 45 minutes. Cost: free, apart from about 30 seconds of a small e2-small VM in the trap step (a fraction of a cent). We delete everything at the end.
Every command below was run for real by the CareerByteCode Team on a fresh Google Cloud project, and every output and screenshot is the real result we got. Prices are the list prices in US dollars that Google's price list returned on the day we ran the lab; they change from time to time.
🧪⭐ Recommended by CareerByteCode · ByteLabs project bundleCloud and DevOps Realtime Starterโน499Build the projects →Part A: the three kinds of "free"

- Free trial credit: new accounts get a credit (USD 300 at the time of writing) for 90 days to try almost anything. When it runs out or expires, paid use stops unless you upgrade.
- Always Free: a fixed amount of some products every month, forever, even after the trial, as long as you stay inside the limits. This is what this lab is about.
- Free because it is tiny: many services charge per use, and a few calls cost less than a cent. That is not "free", but it is small.
The Always Free amounts we use in this lab (check the official Free cloud features page for the current list):
| Product | Always Free each month | The catch |
|---|---|---|
| Compute Engine | 1 e2-micro VM, 30 GB standard disk | Only in us-east1, us-west1 or us-central1; one VM per account |
| Cloud Storage | 5 GB in a regional bucket | Only US regions, Standard class |
| BigQuery | 1 TB of queries, 10 GB of storage | Bytes scanned count, not rows returned |
| Cloud Run | 2 million requests (plus CPU and memory time) | Per billing account |
| Pub/Sub | 10 GB of messages | |
| Secret Manager | 6 active secret versions, 10,000 access calls |
Real-life example: a gym with a free daily pass for the treadmill. The treadmill is free; the sauna next to it is not, and a sign on the door does not stop you from walking in.
The free amounts are applied to your bill automatically: you do not switch anything on, and nothing stops you from going past them. That is why the budget alert matters.
Before you start
- A Google Cloud account with billing set up (the free trial works) and a project.
- Open Cloud Shell (the
>_icon at the top right of the Google Cloud console) and set your project. Every command in this lab runs in Cloud Shell.
export PROJECT_ID="your-project-id"
gcloud config set project $PROJECT_IDPart B: the lab
Step 1: turn on the APIs
Why: each product has an API that must be enabled in the project. cloudbilling is for the price list in Step 3.
gcloud services enable compute.googleapis.com run.googleapis.com pubsub.googleapis.com secretmanager.googleapis.com bigquery.googleapis.com storage.googleapis.com cloudbilling.googleapis.com
gcloud services list --enabled --format="value(config.name)" | grep -E "^(compute|run|pubsub|secretmanager|bigquery|storage|cloudbilling)\." | sortOperation "operations/acat.p2-PROJECT_NUMBER-f914f54c-12ee-4780-ad4c-29f4e1fb5b15" finished successfully.
bigquery.googleapis.com
cloudbilling.googleapis.com
compute.googleapis.com
pubsub.googleapis.com
run.googleapis.com
secretmanager.googleapis.com
storage.googleapis.comStep 2: the free VM, set up exactly right
Why: the free VM must be an e2-micro, in one of the three US regions, with at most 30 GB of standard persistent disk (pd-standard). We make the disk 30 GB (the most you get free) and give the VM no Google Cloud permissions. You do not SSH into this VM in this lab: this box and every box after it run in Cloud Shell.
gcloud compute instances create free-vm --zone=us-east1-b --machine-type=e2-micro \
--image-family=debian-12 --image-project=debian-cloud --boot-disk-size=30GB --boot-disk-type=pd-standard \
--no-service-account --no-scopes 2>&1 | grep -v "^WARNING\|disk size" | tail -2
gcloud compute instances describe free-vm --zone=us-east1-b --format="value(machineType.basename(),zone.basename())"
gcloud compute disks describe free-vm --zone=us-east1-b --format="value(sizeGb,type.basename())"NAME ZONE MACHINE_TYPE PREEMPTIBLE INTERNAL_IP EXTERNAL_IP STATUS
free-vm us-east1-b e2-micro 10.142.0.26 EXTERNAL_IP RUNNING
e2-micro us-east1-b
30 pd-standardStep 3: what would this VM cost without the free tier?
Why: a real cost check, with Google's own Cloud Billing Catalog (the price list API). The script reads the list of Compute Engine prices (over 33,000 lines called SKUs), finds the E2 CPU and memory prices for two regions and the standard disk price, and works out a month (730 hours). An e2-micro counts as a quarter of a vCPU plus 1 GB of memory.
python3 - <<PY
import json, subprocess, urllib.request
tok = subprocess.run("gcloud auth print-access-token", shell=True, capture_output=True, text=True).stdout.strip()
url = "https://cloudbilling.googleapis.com/v1/services/6F81-5844-456A/skus?currencyCode=USD&pageSize=5000"
items, page = [], ""
while True:
r = json.load(urllib.request.urlopen(urllib.request.Request(url + ("&pageToken=" + page if page else ""), headers={"Authorization": "Bearer " + tok})))
items += r.get("skus", []); page = r.get("nextPageToken", "")
if not page: break
def price(words, region):
for s in items:
d = s["description"]
if d.startswith(words[0]) and all(w in d for w in words) and region in s.get("serviceRegions", []) and s["category"]["usageType"] == "OnDemand":
u = s["pricingInfo"][0]["pricingExpression"]["tieredRates"][-1]["unitPrice"]
return d, int(u.get("units", 0)) + u.get("nanos", 0) / 1e9
for region in ["us-east1", "europe-west2"]:
dc, c = price(["E2 Instance Core running in"], region); dr, m = price(["E2 Instance Ram running in"], region)
vm = 730 * (0.25 * c + 1 * m) # e2-micro = 2 shared vCPUs that together count as 0.25 vCPU, and 1 GB RAM
print(f"{region:13} core {c:.6f}/h ram {m:.6f}/GB-h -> e2-micro about USD {vm:.2f} a month")
dd, p = price(["Storage PD Capacity"], "us-east1")
print(f"us-east1 standard disk {p:.3f}/GB-month -> 30 GB about USD {30*p:.2f} a month")
print("SKUs read from the price list:", len(items))
PYus-east1 core 0.021812/h ram 0.002924/GB-h -> e2-micro about USD 6.11 a month
europe-west2 core 0.028104/h ram 0.003766/GB-h -> e2-micro about USD 7.88 a month
us-east1 standard disk 0.040/GB-month -> 30 GB about USD 1.20 a month
SKUs read from the price list: 33659
The same VM would cost about USD 6.11 a month in us-east1 and USD 7.88 in europe-west2, plus about USD 1.20 for the 30 GB disk. In us-east1 all of that is covered by Always Free. In europe-west2 none of it is: the region decides.
Step 4: a free Cloud Storage bucket
Why: 5 GB a month is free in a regional bucket in a US region with the Standard class. A multi-region bucket (US) or another region is not free.
BUCKET=free-tier-demo-$RANDOM$RANDOM; echo $BUCKET > bucket.txt
gcloud storage buckets create gs://$BUCKET --location=us-east1 --default-storage-class=STANDARD --uniform-bucket-level-access 2>&1 | tail -1
echo "hello from the free tier" > hello.txt && gcloud storage cp hello.txt gs://$BUCKET/ 2>&1 | tail -1
gcloud storage buckets describe gs://$BUCKET --format="value(location,default_storage_class)"
gcloud storage du -s gs://$BUCKETCreating gs://free-tier-demo-10658104/...
..........
US-EAST1 STANDARD
25 gs://free-tier-demo-10658104US-EAST1 STANDARD is exactly the free combination. Our file is 25 bytes.
Step 5: BigQuery, 1 TB of queries a month
Why: BigQuery charges for the bytes a query scans, not the rows it returns. --dry_run tells you the bytes before you run anything and costs nothing. Here we ask a public dataset for the 3 most common names in Texas.
bq query --use_legacy_sql=false --dry_run "SELECT name, SUM(number) AS total FROM \`bigquery-public-data.usa_names.usa_1910_2013\` WHERE state = \"TX\" GROUP BY name ORDER BY total DESC LIMIT 3" 2>&1 | sed "s/ of data//"
bq query --use_legacy_sql=false --format=pretty "SELECT name, SUM(number) AS total FROM \`bigquery-public-data.usa_names.usa_1910_2013\` WHERE state = \"TX\" GROUP BY name ORDER BY total DESC LIMIT 3"Query successfully validated. Assuming the tables are not modified, running this query will process 110355534 bytes.
+---------+--------+
| name | total |
+---------+--------+
| James | 272793 |
| John | 235139 |
| Michael | 225320 |
+---------+--------+
The query scans 110,355,534 bytes (about 110 MB). The free terabyte would cover about 9,000 queries like this a month. Always dry-run big tables first and select only the columns you need: SELECT * scans every column.
Step 6: Cloud Run, 2 million requests a month
Why: Cloud Run runs a container only while it answers requests and scales to zero when idle, so a small app costs nothing at rest. We deploy Google's sample container. --max-instances=1 caps how far it can scale, a good habit for practice apps.
gcloud run deploy free-hello --image=us-docker.pkg.dev/cloudrun/container/hello --region=us-east1 --allow-unauthenticated --max-instances=1 --quiet 2>&1 | grep -E "Service \[|URL"
URL=$(gcloud run services describe free-hello --region=us-east1 --format="value(status.url)")
curl -s $URL | grep -o "<title>.*</title>"
curl -s -o /dev/null -w "HTTP %{http_code} in %{time_total}s\n" $URLService [free-hello] revision [free-hello-00001-vg6] has been deployed and is serving 100 percent of traffic.
Service URL: https://free-hello-PROJECT_NUMBER.us-east1.run.app
<title>Congratulations | Cloud Run</title>
HTTP 200 in 0.180286sStep 7: Pub/Sub and Secret Manager
Why: both have small free amounts that cover practice: a topic and a message for Pub/Sub, and one secret with one version for Secret Manager (6 active versions are free).
gcloud pubsub topics create free-topic --format="value(name.basename())"
gcloud pubsub topics publish free-topic --message="order 1001 paid" --format="value(messageIds)" | sed "s/[0-9]/N/g"
printf "demo-not-a-real-password" | gcloud secrets create free-secret --data-file=- --replication-policy=automatic --format="value(name.basename())"
gcloud secrets versions list free-secret --format="value(name,state)"Created topic [projects/your-project-id/topics/free-topic].
free-topic
NNNNNNNNNNNNNNNNN
Created version [1] of the secret [free-secret].
free-secret
1 enabled
Break it: the trap, a slightly bigger VM
🎓⭐ Recommended by CareerByteCode · Live trainingCloud & DevOps Live Cohort Internshipโน2,360See the training →The most common surprise bill: someone picks e2-small ("just a bit more memory") or the console's default pd-balanced disk. Neither is in Always Free. We create one, look at both VMs side by side, and delete it at once.
gcloud compute instances create paid-vm --zone=us-east1-b --machine-type=e2-small \
--image-family=debian-12 --image-project=debian-cloud --boot-disk-size=10GB --boot-disk-type=pd-balanced \
--no-service-account --no-scopes 2>&1 | grep -v "^WARNING" | tail -1
gcloud compute instances list --filter="name:(free-vm paid-vm)" --format="table(name,machineType.basename(),zone.basename())"
gcloud compute disks list --filter="name:(free-vm paid-vm)" --format="table(name,sizeGb,type.basename())"
gcloud compute instances delete paid-vm --zone=us-east1-b --quiet 2>&1 | tail -1paid-vm us-east1-b e2-small 10.142.0.27 EXTERNAL_IP RUNNING
NAME MACHINE_TYPE ZONE
free-vm e2-micro us-east1-b
paid-vm e2-small us-east1-b
NAME SIZE_GB TYPE
free-vm 30 pd-standard
paid-vm 10 pd-balanced
Deleted [https://www.googleapis.com/compute/v1/projects/your-project-id/zones/us-east1-b/instances/paid-vm].
Both VMs look the same in the list. Only the machine type and the disk type tell you which one is billed. The console's Create instance page shows an estimated monthly price on the right: check it every time.
Step 8: the safety net, a budget alert
Why: nothing in Google Cloud stops you at the free limit. A budget sends an email at the percentages you choose. It does not stop spending, but it tells you early. In the console: Billing > Budgets & alerts > Create budget, name it Lab budget, with alerts at 50, 90 and 100 percent. Then check it from Cloud Shell. The first line turns on the Budget API, which the check needs (it may print an Operation ... finished successfully line). Our own budget looked like this:
gcloud services enable billingbudgets.googleapis.com
BA=$(gcloud billing accounts list --filter=open=true --format="value(name)" --limit=1)
gcloud billing budgets list --billing-account=$BA --format="table(displayName, thresholdRules[].thresholdPercent.list())" 2>/dev/null | grep -E "DISPLAY|Lab budget"DISPLAY_NAME THRESHOLD_PERCENT
Lab budget 0.5,0.9,1.0Set a small amount for a practice project. The billing admin email gets the alerts.
Clean up (delete everything)
Why: free amounts are per month and per account, and a forgotten bucket or VM keeps counting. Delete everything, then prove it.
gcloud compute instances delete free-vm --zone=us-east1-b --quiet 2>&1 | tail -1
gcloud storage rm -r gs://$(cat bucket.txt) 2>&1 | tail -1
gcloud run services delete free-hello --region=us-east1 --quiet 2>&1 | tail -1
gcloud pubsub topics delete free-topic 2>&1 | tail -1
gcloud secrets delete free-secret --quiet 2>&1 | tail -1
rm -f bucket.txt hello.txt
echo "VMs: $(gcloud compute instances list --format="value(name)" | grep -c -E "free-vm|paid-vm") disks: $(gcloud compute disks list --format="value(name)" | grep -c -E "free-vm|paid-vm") buckets: $(gcloud storage buckets list --format="value(name)" | grep -c free-tier-demo) services: $(gcloud run services list --region=us-east1 --format="value(name)" | wc -l) topics: $(gcloud pubsub topics list --format="value(name)" | wc -l) secrets: $(gcloud secrets list --format="value(name)" | wc -l)"Deleted [https://www.googleapis.com/compute/v1/projects/your-project-id/zones/us-east1-b/instances/free-vm].
..........
Deleted service [free-hello].
Deleted topic [projects/your-project-id/topics/free-topic].
Deleted secret [free-secret].
VMs: 0 disks: 0 buckets: 0 services: 0 topics: 0 secrets: 0
POC: prove it works
- An
e2-microwith a 30 GBpd-standarddisk inus-east1: the exact free setup. - The price list showed the same VM would cost about USD 6.11 a month in
us-east1without the free tier, and that ineurope-west2it is not free at all. - A regional Standard bucket in
us-east1, a BigQuery query dry-run at 110 MB, a Cloud Run service answering HTTP 200, a Pub/Sub message and a secret: all inside the free amounts. - An
e2-smallwithpd-balancedsat next to the free VM to show the trap, and was deleted. - A budget with 50, 90 and 100 percent alerts watches the project, and the clean-up left 0 resources.
Quiz task: check what you learned
- You create an
e2-microinasia-south1(Mumbai). Is it free? (Answer: no. Onlyus-east1,us-west1andus-central1.) - Your free VM has a 50 GB disk. What do you pay for? (Answer: the 20 GB above the free 30 GB of standard disk.)
- How do you know what a BigQuery query will scan before you run it? (Answer:
bq query --dry_run, or the estimate in the console query editor.) - Does a budget stop your spending at 100 percent? (Answer: no, it only alerts. You must act, or automate a stop yourself.)
- Which bucket is free:
USmulti-region orus-east1regional, Standard class? (Answer:us-east1regional, Standard.)
FAQ
Will I be charged when the free trial ends? Not automatically. After the trial, paid use stops until you upgrade to a paid account. Always Free continues in both cases.
Is the external IP address free? Google Cloud prices public IPv4 addresses separately, so check the current Free cloud features page for what is covered for the free VM. Two habits keep you safe: release any reserved static IP you do not use (an idle reserved IP is always charged), and if you only need SSH, create the VM with --no-address and connect with gcloud compute ssh --tunnel-through-iap.
Why did the price check say USD and my bill says rupees? We asked the price list for USD to compare regions. Your bill uses your billing account's currency, converted by Google.
Can I run two free VMs? The free amount is one e2-micro per billing account per month (730 hours). Two running all month means you pay for one of them.
What about GPUs and big AI models? They are never in Always Free and can be expensive. Use small CPU models first, and always set a budget.
Where do I see what I actually used? Billing > Reports shows cost by service and SKU, including the free-tier credits that brought it to zero. Data appears with a delay of up to a day.
Troubleshooting
| You see | Why | Fix |
|---|---|---|
| A charge for Compute Engine | Wrong region, a bigger machine, pd-balanced disk, or a second VM | Check machineType, zone and disk type; keep one e2-micro |
| A charge for Cloud Storage | A multi-region or non-US bucket, or Nearline/Coldline | Use a regional US bucket, Standard class |
| BigQuery query is bigger than expected | SELECT * or no partition filter | Dry-run, select only needed columns |
HTTP Error 429: Too Many Requests from the price list | Too many calls in a short time | Wait a minute and run it again (we hit this once) |
| No budget emails arrive | Alerts go to billing admins and users | Check the budget's notification settings and your spam folder |
billing account ... not open | The trial ended or billing was closed | Upgrade or re-open billing in Billing |
What next
- Your very first steps with projects and billing: Google Cloud for Absolute Beginners: Projects, Billing and Console.
- Read and cut a real bill: FinOps for Beginners: Read and Cut Your Cloud Bill.
- Use your free VM well: Linux for Cloud Beginners: 50 Commands on a Free VM.
- Use your free terabyte: BigQuery for Beginners: Query Billions of Rows for Free.
- More hands-on posts: ByteBlog. Practice in ByteLabs and see the courses.
Prepared by the CareerByteCode Team from our tested lab, with AI help for the write-up.
⭐ Keep learning with CareerByteCode
Hand-picked to go deeper on this topicGet CareerByteCode Team's next blog by email
One email a week when they publish. Add the weekly Best of ByteBlog too. No spam, unsubscribe with one click.
We email you once to confirm. By subscribing you agree to the privacy policy.
Related blogs
CareerByteCode TeamLinux for Cloud Beginners: 50 Commands on a Free VM
What you build: a free e2-micro Linux VM where you practise 50 everyday commands for files, text, permissions, processes, network and packages, in your own Google Cloud account. Every step tested.
#beginners
CareerByteCode TeamLinux Users, Groups and sudo Explained
What you build: a shared Linux server for 3 people on a free VM: users, a developers group, a sudo rule that allows one job only, visudo catching a typo, the sudo log, and an account locked and remove
#beginners
CareerByteCode TeamLinux File Permissions Explained with Real Mistakes
What you build: a script, a team folder, an SSH key and a config file that break with Permission denied, then work with the right chmod, chown and group, on a free VM.
#beginners
CareerByteCode TeamLinux Networking Commands Every Cloud Engineer Needs
What you build: ip, ss, dig, curl, tcpdump and nc on real traffic on a free VM, plus three real breaks: a wrong listen address, a VPC firewall and a bad /etc/hosts line.
💬 Comments (0)
Top · NewestSign in to comment