FormZero vs Formspree

Choose ownership or a managed submission workflow

Our recommendation is to evaluate FormZero for a small form where reading and exporting submissions in an operator-owned dashboard is the main requirement. Evaluate Formspree when managed notifications, spam tooling and integrations are central, or when nobody can maintain a backend. This is an assessment of the reviewed sources, not a side-by-side benchmark.

Decision	FormZero at the reviewed commit	Formspree
Hosting	Your Workers/D1 deployment and maintenance	Vendor-managed service
Code license	MIT; retain its notices	Subscription terms; no self-hosting right established here
Submission workflow	HTML form data or JSON written to D1	Hosted form endpoints with plan-specific plugins
Export	Dashboard CSV documented	Dashboard CSV/JSON export documented on paid plans
Notifications	Optional SMTP code; delivery untested	Notification plugins and paid autoresponses
Spam handling	README's proof-of-work/honeypot feature is marked coming soon	Published basic filtering and configurable protections
Limits	Cloudflare quotas and application behavior	Account-wide submission and storage allowances

Test the existing form before changing its action

Inventory field names and special inputs from your current form. Formspree documents integration-specific behavior for fields such as email, subject and newsletter opt-in. Sending the same names to another endpoint does not recreate those integrations automatically.

FormZero's pinned submission route selects parsing based on content type, stores data in D1 and returns JSON or an HTML redirect. Compare status codes, the JSON response your frontend expects, validation failures and the final thank-you page. An AJAX handler built around another service's response may need changes even when the visible HTML fields remain identical.

Read the SMTP implementation alongside the README

The README still lists a future Resend notification feature. The reviewed runtime already calls an SMTP notification helper after storing a submission, using global settings in D1. Both pieces of evidence matter: this is implemented code for a different provider path, not a verified Resend integration.

SMTP configuration includes account credentials stored in application settings. Review access to those settings and database backups before entering a real credential. The code catches notification failures, so a successful submission response can coexist with failed delivery. Verify receipt at an authorized inbox and define how the operator notices errors before relying on email to handle leads.

Keep exports separate from an automatic migration

Formspree documents CSV and JSON exports; FormZero documents CSV export of its own submissions. Neither fact establishes that FormZero can import a Formspree archive unchanged. Keep the original export, inventory attachment references and preserve field names. Build and test any importer separately if historical records must appear in the new dashboard.

Compare total cost and a reversible pilot

Use the Formspree pricing guide for current subscription rates and the alternatives shortlist for other options. Then use the Cloudflare pilot guide with one non-critical form. The FormZero project page retains the original README, license, upstream screenshot and expanded configuration evidence. No fresh deployment, delivery test, spam benchmark or completed migration was performed for this guide.