Support Next.js Image Optimizations
Using Next/Image on Firebase App Hosting makes images load slowly. Are Next's built-in image optimizations working with Firebase App Hosting? When a second container starts, does the new container need to optimize every image again, or do containers share image files somehow? When a container shuts down, are those optimized images lost, or are they stored in persistent file storage?
Kaleb Kloppe
shared this idea
-
Patrik Csak commented
Can we get an update on this?
The Image Processing Extension was archived 4 months ago (https://github.com/invertase/firebase-extensions), and Firebase Extensions are shutting down in 7 months
This Firebase Blog post from 4 months ago (https://firebase.blog/posts/2026/03/nextjs-adapters/) announces the Deployment Adapter API and says 'Next.js 16.2 is our new baseline for stability’ but the Next.js support schedule (https://firebase.google.com/docs/app-hosting/frameworks-tooling#runtimes-for-app-hosting) only goes up to 15.2
Next.js 16 was released 9 months ago and 15 is EOL in 3 months
-
Steffen Roemer commented
Is there a fix in sight?
-
Hi folks - wanted to provide an update for you. We're still working on supporting native Image Optimization for Next.js. In the meantime, we've published a solution guide for how to use the Firebase Image Processing Extension with a custom image loader in your Next.js apps on App Hosting:
https://firebase.google.com/docs/app-hosting/optimize-image-loading
Let us know how this works for you. Thanks for your patience as we continue to improve this experience.
-
Isaac Méndez Altuzar commented
I need this for all my aplications since SEO is very important for my clients.
