RSVP form

An RSVP form that collects a name, a yes/no/maybe, and a guest count, then emails each reply to you. The backend is already wired in, spam is filtered, and there is no CAPTCHA between your guests and their reply.

How to use this form

  1. Create a form in your Formpaste dashboard and copy its access key.
  2. Paste the template below into your project and swap YOUR_ACCESS_KEY_HERE for your key.
  3. Set your destination email and allowed domains in the dashboard.
  4. Deploy - submissions land in your inbox, spam filtered, no CAPTCHA.

Framework guides for this form

Prefer a guide for your exact stack? Open the per-framework walkthrough.

What is an RSVP form?

An RSVP form collects replies to an invitation. A guest confirms whether they are coming, and how many people they are bringing, and you get a running headcount without chasing anyone by text or in a group chat. It is the difference between guessing how much food to order and knowing.

The form does one job and does it cleanly: turn “are you coming?” into structured data you can total. Because attendance is a dropdown and guest count is a number, you are not left parsing free-text replies like “yeah probably, might bring my partner” into a spreadsheet at 11pm the night before.

When to use it

Reach for an RSVP form any time you need a headcount ahead of a date. A birthday party, a wedding, a workshop, a company offsite, a community meetup, or a webinar all work the same way: send the link, let people reply on their own time, and watch the count build.

It shines when the guest list is bigger than you can track in your head but the event itself is informal enough that you do not need ticketing or payment. If money changes hands or seats are limited and enforced, reach for a proper ticketing tool. For “tell me if you are coming,” this is the lightest possible way to find out.

What to include

This template carries exactly the fields an RSVP needs. Name and email are required, so you know who replied and can reach them if plans change. The attending field is a select with Yes, No, and Maybe, so every reply is one of three clean values you can filter and count instead of interpreting. A guests number field captures party size, so totaling your headcount is arithmetic rather than reading.

That combination, name plus email plus a dropdown plus a number, covers the vast majority of events. Keep it that lean on purpose. The one field worth adding, and only if you truly need it, is a short notes textarea for dietary restrictions or accessibility needs. Everything beyond that is friction that quietly costs you replies from the guests who are already halfway out the door.

Tips for an RSVP that gets a reply

Confirm you have them down. Reply-to is set to the guest, so a one-line “Great, see you there” reply doubles as their confirmation and reassures anyone who was not sure their RSVP went through.

Count with the structured fields, not by reading. Because attending is a select and guests is a number, you can sort by “Yes” and sum the guest column in seconds. Do not undo that by adding a free-text “will you attend?” field alongside it.

Pipe big lists somewhere you can see them. If you are tracking more than a handful of guests, forward each RSVP to a spreadsheet with a webhook so the whole list lives in one sortable place instead of scattered across your inbox.

Also works on

No dedicated guide yet, but this form drops into any of these too. Open the platform overview to get started.

Frequently asked questions

Paste a form. Get submissions.

Instantly without setting up any backend, servers or databases. 250 submissions/mo free - no credit card.

More form templates