Everything you build in HTML Studio is browser-side code, and all of it can leave: any draft exports as a free ZIP of plain HTML, CSS, and JavaScript, identical on Free, Lite, and Pro. No publish first, no credits.
What's in the ZIP
The package holds the piece's source: HTML, CSS, JavaScript, and the files the page needs to run. It snapshots the current draft, not a published version, so nothing needs publishing first, and later edits never reach a ZIP you already have. Downloading changes nothing either: no version is created, the published address stays put, no credits move. Media library originals, other workspaces' files, and the private trail of briefs, chats, task and credit records, and publishing history stay out. So does the delivery shell: the x-rush.ai footer on a published page belongs to the hosting wrapper, not your source.
Same on Every Plan
Every author can export on every plan. There is no preview-only tier, no Enterprise plan, and no public API; work moves through the workbench itself, as a ZIP download or a publish link. The plans change volume, not access: credits per cycle, and one, two, or three generations running at once.
Boundaries Worth Knowing
The ZIP is one-directional: no import exists, and a package is not promised to load back into a workspace. Files belong in a piece through the editor, by hand, for free. External dependencies stay external, offline running is not guaranteed, and there is no backend, database, or server function in it to export.
Taking It Elsewhere
The files are static: any static host or ordinary web server serves them as-is. One difference matters. Published pages on x-rush.ai run inside a security shell, with the platform footer and an interstitial that screens outbound clicks. Your ZIP has neither, so outside x-rush.ai, outbound links are yours to vet.
Worth fixing before you export:
- Real copy in place of placeholders
- A title and meta description that match the finished page
- Final assets instead of test images
Keep the workspace afterward: it stays the piece's editing home, and re-exporting is how a hosted copy catches up.