Skip to content

Colab notebook — the fine print

The highest-staleness details behind the Google Colab notebook option page: the runtime limits, why running needs a sign-in, the API-key catch, and what "anyone with the link" really means.

Last verified: 2026-06-07

Viewing is account-free; running is not

The common surprise: someone opens the link fine, reads the code, then can't make a cell go. Viewing by link needs no Google account at all, but pressing play (or Copy to Drive) spins up a free machine tied to a Google account — so the runner needs to sign in, then make their own copy. That's the un-delegable friction on the recipient's side. [confirmed]

The free machine is temporary

A free session runs at most 12 hours and drops if left idle. On reconnect, variables and downloaded files from the old run are gone — re-run from the top. [confirmed]

The exact idle cutoff isn't published: the FAQ says runtimes "time out if you are idle" without giving a number. [unclear] (idle duration only — checked 2026-06-07)

API keys never travel with the notebook

If the code needs an API key, the key does not ride along when you share — Colab strips it. The recipient pastes their own into the 🔑 Secrets tab, or the code errors. Spelled out in the tutorial. [confirmed]

A link forwards, and whoever holds the string is in. Keep anything sensitive on named-people access instead. → Who can see it? [confirmed]

Sources