Formspree pricing starts with a free plan of 50 submissions a month, a 30-day submission archive, and no file uploads or export. Paid plans are Personal at $15/month (200 submissions, Google Sheets), Professional at $30/month (2,000 submissions, webhooks and auto-responses), and Business at $90/month (20,000), or $10, $20, and $60 a month billed yearly, per Formspree's plans page in November 2026.
So the comparison with OSForms mostly comes down to who pays for the integrations. Both are form backends: you point a form's action at an endpoint, and the service stores each submission and sends it on. Formspree is the mature hosted product, with a wider plugin catalog, real file uploads, and integrations priced by tier. OSForms is open source (MIT) and runs integrations on your own API keys, so email through Resend, Google Sheets, and signed webhooks all come with a free tier of 100 submissions a month. If your form collects files or needs one-click Mailchimp, pick Formspree. If you want Sheets and webhooks without a subscription, or the option to run the whole thing yourself, pick OSForms.
I built OSForms, so read this with that in mind. Every Formspree number below comes from Formspree's own plans page and help center, checked on November 8, 2026. Every OSForms claim is checked against the code in the public repo. If you are weighing more than two tools, the roundup of Formspree alternatives covers the wider field. This post is the narrow version: two products, compared row by row.
OSForms vs Formspree at a Glance
| OSForms | Formspree | |
|---|---|---|
| Free tier | 100 submissions/mo, every integration | 50 submissions/mo, email and chat plugins (Slack, Discord…) |
| Free-tier submission archive | No expiry | 30 days |
| Google Sheets | Free, through your Google account | Personal plan and up ($15/mo) |
| Webhooks | Free, optional HMAC-SHA256 signature | Professional and up ($30/mo) |
| Auto-reply to the submitter | Free, through your Resend key | Professional and up ($30/mo) |
| Custom redirect after submit | Free | Personal and up ($15/mo) |
| Export | CSV, every tier | CSV or JSON, Personal and up |
| Read submissions via API | Read-only pull API, free | Professional and up ($30/mo) |
| File uploads | Not stored (placeholder string) | Personal and up: 1 GB, 5 GB, or 10 GB |
| Plugin catalog | Email, Google Sheets, webhooks | Wider: Zapier, Stripe, Mailchimp, Notion, Trello, Slack, more |
| Spam protection | Honeypot you name, reCAPTCHA or hCaptcha | ML filtering on every plan; custom honeypot on Business |
| Source code | Open source, MIT | Closed; original repo archived July 2023 |
| Self-hosting | Yes (Next.js + MongoDB, Docker Compose) | No |
| React library | @osforms/react (<OSForm /> component) | @formspree/react (useForm hook) |
The core job is identical. The differences are in who pays for the routing, how long your data sticks around, and what leaving looks like.
Formspree Pricing and Free Plan Limits vs OSForms
Formspree's pricing page shows this ladder (November 2026, billed monthly). It's unchanged from when I first drafted this post in July:
- Free ($0): 50 submissions/month, 30-day submission archive, 2 linked emails, no file uploads, email and chat plugins only.
- Personal ($15/mo): 200 submissions, 1 GB of uploads, unlimited archive, Google Sheets and other basic plugins (Notion, Trello), a custom thank-you page, CSV or JSON export.
- Professional ($30/mo): 2,000 submissions, 5 GB, all premium plugins (webhooks, Zapier, Stripe, Mailchimp), auto-response emails, API access, 2 team members.
- Business ($90/mo): 20,000 submissions, 10 GB, unlimited team members, a rules engine, custom spam rules and honeypot.
- Custom: contact sales, for unlimited volume.
Yearly billing brings the three paid tiers down to an effective $10, $20, and $60 a month, which is why you'll see both sets of numbers quoted around the web.
The free plan works for a portfolio contact form. The friction is in the middle. $15 a month buys 200 submissions, about 7.5 cents each, and the integration a lot of developers want first (a webhook into their own app) still needs the next tier. A form that posts to a webhook costs $360 a year billed monthly, or $240 billed yearly.
OSForms has one hosted tier: 100 submissions a month, free, with every integration included. That's twice Formspree's free count with nothing gated inside it. Each form also gets a per-IP rate limit (10 requests a minute by default, adjustable) and a CORS allowlist, because those are safety features rather than upsells.
What OSForms doesn't have is a paid hosted tier. There is no $90 plan that takes 20,000 submissions a month off your hands; paid plans are planned but not live. Past 100 a month, the path today is self-hosting, which I cover below along with its rough edges.
Retention is the pricing difference people miss. Formspree's free plan keeps submissions for 30 days; paid plans lift that to unlimited. OSForms keeps them until you delete them, on the free tier too. The submission schema has no expiry logic at all. If you need a lead from six months ago and you aren't paying anyone, that matters more than the submission counts.
Integrations: Who Pays for What
This is the real split between the two products.
Formspree runs integrations on its side and prices them by tier. That's a coherent model: Formspree operates the connections and maintains a long list of them, and you pay for that convenience. It also means a subscription sits on top of API calls that cost little or nothing at the source.
OSForms works the other way. You bring your own keys, so the integration layer costs nothing extra; you pay the actual provider, if anything:
- Email goes through your own Resend API key. Resend's free plan covers 3,000 emails a month (capped at 100 a day), far more than a 100-submission form needs. You get a notification on each submission plus an optional auto-reply to the person who filled in the form, with
{{field}}variables filled from the submission. On Formspree, auto-response is a Professional feature. The form email notifications guide walks through the setup. - Google Sheets connects through your own Google account using the narrow
drive.fileOAuth scope, so OSForms can only touch spreadsheets it created, not the rest of your Drive. Each submission becomes a row, and when your form gains a field, the missing column is added to the header row for you. Details are in how to send form submissions to Google Sheets. - Webhooks POST a JSON payload (
event,formId,formName,submissionId,submittedAt,data) to any URL with a 30-second timeout. Set a secret and every request carries anX-osforms-Signatureheader: a hex HMAC-SHA256 of the raw body, with no prefix. Verifying it in Node:
const crypto = require('crypto');
// rawBody is the exact request body string, before JSON.parse
const expected = crypto
.createHmac('sha256', process.env.OSFORMS_WEBHOOK_SECRET)
.update(rawBody)
.digest('hex');
const received = req.headers['x-osforms-signature'] || '';
const valid =
received.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(received), Buffer.from(expected));The fair question about BYOK is whether handing a SaaS your Resend key is safe. Keys are encrypted at rest with AES-256-GCM, decrypted only when an integration runs, and never sent to the browser. Since the code is public, you can check that yourself. The bring-your-own-key explainer covers the trade-offs, which do exist; leaked keys just aren't the default one.
Reading data back out follows the same pattern. Formspree lists API access ("fetch all your submissions programmatically from a JSON HTTP endpoint") on Professional and up. OSForms has a read-only pull API on the free tier: create an osf_live_ key scoped to specific forms, then call GET /api/v1/submissions with cursor pagination. Pulls don't count toward your monthly quota, and the response never includes IP addresses or user agents. The pull API reference has the parameters.
Now the concession. Formspree's catalog is much wider: Zapier, Stripe, Mailchimp, Notion, Trello, and chat apps like Slack, Discord, Telegram, and WhatsApp (the chat ones even on the free plan). OSForms has exactly three integration types: email, Google Sheets, and webhooks. A webhook can reach anything with an HTTP endpoint, Zapier and Make included, but that's wiring you build, not a toggle. If your workflow lives on one-click Mailchimp sync or Stripe payments in the form, Formspree earns its subscription.
Data Ownership, Exports, and Self-Hosting
Formspree started as an open-source project and more or less created this category. The original repository was archived on July 14, 2023, and its README now says the hosted product's "source code is not available." What you sign up for today is a closed, hosted service. Your submissions live on its servers, and exports depend on your plan: CSV or JSON from Personal up, none on Free.
OSForms is MIT-licensed end to end, which matters in three practical ways:
- You can read the code that handles your data. The submission endpoint, the encryption, and the integration handlers are all public.
- You can export on any tier. Every form has CSV export of all submissions, free tier included. It's CSV only for now; if you want JSON files, Formspree's export is ahead, though the pull API returns JSON if you're scripting it.
- You can leave without a rewrite. Self-hosting isn't a separate enterprise edition. It's the same codebase, started with
docker compose upor deployed to Vercel with MongoDB Atlas, which is what osforms.com runs on.
Self-hosting has rough edges today, and you should know them before counting on it. System emails (signup OTP, welcome, failure alerts) are sent from fixed @osforms.com addresses, so a self-hosted instance can't deliver them yet; you verify your account by reading the OTP from MongoDB. And every account starts at the same 100 submissions a month. No env var changes that, but one updateMany in MongoDB does, as the self-hosting guide shows. Workable for a developer, not yet a turnkey install for a non-technical client.
That exit is the real lock-in test. If a hosted tool changes its pricing, your options are pay or rebuild. With OSForms the exit is git clone. The guide to owning your form data makes the longer argument.
Spam is where Formspree does more for you out of the box. Its Formshield filter applies machine learning to every plan, free included, with advanced controls on Professional and custom honeypots on Business. OSForms has no automatic filter. It gives you a honeypot field you name yourself (on every tier) plus reCAPTCHA or hCaptcha with your own site keys. Formspree wins this one if you don't want to configure anything.
Which One Should You Pick?
Pick Formspree if:
- Your form collects files. The clearest case. OSForms accepts multipart posts but stores a placeholder string, not the file. Formspree stores uploads from the Personal plan up: up to 25 MB per file and 10 files per submission, according to its file uploads help article.
- You need plugins beyond email, Sheets, and webhooks. Stripe, Mailchimp, Notion, and Zapier are toggles on Formspree and webhook projects on OSForms.
- You want spam handled without setup. Formshield runs on every plan with no keys to paste.
- You want high volume on someone else's servers. 20,000 hosted submissions a month on Business, with support and team seats, is a fair thing to pay $90 for when self-hosting is off the table.
Pick OSForms if:
- You want Google Sheets, webhooks, and auto-replies without a subscription. These are the features Formspree tiers at $15 to $30 a month, and they're free here because your own keys power them.
- Your data should outlive 30 days on a free plan. Submissions stay until you delete them, and CSV export and the pull API are on every tier.
- You want the exit hatch. MIT source and Docker self-hosting mean a pricing change can't strand you.
- You'd rather email go through your own provider. Notifications send from your Resend account, so the sending domain and delivery logs are yours.
The cheapest test is to run both free tiers side by side: Formspree's 50 a month against OSForms' 100. Setup is the same shape on each, one endpoint URL in your form's action, and the two-minute setup guide covers the OSForms half. Switching later in either direction is a one-line change. For the full set of options beyond these two, DIY serverless functions included, start with how to handle form submissions without a backend.
