Discover public pages from site links and the sitemap.
Example: https://your-published-duda-site.com
Some Duda hosts block automated capture; FNJ will report that instead of creating an incomplete export. Stores, appointments, forms, and dynamic content need a replacement backend. Next.js export is in development.
What a Duda HTML export includes
FNJ reads a published Duda site just as a visitor can access it and saves the pages and assets it can reach. Some Duda hosts reject automated requests; in that case FNJ reports the block instead of claiming a complete export.
How to convert a Duda site to HTML
- 01 / Paste a public URL
Use a published Duda 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
Start with a public page on the site's live domain. If capture succeeds, review every responsive layout and dynamic widget. Set up new services for appointments, stores and forms before publishing the static version.
Duda 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:
- If Duda returns a capture block, try its published custom domain; FNJ cannot bypass access controls.
- Compare responsive sections and images at desktop and mobile widths.
- Book a test appointment and submit a test form through replacement services before changing DNS.
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 →Duda to HTML: export and hosting FAQ
- Why might my Duda URL fail to convert?
- Some Duda-hosted sites block server-side fetching. FNJ cannot bypass that restriction, so try a publicly accessible domain and check the reported error.
- Are Duda store products included?
- Visible product pages may be captured as static pages, but inventory, checkout and order management are not exported.
- Can FNJ bypass a Duda capture block?
- No. Use a publicly accessible published address and review the reported error. FNJ does not bypass passwords or platform access restrictions.
- Can I edit the Duda 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 Duda do not automatically sync.
- Can I host the Duda 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 Duda 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 Duda HTML
Host your Duda HTML export on Cloudflare
Deploy Duda HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Duda HTML code to GitHub
Put your Duda 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 Duda 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