Why publish WordPress as static HTML?
Most WordPress sites are read thousands of times for every edit. Yet on every visit, PHP boots, plugins load and MySQL is queried — just to rebuild a page that hasn't changed. Publishing a static copy moves that work to build time:
- Speed. Visitors get pre-built HTML straight from a CDN, which typically improves Time to First Byte and Largest Contentful Paint.
- Security. The public site has no PHP, no database and no admin login. Plugin vulnerabilities can't be exploited on a site that doesn't run plugins.
- Cost and uptime. Static files can be hosted on Netlify, Cloudflare Pages, GitHub Pages or S3 — often for free — and don't fall over under traffic spikes.
WordPress stays where it is, ideally on a private URL or behind a login. You keep writing in the editor you know; only the published output changes.
Plugin vs. crawler: two ways to go static
Static-export plugins run inside WordPress. They're a good fit when you control the server, but they add another plugin to update, compete for PHP memory and execution time on large sites, and stop working if the host restricts background jobs.
Static Converter takes the crawler approach: it visits your published site like a browser would, follows internal links, downloads every page and asset, and rewrites the links so the bundle works on any host. Because it only needs a URL:
- It works on managed hosts where you can't install plugins or run long jobs.
- It captures exactly what visitors see — theme, page builder output (Elementor, Divi, Gutenberg) and all.
- It works the same way for sites that aren't WordPress, if you later migrate.
What carries over — and what needs a plan
Everything that renders as HTML carries over: pages, posts, archives, menus, images, CSS, JavaScript and fonts. Features that need WordPress to answer a request at runtime need a substitute on a static host:
- Forms (Contact Form 7, WPForms, Gravity Forms): map each form to a live endpoint and the converter rewrites submissions to
fetch()calls, with optional reCAPTCHA v3. - Comments: switch to a hosted comment service, or disable them.
- Site search: use a client-side index or a hosted search service.
- WooCommerce checkout, memberships, logged-in areas: these need a live backend. Keep those sections dynamic or on a subdomain.
For SEO, the export generates sitemap.xml and robots.txt, and fills missing titles, descriptions and image alt text from per-site fallbacks. Keep the same URL structure and your rankings move with you — see our guide to migrating to static without losing SEO.
How to do it with Static Converter
- 1Add your WordPress siteCreate a free account, add your site URL, and choose crawl depth (homepage, first-level links or the full site).
- 2Choose optimizationsWebP images, CSS/JS minification, WordPress cleanup and portable links are on by default. Map any forms to live endpoints.
- 3Run the conversionThe crawl runs in the background with a live log. Large sites don't time out, and you can cancel at any point.
- 4Deploy and keep it freshDownload the ZIP for any host, or deploy to Netlify in one click. Schedule daily or weekly re-crawls (with optional auto-deploy) so the static copy follows every change you make in WordPress.