Discover public pages from site links and the sitemap.
Example: https://your-site.tilda.ws
Tilda forms, store, CRM, and dynamic integrations need a replacement backend. Next.js export is in development.
What a Tilda HTML export includes
FNJ reads the public output of a published Tilda site and captures the HTML and accessible assets. This gives you an editable page snapshot without transferring the Tilda editor, account data or private project settings.
How to convert a Tilda site to HTML
- 01 / Paste a public URL
Use a published Tilda page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
Use the published URL and compare fonts, layouts and motion against the original. Test forms and store actions; the static files do not include Tilda's CRM or the service that receives submissions.
Tilda migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- Compare Zero Block layouts and animation behavior with the live Tilda page.
- Check whether fonts and media still request files from Tilda after deployment.
- Submit a form and complete a store test using your replacement CRM or checkout.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →Tilda to HTML: export and hosting FAQ
- Will Tilda forms work on a different host?
- A form needs a submission endpoint. The visual form can be present in HTML, but you must connect and test the service that receives its data.
- Does the conversion produce a Tilda project?
- No. FNJ produces editable public-page HTML; it does not export a project that can be reopened in the Tilda editor.
- Can I import the exported HTML back into the Tilda editor?
- FNJ generates editable page files, not a Tilda project format. Maintain the exported HTML and CSS in your code workflow rather than expecting editor round-trip support.
- Can I edit the Tilda HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in Tilda do not automatically sync.
- Can I host the Tilda HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the Tilda converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your Tilda HTML
Host your Tilda HTML export on Cloudflare
Deploy Tilda HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Tilda HTML code to GitHub
Put your Tilda HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your Tilda export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters