Formspark review: prepaid forms and the workflow tradeoffs

How to evaluate a prepaid form service

With a prepaid service, estimate the expected life of a balance rather than comparing its headline number directly with a monthly plan. A seasonal landing page and an always-on advertising campaign can consume the same balance very differently. Keep a top-up owner in your operational checklist.

Formspark’s limits guide describes a buffer and held submissions after the balance runs out. It also differs from the pricing page on upgraded team limits: pricing lists 50 members, while the guide describes no practical limit. Confirm the applicable limit if collaboration is central to the purchase.

Sources: Formspark allowance and workspace rules · Formspark pricing

File uploads use another storage provider

Formspark’s upload guide describes uploading to a service such as Uploadcare or Cloudinary and submitting the resulting URL. Formspark stores that reference rather than the file. This can work well when the website already has an upload pipeline.

Include the storage provider’s allowance, access policy and deletion behavior in the evaluation. A submission containing a file link is only useful for as long as the link remains available to the people who need it. Test the complete workflow, including the recipient opening the file.

Sources: Formspark upload documentation

Webhooks and the management API serve different jobs

The webhook guide says Formspark sends a JSON POST to your configured receiver and does not sign requests. Validate incoming data and choose an appropriate authentication arrangement for the receiving application; knowing a URL is not proof that the caller is the form vendor.

The REST API is separately authenticated and available on upgraded workspaces for managing forms and reading submissions. Its documentation warns that repeating a write can create another resource. Keep those management credentials on an authorized server or client, not in your public form.

Sources: Formspark webhooks · Formspark API

Spam protection is broader than a honeypot

Formspark documents automatic filtering, custom spam words, honeypots and integrations with Botpoison, reCAPTCHA, hCaptcha and Turnstile. Its documentation says rejected spam does not consume submission credits. Choose controls appropriate to your traffic rather than assuming a single hidden field is the entire protection model.

Sources: Formspark spam controls

When SplitForms is the better fit

SplitForms is worth shortlisting when you need a monthly allowance and HMAC-SHA256 signed webhooks in one service. Pro is $5/month, and the Free plan starts with 500 submissions total. Paid uploads use a connected Storage integration. Check the live pricing page for the complete plan limits.

The migration decision should account for files, redirects and downstream payload mapping as well as the action URL. Preserve your form fields, configure the new backend and validate a representative submission. Formspark can remain the cheaper choice for a site that consumes its prepaid credits slowly.

Sources: SplitForms pricing · Migration checklist