There is usually a specific document behind the search. A membership application, a maintenance request, an intake sheet, a consent form. It exists as a PDF because somebody laid it out once and it looked right, and now it gets emailed out with a line asking people to fill it in and send it back. Some of them do. Some print it, write on it, photograph it and send the photograph. Some open it in a browser preview, type into it, and return a file with every field blank because the preview never saved them.
The question is not really which tool adds fields to a PDF. Several do that competently. The question is whether the document has to stay a document, and what the answers turn into once they come back.
Three different things get called fillable
The word covers three arrangements that behave nothing alike, and the confusion between them causes most of the trouble.
A PDF with real form fields. Text boxes, checkboxes and dropdowns are embedded in the file itself. The respondent opens it in a PDF reader, types, saves, and returns a PDF that carries the values. This is what a PDF form creator produces.
A flat PDF that looks fillable. Lines and boxes are drawn on the page, but they are artwork. Nothing can be typed into it. This is the version that gets printed, completed by hand and scanned back, and it is the version most people are actually working with when they go looking for a tool.
A web form that produces a PDF afterwards. Answers are collected in a browser, stored as records, and a PDF is generated from them when a document is needed for signing or filing.
The third arrangement is the one people rarely consider at the start, because the PDF feels like the thing being built. It is worth separating the document from the data early. If the layout is prescribed by somebody else, the document matters. If the layout exists only because a PDF was the easiest way to write it down, the data matters and the document is a habit.
Where a fillable PDF is the correct answer
Some situations genuinely require the file, and no amount of web form convenience changes that.
The layout is set by a third party. A regulator, a landlord, an insurer or a parent organisation supplies the form and expects that form back. Reproducing the questions in a browser does not help, because what has to arrive at the other end is their document with their field positions.
Something has to be signed and kept. Where the completed page is the record and may be read years later by somebody with no access to the original system, a PDF with fields is a reasonable container. It carries its own layout, opens anywhere, and does not depend on a service continuing to exist.
Work happens offline. Site inspections, field visits, ships, remote clinics. A file that can be filled with no connection and returned later solves a problem a web form cannot.
The respondent is one organisation, not a hundred people. Sending a fillable PDF to a single counterparty who returns it once is fine. The difficulties below are all volume problems, and at volume of one there is no volume problem.
Where the round trip breaks
Everything that goes wrong with a fillable PDF goes wrong in the gap between sending it and getting it back.
The reader is not under your control
PDF form fields behave according to whichever application opens them. Browser previews, phone mail clients and lightweight readers vary in how they handle saving, calculations and required fields. A form that validates correctly on the desk it was built at can come back empty from a phone. There is no way to test every reader a respondent might use, and no signal on your side that anything went wrong until the blank file arrives.
Validation is advisory
A web form can refuse to submit. A PDF can only ask. Required field markers, format masks and calculated totals exist in the specification, but they depend on the reader honouring them, and none of them prevent a file being saved half finished and emailed anyway. The result is the same follow up message sent over and over: the date is missing, the second page is blank, the total does not add up.
Forty files are not a list
This is the part that costs real time. Twenty completed PDFs are twenty attachments in a mailbox. To see all the answers together, somebody opens each one and types the values into a spreadsheet. To know which ones have been dealt with, somebody adds a column and maintains it by hand. To reply, somebody writes a fresh message and hopes not to reply twice to the same person. None of that work appears in any budget, and all of it scales linearly with the number of respondents.
There is no shared state
Two colleagues both looking at the same mailbox have no way to tell which submissions the other has handled, other than by asking. The two familiar failures follow: the applicant who gets two different answers from two people, and the applicant who gets none because each assumed the other had it.
What the tools charge for, which decides when they break
Below are current published figures for tools that sit on the boundary between documents and web forms. All checked in September 2026, monthly billing unless noted.
| Tool | What it does about PDFs | Free option | Cheapest paid plan | What runs out |
|---|---|---|---|---|
| Jotform | Uploads a PDF and converts it into a web form, keeping the original layout | 5 forms, 100 submissions a month | Bronze, 39 USD / month | 1,000 submissions a month, 25 forms |
| Cognito Forms | Unlimited forms, entries metered, custom document templates on the top plan | 100 entries a month, 1 user | Pro, 24 USD / month | 2,000 entries a month, 1 user |
| Tally | Web forms only | Unlimited forms and submissions under fair usage | Pro, 24 USD / month | Files over 10 MB on the free tier |
| Typeform | Web forms only | Yes | Basic, 39 USD / month | 100 responses a month, 1 user |
| Docusign | Signature envelopes built on documents | None listed | Personal | 5 envelopes a month on Personal, 100 per user a year on Standard |
Two of those numbers are worth pulling out, because they are the ones that surprise people.
Cognito Forms puts no cap on the number of forms on any plan, including the free one, and meters entries instead. The free tier allows 100 entries a month with one user, Pro at 24 USD a month raises that to 2,000 entries and adds electronic signatures and save and resume, and only the top plan at 199 USD a month lifts the entry cap entirely. Custom document templates, which is the feature that generates a formatted document from the collected answers, also sits on that top plan.
Docusign meters envelopes rather than responses, and the allowances are small in a way that catches people planning to use it as an intake channel. The Personal plan sends five envelopes a month. The Standard plan is priced per user and includes 100 envelopes per user per year. That is appropriate for contracts and wrong for anything that arrives continuously.
Tally is the outlier on volume, with unlimited forms and unlimited submissions on its free tier subject to fair usage, and a Pro plan at 24 USD a month that removes branding, adds custom domains and lifts the 10 MB per file limit. It does not pretend to be a document tool.
Desktop PDF editors belong in the conversation too, and they solve a different problem. They add real fields to the file itself, which is exactly right when the file has to be the deliverable. What none of them do is tell you which of the returned files has been handled, by whom, and whether anybody replied.
The question that actually decides it
Not the format. The volume, and whether work continues after arrival.
Count how many of these are true. The same form is completed by more than about twenty people. More than one colleague needs to see the answers. Somebody has to reply to each respondent. A respondent moves through stages, such as received, reviewed, accepted. Somebody will be asked in three months what happened to a particular submission.
At zero or one, a fillable PDF is fine and adding a tool would be overhead. At three or more, the document has become a database with extra steps, and the honest comparison is no longer between PDF editors. It is between maintaining the spreadsheet by hand and using a form tool where each response already carries an owner, a status and a record of what was sent.
That is the part worth checking against your own case rather than in the abstract. A form tool with response management keeps each submission as a record with a stage and an owner, lets colleagues see who has what, and keeps replies attached to the response instead of scattered across a mailbox. The features list and the pricing are where to look for whether that applies at your volume, since some tools meter responses and some meter people, and the two choices fail in opposite conditions.
You can keep the document and drop the round trip
These are not mutually exclusive, and treating them as a choice is what makes the decision feel harder than it is.
Collect the answers in a browser, where validation is enforceable and every submission becomes a record. Generate the document afterwards, from the stored answers, when a document is genuinely needed for signature, filing or an archive. The layout is produced once by the tool rather than typed in by every respondent, which removes the most common failure entirely, because nobody can return a blank version of a document that is generated after the fact.
Several tools support some version of this. Jotform's route runs the other way and is useful if the existing PDF is the starting point: upload it, and it becomes a web form that keeps the original layout. Cognito Forms generates documents from entries using templates on its top plan. Where signatures are the point, a signature service takes the completed document and handles that step, metered by envelope.
The practical test, whichever route you pick, is not building the form. It is this: submit one response, hand it to a colleague, mark it as dealt with, send a reply from inside the tool, and find that reply a week later. A trial spent rebuilding the whole form tells you about the editor, which is the part that matters least once the thing is running.
What to change first
Look at where last month's completed forms are sitting right now. If the answer is a mailbox folder and a spreadsheet somebody maintains by hand, the document was never the problem and a better PDF editor will not help. Collect in a browser, keep an owner and a status on every response, and generate the PDF only where a document is actually required, which you can see working on real responses in the demo of Halict or any tool built the same way.
Q1. Can a PDF form be made to validate answers properly?
Only partially, and not reliably. Required field markers and format checks exist in the PDF specification, but whether they are enforced depends on the application the respondent opens the file in, and none of them stop a partly completed file being saved and emailed back. A web form can refuse to submit, which is a different kind of guarantee.
Q2. Is it possible to turn an existing PDF into an online form without rebuilding it?
Yes. Jotform's Smart PDF Forms takes an uploaded PDF, converts it into a web form and keeps the original PDF layout, which is the shortest path when the document already exists and its layout has to survive. Start from the questions rather than the file if the layout was never prescribed by anyone.
Q3. What does it cost to collect forms online instead of by PDF?
It depends entirely on what the tool counts. Tally allows unlimited forms and submissions on its free tier under fair usage. Cognito Forms puts no cap on forms but meters entries, starting at 100 a month free and 2,000 a month on Pro at 24 USD. Typeform's Basic plan at 39 USD a month includes 100 responses a month and one user. Check which number moves in your busiest month before comparing headline prices.
Q4. When is a fillable PDF still the right choice?
When somebody else prescribes the layout and expects their document back, when the completed page itself is the record that has to survive independently of any service, and when the work happens offline. Also when the respondent is a single organisation returning it once, since every problem described here is a volume problem.
Q5. How do signatures fit in?
Signature services meter documents rather than responses, which matters for planning. Docusign's Personal plan sends five envelopes a month and its Standard plan includes 100 envelopes per user per year. That suits contracts signed occasionally and does not suit an intake channel where submissions arrive continuously, so the usual arrangement is to collect in a form and send only the ones that need signing.