CVRLanding
Get started

Exports and handoff

Download a page as static HTML, an AI handoff document, the JSON funnel spec or React source, and decide whether its forms and analytics keep running through CVRLanding.

Updated October 14, 2026

On this page

Export formats

You export a page from the project’s Publish & domains page. There are four formats:

  • HTML ZIP

    What you get

    Standalone static HTML, CSS, JavaScript and all assets, with production builds of the trusted CRO components. It runs on common web hosting.

  • AI handoff Markdown

    What you get

    Product and campaign facts, source URLs, visual tokens, sections and copy, the funnel flow, analytics instrumentation, triggers, form schemas, consent requirements and export instructions.

  • JSON funnel spec

    What you get

    The complete canonical page schema, with its version and its schema and migration references. Exporting and importing it again gives back the same page, with nothing lost.

  • React/Next.js source ZIP

    What you get

    Renderers, design tokens, assets, an example environment config, build scripts and documentation. It is code you own, not a copy of the CVRLanding service.

Formats by plan

Which formats you can download depends on your plan:

  • Trial

    Formats

    AI handoff Markdown, JSON funnel spec

  • Starter

    Formats

    HTML ZIP, AI handoff Markdown, JSON funnel spec

  • Growth

    Formats

    HTML ZIP, AI handoff Markdown, JSON funnel spec, React/Next.js source

  • Pro

    Formats

    HTML ZIP, AI handoff Markdown, JSON funnel spec, React/Next.js source

  • Agency

    Formats

    HTML ZIP, AI handoff Markdown, JSON funnel spec, React/Next.js source

Plans can change. The pricing page always shows the current ones.

Managed or completely self-hosted

For exports that run as a website, the HTML ZIP and the React source, the export wizard asks how forms and analytics should work.

Managed

Forms, analytics and experiments keep working through a tracking SDK and endpoint scoped to your project and domain. Leads, bookings and orders still arrive in your CVRLanding inbox. This depends on visitor consent, as on any published page, and on an active subscription.

Completely self-hosted

Nothing calls CVRLanding. The export includes the documented endpoint contract that your own backend has to implement. Until you run that backend, leads, A/B tests and AI CRO analysis will not work for the exported page.

Forms in exported pages

An exported form either posts to a real, working endpoint, which is CVRLanding’s in managed mode and yours in self-hosted mode, or it shows visitors a clear message that no backend is configured. It is never a dead form that silently drops leads.

Booking, order and checkout steps follow the same rule: nothing tells a visitor that a payment went through when it didn’t. After you upload an export, submit a test form and check that it arrives before you send paid traffic to the page.

What an export never contains

  • Secrets: API keys, access tokens, signed webhook URLs and webhook signing secrets.

  • Paddle or AI provider keys.

  • Data from other workspaces.

  • Raw personal data. Your leads, bookings, orders and session replays are not part of a page export.

Public identifiers the page needs to run, such as a Pixel ID or a Google tag ID, are included because they are public by design. To export your leads, use CSV export in the inbox.

Handing off to a developer or AI tool

Give the developer or AI coding tool two files. The Markdown handoff explains the page: its facts and their sources, the copy, the funnel flow, and the tracking and consent rules. The JSON funnel spec defines its exact structure. Add the React source if they will build on it.

  • Tell them which mode you exported. In self-hosted mode, they need to implement the endpoint contract included in the export.

  • Ask them to keep event names and section IDs, so your numbers stay comparable across versions.

  • Check claims against the source URLs before you publish anything the other tool rewrote.

GitHub integration

A GitHub integration, which would create a repository, branch or pull request straight from an export, is planned but not available yet. For now, download the ZIP and add it to your repository yourself.