Free toolCloud Functions Node.js 20 runtime checker

Deprecated vs decommissioned

Google retires a runtime in two steps. For Node.js 20, the first step started on April 30, 2026 and the second starts on October 30, 2026.

What still runs after October 30: Google doesn’t say functions on Node.js 20 stop that day. It says you can no longer create or update them, so any bug fix or config change means upgrading the runtime first, and that workloads left on a decommissioned runtime may be disabled, without giving a date.

What it checks

firebase.json

Firebase runtime setting

The "runtime" value in the functions block, such as "nodejs20".

package.json

Node.js engines field

The "engines": { "node": "20" } value. Any package.json you paste is read, so paste the one in your functions folder. A range such as ">=18" is shown as a check, since it doesn’t name one version.

gcloud and Terraform

Deploy commands and infrastructure files

gcloud functions deploy --runtime, gcloud run deploy --base-image, serverless-runtimes image paths, and runtime = "..." in Terraform or YAML.

Every language

Node.js, Python, Go, Ruby, PHP and .NET

Each runtime ID is matched against Google’s support table, so a Python 3.10 or Go 1.23 function shows up with its own dates.

What this tool can’t see

It reads the text you paste. It can’t see functions deployed from another project, codebase or machine, so open the Cloud Run functions or Firebase console and check the runtime of each function. Container images you build and deploy to Cloud Run yourself are not covered by Google’s runtime schedule, and App Engine has a schedule of its own.

Using Firebase beyond Functions? The free Firebase shutdown checker looks for Dynamic Links, Extensions, Firebase ML and the other Firebase products with a shutdown date.

Questions

Are my files sent anywhere?

No. The check runs in your browser with JavaScript, and what you paste never leaves the page. Only an anonymous count of matches is recorded for usage statistics, and the example is not counted.

When is Node.js 20 decommissioned for Cloud Functions?

Google’s runtime support table for Cloud Run functions lists nodejs20 as deprecated on April 30, 2026 and decommissioned on October 30, 2026, for both 1st gen and Cloud Run functions. Cloud Run’s base image table has the same dates.

Will my Node.js 20 functions stop on October 30?

Google doesn’t say they stop that day. It says that after the decommission date you can no longer create or update workloads on the runtime, and that workloads that continue to use it may be disabled. So the next deploy of those functions fails until you change the runtime.

Does this apply to Cloud Functions for Firebase?

Yes. Cloud Functions for Firebase deploys to Cloud Functions (1st gen) and Cloud Run functions, so their runtime table sets the dates. Firebase lets you set the Node.js version in firebase.json or in the engines field of functions/package.json.

Which Node.js version should I move to?

Node.js 22 is decommissioned on October 31, 2027 and Node.js 24 on October 31, 2028. Moving to the newest version your platform and dependencies support saves you another upgrade next year.

If the checker finds nothing, am I clear?

Not necessarily. It reads only the text you paste. Functions deployed from other projects or machines don’t show up, so check the runtime column in the Cloud Run functions or Firebase console as well.

Sources, checked October 23, 2026: Cloud Run functions runtime support, Cloud Run runtime support, Firebase: manage functions (Node.js version).

Link to this checker

Writing about the Node.js 20 runtime retirement for Cloud Functions or Firebase? You’re welcome to link here. The checker is free, needs no sign-up, and never uploads what you paste.