This is less of a "use Firebase" pitch and more of a story about a time it genuinely helped, back when the options were more limited than they are today.
The Situation
We pushed a new release to production and clients started reporting issues almost immediately. No time to dig through Git history or rush a hotfix. In my team, the first thing we agree on is: get the app stable first, figure out what went wrong after. That's where Firebase Hosting's rollback feature has been a real lifesaver.
How to Roll Back in Firebase Hosting
You can do this entirely from the Firebase console — no CLI needed.
- Open the Firebase console and select your project.
- Go to Hosting → Deploy history.
- Find the version you want and click Rollback.
- Confirm the action — Firebase will serve that version immediately.
No CLI, no Git revert, no re-deploy pipeline. Just a button.
That's it. For more details on managing hosting releases, check the official docs.
Context That's Worth Mentioning
This was useful at that time. Today, Cloudflare Pages has had rollback built in for a while, and honestly it's just as straightforward. So does Vercel, Netlify, and a few others. The feature isn't special to Firebase anymore — it's become a standard expectation for any frontend hosting service worth using.
If you're starting fresh now, pick whatever fits your stack. The ability to roll back a frontend deployment quickly should just be on your checklist, not a reason to choose one platform over another.
How does your team handle production rollbacks? Curious if anyone's had a close call that a quick revert saved. I'd love to hear how your team handles production incidents.
Top comments (0)