What changed
Time to bail on App Engine apps on PHP 8.2? Act. You can stay. After December 31, 2026 you cannot deploy PHP 8.2 apps on App Engine. They keep serving traffic.
On our scale this is Act: change a setting or plan before the date. You can stay.
Google ends support for PHP 8.2 on the App Engine standard environment on December 31, 2026. Apps keep running. But you can no longer deploy new versions on it, and it gets no security fixes.
Here are the facts we checked:
- End of support: December 31, 2026 (Google Cloud)
- Runtime: PHP 8.2 (runtime ID php82) in the App Engine standard environment (Google Cloud)
- After end of support: Your app keeps running and serving traffic, but you can no longer create or update it on this runtime (Google Cloud)
- Security fixes: Google no longer applies security updates or patches to the runtime (Google Cloud)
- Exception: An organization policy can re-enable deployments until the runtime is deprecated (Google Cloud)
- Deprecated: December 31, 2027 (Google Cloud)
- Can the dates change?: Google says key dates might be delayed (Google Cloud)
- Newer runtimes: php83 ends support December 31, 2027, php84 December 31, 2028, php85 December 31, 2029 (Google Cloud)
- Apps on PHP 8.2: Cannot be deployed again after December 31, 2026 without an exception (Google Cloud)
You can stay on App Engine. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Google Cloud is the main source for this page. App Engine has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Who is affected
Apps on PHP 8.2: Cannot be deployed again after December 31, 2026 without an exception.
The date to remember is December 31, 2026. Make the change before then.
What to do before December 31
- Find services on PHP 8.2. Check the runtime line in each app.yaml, or the runtime of each service and version in the console.
- Change the runtime. Set runtime to php84 or php85 in app.yaml and update your dependencies.
- Deploy and test. Deploy each service on the new runtime before December 31, 2026.
A few tips:
- Make the change yourself before the date. Do not wait for the last reminder email.
- Write down your current plan or settings first, so you can compare after the change.
- After the change, open your settings again and check that it worked.
How to tell your users
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Options people mention
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
Questions people ask
No questions collected yet.
Sources