Invoices, dashboards, statements, and customer portals often begin as HTML. The risky part is the handoff: a page may load CSS late, fetch data in JavaScript, or depend on local fonts and images. A useful renderer makes those conditions explicit and gives the agent one output path to verify.
Keep the page you already own
Jetformat accepts a local HTML file, a directory with its assets, or an HTTPS URL. The same command works for a report checked into a repository and a page already deployed behind your application.
jetformat html to-pdf page.html -o page.pdf
jetformat html to-pdf ./report-site -o report.pdf --page-size A4 --landscape
jetformat html to-pdf https://example.com/report -o report.pdfMake asynchronous pages deterministic
Dashboards and charts should be captured after they are ready, not after an arbitrary click. Wait for a selector, require it to be visible, or add a short settling delay when the page needs one.
jetformat html to-pdf dashboard.html -o dashboard.pdf \
--wait-ready ".dashboard-ready" \
--wait-visible "svg.chart"Use the same local workflow as Office files
The agent can prepare data, call the HTML renderer, then inspect the generated PDF with the PDF commands. Source files stay in the workflow that owns them, and the output path is concrete enough to show the user.