Poor mobile completion
Fixed pages, tiny controls, and print-oriented layouts become difficult to use on a phone.
Early access · Gravity Forms first
Turn document-based forms into online forms people can actually complete.
FileToWeb converts the source, lets your team review the HTML in Studio, and then produces a source-grounded form specification. Gravity Forms is the first working adapter, and your team reviews the draft before it replaces a public document workflow.
Document form
Original source
FileToWeb conversion
Responsive HTML
Studio review
Inspect · refine · approve
Form specification
Fields · rules · evidence
Online form
Editable, tested, approved
Human review required before public replacementEarly access · Gravity Forms first
Documents create completion barriers
A form should be easier to complete than to download
Document-based workflows often move the burden from the organization to the person trying to submit information—and back to staff who must process it.
Download-first journeys
People must save, open, edit, print, scan, or re-upload a file before they can finish.
Manual re-entry
Staff may need to copy information from email attachments or scanned documents into another system.
Mixed public and staff fields
Internal-only routing and administrative fields can be difficult to distinguish from questions for the applicant.
Difficult updates
A small policy or field change can require a new file, new links, and another distribution cycle.
A four-stage workflow
Configure, generate, review, then publish
The current early-access workflow creates an editable draft and keeps the final approval step with the WordPress administrator.
- 1
Configure
Choose the form title, single-page or multi-step layout, and the staff notification address.
- 2
Generate
Build a source-grounded form specification from HTML reviewed in FileToWeb Studio and create an editable draft.
- 3
Review
Preview, test, inspect source evidence, and resolve warnings or unsupported details.
- 4
Publish
Approve the draft before changing the public workflow or replacing a document link.
Structured, inspectable output
See what was generated and why it is there
The specification preserves source context alongside supported form structure so reviewers can trace fields and identify uncertainty.
Sections
Group related questions into a readable single-page or multi-step flow.
Supported fields
Represent supported text, contact, selection, date, address, and other field types explicitly.
Choices
Keep source-backed radio, checkbox, dropdown, and other choice values visible for review.
Direct conditions
Capture direct show-or-hide conditions when the source clearly establishes them.
Attachments
Represent supported file-upload requests and flag details that require staff review.
Administrative fields
Mark staff-only information so it can remain hidden from the public form.
Source evidence
Retain evidence references that help a reviewer confirm each generated field against the source.
Review warnings
Surface ambiguity, unsupported behavior, and details that should not be guessed.
First working adapter
A concrete Gravity Forms workflow inside WordPress
The current add-on works with FileToWeb Integration and Gravity Forms to create a draft form and a draft WordPress page for review.
- Choose a single-page or multi-step layout.
- Set the title and staff notification address.
- Generate an editable Gravity Forms draft and draft WordPress page.
- Preview and test the full completion path.
- Review warnings and source evidence before approval.
- Approve the form before changing the public document workflow.
Permit request
Generated from reviewed FileToWeb HTML
Applicant name
Email address
Describe your request
Review required: confirm the routing address and any policy-specific instructions before publishing.
Human-controlled generation
Generate structure without inventing policy
The system is designed to extract and structure what the source supports, then call attention to decisions that belong to staff.
- Do not invent fees, policy, recipients, deadlines, or legal terms that are not supported by the source.
- Gravity Forms entries and uploaded files remain in WordPress under the site's own configuration.
- Staff controls notifications, payments, and other WordPress or Gravity Forms add-ons.
- The original PDF and the reviewed FileToWeb version remain available to administrators.
A draft is proof to review, not a promise to publish
Test required fields, conditions, uploads, notifications, data handling, policy language, and accessibility with representative users before changing the public form path.
Provider-neutral specification, Gravity Forms today
The form specification is designed around provider-oriented structure, while Gravity Forms is the only implemented target today. Early-access inquiries help us understand which provider and workflow should be scoped next; they do not imply an existing adapter.
Early-access questions
What to expect from FileToWeb Forms
Current scope is intentionally narrow while the workflow is tested with real document forms and editorial teams.
What does the current Gravity Forms workflow require?
It currently requires the FileToWeb Integration WordPress plugin, a supported Gravity Forms installation, a reviewed FileToWeb HTML version, and administrator access to configure and approve the generated drafts.
What form content can it generate?
It can represent supported sections, fields, choices, direct conditions, attachments, administrative fields, evidence, and review warnings. Complex calculations, unsupported widgets, policy decisions, and unclear logic require manual work.
Does generation remove the need for review?
No. A person must compare the draft with the source, test the completion and notification workflow, address warnings, and approve any public replacement.
Where do submissions and uploads live?
With the current Gravity Forms adapter, entries and uploads remain in WordPress according to that site's WordPress and Gravity Forms configuration. FileToWeb does not decide the site's retention, notification, payment, or add-on policies.
Is FileToWeb Forms generally available?
No. It is an early-access workflow with Gravity Forms as the first working adapter. Contact us with a representative use case so we can assess fit and scope.
Early access
Bring one representative document form into a reviewed online workflow.
Tell us about the source form, the WordPress environment, and the staff review process you need to preserve.