Open colab.research.google.com, sign in with a Google account, and roughly 30 seconds later you’re typing Python into a machine that has a GPU attached. No credit card, no trial countdown, no call with a salesperson. That’s the entire pitch behind Google Colab Free, and it explains why so many machine learning tutorials start with the same four words: just run it in Colab.
The limits are real, but they’re written down in a help page most people skim past. Knowing them beforehand is the difference between a smooth afternoon and a runtime that dies at hour two with your fine-tune half finished.
What the Free Tier Actually Gives You
Here’s the hardware you get handed when you request a GPU runtime:
- GPU: usually a Tesla T4 with 16 GB of VRAM. You may occasionally land on a P100 or an older K80, and during busy periods you may get no GPU at all.
- System RAM: around 12.7 GB.
- Disk: roughly 78 GB usable out of about 108 GB, and it gets wiped the moment the session ends.
- Session length: a hard ceiling of 12 hours.
- Idle disconnect: about 90 minutes with the tab open, and much faster if you close it.
Everything else comes included at no cost: the notebook editor, the Drive integration, the free Gemini assistance in the sidebar. Notebooks live in your Google Drive, so the code survives even when the machine doesn’t.
Where Colab Free Quietly Breaks Down
The idle clock runs faster than you expect
Ninety minutes sounds generous until you step away for lunch and come back to a disconnected runtime and a variable table that’s simply gone. The fix is boring but effective: keep the tab focused, and never leave a long job running without something actively writing to disk.
GPU quotas are never published anywhere
Google doesn’t say how many GPU hours you get per day on the free tier, because the number floats with demand. What you’ll see instead is a dialog reading “You cannot currently connect to a GPU due to usage limits.” Wait a few hours and it usually comes back. There’s no support ticket to file, and no way to buy your way back in without upgrading.
Free users also sit behind Pro subscribers in the queue. On a busy weekday afternoon in the US, that can mean waiting, or landing on CPU-only hardware while a 7B model training job stares back at you.
Workloads That Fit Comfortably Inside the Free Tier
Plenty of genuinely useful work finishes well inside 12 hours on 16 GB of VRAM. These are the ones that come up again and again:
- Transcribing a one-hour podcast with Whisper. The large model runs on a T4 in a few minutes.
- Fine-tuning a 7B language model with LoRA or QLoRA at 4-bit precision. A 5,000-example dataset typically converges in two to four hours.
- Batch image generation from Stable Diffusion checkpoints. If you want a gentler on-ramp than a raw diffusers script, the setup guide for Fooocus, the open-source image generator that just works, describes a pipeline that survives a Colab session nicely.
- Exploratory analysis on a CSV up to a few hundred megabytes with pandas and scikit-learn.
- Prototyping against a hosted model API instead of a local one. A free key from Google AI Studio’s Gemini workspace drops straight into a notebook cell and costs nothing for light use.
What these have in common is that they’re bounded. They start, they finish, they save their output. Work that runs for 20 hours, or that wants 40 GB of VRAM, isn’t a Colab Free problem you can optimise your way out of.
Habits That Stretch Every Free Session
None of this is clever. It’s just the stuff that separates a session that finishes from one that restarts from zero.
Mount Drive before anything else
One line at the top of the notebook and your checkpoints and model weights persist between sessions. Re-downloading a 15 GB model because you forgot is a genuinely painful hour.
Checkpoint on a schedule, not at the end
Set the training loop to save every 200 steps or every 20 minutes, whichever comes first. If the runtime dies at hour three, you resume instead of restarting.
Install quietly and pin your versions
Long pip output clogs the browser and eats notebook memory, so add -q to installs. Pin the versions that worked, too. A silently upgraded library is one of the most common reasons a notebook that ran yesterday fails today.
Look at the runtime before you commit to it
Two cells at the start tell you what you’re working with: nvidia-smi for the GPU model and its memory, and a quick torch call for the CUDA version. Discovering you’re on a K80 after 40 minutes of setup is far worse than discovering it in 10 seconds.
Size batches to the hardware you actually have
A batch size that fits in 16 GB with room to spare beats one that triggers an out-of-memory error and a restart. Start small, then step up one notch at a time and watch the memory readout.
When Ten Dollars a Month Beats an Hour of Waiting
Colab Pro costs around $10 a month and changes three things that matter: longer sessions, more system RAM, and access to faster GPUs including the A100 and V100 lines. Background execution means a training run keeps going after you close the laptop.
The decision is arithmetic. If you’re burning two or three sessions a week waiting out quota messages, or restarting long jobs because the 12-hour ceiling hit, the subscription pays for itself in a single afternoon. If you open a notebook twice a month to test an idea, stay on the free tier.
There’s a third option worth knowing about when your goal is inference rather than training: run the model on the machine already in front of you. Quantised models now handle text and images locally, which removes the session clock entirely. The move toward capable multimodal models running on-device is the main reason an ordinary laptop is now a viable runtime for tasks that used to demand a rented cluster.
The Free Tier Rewards Planning, Not Luck
Treat a Colab notebook as somewhere to prove an idea, not somewhere to live. Sketch the pipeline on a small slice of data, confirm the loss curve moves in the right direction, then decide whether the full run belongs on a rented GPU or a paid runtime. Save early, save often, keep your data and weights on Drive.
Do that and the free GPU stops feeling like a lottery ticket. It becomes what it actually is: a remarkably good machine that someone else pays for, available the moment you have something worth testing on it.