Is Google Colab Free in 2026? GPU Limits, T4 and Runtime Caps

Google Colab is free to use, but Google does not publish a fixed number of free GPU hours. Free-tier GPU access, idle timeouts, maximum VM lifetime and available accelerator types change with demand and usage history. A free notebook can run for at most 12 hours and may end sooner; neither a GPU nor a particular GPU model is guaranteed.

Short answer: There is no reliable daily or weekly free GPU allowance to quote. Check the official Google Colab FAQ for usage policies.

Google Colab free tier limits at a glance

Source: Google's official Colab FAQ.

What Google officially guarantees, and what it does not

Colab is a hosted Jupyter Notebook service that requires no local setup. It is designed primarily for interactive programming, machine learning, data science and education. A notebook runs inside a virtual machine assigned to your account, while the notebook itself can be stored in Google Drive.

The important distinction is between access and entitlement. Free Colab may give you a CPU, GPU or TPU runtime, but it does not promise that a GPU will be available when you need one. It does not promise a particular model, a fixed idle timeout or a set number of sessions each week. Google says overall limits, maximum VM lifetime, idle periods and available hardware can fluctuate.

The official Google Colab FAQ also says free notebooks can run for at most 12 hours. “At most” matters: it is a ceiling rather than a minimum service level. A session can end earlier because it has been idle, demand is high, the workload conflicts with Colab’s priorities or the account has recently consumed substantial resources.

Paid plans improve access rather than creating unlimited compute. If a paid account exhausts its compute units, it returns to free-tier policies and restrictions until the balance is replenished. Premium accelerators also remain subject to availability.

Does Colab Free include a T4 GPU?

Free Colab may provide access to an NVIDIA T4 GPU, but the model is not guaranteed and availability is subject to quota restrictions. The NVIDIA T4 has 16 GB of GDDR6 memory.

Do not plan a job around receiving a T4 or assume that another user’s session length represents your allowance. Select a GPU runtime only when the code can use it, save progress regularly and make the job restartable.

Google Colab paid options and compute units

Google lists Colab Pro, Colab Pro+ and Pay As You Go as paid options. Those options provide increased compute availability through a compute-unit balance; if the balance is exhausted, the account returns to free-tier policies until more units are available.

A compute unit is not the same as one GPU hour. The rate at which units are consumed depends on the virtual machine, accelerator and other resources selected. A faster GPU can use the balance more quickly than a standard CPU runtime. It is therefore misleading to turn a unit balance into a universal number of hours without knowing the runtime configuration.

For the wider reasons compute prices and allowances vary, read my guide to the real economics of AI pricing.

Which Colab plan should you choose?

Start with the free tier when the work is interruptible and you are still proving that the notebook works. CPU-based data cleaning, spreadsheet transformation, small model tests and teaching exercises often do not justify a subscription.

Pay As You Go makes sense when you need a temporary increase but cannot predict regular monthly use. Pro is the more natural choice for someone opening Colab throughout the month and wanting a recurring allocation. Pro+ is aimed at heavier users who can benefit from a larger balance and longer background execution.

None of these plans should be treated as a guaranteed production server. If a customer-facing process must start at a precise time, run continuously or meet a service-level agreement, use infrastructure with explicitly reserved capacity. Colab is strongest as an interactive development and batch-processing environment.

How to make Colab batch jobs survive interruptions

1. Use small batches. Process a defined group of files, save the results and then start the next group. Do not leave all progress in runtime memory.
2. Make the script resumable. Keep a manifest of completed file names or record status in a CSV so a restarted notebook skips finished work.
3. Copy working data to the runtime. Repeatedly reading thousands of small files from a mounted Drive folder can be slow and may hit Drive limits. Transfer an archive, unpack it locally and upload completed batches.
4. Choose the cheapest adequate runtime. A GPU runtime consumes scarce resources even when the code is not using the GPU. Use a standard runtime for ordinary Python, file handling or spreadsheet work.
5. Validate output continuously. Check dimensions, file counts, empty outputs and a visual sample after each batch. AI-generated code still needs review and testing.

Workloads restricted on managed runtimes

Colab’s managed runtimes prohibit workloads including cryptocurrency mining, password cracking, denial-of-service attacks, torrents and using multiple accounts to work around resource limits.

On free managed runtimes without a positive compute-unit balance, restricted uses also include SSH or remote desktops, distributed-computing workers and bypassing the notebook interface mainly to use another web interface.

Colab is therefore a better fit for interactive notebook work and interruptible batch jobs than for unattended infrastructure. If the workflow matters to a customer or business process, design it so that a terminated runtime does not lose the source data or completed output.

Google Colab limits: common questions

How many free GPU hours does Google Colab provide?

There is no published fixed allowance. Free GPU availability and usage limits vary with demand, account usage and available hardware.

Does Colab Free guarantee an Nvidia T4 or another GPU?

No. A GPU is not guaranteed, and Google says available GPU and TPU types change over time.

Is Google Colab Pro unlimited?

No. Resource availability remains dynamic, and exhausted balances revert to free-tier policies.

How long can a Colab notebook run?

Free notebooks can run for at most 12 hours and may stop sooner. In general, Colab sessions are temporary.

Is Colab suitable for business automation?

It is useful for experiments, analysis and interruptible batch work. It is a poor foundation for a process that requires guaranteed hardware, permanent storage, continuous availability or a contractual service level.