Black Friday 2026 is on Friday, November 27, with Cyber Monday following on November 30. For WordPress site owners it’s the one week a year when the plugins and services…
Table of contents
Which contact form template you end up with is mostly decided by the platform. Static sites tend to start from an HTML snippet and WordPress sites from a plugin template, while hosted builders such as Jotform give you an embed. Wix has its own forms built in, so a Wix site starts from yet another place. None of them send anything by themselves. That takes a handler, which might be a mail script, a plugin or a form backend.
Plenty of forms also fall down on the basics. WebAIM’s 2026 analysis of the top one million home pages (data from February 2026) found that 33.1% of form inputs were not properly labeled.
What a contact form template includes
Fields, styling, validation and a submit action, all pre-built, so a site owner can start collecting visitor messages without building the form from scratch. That’s the whole package.
A contact page is a different thing. It wraps the form with an address and opening hours, plus a map.
Core fields

Almost every template starts from name, email, subject and message. Their labels and input types matter more than the styling.
- A plain text input for the name, usually required.
- An email-type input, so phones show the right keyboard and the browser checks the format.
- The subject can be short text, though a dropdown is better if it routes the message to the right inbox.
- The message field is a multi-line text area, and it’s always required.
The submit button closes the form. Its text should name the action (“Send message”), not the default “Submit”.
On WordPress, the IvyForms simple contact form template is one starting point for this layout.
Every field beyond these adds effort for the visitor. A fuller breakdown of form fields and the input types behind them helps when a project needs something unusual.
Optional fields
Optional fields earn a place only when the team actually uses the answer. Phone number and company name are the usual extras, and a file upload field makes sense when people need to send screenshots or briefs. A consent checkbox is required wherever privacy law demands recorded consent.
Mark required fields with an asterisk or the word “Required”. Wix lets the owner pick either style, or none.
Labels stay visible above each field. Placeholder text disappears the moment a visitor types, so it hints at format and never replaces the label, as these examples of placeholder wording show.
Contact form template types by use case

Template libraries tend to sort contact forms into general, multi-step, booking and industry-specific versions. Which one fits depends on how much the team needs to know before replying. A browsable set of WordPress contact form templates shows the general type in practice.
| Type | Collects | Fits |
|---|---|---|
| General | Name, email, subject, message | Small business sites, blogs |
| Multi-step | The same data across several screens | Lead qualification, longer enquiries |
| Consultation booking | Contact details plus a time slot | Coaches, clinics, agencies |
| Industry-specific | Extra questions such as property or policy type | Real estate, insurance, photography |
Industry templates are the general form with different questions. involve.me ships real estate and insurance variants, and Visme lists photography, tenant and trade show versions.
Multi-step templates ask one or two questions per screen.
They suit forms that collect qualifying details beyond the basic four fields, and the examples in this set of multi-step form templates show how screen breaks and progress bars are handled. For a plain message form they add clicks without removing any effort.
Consultation booking templates merge the contact fields with a slot picker. When the visitor wants an appointment and not an answer, dedicated booking form templates beat a message form with a “when are you free?” line.
HTML libraries add layout to the mix. Colorlib’s HTML5 collection includes split-screen and Google Maps versions, and a map belongs on the page only when visitors travel to a physical location.
Contact Form Templates
Modern Contact Form
See the Pen
Modern Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Two-Column Contact Form
See the Pen
Modern Two-Column Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Dark Contact Form
See the Pen
Modern Dark Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Help Desk Support Form
See the Pen
Modern Help Desk Support Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Multi-Step Contact Form
See the Pen
Modern Multi-Step Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern E-commerce Contact Form
See the Pen
Modern E-commerce Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Conditional Logic Contact Form
See the Pen
Modern Conditional Logic Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Modern Split-Screen Contact Form
See the Pen
Modern Split-Screen Contact Form by Bogdan Sandu (@bogdansandu)
on CodePen.
Multi-Language Contact Form with Advanced Micro-Interactions
See the Pen
Multi-Language Contact Form with Advanced Micro-Interactions by Bogdan Sandu (@bogdansandu)
on CodePen.
HTML snippet, plugin or hosted builder: which template format fits?

Platform decides most of it, and submission volume decides the rest. Static and custom-code sites get an HTML snippet, WordPress gets a plugin template, and a hosted builder template is the fallback for everything else.
| Format | Sends mail by itself | Best fit | Main constraint |
|---|---|---|---|
| HTML/CSS snippet | No, needs a PHP script or form backend | Static and custom-code sites | You build and maintain delivery |
| Plugin template | Yes, through the site’s mail setup | WordPress sites | Advanced features sit in paid tiers |
| Hosted builder template | Yes, on the builder’s servers | Any site that accepts an embed | Monthly submission caps |
HTML and CSS snippets
Snippets cost nothing and give full control over the markup. Colorlib’s library is typical: it hands over the HTML and CSS files and leaves the backend or form service to you.
If you don’t want to write the markup from scratch, a contact form generator can help you create a basic HTML form with the fields you need. It’s a practical starting point for static websites and custom-coded pages, where you can adjust the layout and styling yourself. You’ll still need to connect the form to a working backend to receive submissions, since generating the HTML doesn’t handle delivery.
Bootstrap and Tailwind CSS cover the visual layer. The component classes are laid out in this guide to Bootstrap forms.
The upside is no plugin and no account, and no recurring fee either. You control the markup and the accessibility attributes, and nothing third-party loads unless you add it. The catch is that a snippet sends nothing until a handler is attached, and spam protection and validation are yours to build.
Plugin templates
Contact Form 7 lists 10+ million active installations on WordPress.org (October 2026).
In its default configuration it writes no personal data to the database, sends nothing to external servers and sets no cookies, per its plugin page. Switching on reCAPTCHA, Akismet or Turnstile changes that, because the submitter’s data, including the IP address, goes to the provider.
WPForms Lite goes the other way. It ships with more than 2,100 pre-built templates, but multi-page forms, file uploads and conditional logic belong to the Pro version, according to its WordPress.org listing.
A wider comparison of WordPress contact form plugins covers the rest of the field.
Delivery, templates and spam options all live in one admin screen, and updates arrive through WordPress. The plugin only works on WordPress, though, and the feature you need most often tends to sit behind the paid tier.
Hosted builder templates
Jotform, Tally and Typeform host the form and the delivery, and they keep the submission archive too. The site only embeds the result.
No markup and no mail setup is the draw. Against that, Jotform’s free Starter plan puts Jotform branding on every form, and design control stops where the builder’s settings stop.
Free tier limits
Free tiers cap submissions, not forms, and the caps differ by a factor of 5 between two common backends.
- Formspree’s free plan allows 50 submissions per month and no autoresponses (Formspree plans page, as of October 2026).
- Web3Forms gives 250 submissions per month on its free plan, hCaptcha included (Web3Forms pricing page, as of October 2026).
- Jotform Starter means 5 forms and 100 submissions per month (Jotform pricing, as of October 2026).
- Wix offers 4 free forms before a paid upgrade (Wix Help Center, as of October 2026).
Web3Forms stops accepting new submissions until the next month once the cap is reached, per its pricing FAQ.
Sources don’t all agree on Netlify Forms. Older guides describe it as limited to a small free monthly allowance, but Netlify’s own documentation, last updated in September 2026, says forms are free and unlimited on credit-based plans and metered only on legacy plans.
A form on a busy page reaches a 50-submission cap fast. For a low-traffic brochure site a free hosted tier is enough, but a page with steady enquiries is better served by a plugin or a self-hosted snippet with SMTP.
How to add a contact form template to a website
The process barely changes between platforms. The embed step is the only part that differs.
- Choose the template format that matches the platform.
- Set the recipient address, subject line and reply-to address.
- Add the form: paste the markup, insert a shortcode or block, or paste an embed snippet.
- Turn on spam protection before the page goes live.
- Send a test message from a different email address and confirm it arrives.
- Open the page at phone width and submit once more.
Static and custom-code sites
Point the form’s action attribute at a handler and set the method to POST. Formspree describes this as pointing a form at its endpoint, while Netlify asks for a data-netlify=”true” attribute on a form deployed to Netlify.
Netlify Forms only works on sites it builds. A snippet that must run on any host needs an independent backend such as Formspree or Web3Forms.
Markup habits like label association and input types are covered in this guide to HTML form best practices.
WordPress
Contact Form 7 adds a Contact menu and one block that inserts a saved form. WPForms Lite adds a form selector block and a builder that starts from templates.
A plugin is optional. A hand-coded form works as well, as this walkthrough on creating forms in WordPress without plugins shows, but the owner then writes the mail handler.
Wix and Squarespace
On Wix, open Add Elements, choose Contact & Forms, then drag a new form onto the page or pick one from Premade Forms.
The new Wix Forms include built-in spam filters with reCAPTCHA, and the owner raises the filter level in the form settings.
Squarespace builds forms into its editor through a form block, so the same pattern applies without extra code.
Hosted builder embeds
Hosted builders generate an embed snippet. Paste it into a custom code or embed element and the form renders from the builder’s servers.
The trade-off is design control. Jotform’s free Starter plan keeps its branding on every form, so a clean look means a paid plan.
How a contact form template sends submissions
Nothing in the template itself sends anything. Delivery needs a handler, meaning a server script, a plugin, or a backend endpoint that the form’s action attribute points to.
That handler can be a PHP file that calls mail() or uses PHPMailer with authenticated SMTP. It can be the WordPress plugin, sending through the site’s mail configuration. Or it can be a form backend like Formspree, Web3Forms or Netlify Forms, which receives the POST and forwards it by email.
Netlify Forms works differently from the other backends. Its build step scans the deployed HTML for a form carrying data-netlify=”true”, strips the attribute and injects a hidden form-name input, per the Netlify documentation (September 2026).
The form must therefore exist in the static HTML at deploy time. AJAX submissions need a URL-encoded body because Netlify does not support JSON form data.
Notifications and auto-replies depend on the service and the plan. Formspree sends autoresponses only from its Professional plan upward, and Wix builds its notification emails on Wix Automations.
What the visitor sees after sending is a separate setting. Netlify shows a generic success page unless the form’s action attribute names a custom one, while Wix lets the owner show a message or redirect to a URL. On WordPress, a plugin’s confirmation settings can show a success message, redirect to a page or custom URL, or hide the form after submit.
A clear form submission confirmation message states that the message arrived and when a reply comes.
A form that looks fine and sends nothing is one of the more annoying things to debug. The cause is usually one of these:
- No handler is attached, so the HTML posts to nowhere.
- PHP mail() has no mail server behind it. On Windows it reads the SMTP directive from php.ini, which defaults to localhost (PHP manual).
- A set sendmail_path makes PHP ignore the smtp, smtp_port and sendmail_from settings (PHP manual).
- Messages land in spam because they leave a web server without SMTP authentication.
On WordPress, the site’s WordPress email settings and an SMTP plugin fix the last two cases. Test every form from an outside address after any change.
Spam protection options for contact form templates
Start with a honeypot and add a CAPTCHA only when spam still gets through. A challenge costs every visitor a few seconds, while a hidden field costs them nothing.
A CAPTCHA is not mandatory. WCAG 2.2 (W3C Recommendation, 12 December 2024) does require alternative forms for different senses wherever one is used, so a puzzle with no alternative creates an accessibility failure of its own.
| Option | What the visitor sees | Where the check runs |
|---|---|---|
| Honeypot | Nothing | Your server or form handler |
| reCAPTCHA | v3: nothing. v2: a checkbox or a challenge | Google, verified on your server |
| hCaptcha | Checkbox or invisible challenge | hCaptcha, verified on your server |
| Turnstile | Managed, non-interactive or invisible widget | Cloudflare, verified on your server |
| Akismet | Nothing | Akismet’s spam database, WordPress plugin |
Honeypot field

A honeypot is an extra field hidden from people with CSS. Bots fill every field they find, and the handler discards any submission where the hidden field holds a value.
It stops simple bots and adds zero friction. A script that renders the page or targets only named fields walks straight past it.
The mechanics, including how to name the field so bots take the bait, are laid out in this explainer on what a honeypot is and how it traps form spam.
It’s free and invisible, and it’s also the weakest filter in the table.
Google reCAPTCHA
v3 runs without any visitor interaction and returns a score the site acts on. The v2 checkbox, the “I’m not a robot” box, either passes the visitor at once or shows a challenge. v2 invisible fires from an existing button, and by default only the most suspicious traffic sees a challenge.
One dated detail: as of October 2026, the reCAPTCHA guide on Google for Developers carries a deprecation banner that points to Google Cloud documentation. Check which console your keys live in before building on a template that hard-codes the old script.
Setup steps for the WordPress side are covered in this walkthrough on adding reCAPTCHA to a WordPress contact form.
It’s familiar, and v3 shows visitors nothing. The catch is that v3 hands you a score, so the template has to decide which score to reject.
hCaptcha
hCaptcha tokens expire after 120 seconds by default and work only once (hCaptcha developer guide, 2026).
That breaks many copied templates. A form that shows the widget but never posts the token to the siteverify endpoint blocks nothing, because the docs state that a frontend callback alone does not authorize a request.
The verification call must be a URL-encoded POST, not JSON. hCaptcha methods are API-compatible with reCAPTCHA, so moving an existing template over takes few edits.
A free account is enough to start, and the migration path from reCAPTCHA is short. A token that expires mid-typing forces a retry on long messages, though, and the server-side check is yours to write.
Cloudflare Turnstile
Turnstile runs small non-interactive browser challenges and picks the visible result per visitor. Cloudflare’s documentation lists managed as the recommended widget type, alongside non-interactive and invisible ones.
It can be embedded without sending site traffic through Cloudflare. Cloudflare also states that it does not access, store or transmit form entries, and that the widget is WCAG 2.2 AA compliant.
That conformance claim is the vendor’s own, so run a keyboard test on the finished form anyway.
In a WordPress form, a Turnstile field adds the widget from the builder, with no template code to edit.
Akismet
Akismet checks contact form submissions against a global spam database and shows the visitor nothing. Version 5.7 (April 2026) improved detection of automated front-end submissions, and 5.7.2 (19 August 2026) fixed its Fluent Forms integration on WordPress versions older than 6.1.
There’s no widget and no visitor friction. The API key is free for personal blogs, but business and commercial sites need a paid subscription.
Making a contact form template accessible
Before launch, every input needs a label or instruction and every error message has to name the field it belongs to. Name and email fields need autocomplete values, pointer targets should measure at least 24 by 24 CSS pixels, and text needs a 4.5:1 contrast ratio.
| WCAG 2.2 criterion | Level | What to test |
|---|---|---|
| 3.3.2 Labels or Instructions | A | Every input has a label or instruction |
| 3.3.1 Error Identification | A | The field in error is named and the error is described in text |
| 1.3.5 Identify Input Purpose | AA | Name, email and phone fields carry autocomplete values |
| 2.5.8 Target Size (Minimum) | AA | Buttons and checkboxes measure at least 24 by 24 CSS pixels |
| 1.4.3 Contrast (Minimum) | AA | Text reaches a 4.5:1 ratio against its background |
The W3C Recommendation of WCAG 2.2 is dated 12 December 2024. Criteria 2.5.8, 3.3.7 and 2.4.11 are new in 2.2, so a template written against WCAG 2.1 can miss all three.
These criteria become design rules in this guide to form accessibility best practices.
Error handling is where templates fail most. Colour alone cannot mark the bad field (criterion 1.4.1), so a red border needs a text message beside it.
When the fix is known, state it. “Enter an email address like [email protected]” meets 3.3.3 (AA), while “Invalid input” does not.
Wording is easier to borrow than invent, and these form error message examples cover the common failures.
Keyboard users need a visible focus indicator (2.4.7, AA). Under 2.4.11 the focused field also cannot be entirely hidden by author-created content, and a sticky header on a contact page is the usual offender.
Multi-step templates add one more rule. Criterion 3.3.7 (Redundant Entry, Level A) says information already entered in the same process is auto-populated or selectable, unless re-entry is genuinely needed.
Privacy and GDPR consent for contact form templates

A contact form needs a consent checkbox only when consent is the lawful basis for something the form does. Replying to an enquiry the visitor chose to send can rest on legitimate interests, which the ICO frames as a three-part test covering purpose, necessity and balancing (ICO guidance, updated 23 March 2026).
This is general information, not legal advice.
Where a checkbox is the right tool, the GDPR (Regulation (EU) 2016/679) sets some firm conditions.
- Recital 32 says silence, pre-ticked boxes or inactivity are not consent, so the box starts unticked.
- Article 7(2) requires the request to be clearly distinguishable from other matters in the form.
- Withdrawing consent has to be as easy as giving it (Article 7(3)).
- Article 7(4) weighs whether a service depends on consent to data it does not need.
A build checklist for all of this sits in this guide on how to create GDPR compliant forms.
Retention is the part templates ignore. Article 5(1)(c) limits collection to what is necessary, and Article 5(1)(e) allows identifiable data to be kept no longer than the purpose requires.
Pick a retention period for submissions and delete on that schedule. A form tool that archives entries by default leaves the clearing to the owner.
Spam services receive data too. Cloudflare states that Turnstile does not access, store or transmit form entries, while Akismet checks the submitted text against its database, so the message leaves the site.
The Akismet 5.3.1 changelog (January 2024) records a fix for contact forms that sent unnecessary data in the comment_content parameter. That makes the choice of spam filter a data minimisation decision.
Put a privacy policy link beside the submit button and name each processor in it. If legitimate interests is the basis, the ICO says the privacy information must state that and explain the interests.
Wording for the checkbox itself is easier to adapt than to draft, and these GDPR consent form examples show common phrasings. IvyForms adds the box as a dedicated GDPR field.
A template supplies the checkbox and the link, not compliance. The lawful basis, retention period and processor list are decisions the site owner documents.
When a contact form template is the wrong choice
A contact form template is the wrong tool when the form must route, validate or protect data in ways its settings cannot express.
| Situation | Why a template falls short | Better route |
|---|---|---|
| Sensitive or regulated data | Default setup emails data and involves third-party processors | A vetted processor and a risk assessment |
| Routing by answer, CRM sync | Default setup sends every message to one place | A form tool with conditional logic or integrations |
| Strict brand or WCAG target | Fixed markup and styling | A custom-coded form, tested |
| A handful of messages a year | The form adds spam and upkeep | A published email address |
Sensitive data is the hard stop. The ICO says legitimate interests is not often the most appropriate lawful basis where personal information is used in ways people would not reasonably expect or that could carry high risk, and a data protection impact assessment is required where processing is likely to result in a high risk to individuals.
Netlify’s documentation adds a concrete case: forms that accept file uploads containing personally identifiable information need extra security configuration, and it points to the Very Good Security integration. A contact form template that quietly accepts ID scans or medical documents has skipped that step.
Routing is the second limit. Showing fields by answer, or sending sales questions to one inbox and support to another, requires conditional logic, which basic templates often leave out. Separate inboxes can also be handled with conditional sending in the form’s notification settings.
Goal mismatch is the third. A site that wants qualified leads at volume needs a different form, a distinction covered in this comparison of contact forms and lead generation forms.
Design limits matter when the standard is strict. A hosted embed whose markup you cannot edit cannot be fixed on your side if it fails a WCAG check.
For a site that receives a handful of messages a year, a published email address does the job with nothing to maintain. The cost is that scrapers can harvest it.
Contact Form Templates FAQ
How many fields should a contact form have?
As few as the reply needs. Name, email and message cover most sites, and a subject line earns its place only when messages route to different inboxes.
GDPR Article 5(1)(c) also limits collection to what is necessary for the purpose.
Should the phone number field be required?
No, unless someone will actually call back. A required phone field asks every visitor for data that only some replies use.
Where the field stays, give it the telephone input type and the tel autocomplete value so browsers can fill it (WCAG 1.3.5).
Can I use a free HTML template on a commercial site?
Usually yes, but the license decides. Colorlib lists its Contact Form v7 template under CC BY 3.0, which allows commercial use and requires credit to the author.
Read the license line on every template before it goes live.
How do I restyle a template to match my brand?
On an HTML snippet, edit the CSS for colours, fonts and button styles. On Wix, the form settings include a Design tab covering the background, fields, header, paragraphs and buttons.
Retest text contrast and the focus outline afterwards, because a new palette changes both.
Can I add a file upload field to a template?
Yes, wherever the form handler supports it, and every handler sets limits. Netlify Forms accepts a file input, allows one file per field, caps the form request at 8 MB and times uploads out after 30 seconds.
Check the equivalent limits on any plugin or builder before promising visitors they can attach large files.
Keeping a Contact Form Template Delivering After Launch
What keeps a template form working is testing the full path from submit button to inbox, once after launch and again after every change to hosting, plugins or mail settings.
Send a test from an outside address, and send a real-looking message past the spam filter too. Repeat both after each change.
Delivery goes first because a failing handler and an over-strict spam filter both end the same way, with a message that vanishes.
The trade-off is a recurring manual test, since a form that fails silently raises no error for anyone.
Plan limits and platform behaviour change, so caps and documentation verified in October 2026 deserve a recheck before launch.
Once delivery holds, the next measurable gain comes from ways to increase form conversions.


