Discover public pages from site links and the sitemap.
Example: https://your-site.carrd.co
Carrd forms, embeds, and integrations may still use their original service or need a replacement. Next.js export is in development.
What a Carrd HTML export includes
Carrd sites are often a single public page, which makes the page-only option a useful starting point. FNJ captures the markup and assets it can retrieve from the published address; you can then edit the static result.
How to convert a Carrd site to HTML
- 01 / Paste a public URL
Use a published Carrd 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
Paste your live Carrd URL and preview the HTML on phone and desktop. Check contact forms, third-party embeds and any links to external services. Those services are not recreated by copying the page.
Carrd 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:
- Check anchor navigation on a phone as well as a desktop screen.
- Send a test message through every form on the new host.
- Verify embeds and custom-domain links after the export is deployed.
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 →Carrd to HTML: export and hosting FAQ
- Can I export a Carrd page without account access?
- FNJ needs the public page URL, not your Carrd login. Private or unpublished pages cannot be captured.
- Will my Carrd form collect submissions after I move hosts?
- Only if it still has a working service behind it. Set up and test a form destination before replacing the live page.
- Should I use page or site scope for Carrd?
- Page scope is usually the starting point for a one-page Carrd site. Choose site scope if you need FNJ to discover additional linked public pages, then inspect the capture report.
- Can I edit the Carrd 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 Carrd do not automatically sync.
- Can I host the Carrd 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 Carrd 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 Carrd HTML
Host your Carrd HTML export on Cloudflare
Deploy Carrd HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Carrd HTML code to GitHub
Put your Carrd 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 Carrd 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