Guides · use cases

Use cases

These all start from the same place: a form that already exists as an HTML page in your own app, and somebody who needs it as a PDF they can type into — a customer, a tenant, a patient, a parent. The usual answers are a PDF library and coordinate arithmetic, or a Word template maintained by hand next to the real code, drifting out of sync with it.

snapdok.io renders the page you already have with real Chromium and, with pdf_forms: true, keeps its <input>, <select> and <textarea> controls as genuine AcroForm fields in the PDF — so the web form stays the one source of truth. Each page below is a worked example: what the problem looks like in that setting, the request that solves it, and the guides that go deeper.

Working code in Python, Node.js, PHP and Ruby is in the guides; every parameter used here is in the API reference. Free keys need no card — get one and try it on your own form.