Can the plugin convert password-protected or private WordPress pages?

Yes. If the page is not public, requires a WordPress login, uses a password, or is on a staging or local site, set the Conversion Mode option to match how the page can be opened.

Use URL for public pages

Keep URL when the page has a public URL and can be opened without a login, firewall, or IP restriction. This is the default mode.

Use Upload when the page is not public

Use Upload when the page works in WordPress but cannot be opened directly by the converter, for example on a password-protected, member-only, admin, or staging page.

Use Content when the visitor's current view matters

Use Content when the conversion must include what changed in the visitor's browser before clicking the button, such as entered form values, selected filters, or generated content.

For entered form values specifically, use the guidance in Can the plugin convert web forms with user-entered data?.

Use Development for localhost or intranet sites

Use Development when the site has no public internet address, such as localhost or an internal development site. Some local images or CSS may still be missing because only some local assets can be included.

For staging sites with browser password prompts

If a staging URL is public but protected by HTTP authentication, set the HTTP Auth User Name and HTTP Auth Password options. This is different from a WordPress login form.

If the output still shows the wrong page

If the output shows a login page or a public fallback instead of the protected content, the converter is not receiving the page you see in WordPress. Try Upload first. If the page changes in the browser before clicking the button, use Content.