If DocRaptor returns a PDF that looks blank, start with the job status and that document’s log—not with a guess about CSS. The log lets you compare the HTML you submitted with the HTML after JavaScript processing, review asset-loading errors, and see where generation stopped or completed. That evidence helps distinguish a failed job from a successfully generated PDF with missing content.
1. Confirm whether the conversion failed or completed
First check the API response or, for an asynchronous request, the job status and any validation errors. DocRaptor jobs may be queued, working, completed, or failed. A failed job needs error diagnosis; a completed job that opens but appears blank calls for inspection of its content and rendering path. Record the document identifier and the response details before changing the request. DocRaptor API documentation
2. Use the document log to find where content disappeared
Open the log for the affected document. Compare the submitted HTML and API parameters with the HTML after JavaScript processing. Then review asset-loading errors and the conversion pipeline stage. If expected text or markup is absent from the post-JavaScript HTML, investigate the input or script execution. If it is present, check resource loading and subsequent conversion stages. DocRaptor troubleshooting documentation
3. Check JavaScript-generated content
DocRaptor’s JavaScript execution is disabled by default. If your page creates the PDF content with JavaScript, enable the appropriate option in the request. For scripts that finish asynchronously, make rendering wait for their work to complete using DocRaptor’s documented completion mechanism or a suitable delay. Verify the post-JavaScript HTML in the document log before investigating layout; if the expected content is missing there, the renderer did not receive it in time or the script did not produce it.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Check the JavaScript and API documentation for the option and completion behavior supported by the API or client library version you use: DocRaptor JavaScript documentation and DocRaptor API documentation.
4. Verify that DocRaptor can reach every asset
Stylesheets, scripts, images, and fonts referenced by your HTML must be accessible from DocRaptor’s conversion environment—not merely from your browser or development machine. Use absolute HTTP(S) URLs, or provide a usable base URL through the API or an HTML <base> element so relative paths resolve correctly. A relative or protocol-relative URL without a suitable base may fail.
Rank #2
A resource available only at localhost on your computer is not reachable by the conversion service. For local development, send the document content directly, embed suitable resources, or make them available through a test server the service can reach. See DocRaptor’s guidance on remote assets and localhost development.
5. Surface resource errors while diagnosing
DocRaptor generally ignores resource errors by default, so a conversion can complete while omitting an image, stylesheet, font, or other dependency. During diagnosis, temporarily configure the documented behavior that fails generation when resource errors occur, then inspect the resulting error details. The API reference names ignore_resource_errors; confirm its exact spelling and support in the client library and version you use before changing a production request. Restore your intended production behavior after the investigation. DocRaptor API documentation
Rank #3
- hole punched
- high quality card stock
- 4 pages
- made in USA
- keyboard shortcuts
6. Escalate with document-specific evidence
If the log does not identify the issue, submit a Help Request from that document’s log. DocRaptor says this allows its support team to access the content and help debug the document; the details view also shows steps taken and problems encountered. Do not include API credentials in a public issue. DocRaptor support documentation
Troubleshooting by symptom
| What you see | What to check | Next step |
|---|---|---|
| The API reports failure or validation errors | Job status, response details, and document identifier | Resolve the reported request or validation issue before treating it as a blank-rendering problem. |
| The job completed, but expected content is absent from post-JavaScript HTML | Whether JavaScript is enabled and whether asynchronous work completed | Enable the relevant JavaScript option if needed, wait for completion, and check the log again. |
| HTML contains the content, but images, styles, or fonts are missing | Asset errors, URL reachability, and the base URL for relative paths | Use reachable absolute URLs or provide a usable base; temporarily fail on resource errors to expose failures. |
| Assets work in a browser but fail in conversion | Whether the URLs are reachable outside your local machine or authenticated session | Make resources accessible to the conversion service, or embed suitable content. |
| The log does not explain the result | Document details and the pipeline steps recorded in the log | Submit a Help Request from that document’s log rather than posting credentials publicly. |
Or skip the browser setup
If the task is to capture a web page as an image or PDF rather than debug a DocRaptor conversion, ScreenshotNeo provides a website screenshot API and MCP server. Its one-call API can return a screenshot or PDF:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. It accepts cookie and consent banners before capture and removes 60+ known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, no card required.
Frequently Asked Questions
Does a completed DocRaptor job guarantee that the PDF contains all expected content?
No. Resource errors may be ignored by default, so inspect the document log even when generation completes.
Can I debug an asset that only exists on my computer?
Not through a URL that resolves only to your computer’s localhost. Embed suitable content or make it reachable to the conversion service.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
