Export: HTML

The HTML export turns a page into a single, self-contained .html file you can host anywhere — an S3 bucket, a static host, or a folder on your laptop. This page covers what the file contains and, just as importantly, what it can and cannot do off-platform.

One file, everything inlined

Choosing Export → HTML file from the designer's top bar generates one document and downloads it straight to your machine. There are no sidecar files, no assets/ folder, and no external requests to fetch:

• Styles are inlined. A small base stylesheet lives in a single <style> block (fonts, colors, resets), and every element carries its own inline style attribute resolved from your theme and per-breakpoint settings. There is no external CSS file to link.
• The theme is baked in. Your palette and typography — background, foreground, primary color, heading and body fonts — are resolved to concrete values at export time and written directly into the markup.
• Images travel with the page when they were uploaded as inline assets (data URLs); externally-hosted images stay as their original URLs.
• The title and description from the page settings are written into <title> and, when set, a meta description plus og:description. See SEO & metadata.

Sections render in order, each wrapped with the same outer and inner spacing the editor uses, so the exported page keeps its visual rhythm. Nodes you have flagged as hidden are dropped entirely from the output.

Limitations: display-only off-platform

The exported file is a faithful visual copy of your page. It is not a working FlowRunner app. The single most important thing to understand:

WARNING

Forms in an exported HTML file are display-only. The fields render — text inputs, selects, checkboxes, file pickers, buttons — but there is no FlowRunner backend behind them. A submission has nowhere to go unless you wire the form's action up to your own endpoint. No flow runs, no submission is stored, no email is sent.

More precisely, off the platform:

• No flow runtime. The "run a flow on submit" wiring only exists inside FlowRunner. An exported page cannot trigger it.
• No submission storage. Submissions and uploads are FlowRunner features; a static file has no database.
• No conditional logic. Show/hide rules are evaluated in the browser by the live runtime. The exporter emits every node unconditionally, so conditional visibility is not applied in the static file.
• Limited interactivity. Some components degrade to their simplest native form — an Accordion becomes native <details> blocks, Tabs render as a static label row. There is no JavaScript bundled to power richer behavior.

When to use it

The HTML export is ideal for a static marketing page, landing page, or brochure where the content is the point and any form is a link-out or wired to a third-party endpoint. If you need working forms, stored submissions, or flows, either serve the page on FlowRunner itself (see Publish & share) or reach for the Next.js export, which gives you a full app to extend.

See also

• Publish & share
• Export: Next.js
• Export: React Native
• Theme & design tokens