This is set to 1, by default, in order to allow exporting on low-resource environments, such as shared hosting servers. Each increment is the amount of files the server will try to process on each request that the browser sends it. Incrementing this will speed up your exports, by processing more are a time. If your export is failing, due to resource (memory, CPU) limits being reached, try setting this to a lower number.

This is set to 1, by default, in order to avoid execution limit timeouts on restricted environments, such as shared hosting servers. Each increment is the amount of files the server will try to deploy on each request. Incrementing this will speed up your exports, by processing more are a time. If your export is failing, due to execution limits or API rate limits being reached, try setting this to a lower number.

This is set to 0, by default, but if your deploy is hitting GitLab's API too rapidly, you can increase this to add a delay between each API request.

Replacing the former, limited support for scheduled deploys via WP-Cron, WP2Static now integrates with the great WP-CLI for programmatic access to deploying your WordPress site statically. Control settings and trigger deployments to better suit your development workflow.

More information available on the GitHub project page: https://github.com/leonstafford/wp2static

If you're happy with how your site is looking after exporting to a subdirectory, you can choose to start serving this content to your visitors, instead of your current WordPress site. To do this, you will need to adjust your .htaccess file. This community guide may be able to help you.

Be alerted when your deployment process is complete.

When deploying, WP2Static will check each file to see if it's changed since the last deployment. It will skip unchanged files based on this information. If you want to force an uncached deployment, click this button and any caches will be emptied, requiring a full deploy on the next run.

Will slow down operations, but give verbose output to the Export Log in the Logs tab. Use this when you have a failed export to help pinpoint the cause.