Do I still need Firebase?

Only for backend services the app uses. The files themselves don't need it.

Will Firestore and Auth keep working?

Yes. Those requests go from the browser to Firebase directly and don't involve the host.

Can I host server-rendered output?

No. Anything needing a Node server at request time has to run somewhere that executes code.

Hosting here is free. Whether that matters depends on your Firebase usage, but for a static prototype it's simply less to manage.

Yes, every publish is kept as a version.

Host a Firebase Studio build without the Firebase project

Studio builds the app and expects it to live in your Firebase project. For a static front end, that's more infrastructure than the job needs.

You can host:

Drop your Firebase Studio build here

Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site

Free to use, live at your-name.99helpers.site in about ten seconds.

Why you might not want to leave it there

Firebase Studio will get you from a prompt to a working app quickly, and then assumes you're staying in the ecosystem — a project, a CLI, hosting configuration, a deploy command. That's a reasonable assumption for something you're going to run properly, and a lot of ceremony for a prototype or a landing page that happens to have been built there.

What Firebase Studio gives you

A full workspace with the project source
Static builds from whichever framework you chose
Apps wired to Firebase services, if you asked for them

A project per experiment

Every prototype wants its own Firebase project, and nobody ever deletes the old ones.

CLI and config for one page

Install, log in, init, configure, deploy — a long path to a page that might be up for a week.

Console-shaped addresses

Generated hosting URLs are long and say more about the platform than the project.

Putting Firebase Studio output online

1
Build in the workspace
Run the project's build and locate the output folder, usually dist or build.
2
Download and drop it in
Get that folder onto your machine and drag it into the box above.
3
Choose an address
Pick a name and publish. No project, no CLI, no configuration file.

Worth knowing

An app using Firestore or Auth still needs its Firebase project — those calls come from the visitor's browser and are unaffected by where the files live.
Publish build output, not source.
Restrict Firebase API keys by referrer to your published address as a matter of habit.
Add a 404.html copy of index.html for client-side routing.
Delete the address when the experiment is over, rather than leaving a project behind.

Questions

Do I still need Firebase?: Only for backend services the app uses. The files themselves don't need it.
Will Firestore and Auth keep working?: Yes. Those requests go from the browser to Firebase directly and don't involve the host.
Can I host server-rendered output?: No. Anything needing a Node server at request time has to run somewhere that executes code.
Is this cheaper?: Hosting here is free. Whether that matters depends on your Firebase usage, but for a static prototype it's simply less to manage.
Can I roll back?: Yes, every publish is kept as a version.

Try it with what Firebase Studio just made you

Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the top Every AI tool we cover

Hosting artifacts from other tools

Hosting guides by file type

Everything gets its own address on 99helpers.site — see AI artifact hosting for every tool or free file hosting for any file type.