G2

Alesia N.

Project Manager

Information Technology and Services

Mid-Market (51-1000 emp.)

9/1/2026

"Magic Fields completely cut down our PDF prep time"

5/5

What do you like best about pdfFiller?

Magic Fields saves us a noticeable amount of setup time on documents that already have a clear structure. It can spot areas for names, dates, and signatures and convert them into fillable fields, so we’re not placing every field manually from scratch. It still doesn’t understand the entire document for us, and checkboxes or radio buttons need extra attention, but on forms with predictable text areas it eliminates a lot of repetitive work. We pair that with Reusable Templates, Shared Templates, LinkToFill, and Request eSignatures for agreements, change requests, approval forms, and other documents that come back again and again. Rather than creating a fresh copy each time, we keep a standard version in the workspace, let the client enter the required information through LinkToFill, and then move the final document into the signature flow with the right recipients and signing order. The Online PDF Editor also covers the small edits that used to send us back to Word or design, like fixing a sentence, hiding information, adding an image, reordering pages, or converting the file. Audit Trail and version history have been especially helpful when several people touch the same document, because we can see who opened, edited, shared, or moved it, and recover from a bad change without guessing which attachment was the last clean version. Review collected by and hosted on G2.com.

What do you dislike about pdfFiller?

Magic Fields feels like a head start rather than an autopilot. It does a solid job recognizing fields that are laid out with clear lines and empty spaces, but it doesn’t always understand every relationship within a more complex form. We still need to review field ownership, which values are optional versus required, signing roles, and the order someone is expected to complete the document. For anything involving checkboxes, radio buttons, or less predictable layouts, that QA step really matters. It definitely saves preparation time, but I still wouldn’t send a client-facing document just because the automatic detection finished successfully. Review collected by and hosted on G2.com.

What problems is pdfFiller solving and how is that benefiting you?

We used this workflow on an implementation project where the client needed to provide technical information, approve the scope, and sign off before the next phase could begin. Before that, each item was being sent around as a separate email attachment, which made it surprisingly easy for someone to fill out or approve an older version by mistake. We converted the intake form using Magic Fields, saved the scope as a Reusable Template, and kept both in the shared workspace. The client submitted the initial information through LinkToFill, we reviewed it, and then generated the final document for Request eSignatures with the correct signing sequence. In our first test run, we caught two optional fields that were assigned to the wrong recipient, plus a checkbox that Magic Fields didn’t detect at all. We corrected the template before it became the version everyone would reuse. Once the document moved through signature, Audit Trail gave us a clear record of when it was opened, completed, and approved before the project status changed. The bigger win wasn’t only faster field creation. It was having the intake, reusable content, signatures, and document history in one controlled flow, instead of managing approvals through a stack of attachments with nearly identical filenames. Review collected by and hosted on G2.com.