Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →If a Base64 image is missing from a wkhtmltopdf PDF, first check that image loading is not disabled, then test the exact data URI in a minimal HTML file using the same wkhtmltopdf binary and command options. If the command uses --print-media-type, compare it with a run without that flag and check whether the image is present only in print-specific CSS. These checks narrow the cause; no single fix is established for every Base64 rendering failure.
Why is my Base64 image not showing in wkhtmltopdf?
A missing image can come from several different layers: the data URI or image itself, the HTML or CSS that selects it, the wkhtmltopdf command options, or behavior tied to a particular build. A report involving images generally is not proof that Base64 images have the same cause. Diagnose with the exact input and installed binary rather than changing several settings at once.
The wkhtmltopdf command-line manual says image loading is enabled by default and documents --no-images as the option that disables it. Local-file access options are a separate concern: they govern access to local resources and are not an established fix for an inline data: URI. See the wkhtmltopdf command-line documentation.
Start with a reproducible test
Record the environment and command
Before editing the HTML or upgrading, capture the exact command and environment. Include the full output of wkhtmltopdf --version, your operating system, how wkhtmltopdf was installed, and whether the build reports patched Qt. Preserve every command-line option, especially --no-images and --print-media-type. This information is useful both for diagnosis and for a project report: the project’s support guidance requests the version and a detailed, reproducible example. Review the project’s issue-reporting guidance.
Recommended Free Tools
#1 Best Overall
Reduce the page to one image
Save a minimal HTML file containing a single <img> whose src is the exact data URI from the failing page. Use the original image payload and its declared media type; do not silently replace either during the test. Open the same file in a browser and render it with the same wkhtmltopdf binary. If the browser also fails, investigate the markup and data URI first. If only wkhtmltopdf fails, the comparison points toward a renderer, command, CSS, or build-specific difference.
For example, the structure should be as simple as <img src="data:image/png;base64,PASTE_THE_EXACT_ENCODED_PAYLOAD_HERE">. The text in that example is an instruction, not a valid image payload. Confirm independently that your actual payload and media type correspond to the original image. A successful browser display does not by itself establish that every aspect of the wkhtmltopdf input is equivalent.
Change only one variable per comparison
Keep the HTML, image, output path, and binary fixed while comparing one factor at a time: the image source, --print-media-type, or the wkhtmltopdf build. This makes the result interpretable. If you change the image and upgrade simultaneously, for instance, a successful PDF will not tell you which change mattered.
Check image loading and print-specific CSS
Make sure images have not been disabled
Inspect the complete command for --no-images. The manual lists image loading as enabled by default, so you generally do not need a separate enable flag; remove --no-images if it is present and rerun the minimal case. Check wrapper or application configuration too, because a library may construct the final command on your behalf.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Compare print media on and off
If your command includes --print-media-type, run the same minimal input without it. Then inspect whether CSS in @media print hides, replaces, or introduces the image. One issue report for wkhtmltopdf 0.12.5 describes an image referenced only in print-media CSS that did not render; the reporter described also referencing it in default media as a workaround. That is a case-specific report, not a guaranteed fix for Base64 data. Read the 0.12.5 print-media issue.
A separate report describes images missing with --print-media-type in 0.12.6 with patched Qt on macOS 12.6.1. It does not establish a Base64-specific cause or a universal resolution. Treat it as a reason to test the flag and build combination, not as proof that either is responsible for your page. Read the 0.12.6 report.
Keep local-file permissions in the right diagnostic branch
Options such as --disable-local-file-access and --enable-local-file-access concern access to local files. They matter if the HTML references a file path, stylesheet, or other local resource. An inline Base64 image is embedded in the HTML, so changing local-file access is not an established direct fix for it. Do not broaden filesystem access just to troubleshoot an inline URI.
When rendering untrusted HTML, filesystem access is also a security boundary, not merely a convenience setting. The project’s AppArmor guidance discusses limiting filesystem access and cautions against using wkhtmltopdf on untrusted content without safeguards. Read the wkhtmltopdf AppArmor guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Test whether the installed version or build matters
Once the minimal case is stable, compare it with a newer appropriate wkhtmltopdf build if your installed build is old or the failure appears build-specific. Keep the test controlled and record the exact version and build details for each run. An old Stack Overflow answer reports that upgrading fixed one Base64-image problem, but that is an anecdotal lead, not evidence that a particular release fixed all such failures. See the reported upgrade case.
Rank #4
The available evidence does not identify a release where a general Base64 rendering defect was fixed, establish which formats your binary supports, or prove that your payload is valid. If the minimal file still fails, retain it as the basis for further diagnosis rather than assuming an upgrade or a permission change is the answer.
Troubleshoot by symptom
| What you observe | What to check next | What the result tells you |
|---|---|---|
| The image is missing in both browser and PDF | Recheck the exact data URI, embedded payload, and declared media type. | The problem is not isolated to wkhtmltopdf; first establish that the input displays in the browser. |
| The browser shows it, but wkhtmltopdf does not | Use the same minimal HTML with the same binary and command; inspect --no-images and print-media behavior. |
A renderer, option, CSS, or build difference is implicated, but the comparison alone does not identify which one. |
The image appears without --print-media-type only |
Inspect print-specific CSS and test a minimal page with the image also referenced in default media. | This resembles a reported print-media issue, but does not prove the same underlying defect. |
| The page contains local image or stylesheet paths too | Test local-file access separately from the inline data URI. | Local access can affect file references; it should not be treated as a direct Base64 remedy. |
| A version change alters the result | Record both exact version outputs, build details, OS, and the unchanged reproducer. | The behavior is version/build-sensitive in that environment; the observation does not establish a universal fixed release. |
| The output remains broken after these checks | Prepare the complete command, minimal HTML/CSS/JavaScript, expected output, actual output, OS, and version for the project’s issue path. | A maintainable reproducer lets others investigate the same conditions. |
Report a persistent failure clearly
If you cannot isolate the cause, submit the smallest case that still fails through the project’s issue-reporting path. Include:
- The complete output from
wkhtmltopdf --version, operating system, and installation/package source. - Whether the build uses patched Qt, if known.
- The exact command, including all flags, or the wrapper configuration that generates it.
- The minimal HTML, CSS, and JavaScript needed to reproduce the missing image, with sensitive content removed without changing the failure.
- What you expected, what the PDF actually shows, and whether the same file displays in a browser.
- The result of controlled comparisons such as print-media on versus off or the installed build versus a newer one.
These details align with the project’s request for version information and a detailed, reproducible example. Avoid attaching confidential source material or untrusted HTML without considering the security implications of sharing it.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Or skip the browser setup
For a screenshot rather than a wkhtmltopdf-specific PDF, ScreenshotNeo is a website screenshot API and MCP server. Its API accepts one GET request with a URL and returns an image or PDF; it does not diagnose or repair a failing wkhtmltopdf data URI. Cookie banners, newsletter popups, and chat widgets are removed before capture, and bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. AI agents can use its MCP server tools, including take_screenshot, get_page_info, and capture_pdf. One thousand screenshots per month are free without a card; paid plans start at $5 for 3,000. See ScreenshotNeo API documentation.
Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL with the page you need to capture and provide your API key. This is an alternative capture workflow for a web URL, not a drop-in wkhtmltopdf fix. Learn about ScreenshotNeo, or sign up for 1,000 free screenshots a month with no card.
Frequently Asked Questions
Does wkhtmltopdf support Base64 images?
The evidence cited here does not establish a format-by-format support guarantee. Test the exact data URI and image format in a minimal file with your installed binary.
Will enabling local-file access fix a Base64 image?
Not as an established direct fix. Local-file access governs local resources, while an inline data URI is embedded in the HTML.
Which wkhtmltopdf version fixes missing Base64 images?
No specific fixed release is established. A reported upgrade helped one case, so compare builds using the same minimal reproducer rather than assuming a general fix.
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.
