How to Create a FREE Google Cloud Account with $300 Credit - Step by Step Sign-Up, What the 90-Day Trial Really Covers, the Always Free Tier Limits, Budget Alerts and How to Avoid Any Charges (Google Cloud Part-1)

Every cloud journey starts with the same boring but important step - getting an account without getting a bill. In this Part-1 of my Google Cloud series we are going to create a Google Cloud account from scratch, claim the $300 welcome credit, and - this is the part most tutorials skip - understand exactly what the Free Trial covers, what the Always Free tier covers, and where the two differ, so that you can run the labs from the rest of this series without ever paying a cent.

I am writing this against the current Google Cloud free program documentation, because the terms have changed a few times over the years (the trial used to be 12 months, then 90 days, and the Free Tier product list keeps moving). Where a number comes from the docs I link to the page, so that you can verify it yourself.

Table of Content

1. Free Trial vs Free Tier - two different things
2. What you need before you start
3. Step 1 - Start the Free Trial sign-up
4. Step 2 - Account information and terms
5. Step 3 - Payment verification and the $0 to $1 hold
6. Step 4 - Your first project and billing account
7. What the Free Trial blocks
8. How to check your remaining credit and days
9. Set a budget alert on day one
10. The Always Free tier - monthly limits that never expire
11. What happens on day 90 - auto-close, grace period, deletion
12. Your first lab - a free e2-micro VM
13. Seven rules so that you never see a charge
14. Conclusion

1. Free Trial vs Free Tier - two different things

This is the first thing I want you to get right, because the two programs are constantly mixed up -

So during the 90 days you effectively get both - the Free Tier usage is not even counted against the $300. After day 90 only the Free Tier remains, and only if you have upgraded to a paid account (more on that in section 11).

2. What you need before you start

1. A Google account - a personal Gmail works. If you run Google Workspace for your company you can use that account too, but for learning I prefer a personal one so that the billing account is unambiguously yours.
2. A credit or debit card that is valid for the whole 90 days. Google uses it only for identity verification - nothing is charged during the trial. Prepaid and virtual cards are frequently rejected, so use a real one.
3. In some countries Google asks for bank account verification as well. The Free Tier docs call this out - it depends on your country.
4. Your address - it must match the country of the card.
5. Ten minutes.

One more thing - the eligibility check is per Google account and per person. If you had a Free Trial years ago on the same Gmail, you will not get a second one. Google does not publish a list of countries, so if the sign-up page tells you the trial is not available where you are, that is the only reliable answer.

3. Step 1 - Start the Free Trial sign-up

1. Go to cloud.google.com/free and click Get started for free. It takes you to console.cloud.google.com/freetrial.
2. Sign in with the Google account you want to own the cloud account.
3. You land on a two-step wizard - Account information and Payment information verification.

If instead of the wizard you land straight in the console, your account already has a Google Cloud presence (maybe from Firebase or Maps). Look for the blue Activate or Start free trial button at the top of the console - it opens the same wizard.

4. Step 2 - Account information and terms

On the first step you fill in -

1. Country - this decides the currency, the tax treatment and which payment methods are accepted. It cannot be changed later for this billing account.
2. What best describes your organisation or needs - pick anything, it only steers the console's onboarding tips.
3. Terms of Service - tick the Google Cloud Platform Free Trial Terms. The Free Trial Terms are the document that lists the restrictions I cover in section 7, so have a quick look.
4. Optionally the email-updates box - leave it unticked, you will get the important billing mails anyway.

Click Continue.

5. Step 3 - Payment verification and the $0 to $1 hold

The second step is the one that scares people, so let's be very precise about what happens -

1. Account type - Individual or Business. For learning choose Individual. Business asks for a tax ID in many countries and makes you the legal entity's representative; you do not need that for labs.
2. Name and address - must match the card's billing address.
3. Payment method - the card. Google puts a temporary authorisation hold between $0.00 and $1.00 (or the local equivalent) on it to confirm it is real. This is a hold, not a charge - it shows as pending and is released by your bank in a few days, sometimes up to a month. You will see it in your banking app; it is normal.
4. Click Start free.

The Free Tier documentation is explicit on the key promise - you are not billed during the Free Trial. Billing starts only when you manually upgrade to a paid billing account. There is no auto-upgrade on day 90.

6. Step 4 - Your first project and billing account

Once the wizard finishes, Google creates two things for you -

1. A project called My First Project (ID like my-first-project-123456). Every resource in Google Cloud lives inside a project - this is Google's equivalent of an AWS account boundary inside your account. You can rename it or create a new one; for this series I create a project per topic.
2. A billing account called My Billing Account, with the $300 credit attached. A billing account can pay for many projects, and a project is linked to exactly one billing account.

Check both - in the console open the project picker (top left), and go to Billing from the hamburger menu. If Billing shows This project has no billing account, link it to My Billing Account - otherwise you cannot create VMs.

I also recommend doing two housekeeping things right now - set your time zone and language under the settings cog, and go to IAM & Admin → Settings to note your project number, you will need it when you start using gcloud.

7. What the Free Trial blocks

The trial is generous but deliberately fenced. From the current free program docs, during the trial you cannot -

1. attach GPUs to VM instances,
2. create Windows Server VMs (licence cost),
3. request quota increases,
4. use Google Cloud Marketplace,
5. create Google Cloud VMware Engine resources,
6. use the $300 for the Gemini API in AI Studio or for partner generative-AI models offered as managed APIs (first-party Vertex AI usage is fine),
7. mine cryptocurrency - the Free Trial Terms forbid it and Google does enforce it.

The trial also cannot be paused or extended. The 90 days are calendar days from sign-up, whether you log in or not. If you are in the middle of a course and you want to avoid losing the credit, sign up when you are actually ready to start.

Quotas are the practical limit you will hit first. A fresh trial project has a small CPU quota per region (historically around 8 vCPUs in a region, but Google adjusts it per account and does not publish a fixed number), so do not plan a big Kubernetes lab on day one. Check IAM & Admin → Quotas before a large deployment.

8. How to check your remaining credit and days

1. Hamburger menu → Billing.
2. If you have several billing accounts, pick My Billing Account.
3. On the Overview page there is a Free credit (or Free Trial credit) pane - it shows the remaining credit and the remaining days.
4. For the detail, open Reports on the left - the chart shows daily cost, and the Credits filter shows how much of each day was covered by the trial credit.

A quick mental model - the credits report shows what you would have paid. If the chart says $2.40 per day, you are burning the credit at $72 per month, which is well inside the $300 for 90 days. If you see $10 per day, something is running that should not be (usually a GPU-less but large VM, a GKE cluster, or a Cloud SQL instance left on overnight).

9. Set a budget alert on day one

A budget does not stop spending - Google is explicit about that - but it emails you when you cross thresholds, and that is enough to catch a forgotten VM. From the Cloud Billing budgets docs -

1. Billing → Budgets & alerts → Create budget.
2. Scope - all projects on the billing account, all services. Give it a name like free-trial-guard.
3. Amount - Specified amount, $300, and tick Include credits in cost - this is important, otherwise the budget tracks the net (zero) cost and never fires during the trial.
4. Thresholds - 50%, 75%, 90% and 100% of actual spend. Tick Email alerts to billing admins and users.
5. (Optional) connect a Pub/Sub topic to the budget - that is how you would trigger a Cloud Function to disable billing automatically when a cap is hit. The docs have an example; I show it in a later part of this series.

Also set a second, small budget - say $10 per month, without credits included - that one stays useful after the trial, when real money is involved.

10. The Always Free tier - monthly limits that never expire

The Always Free usage is per billing account, resets monthly and does not roll over. The list changes, so treat the official page as the source of truth; at the time of writing the ones you will actually use in this series are -

There are also time-boxed product trials on top - Spanner (90 days, 10 GB), AlloyDB, Looker and Cloud SQL (30 days each) - and separate free offers for Google Maps Platform, Google AI Studio and Firebase.

Two gotchas with the free VM - the limit is one e2-micro's worth of hours, so two e2-micros in the same month means one of them is billed for its hours. And the external IP of the VM is covered only while attached to a running free VM; a reserved static IP that is not in use costs money.

11. What happens on day 90 - auto-close, grace period, deletion

This is the part that makes the Free Trial safe -

1. The trial ends when 90 days pass or the $300 is spent, whichever comes first.
2. If you have not upgraded, the trial auto-closes - billing is disabled, every resource is stopped and you lose access to them. Nothing is charged.
3. You then get a 30-day grace period. If you upgrade during these 30 days you can recover the stopped resources. If you do not, the trial resources are permanently deleted.
4. If you did upgrade before day 90, any unused credit stays available until the original 90 days run out, and after that you pay for whatever exceeds the Always Free tier.

So the only way to get a real bill is to click Upgrade yourself (or Activate on the blue banner the console keeps showing). The banner is designed to be clicked - do not, until you have read section 13.

12. Your first lab - a free e2-micro VM

Let's prove the account works and that the Free Tier is real -

1. Hamburger menu → Compute Engine → VM instances. The first visit asks you to enable the Compute Engine API - click Enable and wait a minute.
2. Create instance.
3. Name lab-vm-1, Region us-central1 (one of the three Free Tier regions), any zone.
4. Machine configuration - series E2, machine type e2-micro (2 shared vCPUs, 1 GB). The right-hand cost estimate drops to a line saying the instance is covered by the Free Tier for the first 744 hours per month.
5. Boot disk - Debian or Ubuntu, standard persistent disk, 10 GB (keep the total under 30 GB across the month to stay free; the default balanced disk is not in the free allowance, so change it).
6. Firewall - tick Allow HTTP traffic only if you plan to serve something. Leave SSH to the console's browser SSH button, which uses IAP and needs no public port.
7. Create, then click SSH next to the instance. Run uname -a and curl -s ifconfig.me to see the external IP.

When you are done: stop the VM if you will reuse it (a stopped VM still pays for its disk, but the 30 GB standard disk is inside the free allowance), or delete it. Deleting the whole project (IAM & Admin → Settings → Shut down) is the nuclear option that guarantees nothing lingers.

The Compute Engine quickstart walks through the same steps with screenshots if you want a second reference.

13. Seven rules so that you never see a charge

1. Do not upgrade until you need something the trial blocks. The console will nag you with an Activate full account banner; ignore it.
2. Budget with credits included at $300 (section 9) and a second small budget without credits for after the trial.
3. Stop or delete every lab resource when you finish. VMs, GKE clusters, Cloud SQL instances and load balancers are billed by the hour whether you use them or not.
4. Stay in the Free Tier regions for the e2-micro and the 5 GB bucket - us-west1, us-central1, us-east1.
5. Release static IPs you reserve and do not attach - they cost money the moment they are idle.
6. One project per lab, and shut the project down at the end. It is the cleanest way to be sure nothing survives.
7. Check the Billing report once a week during the trial. If the daily cost jumps, find out why the same day.

More videos on this topic - the next two parts of my Google Cloud series - a complete beginner tour of the Cloud Console, and how to create a Google Cloud project -

14. Conclusion

You now have a Google Cloud account with the $300 welcome credit, you know that the credit lasts 90 days or $300, that the card is only a verification hold, that nothing is charged unless you upgrade, and that the Always Free tier gives you an e2-micro, 5 GB of storage, a terabyte of BigQuery and 2 million Cloud Run requests every month even after the trial. You also have a budget alert in place and your first VM running.

In the next parts of this series we move into the networking that the rest of my cloud content depends on - start with Google Cloud VPC Peering, then Shared VPC, Private Service Connect and the organisation setup with Cloud Identity. If you are comparing clouds, the AWS equivalent of this post is Part-1 of my AWS series on IAM users, and for Azure start with the Azure virtual network post.