PDFCrowd Review: How Well Does It Convert Websites to PDF?
PDFCrowd converts public webpages, HTML, and uploaded files to PDF. See its controls, limits, common failure points, and when a screenshot API may fit better.
PDFCrowd can convert a public webpage, an HTML string, or an uploaded HTML file into a PDF. It offers a one-time browser converter as well as an API and website integrations. Its API gives developers control over page size, margins, print styles, scripts, headers and footers, and selected page content. How well a particular site converts depends on whether PDFCrowd can retrieve the page’s assets and dynamic content, and whether the chosen settings suit the page.
This review explains how to choose a PDFCrowd workflow, what its documented controls and operating limits mean, how to evaluate output, and what to try when a conversion is incomplete. No hands-on conversion was performed for this article, so it does not claim a measured success rate or speed.
What PDFCrowd does and which route to use
PDFCrowd turns web content into PDF through several routes. Choose based on who initiates the conversion and where the source content is available.
| Route | Good fit | What to consider |
|---|---|---|
| Online converter | A person converting a page occasionally | Convenient for one-off browser use; less suited to an application-controlled workflow. |
| HTTP API | A developer generating PDFs from an application or script | Accepts a public URL, HTML content, or an uploaded HTML file/archive. It uses HTTP Basic authentication and form fields. |
| WordPress plugin | A site owner who wants conversion integrated with WordPress | Useful when the conversion starts from a WordPress site. |
| WebSave button | A site owner offering a website conversion button | Adds a conversion route associated with a website. |
| Zapier or Make | A workflow builder connecting conversion to automation | Useful when a no-code automation should trigger the conversion. |
PDFCrowd’s [online converter and product overview](https://pdfcrowd.com/) describe its browser and integration routes. Its [API product page](https://pdfcrowd.com/api/) and [API documentation](https://pdfcrowd.com/api/html-to-pdf/) are the primary references for programmatic conversion and configuration.
How the API request works
The API accepts a public URL, HTML supplied as content, or an uploaded HTML file. A successful call returns PDF bytes in the response body. Authentication for PDFCrowd uses an API username and API key with HTTP Basic authentication; this is separate from any credentials needed to access the source website. The API accepts form fields rather than a JSON request body.
For a URL source, the page must be reachable from PDFCrowd’s servers. A URL pointing to a developer’s own localhost is not reachable from that remote service. For local content, send the HTML or upload a file instead. If an HTML file depends on local stylesheets, images, or fonts, include the supporting resources in an archive as described in the [API guide](https://pdfcrowd.com/api/html-to-pdf/).
Use the current official API documentation for the exact endpoint, required credential names, and input-specific form fields. Those names are deliberately not guessed here. The general request shape is:
POST the documented PDFCrowd API endpoint
Authentication: HTTP Basic (PDFCrowd username and API key)
Content-Type: application/x-www-form-urlencoded (or multipart form for file upload)
Form fields: URL, HTML content, or uploaded HTML file, plus conversion options
Response: PDF bytesThe API reference includes examples and the current endpoint for each supported client. Follow those examples directly so that credentials and parameter names match your account and API version.
Controls that affect the result
PDF conversion is a rendering task as well as a file-generation task. The key question is not only whether the API returns a PDF, but whether the document contains the intended content in a readable layout.
| Control area | Why it matters | How to evaluate it |
|---|---|---|
| Page size and margins | These determine how much content fits on each page and how text wraps. | Check text size, clipped edges, and page breaks on representative long and short pages. |
| Print media and CSS | Some sites provide print-specific styling that hides navigation or changes layout. | Compare output with print styling enabled and disabled if the page has a print stylesheet. |
| Headers and footers | Can add context such as page numbers or document labels. | Check that they do not overlap the page content or consume too much space. |
| JavaScript and wait conditions | Dynamic pages may need time or scripts to reveal content. | Confirm that the content has loaded before capture. Disabling JavaScript also prevents lazy-loaded images and AJAX content from loading. |
| Selected page element | Useful when only an article or content panel should be included. | Verify that the selected element includes required headings, images, and footnotes. |
| Images, fonts, iframes, and ad networks | Remote resources can affect completeness and page layout. | Check resource availability and the documented controls for enabling or disabling these resource types. |
| Custom CSS and JavaScript | Can adapt page presentation or behavior for conversion. | Keep changes narrow and confirm they do not hide required content or make rendering less predictable. |
The [API parameter reference](https://pdfcrowd.com/api/html-to-pdf/) documents these configuration areas. They offer ways to improve readability or work around layout problems, but they do not guarantee identical rendering for every site.
A practical way to review PDFCrowd output
- Pick representative pages. Include the actual types of pages your workflow needs: long articles, pages with tables, pages with images, and pages that load content dynamically.
- Confirm the source is accessible. Check whether the page is public, whether required assets load remotely, and whether it needs site-specific authentication, cookies, or headers.
- Choose the correct input route. Use a URL for a page PDFCrowd can reach, HTML content for generated or local markup, and a file or archive when local assets must travel with the source.
- Set the page layout deliberately. Choose page size and margins, then inspect wrapping, scale, page breaks, and headers or footers in the result.
- Check dynamic content. Test the page with the relevant JavaScript and wait behavior. Make sure lazy-loaded images, AJAX sections, and embedded content appear when needed.
- Inspect the whole document. Look for missing stylesheets, images, fonts, tables, article sections, or content that runs across a page break. Do not judge only by whether a PDF file was returned.
- Repeat with production-like inputs. A successful public article conversion does not establish that a protected page or a page with different scripts and assets will behave the same way.
PDFCrowd’s [FAQ](https://pdfcrowd.com/faq/) specifically addresses missing content and resource problems. Its troubleshooting topics include stylesheets, images, JavaScript, fonts, page breaks, and missing content.
Limits and edge cases to account for
- Remote access: URL inputs must be accessible from PDFCrowd’s servers. A local
localhostaddress or an intranet-only host will not become public merely because it is sent as a URL. - Protected pages: PDFCrowd API credentials authenticate the API request. They do not automatically authenticate the converter to the source website. Use the documented source-page credentials, cookies, or custom headers when applicable, and confirm the page allows the converter to retrieve it.
- Local files: Local HTML and its associated resources need to be submitted as content or files; a remote converter cannot read paths on your workstation. Bundle dependent resources as supported by the API.
- Upload size: The API guide documents a maximum upload size of 300 MB. Large archives may also take longer to transfer and process.
- Processing duration: The service stops conversions that take longer than 60 seconds. Increasing the client-side timeout does not remove this server-side limit.
- Rate and concurrency: Limits depend on the license. Check the current account terms if you need parallel jobs or sustained production volume.
- Asset failures: If the converter cannot fetch a stylesheet, image, font, or script, the PDF can be incomplete or styled differently. A successful response is not proof that every source resource loaded.
These constraints are documented in the [PDFCrowd API guide](https://pdfcrowd.com/api/html-to-pdf/). Check the live documentation and your current plan before designing around a specific quota or limit.
Common problems and fixes
| Symptom | Likely cause | What to try |
|---|---|---|
| Request cannot authenticate | The PDFCrowd username or API key is missing, incorrect, or sent using the wrong authentication scheme. | Use HTTP Basic authentication with the API credentials and check the current API example. Keep these credentials distinct from any source-site login. |
| URL conversion cannot reach the page | The source is local, private, blocked, or otherwise inaccessible from PDFCrowd’s servers. | Use a publicly reachable URL, provide supported source credentials, or submit the HTML/file instead. A remote service cannot fetch your local localhost. |
| PDF is missing images or styles | Assets may be inaccessible, use local paths, or fail to load during rendering. | Check asset URLs and access requirements. For local HTML, package supporting files with the HTML. Review PDFCrowd’s diagnostics and FAQ. |
| Dynamic sections are blank | Content may depend on JavaScript, AJAX, or delayed rendering; JavaScript may have been disabled. | Enable the required scripts and configure an appropriate documented wait condition. Disabling JavaScript also blocks lazy-loaded images and AJAX content. |
| Output has awkward page breaks | The page size, margins, print CSS, or content’s own break behavior may not fit the PDF layout. | Adjust page setup and print styling, then inspect the affected sections across multiple pages. |
| Conversion stops after a long wait | The server-side processing limit is 60 seconds, or the page is waiting on slow or unresolved resources. | Reduce unnecessary resources or simplify the source, and avoid assuming that a longer client timeout will extend the server limit. |
| Requests are throttled or jobs cannot run concurrently | The account’s license has rate or concurrency limits. | Check the current license limits and schedule or queue work to stay within them. |
| Output is a PDF but content is still missing | Some resources or page content failed even though document generation completed. | Inspect the document itself and use the API’s error output and diagnostics. Check missing-content guidance in the official FAQ. |
Performance, reliability, and cost considerations
PDFCrowd’s documented 60-second processing stop, 300 MB maximum upload, and license-dependent rate and concurrency limits are the concrete operating constraints to plan around. For a production workflow, keep representative conversions in a review set, inspect returned files for expected content, and account for the possibility that a source page or one of its dependencies is unavailable. The documentation does not establish a universal conversion speed or guarantee that a particular page will render completely.
PDFCrowd’s current plan entitlements and prices were not verified for this review. A 2021 TechRadar review described its then-current free option and pricing, but those observations are historical and should not be treated as current. Check the [live PDFCrowd product and plan pages](https://pdfcrowd.com/) before estimating spend or relying on a specific allowance.
When deciding whether PDFCrowd fits, estimate the number and size of conversions, whether jobs need to run concurrently, how often source assets fail, and how much engineering time is available to diagnose layout issues. The right configuration is page-specific; a small sample using your real source pages is more useful than assuming that a general conversion setting will work everywhere.
What the independent review says
TechRadar’s Stefan Ionescu published a review on November 23, 2021. It praised ease of use and speed for straightforward conversion, while describing the service as less suited to users needing advanced PDF features. The review’s assessment is dated; its pricing and free-tier observations are not current evidence. The reviewer summarized the product as “a special PDF converter aimed at users who want to use HTML as their input.” Read the [TechRadar review](https://www.techradar.com/reviews/pdfcrowd-file-converter) with its publication date in mind.
ScreenshotNeo: an alternative for screenshot output
PDFCrowd is designed to create PDFs from webpages and HTML. If the deliverable you need is a rendered website screenshot instead of a paginated PDF, try ScreenshotNeo first. It is a website screenshot API and MCP server for developers. It returns PNG, JPEG, WebP, or PDF from one GET request, and supports full-page captures, CSS-selector element captures, device and viewport options, custom CSS and JavaScript, cookies and headers, wait conditions, and PDF settings. See the ScreenshotNeo API documentation for the request options.
ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response identifies the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo has 1,000 screenshots a month free with no card. Paid plans start at $5 for 3,000 screenshots; every feature is on every plan. Create a free ScreenshotNeo account to start with 1,000 screenshots a month at no charge and no card.
Frequently asked questions
Can PDFCrowd convert a page on my computer?
Not by passing a local localhost URL to the remote API. Submit the HTML content or upload the HTML and its supporting files using a documented input route.
Does a successful response mean the PDF is complete?
No. Inspect the returned document for missing content and assets; resource failures can affect the output even when a PDF is generated.
Is PDFCrowd suitable for recurring application workflows?
It offers an API and integrations for recurring workflows. Check the license-specific rate and concurrency limits and test representative pages before relying on it at production volume.
Are the prices in the 2021 review current?
No. They describe the reviewer’s historical observations. Check PDFCrowd’s live plan information for current pricing and allowances.
