Render the pages of a PDF as PNG or JPG images.
PDF to Image renders the pages you choose from a PDF, uploaded or fetched from a URL, as PNG or JPG images and returns a download link for each, valid for 2 days, with its pixel size. The Free plan renders one page per call at 150 dpi; paid plans render up to 10 pages per call and can set the resolution from 72 to 300 dpi.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"pageCount": 14,
"format": "png",
"dpi": 150,
"imageCount": 2,
"expires": 1792400000000,
"images": [
{
"page": 1,
"imageName": "3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png",
"width": 1275,
"height": 1650,
"dpi": 150,
"size": 214533,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdftoimage/3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792400000&Signature=SAMPLE"
},
{
"page": 2,
"imageName": "3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-2.png",
"width": 1275,
"height": 1650,
"dpi": 150,
"size": 198207,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdftoimage/3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-2.png?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792400000&Signature=SAMPLE"
}
]
}
}
About the PDF to Image API
Pages are rendered with Poppler, the PDF engine used by most Linux desktops, so text, vector graphics, images and page rotation come out as a PDF viewer shows them. Very large pages are rendered at a lower dpi so no image exceeds 25 megapixels, and each image reports the dpi it was rendered at. Encrypted PDFs are rejected.
What people use it for
- Document Thumbnails
- Show a preview image of the first page of uploaded PDFs in file lists and search results.
- Page Previews
- Display individual pages of a contract or report as images where a PDF viewer is not available.
- OCR Pipelines
- Turn scanned PDF pages into images for the Image to Text API or another OCR step.
- Social and Email Images
- Use a page of a brochure, menu or flyer PDF as an image in posts and newsletters.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use PDF to Image
Same data, same APIVerve account, same credit balance — one key works on all of them.
How many renders does the Starter plan cover?
What does the Free plan return?
Which pages can I render?
What happens with very large pages?
How long are the images kept?
Request parameters — POST /v1/pdftoimage
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
pdfOptional | string | The PDF file to render (up to 10 MB), or a public PDF URL | |
pagesOptional | string | 1 | Pages to render, as numbers and ranges such as 1-3,5; at most 10 per call on paid plans, 1 on the Free plan default 1 · length 0-100 |
formatOptional | string | png | Image formatpngjpgjpegdefault png |
qualityOptional | integer | 90 | JPG quality from 1 to 100; ignored for PNG default 90 · range 1-100 |
dpiOptionalPremium | integer | 150 | Resolution in dots per inch, from 72 to 300 default 150 · range 72-300 |
curl -X POST "https://api.apiverve.com/v1/pdftoimage" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"pages":"1-2","format":"png","quality":90,"dpi":150}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/pdftoimage
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"pageCount": 14,
"format": "png",
"dpi": 150,
"imageCount": 2,
"expires": 1792400000000,
"images": [
{
"page": 1,
"imageName": "3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png",
"width": 1275,
"height": 1650,
"dpi": 150,
"size": 214533,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdftoimage/3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792400000&Signature=SAMPLE"
},
{
"page": 2,
"imageName": "3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-2.png",
"width": 1275,
"height": 1650,
"dpi": 150,
"size": 198207,
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/pdftoimage/3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-2.png?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1792400000&Signature=SAMPLE"
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
pageCount | number | 14 | Total pages in the PDF |
format | string | "png" | Image format (png or jpg) |
dpi | number | 150 | Requested resolution in dots per inch |
imageCount | number | 2 | Number of pages rendered |
expires | number | 1792400000000 | When the download links expire (Unix time in milliseconds) |
images | array[2] | One entry per rendered page, in the order requested | |
page | number | 1 | Page number |
imageName | string | "3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png" | File name of the image |
width | number | 1275 | Image width in pixels |
height | number | 1650 | Image height in pixels |
dpi | number | 150 | Resolution the page was rendered at; lower than requested only for very large pages |
size | number | 214533 | Image size in bytes |
downloadURL | string | "https://storage.googleapis.com/apiverve/APIData/pdftoimage/3b7e9d21-4c5a-4f80-a1d6-9e2c8b7f5a34-1.png?GoogleAccessId=635500398038-compute%4… | Signed link to download the image, valid for 2 days |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | PDF to Image calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/pdftoimage" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/pdftoimage", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/pdftoimage",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/pdftoimage");
Console.WriteLine(json);Resources
Call it from Go — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/pdftoimage", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/pdftoimage");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — POST /v1/pdftoimage
No SDK to install — this is a plain HTTPS call to /v1/pdftoimage with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/pdftoimage")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive PDF to Image form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — PDF to Image API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the PDF to Image API.
Documents
- HTML to PDF
- Invoice Generator
- Office to PDF
- PDF Merge
- PDF Page Numbers
- PDF to Image
- PDF to Text
- Website to PDF