Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Use wkhtmltopdf --enable-forms input.html output.pdf to ask wkhtmltopdf to create PDF form fields from HTML form controls. Forms are disabled by default in the wkhtmltopdf 0.12.6 command-line documentation. The switch enables field production; it does not guarantee that every prefilled value will appear, remain editable, or print correctly in every PDF viewer. Check those outcomes separately in the software your recipients will use.
What --enable-forms does—and what it does not
The option tells wkhtmltopdf to turn HTML form fields into PDF form fields. Without it, the documented default is --disable-forms. The related libwkhtmltox reference likewise exposes form production as a produceForms setting.
A PDF form field is not the same as static text printed onto a page. Enabling forms asks for controls that can function as fields in a PDF; it does not flatten the source values into the page as a visual guarantee. In practice, “preserved” can mean several different things, so verify the result against the need you actually have:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Field creation: Does a corresponding PDF field exist?
- Value appearance: Is the source value visible as soon as the PDF opens?
- Editability: Can a recipient enter or change a value?
- Viewer consistency: Do the intended PDF readers show the same field and value?
- Print behavior: Do values appear in print preview and on paper?
These checks are related but not interchangeable. A field might exist and accept input while its initial value is not visibly rendered, or its on-screen appearance may differ from its printed appearance.
#1 Best Overall
- Desktop class PDF reader and editor for Android
- Read PDF documents with Mobile-Optimized Text Reflow mode & Text To Speech
- Annotate like a Pro with unmatched annotating tools
- Fill out, Stamp & Sign PDF Forms
- Powerful File Manager features Automatic, Desktop-like syncing with all major cloud services
Convert an HTML form to PDF
Enable form fields on the command line
Run the conversion with the switch before the input and output paths:
wkhtmltopdf --enable-forms input.html output.pdfReplace input.html and output.pdf with the paths for your files. The command requests PDF form fields; it does not establish that every field type, initial value, or viewer behavior will work as you expect. Open the resulting PDF and test it rather than treating a successful conversion as proof of preservation.
Make a small diagnostic HTML file
If an existing page produces an unexpected PDF, narrow the problem with a minimal fixture. Include one text input with an explicit value and one empty input, then convert that file using the same wkhtmltopdf executable and --enable-forms switch. This is a diagnostic you can run; it is not a claim that a particular fixture was tested here.
Keep the test small enough that you can tell whether the issue concerns creation, a prefilled value, editing, or printing. If the simple fixture works but the real page does not, inspect the actual page state and any scripts that populate its controls before the conversion.
Rank #2
- Kit includes 26 six-part W2 forms 2025: Copies A, B, C, D, 1 and 2, plus 3 W-3 Forms, 26 security envelopes and free access to the Helper; print code included
- Make tax season successful and easy; comes with 3 W-3 transmittal forms for summarizing and submitting W-2s to the IRS by mail; 26 self-seal security envelopes included
- Free access and print code for Adams Tax Forms Helper comes with your kit; 10 or more returns? You'll need to eFile; use the Helper for simple eFiling
- W-2 filing deadlines: Employers must file Copy A with the Social Security Administration and provide employee copies by February 2, 2026, regardless of whether they file electronically or by paper.
- Want to share secure links of employee/recipient tax forms? Use PDF File Share, available only on the Helper; this add-on service make tax season easier and paper-free; additional fees apply
Verify values, editability, and printing separately
- Record the converter build. Capture the version reported by the executable and note whether the build uses patched Qt. The wkhtmltopdf command-line documentation describes its invocation in a patched-Qt context, and historical issue reports describe symptoms tied to particular versions or builds. Do not assume two packages behave identically because both are called wkhtmltopdf.
- Check that fields exist. Open the output in the recipient’s PDF viewer and inspect the expected controls. A visible page alone does not show whether controls became PDF fields.
- Check the initial value before editing. For a prefilled control, note whether its value is visible as soon as the document opens. Then edit the field and check it again. A value that appears only after interaction is not the same result as a value that is visible on open.
- Check an empty field. Try entering text in the control that was empty in the HTML. This distinguishes a missing or read-only field from a field that is editable but does not display its initial value as expected.
- Check print preview and paper. Treat printing as its own test. Inspect print preview and, when the workflow requires it, a printed page; do not infer print behavior from on-screen editing.
- Repeat with the recipient’s viewer. If a document is meant for use in a specific reader or browser, verify it there as well as in your own usual viewer.
Keep the original HTML, exact conversion command, wkhtmltopdf version and build information, resulting PDF, and viewer used together when comparing results. Those details make it easier to determine whether a change in the command, converter package, page behavior, or viewer altered the outcome.
When JavaScript supplies a form value
The upstream wkhtmltopdf documentation describes JavaScript as enabled by default and gives a default JavaScript delay of 200 ms. That default is not evidence that a particular page’s scripts have finished populating controls in time. A value written asynchronously may still be absent when conversion captures the page.
Inspect the HTML page’s state at the point it is converted: confirm that the relevant control contains the intended value before generating the PDF. Then repeat the PDF checks above. If the value is supplied by JavaScript, adjust the conversion’s wait behavior to match the page rather than assuming one fixed delay suits all pages. The documented 200 ms default is a starting fact about the tool, not a universal readiness guarantee.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteTroubleshoot common form problems
No PDF fields appear
First confirm that the actual conversion command includes --enable-forms; the documented default disables form production. If it does, run the minimal fixture and record the exact executable version and build variant. This separates a command/configuration mistake from a version- or packaging-specific symptom.
Rank #3
- Quickly print and mail your Form 1096 2026 with this 25 pack bundle, which includes 25 1096 Transmittal/Summary Tax Forms with standarized and legal version of IRS form 1096 2026
- Thick 20 lb paper that will quickly feed through your laser and inkjet printer without worrying of jamming
- All printed fields will perfectly line up with the correct boxes when using QuickBooks or other tax software
- Confidently fill your 2026 1096 Transmittal tax forms with our Internal Revenue Service (IRS) approved documents and designed to be compatible with QuickBooks
Fields exist but are read-only
Test an empty field in the intended PDF reader and compare against the minimal fixture. Historical reports include a user who said fields became read-only after upgrading to 0.12.4 despite using --enable-forms and UTF-8. Another 2019 report described a non-editable field with 0.12.5 on CentOS 7, but the command shown there did not include the enable switch. These cases show why version, build, command, and viewer matter; they do not establish a universal defect in current builds.
A prefilled value is missing or appears only after editing
Check whether the control has the intended value in the HTML state used for conversion. If JavaScript writes it, verify that script completion precedes capture. Then distinguish a conversion problem from a viewer’s display behavior by opening the PDF in the target reader and checking the value before and after editing.
A community report described a prefilled value that appeared empty in Acrobat Reader DC until its field was edited. That is a historical reported case, not proof that every current Acrobat build or every wkhtmltopdf PDF behaves that way. If a recipient sees a discrepancy, record their viewer and version and compare another intended viewer before changing the source or converter.
Values show on screen but not in print
Test print preview separately from the interactive form. A 2015 community thread reported a field that could be filled in some viewers but appeared empty in print preview and on paper. This is evidence of a viewer-dependent failure example, not a general rule. If printing is essential, use the exact viewer and print path recipients will use as part of acceptance testing.
Rank #4
- Quickly print and mail your W2s with our IRS Approved W2 Forms 2026 4 part bundle that includes everything you need to file your W2 for your employees
- Thick 20 lb paper that will quickly feed through your laser and inkjet printer without worrying of jamming
- All printed fields will perfectly line up with the correct boxes when using QuickBooks or other tax software
- Confidently fill your 2026 W2 forms with our Internal Revenue Service (IRS) approved documents
- Bundle includes everything you need for 25 employees including 13 W2 COPY A forms, 13 W2 COPY B forms, 13 W2 COPY C/2 forms, 13 W2 COPY D/1 Forms, 3 W3 Transmittal forms, and 25 self sealing envelopes
Changing PDF internals seems like the only workaround
Do not treat low-level edits to PDF object dictionaries as a general repair based on a community suggestion. The cited discussion does not establish that such edits are safe or a validated current fix. Prefer a reproducible minimal case, verified build details, and the intended reader/print tests before adopting a workaround.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability, and delivery choices
For a reliable workflow, make PDF generation a sequence with an explicit readiness check, conversion, and output validation—not just a command that exits successfully. If the page depends on client-side JavaScript, verify its populated state before conversion and choose a wait appropriate to that page. Keep the wkhtmltopdf build consistent across environments where output needs to match, and include the target viewer and print path in testing.
There is no basis here for a general speed figure, success rate, or compatibility guarantee across wkhtmltopdf builds and PDF readers. A small fixture helps isolate behavior without assuming a specific cause, while a test using the production HTML reveals dependencies such as scripts and viewer behavior. For workflows in which a recipient must edit the PDF, validate field creation and editing; for workflows that need a dependable printed representation, validate the rendered and printed result separately.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
If you need a visual capture of the source page as a companion to PDF-form testing, ScreenshotNeo offers a screenshot API; it is not a replacement for creating or validating editable PDF fields. A one-call screenshot request looks like this:
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. ScreenshotNeo removes cookie banners, popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed; and its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000. Learn about ScreenshotNeo or sign up for 1,000 free screenshots a month, with no card.
Frequently Asked Questions
Does --enable-forms flatten HTML values into ordinary PDF text?
No. It enables PDF form-field production; it is not a command to flatten values into static page content.
Is a 200 ms JavaScript delay guaranteed to capture populated fields?
No. It is the documented default, but pages differ in how long scripts take to set their values.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →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.
