To let other people open a web page that ChatGPT or Claude wrote for you, the files have to live on a server that is always on and has a public address. If all you have is a single HTML file, the fastest route is to drop it onto a static hosting service and you will have a link within minutes. If you have a React project that needs npm run build, you need a host that runs the build for you, or you build it yourself and upload the output. If the code has a backend, a database or API keys, it needs a host that can run Node.js, Python or PHP, such as RoamerHost's Vibe Coding Hosting.
This is where a lot of people get stuck. The page opens fine when you double-click it on your own computer, but when you send it to a friend they just get a file, or the preview link the AI gave you stops working after a while. This guide splits things into four situations based on what you actually have, and covers how to publish each one, where the free options draw the line, how addresses, domains and SSL work, and how to update the site after it is live.
Details about other services were checked against their official documentation in November 2026 and may change. The official pages are the final word.
First, figure out what you have
"A website the AI made" can mean very different things, and how hard it is to put online depends on which one you have. Open the files you saved and you will usually find one of these four.
The first is a single HTML file. ChatGPT or Claude gave you one block of code that starts with <!DOCTYPE html>, with the CSS and JavaScript inside the same file. Save it as index.html, double-click it, and it opens in your browser. Event sign-up pages, personal bios, small games and calculators usually look like this.
The second is a folder with index.html, a few CSS and JS files and some images. It is the same kind of thing as the first, a static website, just split into separate files.
The third is a front-end project. The folder has a package.json and a src directory, and the AI tells you to run npm install and then npm run build. Sites made with React, Vue or Vite, and projects downloaded from Lovable or Bolt, fall into this group. They have to be built into plain static files before they can go online. If you upload the src folder as it is, you will usually get a blank page.
The fourth is an app with a backend: member logins, form entries saved to a database, server-side calls to OpenAI or another API. Next.js, Express, FastAPI, Flask and Laravel projects built with coding agents like Claude Code or Codex are often like this. They need a server that keeps the program running, which static hosts cannot do.
A single HTML file: the quickest options
If you only want people to see it, the AI tools have sharing built in. Claude's help center explains that you can click Share on something you built in Claude and set it to "Anyone with the link", and in most cases people can open and use it without a Claude account. Work that connects to other websites cannot be shared publicly, and once you unpublish something you cannot publish that same item again. ChatGPT's canvas can preview HTML and React code right in the conversation, which is handy for checking how it looks. These links live under the AI tool's own address, which is fine for showing friends. For a real site that goes on a business card or a flyer, most people want an address of their own.
The second option is a static hosting service. Netlify's documentation says you can drag a folder onto Netlify Drop and it goes live, no account required. Without logging in, the files are published as they are; when you are logged in, Netlify detects the framework and runs the build. It takes a folder, so unzip first. With GitHub Pages you put the files in a GitHub repository and the site is served at yourname.github.io, with custom domains supported.
If you already know the site will stay up for a long time and keep changing, you can put it straight on Vibe Coding Hosting. Once the project is set up, upload a ZIP in the file manager, extract it and click Deploy. The platform recognizes a plain HTML static site, and the address and SSL are already set up when the project is created.
What the free options say about their limits
Free static hosting is great for portfolios and practice. Before using it for a business, though, read the rules the providers spell out.
GitHub's documentation describes Pages as a static site hosting service that takes HTML, CSS and JavaScript files. On a free account the repository has to be public, and the published site is public on the internet even if the repository is private. Published sites can be no larger than 1 GB, there is a soft bandwidth limit of 100 GB per month, and a soft limit of 10 builds per hour. GitHub also states that Pages is not intended for or allowed to be used as free hosting to run an online business, an e-commerce site, or any site mainly aimed at commercial transactions or commercial software as a service.
Netlify's free plan now runs on credits. Its documentation lists 300 credits a month with a hard limit and no way to buy more. Each production deploy costs 15 credits and each GB of bandwidth costs 20. When a team runs out, every project in that team is paused until the next billing cycle, visitors see a "Site not available" message, and on the free plan the only options are to wait for the reset or upgrade. A site that gets redeployed every time you tweak it can burn through credits faster than you expect.
What these services have in common is that they serve static files only. Sending form emails, saving data or calling an API that needs a secret key is not something a static site can do by itself. You either wire in third-party services or move to a host that runs backend code.
| Option | Good for | Address | Limits stated officially |
|---|---|---|---|
| AI tool share link (Claude as an example) | Showing a draft, single-page tools | The AI tool's own address | Work that connects to other sites cannot be shared publicly; unpublished items cannot be republished |
| Netlify free plan (including Drop) | Static sites | Netlify address, custom domain supported | 300 credits a month; when they run out, all projects pause until the next cycle; 15 credits per production deploy |
| GitHub Pages | Static sites | yourname.github.io, custom domain supported | Repository must be public on free accounts; site up to 1 GB; not allowed for running an online business or e-commerce |
| Vibe Coding Hosting | Static sites, Node.js, Python and PHP apps | yourname.roamerhost.com plus one custom domain | One site per plan; annual billing only; no Dockerfiles or apps without a web interface |
A React project that needs npm run build
The AI asks you to run npm run build because browsers cannot read the JSX and TypeScript in src. The build turns them into ordinary HTML, CSS and JavaScript and writes them to a dist or build folder, and that folder is what goes online. If you build on your own computer, upload dist. On Netlify Drop, drag dist when you are logged out, or drop the whole project when you are logged in so it can build for you.
Three things go wrong most often at this step. The first is environment variables. In a Vite project, settings that start with VITE_, such as your Supabase URL and public key, are baked into the code at build time. If they are missing during the build, the site loads as a blank page. The second is a 404 on refresh. In a multi-page site built with React Router, clicking around from the homepage works, but refreshing on /about makes the server look for a file called about, which does not exist. The server has to be told to send those paths back to index.html. The third is leaked keys. Anything starting with VITE_ is bundled into the front end, so anyone can read it in the page source. Never put an OpenAI key or a Supabase service_role key there.
On Vibe Coding Hosting you can zip up the whole project and upload it, no need to include node_modules. The platform reinstalls packages from your lockfile and builds with Node.js 22 or 24. The .env file itself is never deployed, but public settings such as VITE_ variables in it are passed into the build automatically, and client-side routes do not 404 on refresh. We have tested React plus Supabase projects made with Lovable and Bolt; your database and logins stay on your own Supabase. The full GitHub setup is in deploying a Lovable app from GitHub.
Apps with a backend, a database or API keys
If the AI wrote you a Next.js, Express, FastAPI, Flask or Laravel app, there is a server program that has to keep running in addition to the web files. Static hosts cannot run it. You need a host that runs Node.js, Python or PHP. The traditional route is renting a VPS and setting up the runtime, Nginx, SSL certificates and a firewall yourself. Our guide to shared hosting, VPS and managed hosting explains who handles what in each setup.
Vibe Coding Hosting detects the project type automatically: Node.js 22 and 24 (Next.js, Express and similar), Python 3.12 and 3.13 (FastAPI, Flask, Django) and PHP 8.4 (Laravel and plain PHP). Databases are off by default. When you need one, turn on PostgreSQL or MariaDB and the connection string goes into the DATABASE_URL environment variable. API keys go into environment variables, which are stored encrypted and not shown again after you save them. Your app just needs to listen on the PORT environment variable, read its settings from environment variables, and keep files that must persist in /data. You can hand those rules straight to your AI.
Some things will not run here: programs with no web interface that only run scheduled jobs (a Discord bot, for example), Dockerfiles, your own Redis or MongoDB, always-on background workers, and anything that needs a GPU. For those, look for a service that supports them.
Addresses, domains and SSL
Every live site has an address. Free services usually give you a subdomain under their own domain. With Vibe Coding Hosting you pick a name at checkout, the project is ready about a minute after payment, and it is served at yourname.roamerhost.com with HTTPS already working and HTTP redirected to HTTPS.
Using your own domain, such as example.com, works much the same way anywhere: buy the domain from a registrar, then update its DNS the way your host tells you to. Each Vibe Coding Hosting plan can connect one custom domain, and once DNS is in place the SSL certificate is issued and renewed automatically. Keep in mind that one plan holds one site. You cannot run several subdomains like api.example.com and blog.example.com on the same plan. If the front end and back end live in the same Next.js project, one plan is enough.
SSL is basically required now. Without the padlock, browsers mark the site as not secure, and forms and logins tend to break. Most hosts handle it for you; just check before you choose.
Updating the site after it is live
Going live is only the start. Dates change, prices change, and the AI adds new features, so you will be updating again. Downloading and re-uploading by hand works, but it is easy to overwrite the wrong version and lose track of which one was good.
There are three smoother ways. If you use a coding agent such as Claude Code, Codex or Gemini CLI, create a token on your Vibe Coding Hosting project page and let the agent deploy over MCP. It can upload the code, read the deploy logs, fix errors and deploy again. If your code is on GitHub, connect the repository and every push to the chosen branch deploys automatically, private repositories included. For a quick text change, edit the file in the online file manager, save, and click Deploy to update the live site.
The web versions of ChatGPT and Gemini cannot connect to Vibe Coding Hosting over MCP. Have them update the code, download it, then upload a ZIP or push it to GitHub.
Whichever route you take, a new version has to pass a health check before traffic switches to it. If it fails, the previous version stays live and visitors never see a broken site. The last three successful versions are kept so you can roll back in one step, though the database is not rolled back with them. The health check only confirms the app started and the homepage responds, so click through the main features yourself.
Which option fits
If you just want a friend or coworker to see it, the AI tool's own share link is fastest. For practice or a personal portfolio, where living under someone else's domain is fine, free static hosting works, as long as you read the provider's rules on commercial use and usage limits.
If you built a page with ChatGPT, Claude or Claude Code, want it live on your own address, and expect to keep changing it, choose Vibe Coding Hosting Basic at NT$3,588 a year (about NT$299 a month) and deploy with your own AI tools. If you are not very technical and want to build a site with members, bookings or an admin area by chatting on the platform, choose Vibe Coding Hosting Pro, about NT$999 a month billed annually, which includes Roamer AI. The Vibe Coding Hosting plans and pricing show the differences.
If what you really need is a business website, a blog or an online store and you would rather not touch code, WordPress with Roamer AI is the better fit: describe what you want and it builds the site, and later you just tell it what to change.
FAQ
Q: The HTML file from ChatGPT opens when I double-click it. Why can't anyone else open it?
When you double-click it, the address bar starts with file://, which means the browser is reading a file on your computer. Other people do not have that file, so it has to be on a server on the internet to get an address everyone can open.
Q: Can I use free GitHub Pages or Netlify for a company or shop website?
Check the official rules. GitHub's documentation says Pages is not allowed for running an online business, e-commerce or SaaS. Netlify's free plan has a monthly credit cap, and when it runs out all projects pause until the next cycle. Read each provider's terms and plan details before using them for a business.
Q: The AI told me to run npm run build. Can I skip it?
Not if you are hosting it yourself. An unbuilt React project usually shows a blank page. Build it and upload the dist folder, or use a host that builds for you. On Vibe Coding Hosting you upload the whole project and the platform installs packages and builds it, and tells you why if it fails.
Q: Can ChatGPT deploy straight to Vibe Coding Hosting?
The ChatGPT web app cannot, because it does not support the way our MCP server connects. Codex, Claude Code and Gemini CLI have been tested and connect, and other tools that support remote MCP, such as Cursor, should work according to their documentation. For code made in the ChatGPT web app, download it and upload a ZIP or push it to GitHub.
Q: Can one plan hold several AI-made pages?
No. Each Vibe Coding Hosting plan holds one site, with one default address and up to one custom domain. Multiple sites or multiple subdomains are not supported. For a second site, get a second plan.
Sources
- GitHub Docs: What is GitHub Pages?
- GitHub Docs: GitHub Pages limits
- GitHub Docs: Creating a GitHub Pages site
- Netlify Docs: Create deploys (Netlify Drop)
- Netlify Docs: Credit-based pricing plans
- Netlify Docs: Resume paused projects
- Claude Help Center: Share artifacts
- OpenAI Help Center: Canvas