Publish WordPress as a static site
Staatic turns a WordPress website into a static publication made from HTML, images, CSS, JavaScript, and other discovered assets. You continue editing posts, pages, menus, media, and settings in WordPress, then publish a static copy for visitors. The public site can be served without WordPress, PHP, or a database in the visitor request path.
This approach separates the editing environment from the public delivery layer. WordPress remains available for administration and publication work, while visitors receive prebuilt files from the selected hosting target. Staatic Premium and Staatic Cloud extend the core publication workflow for projects that need recurring publishing, integrations, and additional automation.
Premium and Cloud capabilities
Staatic Premium adds forms integration, search integration, scheduled publications, change-based publications, additional automation, and Staatic Cloud deployment options. These features are intended for teams that need more than manually generating and deploying a static version of their site.
Staatic Cloud adds the option of managed static WordPress hosting. Together, the paid editions support a workflow in which WordPress is used for content management while the public-facing site is delivered as a static publication.
Publication and deployment workflow
Staatic crawls the WordPress site like a visitor, beginning at the front page or a configured Custom Origin URL. You can also provide additional URLs or paths. The plugin captures generated pages and related assets, then creates a static publication that can be reviewed and deployed.
Publication can be started from WordPress Admin, where the workflow provides publication status, logs, resource details, and downloadable output. A WP-CLI command is also available for command-line publication workflows. Supported deployment targets include Local Directory, Amazon S3 or S3-compatible storage, GitHub, Netlify, SFTP, and a zip archive.
Control over the published site
- Configure redirects and custom 404 pages.
- Add extra URLs and paths to the crawl.
- Use exclude rules to control what is published.
- Set HTTP headers for the static output.
- Use forms and search integrations available with Premium.
- Schedule publications or publish changes through the paid editions.
Staatic works with WordPress Multisite, WPML, and HTTP Basic Auth-protected WordPress origins. It also provides integration hooks and compatibility improvements for common WordPress setups.
When a static workflow fits
A static publication can reduce the work required from the WordPress origin during public requests because visitors receive prebuilt files rather than pages generated on demand by WordPress, PHP, plugins, and the database. It also helps keep the public site separate from the WordPress administration area and database-backed page generation.
Static delivery is not suitable for every dynamic feature. Public-facing functionality that depends on server-side processing, personalized data, native comments, some search implementations, forms posting back to WordPress, eCommerce flows, or membership areas may require changes, a static-compatible service, a client-side integration, or a hybrid architecture. Premium provides ready-made integrations for forms and search.
Installation and first publication
Install Staatic in the WordPress environment, configure the origin and any additional URLs or paths, select a deployment target, and start a publication from WordPress Admin or WP-CLI. Review the status, logs, and resource details, then deploy the generated output. Premium and Cloud users can continue by configuring the available integrations, schedules, change-based publications, automation, or managed hosting workflow.
