Download your published WordPress front end as portable HTML, CSS and JavaScript—without installing a plugin or sharing wp-admin access.
01How it works
Choose what to include
Copy the address of your published site, not its editor. The page must open without a login.
The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.
02How it works
Inside your ZIP download
Your public WordPress pages as HTML and CSS. PHP, editable themes, plugins and the database are not included. Review page titles and search settings before publishing.
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 effects can work when their required files are included. Features that call WordPress or a plugin’s server need replacements.
03How it works
Choose your hosting
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.
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. WordPress admin, PHP, the database and server-side plugin features are not included. Set up forms, search and comments separately. Export again after content changes.
WordPress supports ongoing editing and dynamic features. A static snapshot reduces the public runtime but also removes CMS and plugin-backed behavior.
| What you need | Standard WordPress stack | Recommended path NoCodeExport |
|---|---|---|
Performance footprint | Depends on plugins, theme code, and server tuning. | Serves static files that a CDN can cache; verify each export before launch. |
Security surface area | Includes WordPress core, plugins, and database concerns. | Omits WordPress, PHP, and the database from the exported public front end. |
Elementor and builder migrations | Usually handled inside WordPress and its plugin ecosystem. | Useful when the goal is a final static delivery, not another builder setup. |
Best fit | Content teams editing inside WordPress daily. | Teams that need a lower-runtime static delivery target and can re-export after changes. |
Use these articles for the export checklist, builder edge cases, and the SEO steps that matter during a WordPress to HTML migration.
Export once with Site Pass, or choose Pro for regular updates and client projects.
Try the exporter on one page, with assets linked to the original site.
Features included:
For complete sites: downloaded assets, GitHub and Netlify deploys, the export API and included hosting.
Features included:
For freelancers and agencies handling multiple client sites.
Features included:
Prices: Free $0 · Pro $10/month · Agency $50/month · Site Pass from $15, paid once for one site.
Everything you need to know about the export process.
A live WordPress stack includes PHP, a database, themes and plugins that require updates and monitoring. A static public copy can remove those components from page delivery when the site no longer needs them at request time.
Performance still depends on the exported assets, scripts, hosting and cache configuration. Measure representative source and exported pages with the same settings instead of assuming a fixed Core Web Vitals improvement.
There are two ways to turn WordPress into a static site. A plugin such as Simply Static runs inside your WordPress admin and writes static files from there, so you need admin access and a working install. A URL export like this one needs neither: it loads the public site the way a visitor does and saves the pages it renders.
Choose the plugin when you will keep editing in WordPress and republishing. Choose the URL export when you want a final static copy, cannot install plugins (managed hosting, a client's site), or the install is too old or broken to run one. Either way, comments, search, forms and logins need a replacement, because they depended on PHP and the database.
Keep the same URL structure where possible, add permanent redirects for changed paths, verify canonicals and robots directives, and submit the final sitemap in Google Search Console.
Use the export audit to identify metadata issues, then validate the rendered deployment. No migration can guarantee unchanged rankings or performance, so monitor indexing, traffic and Core Web Vitals after launch.
After downloading the ZIP, deploy to Netlify, Vercel, GitHub Pages, Cloudflare Pages or another compatible host under that provider's current terms and limits.
The export gives you a portable frontend to inspect, host, and maintain. Review media locations, licenses, links, forms, and dynamic features before deployment. For Elementor sites, see our HTML to Elementor conversion guide.
Paste your published URL and review the pages. No payment is needed to scan.