# How to Export ChatGPT Sites and Move Your Files

> Learn how to export a ChatGPT Site, verify every file, move it to Revdoku or another static host, test the preview, and retire the original.

TL;DR: ChatGPT Sites currently has no documented one-click export. For a static Site, ask ChatGPT to collect every generated file, copy the complete directory to your new host, and verify it before changing the original deployment.

![ChatGPT Sites page showing a website ready for export](/assets/en/blog/how-to-export-a-chatgpt-site-and-host-it-elsewhere/chatgpt-sites-page.webp)

*Start from the ChatGPT Sites page and open the Site whose complete file tree you need.*

## Can you export ChatGPT Site files with a button?

OpenAI's current [ChatGPT Sites documentation](https://help.openai.com/en/articles/20001339) covers creating, editing, publishing, sharing, restricting, and deleting a Site, but not a dedicated command for downloading a complete export.

A static Site is not trapped: export its full file tree, including `index.html`, styles, scripts, images, fonts, documents, and other browser-ready assets.

Do not confuse ChatGPT account data export with a deployable website export; a history archive cannot replace a checked static-site folder.

## Ask ChatGPT to prepare the complete ChatGPT Sites export

Use the Site's original conversation to retain project context. Paste:

```text
Prepare a complete portable export of this ChatGPT Site.

Requirements:
1. Create index.html at the root.
2. Include every HTML, CSS, JavaScript, image, font, document,
metadata, and data file required by the website.
3. Preserve the current folder structure and relative paths.
4. Remove secrets, tokens, environment files, private prompts,
customer data, and local computer paths.
5. Give me a file inventory with each path.
6. Check for absolute or missing local references.
7. If Revdoku is connected, copy every file to a new Revdoku bucket
and compare the destination inventory with the source.
8. Otherwise, package the complete folder as a downloadable ZIP.
9. Create a private preview before publishing publicly.
10. Report server functions, databases, storage, authentication,
or platform-only features that are not included in the static export.
```

A file inventory makes the export auditable: 27 source files should mean 27 destination files unless you intentionally excluded something.

## How to host a ChatGPT Site elsewhere with Revdoku

With Revdoku connected:

1. Follow [the Revdoku connection prompt](https://revdoku.com/prompt.md).
2. Complete OAuth for `https://app.revdoku.com/mcp`.
3. Ask ChatGPT to create a new bucket.
4. Tell it to upload the entire file tree without flattening folders.
5. Publish a preview first.
6. Compare the source and destination inventories.
7. Test the preview before selecting the final access mode.

This is usually faster and less error-prone than moving dozens of files through individual chat messages.

For the full flow, see [How to migrate a ChatGPT Site to Revdoku](https://revdoku.com/blog/how-to-migrate-a-chatgpt-site-to-revdoku/).

![Exported static website files stored in a Revdoku bucket](/assets/en/blog/how-to-export-a-chatgpt-site-and-host-it-elsewhere/revdoku-static-site-files.webp)

*The destination should preserve every folder and file required by the static website.*

## Use the ZIP fallback to download ChatGPT website files

If ChatGPT cannot send the export files to your chosen host, ask for a ZIP:

1. Download the ZIP.
2. Extract it locally.
3. Confirm `index.html` is present.
4. Open the folder and check the asset paths.
5. Remove anything private.
6. Upload the complete folder or ZIP to Revdoku.
7. Publish a preview and test it.

**Save Page As** is unreliable: it captures a rendered page, not necessarily the original project, all routes, or every generated asset.

## What ChatGPT Sites export files cannot carry

Static hosting serves files and runs browser-side JavaScript, but cannot automatically reproduce:

- Server functions tied to the original platform.
- Databases or persistent storage.
- Secret environment variables.
- Private APIs that require a backend.
- Platform-specific identity or AI runtime features.
- Scheduled jobs or background workers.

Before moving, list those dependencies; replace or remove them, or keep the relevant service running.

## Test the new host after you export a ChatGPT Site

While signed out, check the preview for:

- Navigation and direct route reloads.
- Images, fonts, icons, and styles.
- Forms and interactive controls.
- Documents and downloads.
- Mobile layout.
- Browser-console errors.
- Static versus SPA routing.
- Access behavior.

Then choose public, password, or verified-email access. Revdoku can preserve the URL across file replacements and record visitor, click, and download activity.

If the content is client-only, read [How to password protect a ChatGPT Site](https://revdoku.com/blog/how-to-password-protect-a-chatgpt-site/). For product differences, see [ChatGPT Sites Alternative: Publish with Revdoku](https://revdoku.com/blog/chatgpt-sites-alternatives-with-revdoku/) and [ChatGPT Sites vs Revdoku](https://revdoku.com/compare/chatgpt-sites/).

## Retire the old version last

After testing the replacement, restrict or delete the original Site in ChatGPT. Check its URL in a private window and update any custom domain or inbound links.

Public Sites may be discoverable. See our [site:chatgpt.site Google test](https://revdoku.com/blog/can-chatgpt-sites-show-up-in-google-what-site-chatgpt-site-r/) before placing confidential material on a public URL.

Move ChatGPT Sites export files in this order: inventory, copy, preview, test, publish, then retire the original.

Just ask to “publish to Revdoku” to
publish your HTML pages presentation dashboard app prototype game prototype
as a fast and secure website

from your Codex , Claude or another AI app publish files or folders

Connect
Skill
MCP

Paste this into your AI app.

Copy

Install the Revdoku skill in your AI app.

Copy
npx skills add revdoku/revdoku --skill revdoku -g

Choose your AI app to connect through MCP.

Codex CLI
Claude Code
Other

Copy codex mcp add revdoku --url https://app.revdoku.com/mcp
codex mcp login revdoku

Copy claude mcp add --transport http revdoku https://app.revdoku.com/mcp
claude mcp login revdoku

Transport Streamable HTTP Auth Browser OAuth

Copy https://app.revdoku.com/mcp

Open the MCP setup guide →

Free · Public or protected · Visitor analytics · Forms and email alerts Building websites for clients? Explore Revdoku for agencies →

## Frequently Asked Questions

### Can I export a ChatGPT Site with one click?

There is currently no documented one-click command for downloading a complete ChatGPT Site. Instead, ask ChatGPT to assemble the full static file tree or package it as a ZIP.

### Which files should a complete ChatGPT Site export include?

The export should include a root-level `index.html` plus every required stylesheet, script, image, font, document, metadata file, and data file. Preserve the original folder structure and relative paths so assets continue to load correctly.

### How can I confirm that no files were missed during migration?

Create inventories of the source and destination files, then compare their paths and totals. Any difference should be explained by an intentional exclusion, such as a secret, private file, or unsupported platform dependency.

### Is using “Save Page As” enough to export the website?

No. That browser feature may capture only the rendered page and can omit routes, source files, or dynamically referenced assets. A complete project folder or verified ZIP is more reliable.

### Will backend features work after moving the Site to static hosting?

Not automatically. Databases, server functions, authentication, private APIs, scheduled jobs, persistent storage, and secret environment variables require compatible external services or replacement implementations.

### What should I test before publishing the migrated Site?

Test navigation, direct route reloads, images, fonts, forms, downloads, interactive controls, mobile layouts, and access restrictions while signed out. Also inspect the browser console for missing files or runtime errors and verify whether the host supports the Site’s routing model.

### When should I delete or restrict the original ChatGPT Site?

Keep the original available until the new version has been inventoried, previewed, and fully tested. After publishing the replacement, update domains and inbound links, verify both URLs in a private window, and only then restrict or delete the old Site.

---

[View the canonical page](https://revdoku.com/blog/how-to-export-a-chatgpt-site-and-host-it-elsewhere/) · [Browse llms.txt](https://revdoku.com/llms.txt)