PDF to Image HTTP API

Overview

Render PDF pages as images with a direct HTTP request from any language or platform. For language-specific client libraries, see the SDK guides.

Quick Start

Choose an input below. Update the input URLs and filenames as needed.

Each example uses cURL and saves the returned ZIP archive to a local file. If a conversion fails, inspect the response for error details.

curl -f -s -S \
  -u 'demo:demo' \
  -o invoice.zip \
  -F url=https://your-server.com/invoice.pdf \
  -F input_format=pdf \
  -F output_format=png \
  -F force_zip=true \
  https://api.pdfcrowd.com/convert/24.04/

curl -f -s -S \
  -u 'demo:demo' \
  -o invoice.zip \
  -F file=@invoice.pdf \
  -F input_format=pdf \
  -F output_format=png \
  -F force_zip=true \
  https://api.pdfcrowd.com/convert/24.04/

Build a Request

Authentication

Use your PDFCrowd username as the HTTP Basic username and your API key as the password. Configure these credentials using your HTTP client's Basic authentication option.

Request Format

Send the input and conversion settings as form fields in a POST request. JSON request bodies are not supported. Your HTTP client handles form encoding and the appropriate headers.

Use the versioned endpoint: https://api.pdfcrowd.com/convert/24.04/. Keep the version explicit in your integration and review API versioning before changing it.

Errors are returned as plain text by default; add ?errfmt=json to the endpoint to receive JSON errors. This changes only the error format; a successful response still contains the converted image or ZIP archive. See Handle the Response for response handling.

Choose an Input

Set input_format=pdf and choose an image output_format, such as png. Supply one of the following inputs:

Upload the file's contents, not its filename or local path as a text field. If the PDF is already in memory, use your HTTP client's file-upload option to send those bytes in the file part. PDFCrowd cannot fetch a PDF from your computer's localhost; upload its contents instead.

Add Conversion Settings

Send conversion settings as additional form fields alongside your input. Common options include:

The parameter reference lists all settings, accepted values, defaults, and constraints. For complete conversion requests, see the HTTP examples.

Handle the Response

Successful Conversion

A successful conversion returns 200 OK with the image or ZIP bytes in the response body. Save those bytes to a file or return them to your application's user.

• One rendered page returns a single image in the selected format.
• Multiple rendered pages return a ZIP containing one image per page.
• force_zip=true returns a ZIP even for one page.

The Quick Start requests return a ZIP, for example:

HTTP/1.1 200 OK
Content-Type: application/zip
x-pdfcrowd-job-id: example-job-id

[ZIP bytes]

Check the HTTP status before processing the body. Use the Content-Type header to distinguish ZIP output (application/zip) from a single image, such as image/png or image/jpeg. Match your file extension and processing to that type. Treat the body as binary data; parsing it as JSON or decoding it as text will corrupt the output.

Errors

An unsuccessful request returns an error HTTP status. PDFCrowd error responses also include a reason code that identifies the specific problem.

By default, the error body is plain text in this format:

<status_code>.<reason_code> - <message>

For structured errors, append ?errfmt=json to the endpoint:

https://api.pdfcrowd.com/convert/24.04/?errfmt=json

An example JSON error body for missing conversion input is:

{
  "status_code": 400,
  "reason_code": 325,
  "message": "There is no input specified to be converted."
}

PDFCrowd JSON errors use Content-Type: application/json. A successful request still returns an image or ZIP archive when errfmt=json is set. If a failed response has a different content type, retain its body and status for diagnosis instead of assuming it is JSON.

Common Status Codes

See all status and reason codes for specific error explanations. For request limits and retry guidance, see Limits and Retries.

Response Headers

Use these headers, when present, to record conversion results and diagnose problems:

Limits and Retries

Request rate and concurrency limits depend on your license. Control how quickly you submit conversions and how many you run at once. A 429 response concerns request rate; a 430 response concerns requests already in progress.

The maximum upload size is 300 MB.

For temporary failures, use a bounded number of retries with increasing delays. Correct invalid input, authentication, or account problems before retrying those requests.

If a conversion exceeds 60 seconds of processing time, PDFCrowd stops it and returns an error response.

Troubleshooting

Inspect a Request

Capture the HTTP status, response headers, and response body when diagnosing a request. Set debug_log to true to enable a conversion debug log, and add errfmt=json to the endpoint's query string for structured error details. Use the input and conversion settings from the request you're investigating.

curl --fail-with-body \
  -u 'demo:demo' \
  -D response.headers \
  -o response.body \
  -w 'HTTP %{http_code}\n' \
  -F url=https://your-server.com/invoice.pdf \
  -F input_format=pdf \
  -F output_format=png \
  -F debug_log=true \
  -F force_zip=true \
  'https://api.pdfcrowd.com/convert/24.04/?errfmt=json'

Check the HTTP status before interpreting the body. A successful response contains image or ZIP bytes; an unsuccessful response should be inspected for error details. If no HTTP response arrives, check the error reported by your HTTP client.

The x-pdfcrowd-debug-log header links to diagnostic information about the conversion. You can also find logs in your conversion history.

Common Problems

For help, contact support and include any available diagnostics and enough detail for us to reproduce the problem.