Staatic Premium

Staatic keeps WordPress as the place to edit posts, pages, menus, media, and settings, then publishes a static copy for visitors. That copy contains the generated HTML and related assets, such as pictures, CSS, and JavaScript. Visitors can receive these documents without WordPress, PHP, or a database handling each request.

What Premium and Cloud add

Staatic Premium includes forms and search integrations, scheduled publications, change-based publications, additional automation, and deployment options for Staatic Cloud. Staatic Cloud provides managed static WordPress hosting. The Community edition can generate and deploy a static version of a WordPress website.

Build and deploy a publication

Staatic crawls the website like a visitor, starting at the front page or a configured Custom Origin URL. You can include extra URLs or paths. The crawl captures generated pages and related assets in a static publication that can be reviewed and deployed.

Start a publication in WordPress Admin or use the WP-CLI command. In Admin, check its status, logs, resource details, and downloadable output. Deployment targets include Local Directory, Amazon S3 or S3-compatible storage, GitHub, Netlify, SFTP, and a zip archive.

Publication controls and compatibility

• Configure redirects, custom 404 pages, HTTP headers, and exclude rules.
• Add URLs and paths to the crawl.
• Use forms and search integrations available with Premium.
• Use the available scheduling, change-based publication, and automation features in 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.

Dynamic features and site requirements

Because the published site consists of files, features that depend on server-side processing may need changes or another implementation. Examples include native comments, some search setups, forms that post back to WordPress, eCommerce flows, membership areas, and personalized server-side data. These may require a static-compatible service, a client-side integration, or a hybrid architecture. Premium provides ready-made integrations for forms and search.

The WordPress origin still needs maintenance. The server must be able to write to the configured work directory and make HTTP requests to the site being published. Large websites, slow origins, strict firewalls, disabled loopback requests, or limited PHP execution time can require tuning.

Installation and first publication

Install Staatic in WordPress, configure the origin and any additional URLs or paths, select a deployment target, then start a publication from WordPress Admin or WP-CLI. Review the status, logs, and resource details before deploying the output. Premium and Cloud visitors can then configure the integrations, schedules, change-based publications, automation, or managed hosting available to their setup.