WeasyPrint 70.0 is the clearest documented choice if CSS custom properties are essential: its current stable API reference explicitly confirms support for custom properties and var(). DocRaptor using Prince 13, Pipeline 8 is another documented option, but that support was announced in 2020 and you must verify that your account or API request uses the relevant pipeline. Neither feature claim guarantees that an entire browser-oriented stylesheet will render as intended.
What to use if CSS variables must appear in the PDF
Start with WeasyPrint 70.0 when you want a currently documented, explicit statement of CSS custom-property support. Its API reference says custom properties and var() notation are supported: WeasyPrint stable API reference.
As an Amazon Associate I earn from qualifying purchases.
DocRaptor is a second documented choice when its Prince 13 Pipeline 8 is selected. DocRaptor’s release note dated October 21, 2020, says Prince 13 added support for CSS variables and explains that the pipeline must be selected; existing users were advised to test and upgrade rather than assume automatic migration: DocRaptor’s Prince 13 release note.
| Converter | What is documented | What to verify |
|---|---|---|
| WeasyPrint 70.0 | Its current stable API reference explicitly confirms custom properties and var(). |
Test the rest of your stylesheet: the same documentation describes limits in areas including right-to-left/bidirectional text and aspects of flexbox and grid. |
| DocRaptor with Prince 13 / Pipeline 8 | DocRaptor’s October 21, 2020 release note says Prince 13 introduced CSS-variable support in Pipeline 8. | Confirm the pipeline selected for your account or API requests. Do not assume an existing integration uses it. |
| Prince | The official Prince 15 guide describes HTML/XML-to-PDF conversion using CSS. | The guide excerpt does not independently establish which Prince version introduced custom-property support. Use DocRaptor’s dated note for the Prince 13 claim. |
| PDFreactor 12.7.1 | The reviewed manual documents HTML5 parsing, HTML-and-CSS rendering, and configurable CSS validation/support-query behavior. | The reviewed material does not explicitly verify custom-property support. Check the relevant current support entry or test it; do not infer support from general CSS rendering. |
Sources: Prince 15 user guide and PDFreactor manual.
#1 Best Overall
- Convert your PDF files into Word, Excel & Co. the easy way
- Convert scanned documents thanks to our new 2022 OCR technology
- Adjustable conversion settings
- No subscription! Lifetime license!
- Compatible with Windows 11, 10, 8.1, 7 - Internet connection required
How CSS variables work—and what a converter must support
CSS custom properties are commonly declared with names such as --brand-color and used through var(--brand-color). They participate in the cascade and can inherit. A fallback such as var(--brand-color, #2457a7) supplies a value when the property is missing or invalid in an implementation that supports custom properties. A fallback does not make an unsupported renderer understand var(). See MDN’s guide to using custom properties.
For example, this is a useful minimal check, not proof that a complex production layout will work:
Rank #2
- Transform audio playing via your speakers and headphones
- Improve sound quality by adjusting it with effects
- Take control over the sound playing through audio hardware
:root {
--brand-color: #2457a7;
}
h1 {
color: var(--brand-color, #333333);
}
Test the actual template with its real variable scopes and fallback patterns. Also include linked stylesheets, fonts, print-media rules, page breaks, and the layout features the document depends on. This is a practical compatibility check, not a cross-product benchmark: the sources cited here do not establish comparative rendering results.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →How to choose between the documented options
Choose WeasyPrint when explicit current documentation matters
WeasyPrint 70.0 has the most direct current documentation for the specific requirement in this comparison: its stable API reference expressly names custom properties and var(). Treat that as a feature-level confirmation, not a promise of browser-equivalent output. Check its current feature documentation against your use of grid, flexbox, text direction, fonts, and other layout behavior.
Rank #3
- The Data Recovery Stick requires no technical skills — simply plug it into your Windows computer, click Start, and the software automatically begins scanning and recovering lost files within minutes. Compatible with Windows Vista, 7, 8, 10, & 11, it's designed to be a reliable first step when accidental deletion occurs.
- Recover photos (JPG, BMP, PNG, TIFF), Microsoft Office documents (Word, Excel, PowerPoint, Publisher, Access), Open Office files, MP3 music files, PDFs, RTF documents, AutoCAD files, and HTML web pages. Whether it's personal memories or critical business files, the Data Recovery Stick covers the file types that matter most.
- Works with hard drives, USB drives, SD cards, memory sticks, and other common storage formats that use FAT or NTFS file systems — making it a single solution for hard drive recovery, USB drive recovery, SD card recovery, and more. Note: a media reader is required for micro SD cards and some mass storage devices.
- No Installation Required - The Data Recovery Stick runs entirely from the USB drive with no software installation on your computer — helping prevent new data from overwriting the files you're trying to recover. This also makes it ideal for use across multiple computers or in emergency situations where installation isn't practical.
- Use the Data Recovery Stick on as many computers as often as needed — simply clear the recovered data between uses to free up storage space. Software updates keep the tool compatible with newer systems and devices, backed by 25+ years of data software expertise from Paraben Consumer Software.
Choose DocRaptor only after confirming its pipeline
DocRaptor’s Prince 13 / Pipeline 8 announcement is specific and useful, but dated. Verify the engine pipeline in the current account configuration or API request, and render a representative document before switching production traffic. The release note says existing users needed to test and upgrade; the feature should not be assumed for every DocRaptor job.
Keep Prince and PDFreactor claims within what is documented
The Prince 15 guide establishes that Prince converts HTML and XML to PDF with CSS, but the reviewed guide excerpt does not independently date its custom-property support. The reviewed PDFreactor 12.7.1 manual establishes HTML5 and CSS rendering and configurable validation/support queries, but does not explicitly confirm custom properties. For either, consult the current feature entry or run a focused test before relying on variables.
Rank #4
- Export or Convert Text, HTML, PNG, JPG, or Camera Pictures to PDFs
- Unlimited use
- No ads
- No personal data taken
- GDPR compliant
Compare operational fit separately
Variable support is only one selection criterion. Establish whether you need a local renderer or hosted service, which runtime and integration model fit your system, and whether your security and scale requirements are met. The material cited here does not establish a comprehensive current price or performance comparison, so obtain those details from vendors rather than inferring them.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Validate the PDF before deployment
- Pin the renderer and configuration. Record the exact WeasyPrint version or, for DocRaptor, the selected Prince pipeline. This makes later rendering differences diagnosable.
- Build a representative fixture. Include inherited and locally scoped custom properties, missing-variable fallbacks, linked CSS and fonts, print rules, page breaks, and production layout features.
- Render and inspect the PDF. Check not only whether the variable-driven color or value appears, but also pagination, font loading, directionality, and layout.
- Test changes before rollout. Re-render the same fixture after an engine or template change and compare the output against the expected result.
Why CSS variables may be missing from a PDF
- The renderer does not implement custom properties. A
var()fallback only helps when the implementation supports custom properties; it cannot add support to an incompatible engine. - The property is unavailable in the relevant cascade or inheritance scope. Check where the
--nameis declared and whether the element usingvar(--name)inherits it. MDN documents the cascade, inheritance, and fallback behavior in its custom properties guide. - The expected DocRaptor pipeline is not active. Verify the configured pipeline rather than assuming an existing account or request was upgraded.
- A different part of the stylesheet is unsupported or behaves differently in print output. Isolate the variable test, then check the renderer’s feature documentation for the grid, flexbox, text-direction, font, or pagination behavior your document uses.
Or skip the browser setup
ScreenshotNeo is a screenshot API, not an HTML-to-PDF renderer, so it is an alternative when the deliverable can be a webpage screenshot rather than a paginated PDF. A single request captures a URL as PNG, JPEG, WebP, or PDF. For PDF work that specifically depends on CSS-variable fidelity, keep using a PDF renderer and validate the output as described above.
Best Value
- Mix an audio, music and voice tracks
- Record single or multiple tracks simultaneously
- Intuitive tools to split, trim, join, and many other editing features
- Loaded with audio effects including EQ, compression, reverb, and more.
- Load an audio file and export to all popular audio formats from studio quality wav to high compression formats
For a one-call capture of a page, see the ScreenshotNeo API documentation:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
ScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; these steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with response headers identifying the page verdict and billing status. Its MCP server offers screenshot and PDF tools for AI agents. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Frequently Asked Questions
Does a fallback in var() make a CSS-variable-incompatible converter work?
No. A fallback provides a value only in an implementation that supports custom properties; it does not add that feature to an incompatible renderer.
Is ScreenshotNeo a direct replacement for an HTML-to-PDF converter?
Not when you need a paginated PDF whose output depends on CSS custom properties. ScreenshotNeo is useful when a screenshot or URL-to-PDF capture meets the need; it does not replace validation in a dedicated PDF renderer.
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.




