Publish and Manage a Reviewed Gab AI Site
Publish a reviewed static HTML page or browser game from Work. Find the separate publishing steps, public-link checks, expiry and site-management controls.
Enlarge preview
Build and refine a website in Work
A public link is a separate publication
My sites manages published static HTML pages, browser games and related assets. A private preview, a file action and a public website are different. Anyone with the live link can view the hosted files; visitors do not need a Gab AI account.
1. Review the selected creation and required files
Test controls/links and check required assets and relative paths. Remove secrets, credentials and private information from every file that would become public. Sites hosts static files; server processes, databases or private API secrets need a different setup or static adaptation.
2. Open Publish site and review the address
Choose Publish site beneath a compatible creation or saved HTML viewer. Review the public-access explanation, name availability and current plan limits. Names use 3–40 lowercase letters/numbers and single hyphens, include a letter and begin/end alphanumeric. Availability and reserved-name checks still apply.
3. Confirm publication and inspect the public result
Choose the final Publish site only when the files and destination are ready. The current direct publishing control reads the selected saved artifact without starting another model turn; its interface says No extra Work credits needed. Creating/revising the content in Work has separate usage. Wait for Ready to share and a confirmed live URL, then open it and test before sharing.
Eligibility, expiry and live-site limits
Publishing requires an eligible Plus plan. The panel/My sites shows the current duration and live-site cap for the account; deployment configuration can change the defaults. This is expiring static hosting, not a permanent-hosting promise. Total site files are limited to 50 MB by the current contract. Review actual errors if a size, plan or name check fails.
4. Manage the live site deliberately
Open My sites to inspect status, public link and expiry. Updating the private creation does not automatically replace its public version. Review the exact existing address and replacement choice before publishing an update; do not assume an expired name is reserved forever.
Unpublishing and visitor copies
Unpublish requires confirmation and removes the hosted site/files. It cannot recall copies visitors already saved. Keep the original creation where needed, and inspect My sites after the action rather than treating an accepted request as completion.
If a site is not ready or a link stops working
Inspect name conflict, plan cap, missing assets, storage/error state and expiry. If a connection drops, check My sites for a completed publication before retrying. Do not share a private preview URL as a substitute for a live site.
Sites questions
Publishing is a separate public action.
Does editing my Work game update its public site?
No automatic update follows from a private edit. Review the intended existing address and publish the appropriate replacement through the supported flow.
Does Publish site start another paid Work turn?
The current direct publishing control reads the selected saved creation without starting another model turn and shows No extra Work credits needed. Content generation/revisions and other Work actions have separate usage.
Are published sites permanent?
No. Current account limits include a duration and live-site cap. Inspect expiry/status in My sites and do not assume renewal or name retention.
Guides and resources
Find more detail and choose your next step.
Review the creation before you share it.
Use My sites to inspect existing public links and expiry. For a new site, return to the intended creation and follow its separate Publish site flow after reviewing the files.