Two different reasons "no signal" breaks most form fillers
The first reason is the obvious one: a tool that fills your form on someone else's server needs to get your file there first. No connection, no upload, no filled form, and it tends to fail three fields from the end rather than at the start. This tool reads, edits and writes the PDF using your own device's processing power, so there is no request that can time out, because there was never a request.
The second reason is less obvious and just as common: plenty of tools that call themselves form fillers only work on a PDF that already has real, built-in fillable fields, the kind you get from a form designed in Acrobat. A huge share of the forms people actually need to fill are not that. A consent slip forwarded as a flat PDF. A government form somebody scanned. Neither has a single fillable field in it, and a tool built only around detecting fields has nothing to detect.
Type directly onto the page
- 1Open the Sign & Fill tool and choose or drag in your PDF. Once the page itself has loaded once, this step works with no connection too.
- 2Pick Text, click where an answer belongs, and type. Use Symbols for a checkmark on a checkbox, or the Signature tool for your name. Drag anything afterward to nudge it into place.
- 3Download the finished PDF. Nothing is sent anywhere to produce it; your device builds the file and hands it straight to you.
Because you're placing what you type directly onto the page rather than searching for a field to jump into, the steps are identical whether the form has real fields, is a flat PDF, or is a photo of a paper one. There is nothing to detect, so there is nothing that can fail to detect it.
It doesn't matter what kind of PDF you were sent
"Form filler" usually implies the software finds the blanks for you. This one doesn't try to find them: you look at the page the way you would on paper, and put your answer where it belongs. That's a lower bar to clear, and it's also why it works on every kind of form below rather than only the well-behaved one.
A photo or scan has no text in it at all, just pixels shaped like text. There's nothing for any tool to detect. Click where an answer goes and type; that's the only method that was ever going to work here.
Most consent slips, letters and one-off forms are exported without any fields built in. Same method as a scan: click, type, move on. Nothing to configure first.
A PDF actually built with form fields in Acrobat or similar. You can still type directly over each one, though there's no Tab-to-next-field yet, so you click each one by hand rather than tabbing through in order.
One thing worth knowing plainly: what you type is drawn directly onto the page, the same way a signature is, rather than written into the PDF's own interactive field data. Anyone who opens, views or prints the file sees exactly what you typed, in the right place. What it doesn't do is set the stored value of a form field the PDF format defines separately, so a script or system built to specifically read a PDF's field data (rather than its page content) won't find one there. For filling out and sending a form, this distinction rarely matters. It's the honest reason to mention it anyway.
One page load, and then the wifi can go
The first visit needs a connection, to fetch the tool itself. After that, or once you've installed it like a regular app, it keeps working with none at all, because filling and signing a PDF was never something this needed a server for. You can check that claim yourself in about a minute rather than take it on faith.
Long forms rarely get finished in one sitting, so your progress is saved to your own device as you go, not to a server. Close the tab, lose the connection, or let your battery die partway through, and your answers, checkmarks and signature are still there when you come back.