Free tools Windows power users keep installed
One-click scans. No signup required.
To install wkhtmltopdf on Windows, download the Windows installer for the stable 0.12.6 release from the official wkhtmltopdf downloads page, run it, allow the installer to add wkhtmltopdf to PATH, and open a new Command Prompt or PowerShell window. Verify with wkhtmltopdf --version, then create a test PDF. If you need a portable setup, use the matching 32-bit or 64-bit 7z archive instead.
This guide covers both installation methods, PATH repair, verification, common conversion failures, security precautions, and an API alternative when you do not want to maintain a browser-rendering installation.
Choose the right Windows package
The stable wkhtmltopdf series is 0.12.6, released on June 11, 2020. The official Windows downloads list an Installer (Vista or later) and separate 64-bit and 32-bit 7z archives.
| Package | Best for | PATH setup | Portability and removal |
|---|---|---|---|
| Windows installer | Most desktop and development installations | Can be enabled during setup | Guided installation and conventional uninstall |
| 64-bit 7z archive | 64-bit Windows deployments that need manual control | You add the executable directory yourself | Portable; remove the extracted folder to remove the files |
| 32-bit 7z archive | 32-bit Windows environments or compatibility requirements | You add the executable directory yourself | Portable; remove the extracted folder to remove the files |
Choose the installer unless you specifically need a self-contained directory, scripted deployment, or a machine where you cannot use the guided setup. Record the exact version and package architecture in deployment notes so another administrator can reproduce the installation. The project repository was archived by its owner on January 2, 2023, so pinning and documenting the binary you deploy is especially important.
#1 Best Overall
- Edit PDFs with Ease. Modify text, images, and layouts directly within your PDF documents.
- Convert & Organize. Export PDFs to Word, Excel, or ePub, and organize files with ease.
- Read & Annotate. Enjoy intuitive reading modes and powerful tools to comment, highlight, and mark up PDFs.
- Create & Manage PDFs. Create new PDFs, combine multiple files, scan documents, and compress for easy sharing.
- Fill & Sign Forms. Complete forms and digitally sign documents with secure e-signature tools.
Install with the Windows installer
- Open the official wkhtmltopdf downloads page.
- In the Windows section, select the installer marked “Vista or later.” Use the architecture appropriate for the Windows installation. If you are unsure, check Settings → System → About → System type.
- Run the downloaded installer executable. Approve the Windows security prompt if it appears.
- Accept the license agreement.
- Keep the wkhtmltopdf component selected. When the installer offers to modify the system PATH, enable that option. PATH is what lets you type
wkhtmltopdffrom any directory. - Finish the setup wizard.
- Close any existing Command Prompt or PowerShell windows and open a new one. A terminal that was open before the installation may still have the old PATH value.
The installer sequence is the simplest route because it performs the file copy and can configure PATH for you. If the PATH option was unavailable or skipped, follow the manual PATH steps below.
Install from a 7z archive
The official page also provides 32-bit and 64-bit 7z archives. This method does not run a setup wizard: you extract the files, locate the executable, and optionally add its directory to PATH.
- Download the 32-bit or 64-bit archive that matches the target Windows environment.
- Extract it to a stable location, such as
C:Program Fileswkhtmltopdf, or to another administrator-approved directory used by your deployment. - Find
wkhtmltopdf.exe. Depending on the archive layout, it may be under abinsubdirectory. - Test it with its full path. For example:
& "C:Program Fileswkhtmltopdfbinwkhtmltopdf.exe" https://example.com example.pdfIf that command creates example.pdf, the binary itself works. You can continue using the full path in scripts, or add the containing directory to PATH.
Add wkhtmltopdf to PATH manually
Add the directory that actually contains wkhtmltopdf.exe, not merely the parent folder. The graphical method works on current Windows editions:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
- EVERY PDF TOOL UNLOCKED - 30+ tools in one app: edit text and images, convert, merge, split, compress, sign, OCR, redact, watermark, batch process, and more. No feature gates, no upsells, nothing held back.
- PAY ONCE, OWN FOREVER — A one-time purchase, not a subscription. Other apps runs $240/year — Scrivar is yours for life, with free updates included.
- UNLIMITED eSIGN, BUILT IN — Send contracts and forms for signature and track every step. Recipients sign in their browser with no account or app needed. Replace DocuSign and save hundreds a year.
- PC, MAC, AND WEB — Install on any Win 10/11 PC or macOS 11+ Mac (Intel or Apple Silicon), or work in your browser at scrivar.com. Same tools, same account, everywhere you work.
- OCR + FULL OFFICE CONVERSION — Turn scanned documents into searchable, selectable text, and convert PDFs to and from Word, Excel, and PowerPoint with formatting kept intact.
- Open Start and search for environment variables.
- Select Edit the system environment variables, then click Environment Variables.
- Under User variables (for only your account) or System variables (for all users), select Path and click Edit.
- Click New and enter the executable directory, for example
C:Program Fileswkhtmltopdfbin. - Click OK on each dialog.
- Open a new PowerShell or Command Prompt window.
In PowerShell, you can inspect the PATH visible to the current session with:
$env:Path -split ';'Look for the directory containing wkhtmltopdf.exe. Do not add the path to a file itself; PATH entries are directories.
Verify the installation
Check the version
In a new terminal, run:
wkhtmltopdf --versionA working installation prints the program name and version information. Seeing 0.12.6 confirms that the intended stable series is being invoked.
Create a basic PDF
Test a simple network conversion:
wkhtmltopdf https://example.com example.pdfConfirm that example.pdf appears in the current directory and opens normally. This test checks command discovery, file output, and a basic URL render.
Rank #3
- EDIT text, images & designs in PDF documents. ORGANIZE PDFs. Convert PDFs to Word, Excel & ePub.
- READ and Comment PDFs – Intuitive reading modes & document commenting and mark up.
- CREATE, COMBINE, SCAN and COMPRESS PDFs
- FILL forms & Digitally Sign PDFs. PROTECT and Encrypt PDFs
- 1 Year License for 1 Windows & 2 Mobile (Android and/or iOS) devices.
Separate installation problems from URL problems
If the URL test fails, create a tiny local file and convert it:
<!doctype html>
<html><body><h1>wkhtmltopdf test</h1></body></html>Save that text as test.html, then run:
wkhtmltopdf "C:pathtotest.html" test-local.pdfA successful local conversion indicates that the executable and output permissions are working; investigate network access, certificates, or page rendering separately for a failing URL.
Fix “wkhtmltopdf is not recognized”
- Use the full path first. Run the executable directly, such as
& "C:Program Fileswkhtmltopdfbinwkhtmltopdf.exe" --version. If this works, the installation is present and the issue is command discovery. - Check the PATH directory. Ensure the PATH entry points to the folder containing
wkhtmltopdf.exe. An entry one level too high will not work. - Start a new terminal. PATH changes are read when a process starts; close and reopen Command Prompt, PowerShell, or the terminal inside your editor.
- Check which copy is being used. In PowerShell, run
Get-Command wkhtmltopdf. This reveals the resolved executable and helps detect an older copy earlier in PATH. - Check architecture and extraction. Confirm that the archive was fully extracted and that you selected the intended 32-bit or 64-bit package.
Common conversion failures and remedies
The command runs but the PDF is blank
First convert a local, simple HTML file. If the local file works, the target page may depend on network resources or client-side rendering that did not complete. Test a simpler URL and verify that the machine can reach the site.
A URL cannot be loaded
Check the URL in a normal browser on the same machine, then test the local file. Differences usually point to network access, certificate validation, authentication, or page-specific rendering rather than PATH.
Rank #4
- PDF editor for all cases - fully edit, merge, create, compare, reduce PDFs, edit page structure
- incl. NEW OCR module: for text and image recognition in scanned documents
- Merge several PDF documents into one document
- Edit text and images directly in the document
- NEW in version 2: 4K and 8K resolution
The output file cannot be created
Write to a directory where the current user has permission, use an explicit output path, and check that the destination PDF is not already open or locked by another process.
The executable works only in one shell
Compare $env:Path in PowerShell with the PATH shown by a newly opened Command Prompt. A user PATH entry and a system PATH entry can differ. Add the directory at the scope required by the account that runs the job, then restart the process that launches wkhtmltopdf.
Security warning for automated and server use
The official downloads page warns: “Do not use wkhtmltopdf with any untrusted HTML – be sure to sanitize any user-supplied HTML/JS, otherwise it can lead to complete takeover of the server it is running on!”
Treat HTML and JavaScript supplied by users or external systems as hostile. Sanitize it before conversion, run the process with the least privilege practical, and restrict outbound network access when your workflow does not need arbitrary URLs. Do not assume that a headless executable is a security boundary.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsBest Value
![Corel PDF Fusion - PDF Creator Toolkit [PC Disc]](https://m.media-amazon.com/images/I/51YTjW7jL6L._SL160_.jpg)
- Assemble, edit, and create PDFs with this easy to use, all in one PDF creator
- Open and view over 100 file types, without purchasing additional software
- Drag and drop multiple different file types into one PDF document
- Easily add new text and comments to PDFs
- Share your created documents with anyone in PDF, PDF/A, XPS or Microsoft Word formats
Operational guidance for repeatable deployments
- Pin the 0.12.6 binary and record whether it is the installer, 32-bit archive, or 64-bit archive.
- Store the executable in a stable path rather than a temporary extraction directory.
- Use an explicit full path in scheduled jobs until PATH has been verified for the service account.
- Keep a startup check that runs
wkhtmltopdf --versionand reports failures before processing a large queue. - Test both a local HTML document and a representative URL after installation or after moving the binary.
Or skip the browser setup
If your goal is a clean website screenshot or PDF rather than maintaining a Windows rendering binary, ScreenshotNeo provides a website screenshot API and MCP server. A single request returns PNG, JPEG, WebP, or PDF output. See the ScreenshotNeo documentation for the complete option list.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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}`);Before capture, ScreenshotNeo accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and each response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server lets Claude, Cursor, and other MCP clients call take_screenshot, get_page_info, and capture_pdf.
Every feature is included on every plan. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. You can sign up for the free ScreenshotNeo plan and test the workflow without installing a browser-rendering tool.
The Bottom Line
For a conventional Windows installation, use the 0.12.6 installer, enable PATH, open a new terminal, and verify with a version check plus a small conversion. Use the 7z archive when portability or manual control matters, and never feed unsanitized user HTML or JavaScript to wkhtmltopdf.
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.
