Supported formats, limits and support
Find current plan information and source limits, and prepare a precise support request without exposing private records.
Reviewed 2026-10-30 · Formesign guides
Check the current product screen and account plan when a feature or limit affects your setup. Formesign's product entry paths share functionality, but their accepted source, enabled controls and output can differ.
Source and format boundaries
| Task | Current boundary |
|---|---|
| Web Document signature entry | The current upload screen is labelled PDF. Use the Docs add-on guide for Google Docs. |
| Google Forms import | Defaults to a copy; an edit-existing alternative is a distinct path. |
| Sheet signature | Starts from a Sheet link or Drive selection and selects the relevant tab. Do not assume automatic per-row requests. |
| Drive saving | Uses My Drive folders; the current setup does not support Shared Drive folders. |
| Final workflow PDF | Depends on required signing completion in current workflows. |
| MCP create_form | Uses text HTML or Markdown documents, not binary file uploads. |
Use any size or format limit shown by the actual upload control. These guides do not publish an invented universal upload size, browser version matrix or delivery-time guarantee. A mobile-friendly signer page does not imply offline submission.
Plans and account usage
Open Manage plan from the dashboard when available, or use current Formesign pricing. Product plans, response allowances, included controls and trial terms can change; check the selected plan before rolling a process out to more users.
If a control asks for an upgrade, identify the specific feature and account before purchasing. The main product pricing page links to signature, approval, HIPAA, intake and suite options. A form's title or template category does not establish which subscription is active for its owner.
Prepare a useful support request
Start with Formesign support. Include:
- The product and entry path used, such as Form signature import or PDF upload.
- The action attempted and the exact error text.
- Approximate time and time zone, browser/device, and whether the issue repeats.
- Expected result and actual result, including the relevant visible state.
- A synthetic or redacted example of the affected question or output where helpful.
Never include a password, authorization token, private patient information, real signature or unrestricted signer link in a public report. If the team needs a private diagnostic artifact, use its instructed private channel.
Try the relevant check first
Use import/access, invitation, workflow or records/sync troubleshooting to identify the failing stage. That context helps distinguish a permissions issue, incomplete signature and output-connection problem without repeatedly recreating the form.