A WordPress Contact Form Without a Plugin

Skipping the plugin entirely

Every WordPress forms plugin adds the same things: a settings screen, its own database tables, front-end CSS and JS enqueued on every page that has a form, and a permanent line item in your update queue. For a single contact form, that's a lot of surface area for something a plain HTML form can do on its own.

The whole setup

Add the form directly to a page (via a Custom HTML block in the block editor) or into a template file if you're working in a child theme, and point its action at a FormBridge endpoint:

<form action="https://app.formbridge.ai/api/forms/fb_8h2k9p" method="POST">
  <input name="full-name" placeholder="Full name" />
  <input name="email" type="email" placeholder="Email" />
  <textarea name="message" placeholder="Message"></textarea>
  <button type="submit">Send</button>
</form>

No shortcode, no plugin settings page, no PHP mail configuration to get right — the form posts straight to FormBridge, which handles delivery.

Why this holds up as a real contact form, not just a demo

• Notifications — set a recipient list, CC list, and subject line from the form's Email Settings, so the right people get alerted every time.
• Autoresponder — reply automatically to the submitter using merge tags pulled from your field names, e.g. {{Full-Name}}.
• Spam protection — every submission is scored automatically before it reaches your inbox, and you can add a honeypot field, CAPTCHA, or an authorized domains allow-list without installing anything.
• File uploads — add enctype="multipart/form-data" and a file input if you need attachments; no extra configuration required.
• An inbox with history — every submission, its status, and a processing log, viewable and exportable to CSV without opening your email client.

Field names are yours to choose

FormBridge doesn't require a naming convention — full-name, email, and message above are just descriptive names, not something you register anywhere first. Hyphenated names are recommended because they get auto-formatted for display and turned into a merge tag automatically, but any name works.

Setting it up

1. Create a form endpoint and copy its URL.
2. Paste the HTML form into a Custom HTML block or your template file.
3. Set notification recipients and, optionally, an autoresponder.
4. Enable spam protection layers from the form's settings if you're getting unwanted traffic.