0.5 Credits

PDF-to-WebP API for image conversion and rendering workflows

Use Nutrient DWS to convert PDF pages into WebP images when the workflow needs efficient rendered-image output instead of static PDFs. Start with a cloud PDF-to-WebP API built for previews, exports, web delivery, and image-based document workflows.

Convert PDF into WebP output

Use a PDF-to-WebP API when the workflow needs efficient rendered-image output for web delivery, previews, exports, and image-based document pipelines.

Built for API-driven rendering

Use REST, Postman, JavaScript, Python, Java, C#, PHP, or HTTP to automate PDF-to-WebP conversion inside rendering and export workflows.

Fast path from evaluation to implementation

Connect WebP rendering to getting started, pricing, and the broader image converter hub so teams can validate the right image output path quickly.

Used by Lufthansa, Disney, Autodesk, UBS, Dropbox, IBM
Lufthansa
Disney
Autodesk
UBS
Dropbox
IBM

Try it out

This example will convert your uploaded PDF file to a WebP image.


Try it out in three steps

  1. Add a PDF file named document.pdf to your project folder.
  2. Run the code from the same folder.
  3. Open result.webp to see the output.
curl -X POST https://api.nutrient.io/build \
-H "Authorization: Bearer your_api_key_here" \
-o image.webp \
--fail \
-F document=@document.pdf \
-F instructions='{
"parts": [
{
"file": "document"
}
],
"output": {
"type": "image",
"format": "webp",
"dpi": 500
}
}'

Start now

Create an account to access your API key and start with 50 free credits per month

Start building with DWS Processor API in minutes — no payment information required.

Already have an account? Sign in →


Security is our top priority

SOC 2 Type 2 audited

Nutrient’s infrastructure is SOC 2 Type 2 audited and GDPR-compliant. See our privacy policy and security documentation for details on data handling.

HTTPS encryption

All communication between your application and Nutrient is done via HTTPS to ensure your data is encrypted when it’s sent to us.

Safe payment processing

All payments are handled by Paddle. Nutrient DWS Processor API never has direct access to any of your payment data.

Frequently asked questions

What is a PDF-to-WebP API?

A PDF-to-WebP API renders PDF pages into WebP images with a single API call. With Nutrient’s DWS Processor API, you can convert PDFs to WebP without building or maintaining your own rendering infrastructure.

How do I render PDF pages as WebP from my code?

Send your PDF to the Nutrient DWS Processor API with the output format set to WebP, and it returns WebP images of the pages you requested. You can call it via REST, JavaScript, Python, Java, C#, PHP, or plain HTTP, or make your first request from the Postman collection.

When should I use WebP instead of PNG or JPG?

WebP produces smaller files than PNG or JPG at comparable quality, which makes it a good fit for web delivery, previews, and image-based document pipelines. If you need a different format, the same PDF-to-image API also renders PNG and JPG.

Which programming languages does the API support?

You can call the API from any language that can make HTTP requests, including JavaScript, Python, Java, C# (.NET), and PHP, or use REST directly with curl or a Postman collection.

Is there a free PDF-to-WebP API?

Yes. You can start for free — sign up to receive processing credits and try the PDF-to-WebP API before choosing a Processor API plan.

Ready to try it?

Create an account to get your DWS Processor API key and start making API calls.