Google
Colab

A Notebook That Lives in Your Browser

Google Colaboratory — universally shortened to Colab — is a free, cloud-hosted Python programming environment developed by Google. It runs entirely inside your web browser and requires absolutely nothing to install on your computer. You open a tab, start writing Python, and run it — the code executes on Google's remote servers, not your machine.

At its core, Colab is built on Jupyter Notebook technology: an open-source format that interleaves executable code cells with rich-text documentation cells (written in Markdown). This makes Colab ideal not just for running code, but for telling the story around that code — explaining what each step does, why it matters, and what the results mean. It is simultaneously a programming environment, a documentation tool, and a presentation medium.

Each code cell is an independent, runnable block. You click the play button (or press Shift + Enter) and the output appears immediately below that cell — plots, tables, printed values, even interactive widgets. Each text cell renders formatted prose, headings, maths (LaTeX), and images, letting you narrate your analysis in-line with the code that produces it.

Two Ways to Run Python — One Important Choice

Both Google Colab and a conventional Python terminal execute the same Python language. The differences are in where the code runs, how you interact with it, and what you can do with it. Understanding these differences helps you choose the right tool for each job.

Feature-by-Feature Comparison at a Glance

What Makes Colab Different

Colab is not simply "Python in a browser." It is a platform with a set of features specifically engineered for data science, machine learning, and education. Each feature below addresses a real friction point that conventional Python environments leave unsolved.

Colab Plans — Free, Pro, and Enterprise

Colab has three tiers. The free tier is generous enough for most students and exploratory work. Pro and Pro+ provide longer runtimes, priority GPU access, and more RAM for demanding models.

From First-Year Students to Research Labs

Colab's combination of zero setup, free compute, and document-like format has made it the default working environment for an unusually broad community — from school students writing their first Python line to Google's own AI researchers publishing state-of-the-art models. Here is who uses it and why.

When to Use Colab — and When Not To

Colab excels in specific scenarios. Knowing its limits prevents frustration when you choose it for the wrong job. Use this guide to pick the right tool every time.

✅ Choose Colab when…

❌ Choose a Local Terminal instead when…

Essential Colab Commands & Shortcuts

These are the most commonly used commands and keyboard shortcuts for working efficiently in Colab. Print this page and keep it beside you for your first few sessions.

How Colab Connects to the Wider Python World

Colab is not an island. It sits at the centre of a rich ecosystem of tools that data scientists, researchers, and engineers use every day. Understanding these connections transforms Colab from "a place to run Python" into a complete cloud data-science workbench.

Google Drive — Your Persistent Storage Layer

Every Colab session starts with a fresh runtime filesystem at /content/. When the session ends, anything stored there is lost. Google Drive is the solution: mount it in two lines and all your files, datasets, and saved models persist permanently across sessions.

GitHub — Version Control for Notebooks

Colab has first-class GitHub support. You can open any public notebook from GitHub by simply replacing github.com with colab.research.google.com/github in the URL. Saving back to GitHub creates commits directly from the Colab UI. This workflow is standard in academic ML research: authors publish paper code to GitHub with an "Open in Colab" badge so anyone can reproduce results with one click, no setup required.

Google BigQuery — Querying Massive Datasets

BigQuery is Google's enterprise data warehouse, capable of querying terabytes of data with SQL in seconds. Colab integrates with BigQuery via the google-cloud-bigquery library and a built-in magic command. This combination is used by data analysts who need to pull large aggregated results from a data warehouse, then analyse and visualise them in a notebook — without ever exporting a CSV file.

Hugging Face — Transformers in One Line

The Hugging Face transformers library gives you access to thousands of pre-trained AI models — BERT, GPT-2, Llama, Whisper, CLIP, and more — with a single pip install. Colab's free GPU runtime makes it practical to run inference on these large models without any hardware. This is how most students first experience large language models and computer vision transformers: a Colab notebook that downloads a model and runs it live.

Kaggle Datasets — Data in Two Lines

Kaggle hosts over 200,000 public datasets. With the Kaggle API and your credentials file, you can download any dataset directly into your Colab runtime — no browser download, no file upload, just code.

The Colab Ecosystem at a Glance

Errors Every New Colab User Hits — Solved

Most frustration with Colab comes from a small set of predictable misunderstandings about how sessions, runtimes, and the filesystem work. This section documents every common issue and its solution, so you spend time learning Python — not fighting the environment.

Mistake 1 — Running cells out of order

Unlike a Python script that always runs top-to-bottom, Colab lets you run any cell in any order. This is powerful but dangerous. If you run Cell 5 before Cell 2, and Cell 5 depends on a variable defined in Cell 2, you will get a NameError. Worse: you might get a silently wrong result if Cell 5 uses a stale variable from a previous run.

Mistake 2 — Variables lost after session reset

Colab sessions reset when: your browser tab is closed, you are idle for 90 minutes (free tier), the 12-hour session limit is reached, or you click Runtime → Disconnect and delete runtime. After a reset, the runtime is a completely fresh environment — all variables, installed packages, and files in /content/ are gone. This catches students off guard when they reopen a notebook the next day and get NameError on every cell.

Mistake 3 — Uploading files that disappear on reset

Using the Files panel to upload a dataset feels convenient — until the session resets and the file is gone. Students who upload large CSV files (50 MB+) are particularly frustrated when they have to re-upload after every session.

Mistake 4 — pip installs not persisting

You install a library with !pip install somelib, use it successfully, close the tab, and next session it is gone. Libraries installed with !pip install only persist for the current runtime session — they are not saved to your Google Drive.

Mistake 5 — Forgetting GPU is not always available

The free-tier GPU is shared among all Colab users. At peak times, Google may assign you a CPU-only runtime even if you requested GPU, or switch you mid-session. Always check your runtime type at the start of a session and verify before starting a long training job.

Quick Error Reference

Test Your Understanding — Interactive Quiz

Answer the ten questions below to check how well you have absorbed this guide. Each question covers a key concept from Sections 1–8. Your score is shown at the end. No sign-in needed — this runs entirely in your browser.

Everything You Need to Remember

Here is the complete picture in compact form — a reference card you can return to whenever you need a quick refresher.