Google Cloud Free Tier 2026 — $300 Credit for 90 Days + Always Free e2-micro

The Three Free Programs — And Why They Confuse Everyone

Google runs three separate free programs simultaneously. This is the root cause of every billing confusion and surprise charge on the platform. Understanding the distinction between these three programs is more important than understanding any individual GCP service.

The interaction that confuses people: your e2-micro VM is always free. But the moment you attach a static IP to it, or upgrade its disk to SSD, or send more than 1GB of egress in a month, those charges get billed to your $300 trial credit. After the trial ends, those charges hit your credit card. The VM itself is free. Everything around it might not be. This is why people who think “I set up a free VM” end up with $20–50 bills — not from the VM, but from the accessories.

$300 Trial Credit — What It Actually Covers

$300 across 90 days works out to $3.33/day of spending capacity. That is enough to run serious hardware for the entire trial. The credit applies to every GCP service without restriction.

One important distinction from Azure: GCP does not automatically charge your credit card when the trial ends. If you do nothing, your trial simply expires and all non-Always-Free resources stop. You must explicitly upgrade to a paid account to continue using services. This is significantly safer than Azure’s model, where the Spending Limit must be manually enabled to prevent automatic charges.

The credit covers genuinely expensive experiments. You could run an n2-standard-4 (4 vCPU / 16GB RAM, ~$138/mo) for 65 days within the 90-day window. Or spin up a Cloud SQL instance alongside a Compute Engine VM for a realistic production environment. Or test BigQuery analytics on large datasets. The $300 is real money for real evaluation — not a token gesture like Lightsail’s $15 value.

Always Free Tier — The Precise Limits That Matter

After your 90-day trial expires, these resources remain free permanently. But “free” has very specific boundaries. I am listing exact numbers because the difference between “free” and “charged” is often a single gigabyte or request threshold.

What is NOT free (and catches people off guard):

• Static IP addresses: $0.01/hr when not attached to a running VM. That is $7.20/month for an idle IP. Delete your VM but keep the IP? You are paying $7.20/mo for nothing.
• SSD persistent disks: $0.17/GB/month. The always-free tier only covers standard HDD. A 30GB SSD costs $5.10/mo.
• Load balancer forwarding rules: $0.025/hr per rule. A single rule costs $18/month.
• Egress to public internet beyond 1GB: $0.12/GB. A site serving 10GB/month in images and downloads adds $1.08/mo.
• GPU and TPU instances: Not available during the trial at all, and never free-tier eligible.
• Windows Server VMs: License surcharge applies to all instances, never free.

How to Claim Your $300 Credit (And Set Up Protection First)

GCP’s onboarding is not a 2-minute experience like Vultr or DigitalOcean. Plan 15–20 minutes for the full setup including billing protection. The billing alert setup needs to happen before you launch a single resource.

1. Visit cloud.google.com/free and click “Get started for free.” You need a Google account. Business email addresses work if they are Google Workspace accounts.
2. Add a payment method. Credit card required. GCP places a $1 authorization hold, released within 3–5 business days. Unlike Azure, GCP will not charge this card after the trial unless you explicitly upgrade to paid.
3. Verify your $300 credit. Go to Billing → Overview. Confirm $300.00 in trial credit with a 90-day expiration date.
4. Create a $1 budget alert. This is the most important step. Billing → Budgets & Alerts → Create Budget. Set the amount to $1. Enable all notification thresholds (50%, 90%, 100%). This catches ANY charge immediately, including charges against your trial credit. It is your early warning system.
5. Enable the Compute Engine API. APIs & Services → Library → Compute Engine API → Enable. Without this, you cannot create VMs. GCP requires explicit API enablement for most services.
6. Create your first VM. Compute Engine → VM Instances → Create Instance. For Always Free: select e2-micro, us-central1 region, standard persistent disk (not SSD), no static IP. For trial-funded testing: any machine type in any region.
7. Bookmark the Always Free page. cloud.google.com/free/docs/free-cloud-features. Reference this before creating any resource to verify whether it will generate charges.

GCP Plans With $300 Credit Applied

This is where the $300 looks great — because you are not thinking about day 91. These are real US-region on-demand rates as of March 2026.

The e2-medium is the pragmatic choice for most evaluations: $26.64/mo means your $300 covers the entire 90-day trial with $220 remaining for Cloud SQL, Cloud Storage experiments, or BigQuery analytics. But remember — after the trial, that same e2-medium costs $26.64/mo indefinitely. Compare that to Hetzner at $4.59/mo for 2 vCPU / 2GB RAM / 20GB NVMe. GCP’s pricing is 5–6x higher for comparable specs. The trial is for evaluating the GCP ecosystem, not for finding cheap permanent hosting.

The Billing Traps — In Order of Frequency

I have read hundreds of GCP billing complaint threads across Reddit, Hacker News, and Stack Overflow. These are the charges that catch people, ranked by how often they appear:

1. Orphaned persistent disks ($0.04–0.17/GB/mo). Deleting a VM in GCP does not automatically delete its persistent disk by default. You must check a box during deletion. A 30GB SSD disk left behind costs $5.10/mo. This is the number one surprise charge on GCP and it has been for years.
2. Idle static IP addresses ($7.20/mo). Reserving a static IP and then stopping or deleting the associated VM means you are paying $0.01/hr for an unused IP. This charge appears constantly in billing complaint threads.
3. Egress beyond 1GB ($0.12/GB). The Always Free tier includes just 1GB of egress. A website serving images, a backup script pushing data off-GCP, or an API with moderate response sizes will exceed this easily. At $0.12/GB, 10GB of monthly egress costs $1.08.
4. Snapshot accumulation ($0.026/GB/mo). Creating snapshots for backup is sensible. Forgetting to delete old snapshots is expensive. A 30GB disk with weekly snapshots held for 3 months: 12 snapshots × 30GB × $0.026 = $9.36/mo. This compounds silently.
5. Load balancer forwarding rules ($18/mo per rule). A single HTTP(S) load balancer with one forwarding rule costs $18/month in fixed charges alone, plus $0.008 per GB of data processed. People add a load balancer for SSL termination without realizing the cost.

The prevention stack that works: $1 budget alert (catches any charge instantly), weekly billing dashboard review, a rule to never create static IPs unless absolutely necessary, and always check “Delete boot disk when instance is deleted” when removing VMs. With these habits, the Always Free tier is genuinely free. Without them, small charges accumulate into real money.

What the e2-micro Can Actually Run

The e2-micro has 2 shared vCPUs and 1GB RAM. “Shared” means Google can throttle your CPU when the physical host is busy. There is no guaranteed baseline like Azure’s B1s (which at least tells you the baseline is 10%). Google’s e2-micro throttling is opaque — you will notice it as variable response times rather than a clear credit-based system.

The e2-micro is best thought of as a permanently free utility server — not a hosting platform. Use it for tasks that benefit from an always-on presence: monitoring, DNS, VPN, webhook receivers, cron-scheduled scripts. For actual application hosting, even basic WordPress, you need to pay. And at GCP’s prices, you are almost always better off paying a dedicated VPS provider under $5/mo than paying for a larger GCP instance.

Alternative VPS Deals

GCP’s $300 trial is the largest by dollar amount, but it carries the most billing complexity. If billing transparency matters to you — and it should — these alternatives deserve serious consideration.

My honest ranking: if you want to learn GCP or evaluate Google-specific services (BigQuery, Cloud Run, Vertex AI, GKE), the $300 trial is unbeatable. If you just want a VPS that works without billing anxiety, AWS Lightsail’s 3-month free tier or DigitalOcean’s $200 trial will cause you far less stress. If you want the cheapest permanent hosting, skip all cloud providers entirely and go with RackNerd at $2.49/mo or Hetzner at $4.59/mo.

Who Should Use This Trial

Frequently Asked Questions

Why is the Google Cloud free tier so confusing?

Because Google runs three separate free programs simultaneously: the $300 trial credit (90 days, any service), the Always Free tier (permanent, specific limits), and free-tier-eligible services that overlap with both. The e2-micro is always free and does NOT consume trial credit. But a static IP attached to that e2-micro IS charged. Google’s documentation spans dozens of pages with footnotes. It is the most generous trial wrapped in the most confusing billing structure.

Is the e2-micro Always Free truly free forever?

Yes, with very specific conditions: only in us-central1, us-east1, or us-west1. One instance per billing account. Non-preemptible only. Includes 30GB standard HDD (not SSD) and 1GB egress/month. Static IPs, load balancers, additional egress, and SSD storage are NOT free. Many people think “free VM” means “everything about this VM is free” — it does not.

How do I prevent unexpected Google Cloud charges?

Create a $1 budget alert in Billing → Budgets & Alerts. Enable email notifications. Never create a static IP unless necessary ($7.20/mo when idle). Always check “Delete boot disk” when deleting VMs. Set a calendar reminder for day 85 of the trial. The most common surprise charge: orphaned persistent disks left after VM deletion.

What is the e2-micro actually capable of running?

With 2 shared vCPUs and 1GB RAM: lightweight static sites (Hugo, Jekyll), a personal VPN (WireGuard), small API endpoints, monitoring agents, and cron scripts. It cannot reliably run WordPress with a database, Docker with multiple containers, or any Java application. Think of it as a utility server, not a hosting platform.

How does the $300 credit interact with Always Free services?

They are tracked separately. The e2-micro usage does NOT count against your $300. You can run the e2-micro alongside trial-funded instances at zero cost. However, anything exceeding Always Free limits (extra egress, static IPs) gets billed to trial credit first, then to your credit card after the trial. This dual-tracking is the source of most confusion.

Google Cloud vs AWS Lightsail for beginners — which is easier?

AWS Lightsail is dramatically easier. Fixed monthly pricing, simple dashboard, 5-minute setup. GCP requires IAM roles, VPC firewall rules, service accounts, and a billing system that takes dedicated study. For first-time cloud users: Lightsail or DigitalOcean. GCP is for people who specifically want to learn GCP or need BigQuery, Cloud Run, or Vertex AI.

Can I use the $300 credit for Cloud SQL?

Yes. The $300 applies to all GCP services: Cloud SQL (MySQL/PostgreSQL/SQL Server), Cloud Spanner, GKE, Cloud Storage, BigQuery, and everything else. Cloud SQL starts at ~$8/mo for db-f1-micro. The $300 covers months of database testing. This is where GCP’s trial genuinely outshines competitors — full-stack evaluation, not just VMs.

What are the most common surprise charges on Google Cloud?

In order: 1) Orphaned persistent disks ($0.04–0.17/GB/mo) left after VM deletion. 2) Idle static IPs ($7.20/mo). 3) Egress beyond 1GB ($0.12/GB). 4) Accumulated snapshots ($0.026/GB/mo). 5) Load balancer rules ($18/mo each). Each is small alone, but they compound. I have seen surprise bills of $50–200 from users who thought they were on the free tier.