Generate a Static Build
Filebase Sites serves static output, which means a Remix project needs to be built with a static adapter or preset. The exact output path can vary, but in many Remix setups it ends up in build/client.
Make Sure Remix Is Static
If your Remix app depends on a server at request time, it is not ready for Filebase yet. The deployable version needs to resolve everything at build time and emit plain HTML, JS, and assets.
Build the Project
From your project root:
npm run buildWith a static Remix setup, the build produces a directory of static files, often build/client. Check your Remix or Vite config if your output path differs.
Upload the Static Output
In Filebase, create a bucket and upload the contents of the static output folder. If you are using build/client, open that folder and upload everything inside it so index.html lands at the bucket root.
Do not upload the parent directory itself. The site root needs the built files directly, not an extra wrapper folder.
Keep only the built site files in that bucket. Once the upload is complete, copy the bucket CID from the bucket storing those files. That bucket CID is what you will use to create the site.
Create the Site
Open Sites in the dashboard and create a new site, then paste in the bucket CID you copied from the bucket storing the site files. Filebase will use that CID as the site’s content source.
Other Frameworks
We also have framework-specific guides for Vite, Next.js, Gatsby, Astro, and Docusaurus.