From published URL to portable files

Bolt to HTML Converter

Turn a public Bolt deployment into a portable static front end for landing pages, demos, archives or developer handoff.

How it works·01

Paste your Bolt URL and choose pages.

scanning…

Pages found0

/
/about
/blog/*
/pricing
/contact

Choose what to include

Paste the public Bolt link

Copy the address of your published site, not its editor. The page must open without a login.

Choose the pages to export

The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.

How it works·02

Download your Bolt site as HTML files.

your-project.netlify.app

HTML

IMAGES

CSS

Inside your ZIP download

Page content and design

The pages and styles visitors see on your deployed site. Original React components, TypeScript and project source files are not included. Review page titles and search settings before publishing.

Images and fonts

Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.

Menus and animations

Interactions can work when their scripts and external services remain available. Server components, API routes and server actions are not exported.

How it works·03

Test your exported site then publish it.

bolt-frontend-export.zip

Vercel

Netlify

Cloudflare

GitHub

Choose your hosting

Test the exported site

Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.

Publish on your chosen host

Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.

Before you move your domain. The ZIP contains the published site, not the original Bolt project. Source components, build tools, API routes, accounts, databases, server functions and private settings are not included.

Common Questions

Review what the workflow covers, what needs separate implementation, and what to verify before making a change.

Bolt's download provides the editable source project. NoCodeExport instead captures the public browser output as a static snapshot, which can simplify a content-only handoff but does not replace the source or backend.

The public URL of your deployed Bolt project — the hosted deployment link or your custom domain. The exporter crawls it like a visitor and packages what it renders.

Front-end only. Server routes, databases, and auth need the running app. Landing pages, marketing sites, and demos export cleanly; keep full apps deployed as apps.

Reachable rendered CSS is packaged under the selected settings. Supported reveals may continue through captured scripts or recovery helpers, but exact motion and app behavior vary and must be tested.