PDFCrowd Image Quality Settings: How to Keep Web Images Sharp in PDFs

To keep web images sharp in a PDFCrowd HTML-to-PDF PDF, choose image_dpi for the document’s destination, keep jpeg_quality high when clarity matters, and start with a sufficiently detailed source image. PDFCrowd’s image_dpi option only downsamples; it cannot make a low-resolution image sharp by upscaling it. Higher DPI can retain more detail but usually increases PDF size. PDFCrowd’s HTML-to-PDF parameter reference documents these settings and its recommendations.

1. Choose image resolution for the PDF’s destination

PDFCrowd’s current reference suggests these image_dpi values by use case. They are vendor recommendations, not a guarantee that every source image will look sharp at every output size.

PDF use	Suggested image_dpi	Trade-off
Professional printing	300	Retains more image detail for print; can increase file size.
Everyday documents	150	A middle ground for ordinary document use.
Screen-only viewing	96	Lower resolution can make the PDF smaller, with less image detail.
Web distribution	72	Prioritizes a smaller file for online delivery over fine detail.
Preserve source resolution	0	PDFCrowd preserves the input image resolution rather than downsampling it.

If maximum image fidelity is the priority, use 0 to preserve the source resolution. If output size is more important, select a lower value appropriate to the destination. The setting only downsamples: raising it does not add missing pixels to a small source image.

2. Set JPEG quality and handle transparency deliberately

PDFCrowd documents jpeg_quality as an integer from 1 to 100, with a default of 100. Higher values favor JPEG visual quality and generally produce larger files. For output where clarity matters, retain 100 unless you have a specific reason to compress. PDFCrowd suggests 70–85 for web distribution. It cautions that values of 50–60 favor file size over clarity and settings below 60 can cause blockiness and color banding.

JPEG does not support transparency, so take care if you enable image conversion with convert_images_to_jpeg:

• none (the default): preserve source image formats.
• opaque: convert only non-transparent images to JPEG.
• all: convert transparent images too. Their transparent regions take the PDF page background color.

Use none to preserve formats, or opaque if you want JPEG conversion without changing transparent images. Choose all only if replacing transparency with the page background is acceptable.

3. Configure a complete HTML-to-PDF request

These examples use the PDFCrowd HTML-to-PDF client for the chosen language. Supply your API credentials through the environment variables the client expects, and follow the matching client’s official setup instructions before running the snippet. Replace the example address with a page you are authorized to convert. The key settings shown are image_dpi, jpeg_quality, and convert_images_to_jpeg.

cURL

curl -u "USERNAME:API_KEY" \
  -F "url=https://example.com" \
  -F "image_dpi=300" \
  -F "jpeg_quality=100" \
  -F "convert_images_to_jpeg=none" \
  -o page.pdf \
  https://api.pdfcrowd.com/convert/24.04/

Check PDFCrowd’s current HTTP API documentation for the endpoint and authentication format applicable to your account before using this illustrative request.

Python

import os
import pdfcrowd

client = pdfcrowd.HtmlToPdfClient(
    os.environ["PDFCROWD_USERNAME"],
    os.environ["PDFCROWD_API_KEY"],
)
client.setImageDpi(300)
client.setJpegQuality(100)
client.setConvertImagesToJpeg("none")
client.convertUrlToFile("https://example.com", "page.pdf")

Node.js

const pdfcrowd = require("pdfcrowd");

const client = new pdfcrowd.HtmlToPdfClient(
  process.env.PDFCROWD_USERNAME,
  process.env.PDFCROWD_API_KEY
);
client.setImageDpi(300);
client.setJpegQuality(100);
client.setConvertImagesToJpeg("none");
client.convertUrlToFile("https://example.com", "page.pdf", (err) => {
  if (err) {
    console.error(err);
    return;
  }
  console.log("Saved page.pdf");
});

Client method names, package setup, and endpoint versions can vary. Use PDFCrowd’s official parameter reference and language-specific client documentation to confirm the exact interface for your installed client. Store credentials in environment variables or a secret manager; do not put them in source code committed to a repository.

4. Diagnose blur by conversion direction

First establish which operation produced the result. HTML-to-PDF, PDF-to-HTML, and WebSave image capture use different controls; a similarly named setting from one workflow does not necessarily apply to another.

HTML-to-PDF

• Set image_dpi based on output purpose. Lower it only when smaller files are worth reduced image detail.
• Inspect the source image at its rendered size. A tiny or already blurry source remains limited; image_dpi does not upscale it.
• Keep jpeg_quality high if the conversion uses JPEG and visual clarity is more important than size.
• Check whether convert_images_to_jpeg=all changed transparent areas to the page background.

PDF-to-HTML

This is the opposite conversion direction, and its controls differ. PDFCrowd’s troubleshooting guidance distinguishes page scale from image resolution: adjust scale_factor when the overall page scale is wrong, and dpi when rendered images are blurry. Do not apply HTML-to-PDF’s image_dpi setting to this workflow. If images are missing, check the image mode and preserve the relative paths of extracted resources when using separate files. See the PDFCrowd PDF-to-HTML documentation.

WebSave screenshot image

WebSave has separate image-output controls, including output_format, screenshot_width, and jpeg_quality. Its documentation demonstrates JPG, width 1600, and quality 85 as an example configuration. Those are example values for screenshot-image output, not universal PDF settings or a guaranteed optimum. See PDFCrowd’s WebSave as Image documentation.

5. Troubleshooting checklist

Symptom	Likely cause	What to check
Images look soft in an HTML-to-PDF file	The source is small or blurry, or output resolution/compression reduces visible detail.	Inspect the source. Try image_dpi=0 to preserve input resolution and keep jpeg_quality=100 where applicable.
The PDF is much larger than expected	Higher image resolution or quality retains more data.	Choose a lower image_dpi suitable for the destination; lower JPEG quality only as much as acceptable.
Transparent graphics have a solid background	convert_images_to_jpeg=all converted transparency to the PDF page background.	Use none or opaque if preserving transparent images is needed.
PDF-to-HTML output has the wrong scale	Page scale and image resolution are separate controls.	Check scale_factor for page scale and dpi for image resolution.
Images are missing from PDF-to-HTML output	Image mode or extracted resource paths may be wrong.	Check the image mode and preserve relative paths when using separate files.
A WebSave image looks different than expected	Screenshot-image settings are being confused with PDF conversion options.	Check output_format, screenshot_width, and jpeg_quality in the WebSave documentation.

6. Performance, reliability, and file size

Resolution and compression are quality-versus-size choices. More retained image data can increase output size; reducing DPI or JPEG quality can reduce it while sacrificing detail. PDFCrowd’s reference does not promise a universal size or sharpness outcome for a given setting, because results depend on the source and document.

For repeatable output, record the conversion direction and the selected resolution, JPEG quality, and conversion mode alongside your document workflow. Keep the original source assets when possible, so a later conversion can use a better source rather than trying to recover detail from a compressed PDF. When diagnosing a change, alter one relevant setting at a time and compare the output at the intended viewing or print size.

7. Capture a page as an image instead of making a PDF

If the deliverable is a screenshot image rather than a PDF, ScreenshotNeo is a separate option: ScreenshotNeo is a website screenshot API and MCP server. It returns PNG, JPEG, or WebP images, or a PDF, from a GET request. For an image capture, the one-call request below saves the response as WebP. See the ScreenshotNeo API documentation for request options.

cURL

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 also supports PDF output and image options including full-page capture, device and viewport selection, retina scale, custom CSS, and waiting for page elements. Its API accepts parameter names used by other screenshot APIs, which can make switching simpler. Clean captures remove known consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing, with verdict and billing details in response headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents.

Or skip the browser setup

Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

Sign up free for ScreenshotNeo and get 1,000 screenshots a month with no card.

8. FAQ

Can I make a small source image sharp by setting a very high DPI?

No. PDFCrowd says image_dpi downsamples and does not upscale low-resolution images. Start with a source that has enough detail at its displayed size.

Should I always set image_dpi to 300?

No. PDFCrowd suggests 300 DPI for professional printing, but gives lower recommendations for everyday documents and screen or web use. Choose according to the destination and desired file size.

Does jpeg_quality affect PNG images?

It concerns JPEG quality. Whether an image is converted to JPEG depends on convert_images_to_jpeg; its default is none, which preserves source formats.

Where can I confirm current parameter names and defaults?

Check the official HTML-to-PDF parameter reference and the documentation for the specific PDFCrowd client you use. Defaults and interfaces may change.