PDFCrowd HTTPS Certificate Error: How to Convert Pages with SSL Problems

If PDFCrowd reports an HTTPS certificate error, first confirm that SSL validation is the cause. For its API, set verify_ssl_certificates to false; the documented default is already false. The command-line equivalent is -verify-ssl-certificates, also defaulting to False. Disabling validation can let PDFCrowd fetch a page with an invalid, expired, or self-signed certificate, but it does not repair the website’s certificate. Use this only for a conversion you are authorized to make; if you control the site, fixing its certificate is the durable solution.

1. Confirm the failure before changing SSL settings

A failed conversion is not necessarily an SSL failure. PDFCrowd recommends inspecting the HTTP status, response headers, and response body, enabling debug_log, and requesting structured errors with errfmt=json. Check those details before changing certificate behavior.

Save the complete error response, including its status and headers.
Enable the API debug log and add errfmt=json so the error is easier to inspect.
Verify that the page URL is correct and reachable from PDFCrowd’s remote converter.
If the evidence points to certificate validation, use the API or CLI option below.

PDFCrowd performs conversion remotely. It cannot directly reach a URL on your computer such as localhost, or a private intranet URL. A page that requires authentication may need HTTP authentication or cookies. These reachability and access problems can look like a conversion failure even when the certificate setting is not the issue.

2. Set certificate verification in the PDFCrowd API

The API parameter is verify_ssl_certificates. Its documented default is false, which allows conversion from HTTPS pages with invalid certificates. Set it to true when you want PDFCrowd to enforce certificate validation. If a particular integration sets it to true, set it to false for the authorized conversion in question.

Value	Behavior	When to use it
`false`	Does not require a valid source-page certificate.	As a targeted workaround when an authorized page has a known certificate problem.
`true`	Enforces certificate validation.	When the source certificate should be valid and you want validation enforced.

Use the parameter name and values supported by your PDFCrowd API client. The example below shows the setting to pass; include it alongside your existing authentication and URL parameters:

verify_ssl_certificates=false

Do not treat this as a certificate repair. It changes how the converter validates the source connection. If you operate the website, renew or correctly configure its certificate and then keep validation enabled where your workflow requires it.

3. Set the equivalent option in the PDFCrowd CLI

The command-line interface uses -verify-ssl-certificates. Its documented default is False. Set the option to False for a conversion that must accept an invalid source certificate, or to True to enforce validation.

# Allow conversion when the source HTTPS certificate is invalid
pdfcrowd -verify-ssl-certificates false https://example.com output.pdf

# Enforce certificate validation
pdfcrowd -verify-ssl-certificates true https://example.com output.pdf

Use the executable name and any required authentication arguments from your installed PDFCrowd CLI setup. The option shown is the SSL setting; credentials and other invocation details depend on your installation.

4. Supply HTML instead of asking PDFCrowd to fetch the URL

PDFCrowd accepts a URL, HTML text, or an uploaded HTML file. If you can render or save the page yourself, supplying its HTML can avoid having PDFCrowd fetch the original HTTPS page. This is useful when the remote fetch is blocked or the certificate cannot be accepted in your conversion workflow.

URL input: PDFCrowd fetches the page. The host must be reachable by the remote converter.
HTML text: Your application sends the markup as input.
Uploaded HTML file: Your application uploads a saved document.

Changing the input does not guarantee a visually complete PDF. HTML can refer to stylesheets, images, fonts, or scripts that the converter must also load. Relative asset paths in supplied HTML may not resolve in the converter’s environment. Resources hosted on localhost or an intranet may be inaccessible. Bundle the needed assets with the HTML where appropriate, or use absolute URLs that the converter can reach.

5. Troubleshoot common errors

Symptom	Likely cause	What to do
The response mentions an invalid, expired, or self-signed certificate.	Certificate validation is rejecting the source HTTPS connection.	Inspect the response and debug log. For an authorized conversion, set `verify_ssl_certificates=false` in the API or `-verify-ssl-certificates false` in the CLI. Repair the certificate if you control the site.
The conversion fails, but the error does not mention SSL.	The cause may be the URL, remote access, authentication, or another conversion error.	Check HTTP status, headers, and body; enable `debug_log` and add `errfmt=json`. Do not assume SSL is responsible.
A localhost or intranet URL cannot be converted.	The remote converter cannot directly access your private network address.	Provide HTML or make the necessary resources reachable to the converter through an appropriate public URL.
A protected page produces an access error or incomplete content.	The page requires authentication or cookies that were not provided.	Supply the required HTTP authentication or cookies using the supported API input for your integration.
The PDF is missing styling, images, or scripts after switching to HTML input.	Referenced resources are relative, private, or otherwise unavailable to the remote converter.	Bundle assets with the HTML or use reachable absolute resource URLs; check each dependency independently.
The CLI/API setting appears to have no effect.	The option may be missing, misspelled, passed in the wrong place, or overridden by the client configuration.	Verify the exact API parameter or CLI flag, inspect the outgoing request/configuration, and review the structured error and debug log.

6. Reliability, performance, and cost considerations

The research available for this guide establishes the SSL setting, input types, and remote-access limitations; it does not establish a PDFCrowd benchmark, processing-time guarantee, or pricing detail. Do not infer that disabling certificate checks makes a conversion faster or more reliable in general. It only changes certificate validation for the source connection.

For repeatable conversions, keep a clear distinction between a temporary workaround and a fixed source site. Record the input type and validation setting used, and preserve error details so a later failure can be diagnosed. When using HTML input, account for every external asset the rendered page needs. A URL that works in a local browser may still be unreachable from a remote conversion service.

Or skip the browser setup

If you need a screenshot rather than a PDF, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Its capture can accept cookie banners and remove known consent platforms, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools for screenshots, page information, and PDF capture.

Here is the one-call screenshot example; see the ScreenshotNeo API documentation for the available options and response behavior:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo includes 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. Sign up free and make your first screenshot.

Frequently asked questions

Does disabling verification fix the website’s certificate?

No. It changes the converter’s validation of the source certificate; the website certificate remains unchanged.

Can I use this option in the PDFCrowd web interface?

The available references establish the setting for the API and CLI, not a control in the consumer web interface.

It avoids fetching the original page URL as the primary input, but linked resources may still need to be fetched. Those assets must be supplied or reachable to the converter.

Why does a page work in my browser but fail in conversion?

Your browser and a remote converter may have different network access, authentication, cookies, and available resources. Check reachability and the conversion error details.