Discover public pages from site links and the sitemap.
Example: https://your-elementor-site.com
WordPress, plugins, forms, WooCommerce, and dynamic data are not exported as a backend. Next.js export is in development.
What a Elementor HTML export includes
FNJ captures the front end of an Elementor-built WordPress site from its published URL. The result is editable static HTML, not a WordPress theme, Elementor project or copy of the WordPress database.
How to convert a Elementor site to HTML
- 01 / Paste a public URL
Use a published Elementor 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 a public page URL and check menus, fonts, images and responsive layouts in the preview. Elementor widgets may rely on WordPress or plugin scripts. Plan replacements for any feature that posts data or reads the WordPress database.
Elementor 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 pages built with Elementor widgets that load data from WordPress or plugins.
- Confirm menus, fonts and images still render when the WordPress domain is not available.
- Replace and test forms, search, login and WooCommerce flows before publishing.
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 →Elementor to HTML: export and hosting FAQ
- Does this migrate my Elementor editor or WordPress admin?
- No. Only public page output is captured. The Elementor editor, WordPress dashboard and plugin settings stay on the original site.
- What happens to WooCommerce checkout?
- A static page cannot process orders. Product pages may be visible in the export, but cart, inventory and checkout require a separate commerce system.
- Is an Elementor HTML export a WordPress backup?
- No. Public HTML does not include the WordPress database, themes, plugin settings, users or admin interface. Keep a separate WordPress backup if you need to preserve that installation.
- Can I edit the Elementor 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 Elementor do not automatically sync.
- Can I host the Elementor 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 Elementor 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 Elementor HTML
Host your Elementor HTML export on Cloudflare
Deploy Elementor HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Elementor HTML code to GitHub
Put your Elementor 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 Elementor 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