How do I fix Save as PDF plugin conversion errors or timeouts?

Start with the exact error message shown by the plugin. Some messages include a PDFCrowd status code because the plugin creates the output through PDFCrowd in the background. You do not need to know the API to use the code.

Copy the error and turn on the debug log

Enable the Debug Log option and run the conversion again. The debug log can show failed page, image, CSS, script, or font requests.

If the page cannot be loaded

If the message says the input URL cannot be loaded, navigation failed, or a download failed, the converter could not open the page or one of its resources.

If the page is private, password-protected, on staging, on localhost, or behind a firewall, change the Conversion Mode option instead of using the default URL mode. For the mode choice, use Can the plugin convert password-protected or private WordPress pages?.

If the page is protected by a browser username/password prompt, set the HTTP Auth User Name and HTTP Auth Password options.

If the message says no input was specified

The plugin did not send a page URL or uploaded page content for conversion. Check that the button is on a normal WordPress page or post and that the page can provide a source for conversion.

If the message says timeout

If WordPress shows a connection timeout, or a message such as cURL error 28, WordPress could not finish its request to PDFCrowd. Try again once, then ask your hosting provider whether outbound HTTPS requests from WordPress to api.pdfcrowd.com are allowed and not cut off too early.

If the conversion starts but takes too long, the page may have slow images, scripts, or third-party resources. Use the debug log to identify the slow request. The Max Loading Time option can help only when slow page loading cannot be fixed directly.

If the debug log shows blocked resources

If images, CSS, scripts, or fonts fail to load, check whether they require a login, are blocked by a security plugin, or are protected by a CDN or firewall. The failed URLs must be accessible to the conversion mode you use.

If support asks for diagnostics

Use the Diagnostics option only when you are investigating the button setup or support asks for it. It displays diagnostic information above the button and can also write details to the WordPress/PHP error log. Turn it off after testing.

If the error includes a numeric code

Use the status-code reference when an error message contains a numeric code. It is technical, but it can confirm what the code means.

Older messages may show deprecated codes such as 471 for a page that cannot be loaded, 452 for missing input, or 458 for a conversion that took too long. The current reference lists newer reason codes for these cases.

Include the exact code and the debug log when contacting support.