- 3 days ago
- 7 min read
Your ChatGPT build deserves a real home: get it live on Wix Headless →
You asked ChatGPT for a website and it gave you one: maybe that's a live link on a chatgpt.site address, maybe it's a wall of HTML sitting in a chat window. Those are two very different starting points and the honest answer to I built a website on ChatGPT, how do I host it? depends entirely on which one you're holding.
Wix Headless takes the site you already built and puts it on hosting trusted by millions of businesses, with a full business backend underneath it. Connect your frontend, keep your workflow and let Wix run the backend.
TL;DR: how to host a website you built with chatgpt
ChatGPT can hand you a deployed Site, raw code in a chat or a project built through Codex. A deployed Site is already hosted, which is useful until you need it to behave like a business but raw code needs a host. This guide covers what you actually have, how to get clean files out and how to put them somewhere that can take payments and bookings.
You'll learn:
The three things ChatGPT might have given you
What ChatGPT Sites does well and where it stops
How to get clean, hostable files out of a chat
Three ways to get a ChatGPT build onto Wix
What breaks the moment a ChatGPT build gets hosted
For the wider view across every AI tool, start with the broader guide on how to host your AI-built site.
What building a website on ChatGPT actually means
There are three versions of this and they lead to different places.
You may have a ChatGPT Site, which is already deployed and sitting on a URL.
You may have code that ChatGPT wrote into the chat or into a canvas, which is just text until you put it somewhere.
Or you may have a real project built through Codex, which is a folder of files like any other codebase.
The middle case is the most common and the most frustrating because the site looks finished on screen and does nothing at all until it's hosted. A block of HTML in a chat window is not a website and its a very different thing from what a website builder produces and knowing which one you have saves a lot of circling.
Understand the basics: What is a headless website
Before you start: work out which of the three you have before you do anything else. A deployed Site needs a migration decision, chat code needs a host and a Codex project needs a deploy step. Skipping this is why people end up trying to solve the wrong problem.
Built in a different tool? There's a companion guide on how to host a website you built with Claude.
If your site is already on ChatGPT Sites
ChatGPT Sites lets you create, preview, publish and share interactive websites and lightweight apps from a prompt. OpenAI positions it for dashboards, project trackers, launch calendars, prototypes, internal portals and reports, and for that work it does the job with essentially no setup.
A few things are worth knowing before you treat it as your permanent home. It's in public beta for workspaces, Plus and Pro accounts, so it isn't on Free or Go and it wasn't available in the EEA, Switzerland or the UK at launch. Usage limits apply across every Site on your account during the beta and reaching one can stop a high-usage Site staying publicly available.
Custom domains work, with a catch worth planning around. Sites doesn't register a domain for you, so you need to already own one and be able to edit its DNS records. Custom domains also weren't available in Enterprise workspaces at launch.
You can take payments through a third-party payment processor but you're responsible for connecting, configuring and maintaining it, and for fulfillment, refunds, customer support and calculating and remitting tax. Some frameworks, databases and background services aren't supported by the Sites runtime either.
Worth being clear on: none of that makes ChatGPT Sites a bad product, it's built for internal tools and prototypes and it's genuinely good at those. A public site that takes orders, manages bookings and holds customer records is a different job and it's the job Wix Headless was built for. Choosing between them is about what the site needs to do next, not which tool is better.
How to get your code out of ChatGPT
Ask for a single self-contained file
Ask ChatGPT to rewrite the site as one self-contained HTML file with the CSS and JavaScript inline. Fewer files means fewer references that can break once the site leaves the chat window, and it sidesteps most of the path problems covered further down.
Save everything it references
If your site does span several files, save all of them into one folder and keep the structure ChatGPT assumed. A stylesheet that was described in the chat but never saved is the single most common reason a downloaded site renders as unstyled text.
Know what the upload accepts
Your entry file needs to be an HTML file at the top level, named index.html. HTML files buried only inside subfolders aren't accepted. Accepted file types cover markup, styles, scripts, images, fonts and data files like JSON or XML. Video and WebAssembly are rejected.
Size limits are 3MB per file and 20MB in total. Uploads deploy static files only, so an Express server, framework API routes or server-rendered templates won't come along for the ride. If your project has a build step, upload what the build produces rather than your source.
Good to know: connecting to Wix Headless requires no server setup and no backend code. But you're still building and owning a frontend, which means some familiarity with your chosen AI tool affects how smooth the process is. The connection itself is handled in one prompt. What you build on the frontend once connected is still entirely up to you.
Three ways to get a ChatGPT build onto Wix
Drag and drop your files
Upload the folder directly and the site goes live on a Wix URL within seconds, with hosting, SSL and the CDN set up for you. For a single self-contained HTML file this is the whole job, start to finish, and it's the fastest route out of a chat window.
Hand it to an AI coding agent
Wix's AI toolkit works with coding agents including Codex, Cursor and VS Code. Point your agent at the Wix Headless skill file at wix.com/headless/skill.md, tell it to connect your project, and it scaffolds and deploys without you editing a config by hand. This is the natural path if your build already came out of Codex.
Deploy from the command line
If you'd rather drive it yourself, the Wix CLI previews the project locally and releases it when you're ready. It's the same deployment either way, so this comes down to taste rather than capability.
Ran Levi, Developer Advocate, Wix
“The hardest part of shipping something real has never been the frontend. Anyone can build a beautiful UI fast now. The wall people hit is always the same: payments, bookings, a CMS that actually works. Wix Headless knocks that wall down. You connect your frontend to the infrastructure millions of businesses already run on, in one prompt. You're not a backend engineer, you're just shipping.”
Worth knowing: Wix-managed headless means Wix handles all hosting, CDN, SSL and scaling automatically. Self-managed headless means you host the frontend on your own infrastructure and connect to Wix business data through the API. Both paths connect to the same complete Wix business backend. The choice comes down to how much control you want over your hosting environment, not what backend features you can access.
What breaks when a ChatGPT build gets hosted
File paths cause most of it because a page that points at images or scripts by where they sit on your computer works perfectly in your browser and fails everywhere else. Relative paths fix it and ChatGPT will rewrite them if you say where the site is going to live.
Next is anything that quietly assumed a server. API routes, server-side rendering and database calls never run on a static deploy, so the page loads and the interactive parts sit there doing nothing. Assets pulled from outside sources fail the same way if that source blocks hotlinking.
Then there's structure, so an entry file not named index.html, or one sitting in a subfolder instead of at the top level. It's a two-second fix that looks like a catastrophic one.
Worth knowing: none of this means ChatGPT built it wrong. A file path that works locally is correct locally and telling it where the site will be hosted before you ask for the files is one extra line in your prompt and it removes most of this list.
Hosting a ChatGPT website FAQ
Can you run an online store on a ChatGPT Site?
You can take payments through a third-party payment processor but you connect, configure and maintain it yourself. You're also responsible for fulfillment, refunds, customer support and calculating and remitting tax. If selling is the point of the site, a headless platform, like Wix, with native commerce removes all of that setup and liability.
Do you need to know how to code to move a ChatGPT site to Wix?
No, uploading a folder of files is a drag and drop, and if you'd rather not touch it at all, an AI coding agent can do the connection for you from a single prompt. Coding knowledge helps when something breaks, not to get the site live.
Does moving to Wix mean rebuilding the site?
No. You keep the frontend ChatGPT produced and Wix runs the infrastructure and business tools underneath it. There's no Wix editor in this setup, so design changes still happen in your code or your AI tool of choice.
