GriffinForms – Contact Form and Form Builder

GriffinForms is a free drag-and-drop WordPress form builder plugin for contact forms, multi-step forms, user registration forms, file upload forms, and payment forms. All core features are free — no paywalls, no upgrade required. It handles a simple contact form as easily as a multi-step application. Build with a visual editor, store all submissions in your WordPress database, and layer in conditional logic, spam protection, MailChimp integration, and AI form building with Griffin Assist — all included in the free core. GriffinForms Pro GriffinForms Pro is an optional paid add-on. It adds Square payments, Google Sheets sync, Klaviyo marketing integration, premium field types (Signature, Rating, Rich Text, Image Selection, Likert Scale), submission export (CSV, JSON, Excel), and frontend submission editing. The core plugin remains free and fully functional without it. Why GriffinForms?

• Free core, no feature walls on the essentials: multi-step forms, user registration, file uploads, Stripe and PayPal payments, conditional logic, spam protection, and email notifications are all included in the free plugin — no licence required.
• Multi-step forms: break longer forms into pages with per-step validation so users can complete structured flows without feeling overwhelmed. You can also add an optional progress bar — stepper or tabs style — so users always know where they are in the process.
• WordPress user registration: create WordPress users from form submissions with immediate, pending-activation, or manual-review workflows, multiple registration workflows per form, role assignment, duplicate-account handling, and account-action visibility in the admin area.
• File uploads: support multi-file uploads per field with controls for file types, size limits, file counts, image constraints, and storage behavior.
• Stripe and PayPal payments: build WordPress payment forms with product-style workflows, product images, a cart-style review step, hosted checkout options, and resume links for pending payments.
• MailChimp integration: subscribe form submitters to MailChimp audiences as part of the submission flow — map form fields to MailChimp merge tags, assign tags, and control consent behavior per form.
• WordPress conditional logic: go beyond simple show and hide with rules that can change labels, values, headings, success messages, redirects, and submit behavior — across fields, rows, and pages.
• Email and notifications: send notifications and autoresponders through WordPress mail, Custom SMTP, SendGrid, or Mailgun, with reusable messages and merge variables.
• Spam protection: choose from reCAPTCHA, hCaptcha, Cloudflare Turnstile, or honeypot, and combine them with native rate limiting on submissions and file uploads for layered protection.
• Builder checks system: a live status bar in the form builder surfaces errors, warnings, and info counts as you edit — covering spam config, email setup, compliance, registration risks, and layout issues before you publish.
• Compliance profiles: per-form GDPR and HIPAA-ready profiles with submission hashing, layout snapshots, configurable retention, and WordPress personal data export and erase integration.
• Templates and theming: turn forms into reusable templates, then style them with built-in themes or your own custom theme variations.
• Submission clarity in WordPress: review entries in a richer admin view with event timelines, per-submission audit logs, metadata, and settings history when troubleshooting production forms.
• Switching from another plugin: if you are already running Contact Form 7, WPForms Lite, Ninja Forms, or Formidable Forms, GriffinForms includes a guided migration tool that imports your existing forms and submissions so you can move without starting over.

Drag-and-drop form builder GriffinForms treats layout as a core part of form building. The drag-and-drop builder uses pages, rows, columns, sidebar controls, and reusable fields to make complex forms easier to shape and maintain. Then you can layer in conditions, uploads, notifications, and payments where needed. This makes longer forms easier to manage and easier for users to complete. Reusable fields also help solve a common admin problem: teams should not need to recreate the same Name, Email, Phone, or Address field across every new form. Common fields can be managed from one place, which helps keep repeated workflows faster to build and more consistent over time. File uploads with practical control File uploads are not limited to a basic attachment field. GriffinForms supports multi-file uploads per field and is designed for workflows where uploads matter, such as applications, support requests, and document collection. For example, an application form can collect resumes, ID documents, certificates, and supporting images in one submission instead of forcing users to send files separately later. You can control allowed file types, per-file and total upload size limits, max file counts, image-specific constraints, and storage behavior, then manage uploaded files from WordPress. Payment workflows with Stripe and PayPal If you enable Stripe or PayPal, GriffinForms can handle payment collection inside the form flow. This is useful for donations, simple product or service requests, paid applications, and other workflows where payment is part of submission instead of a separate checkout. GriffinForms supports a fuller review-and-pay pattern with product-style selections, product images, and cart-style summaries. Stripe can stay on-page for card collection, while PayPal uses its hosted popup approval flow. For pending payments, resume links can bring users back so they can continue from where they left off. Payment workflows can also gate user registration — combining payment collection with WordPress account creation in a single form makes it straightforward to build paid membership signups, paid course registrations, and other workflows where account access should follow a successful payment. Strong conditional logic layer Conditional logic in GriffinForms goes beyond a simple show-or-hide toggle. You can use field, row, and form-level rules to change labels and values, control headings and visibility, swap success messages, trigger redirects, and adjust submit-button behavior. Conditions also go beyond basic text matching. GriffinForms supports checks across field values, counts, password strength, browser time, address parts, and payment-specific conditions such as product, gateway, totals, and counts. That makes it useful for smarter routing, cleaner payment flows, and forms that react as the submission takes shape. For example, you can change the success message or redirect users to a different destination based on what they selected in the form. Themable forms with deeper styling control Forms should not look disconnected from the rest of your site. GriffinForms includes built-in themes, but the theme system goes further than picking a preset. You can create new themes from scratch or modify existing ones with control over typography, layout, inputs, buttons, and states such as hover, focus, and active. Dark themes also look especially strong in GriffinForms, which helps when you want forms to feel more polished and deliberate instead of settling for one generic form look. Submissions, logs, and admin visibility Submissions are stored in your WordPress database, but the admin experience goes further than a simple entry list. GriffinForms includes a richer submission view with metadata, payment context where applicable, submission-specific logs, and event timelines so you can follow what happened to a submission and where it changed. Native logging adds another layer of visibility for production sites. Timeline-style logs, searchable categories, job visibility, retention settings, and settings history make it easier to troubleshoot failed steps, trace changes, and understand what happened over time. GriffinForms also supports partial submissions, which means incomplete multi-step submissions can still remain visible in the admin area when that workflow matters. WordPress account registration workflows GriffinForms includes a flexible user registration workflow for registration forms that need to create or manage WordPress users after submission. You can build a simple WordPress registration form for one account, or use an iterable email field for multi-user registration from a single form submission. GriffinForms lets you choose whether a registration form should use a mapped password or send the native WordPress password setup link, assign the WordPress user role for the account being created, and map optional profile data such as username, first name, last name, and profile image when the form collects it. This user registration system is built for real workflows, not just one fixed registration form pattern. You can decide whether user registration happens immediately, waits for admin activation, or stays in manual review, and you can control how duplicate-account cases are handled. GriffinForms also gives registration forms stronger admin visibility through native logging, submission-side account activity, account-action follow-up, and builder checks that help catch missing mappings, risky password choices, and iterable registration-form edge cases before the form goes live. Helpful docs:

• Registration workflow modes
• Submission Accounts Accordion
• Password strategies

Spam protection and rate limiting GriffinForms supports multiple CAPTCHA providers, including reCAPTCHA, Cloudflare Turnstile, and hCaptcha. It also includes native rate limiting and backend anti-spam checks, so spam protection does not depend on a single layer. That protection applies across the submission flow, including workflows that use file uploads. Email delivery and notifications GriffinForms can send admin notifications and autoresponders through WordPress mail or configured delivery providers — Custom SMTP, SendGrid, or Mailgun — without requiring a separate SMTP plugin. Notifications are queued and processed in the background so form submissions are never blocked by email delivery latency. Helpful docs:

• Email settings
• Managing messages
• Mail merge placeholders

Griffin Assist — AI form building inside the builder Griffin Assist is GriffinForms' built-in AI form builder for WordPress. Describe the form you need using plain-English prompts, and Griffin Assist drafts the structure for you. From there you keep full control — drag, rearrange, and fine-tune using the same builder you already know. This is not a separate AI tool that hands off a static export. Griffin Assist works inside your live draft, so changes appear immediately in the builder as you prompt them. Drafting a new form: type a prompt in the Create Form modal and Griffin Assist generates a starting structure with pages, rows, and fields. The draft opens in the builder ready for you to refine. When you are happy with it, publish it to make it live. If you want to start over, discard it — your other forms are never affected. Editing an existing form: open any form in AI draft mode using the AI Edit action. Griffin Assist targets only the elements you ask about, so editing a field label or adding a new page does not rebuild the whole form or disturb fields and logic you already configured. Chat Mode: toggle Chat Mode on to ask questions, explore ideas, and get suggestions before committing to a change. Griffin Assist returns clickable action buttons so you can review a suggestion and apply it with one click. Structural suggestions such as adding a new section, page, or row appear alongside copy advice. Suggestion pills: each element type in the builder has a set of context-aware suggestion pills — one-tap actions tailored to what is currently selected. Improving a field label, polishing a description, adding a file upload hint, or refining dropdown options all have their own targeted pills. Translation is also available as a one-tap action that rewrites all labels, descriptions, options, and button text into your target language. Griffin Assist requires an active AI provider connection. You can connect OpenAI, Anthropic, Google Gemini, xAI Grok, or Mistral from the AI settings tab using your own API key. Griffin Assist also works with WordPress 7 AI Connector keys — if a provider is already configured site-wide through WordPress Connectors, Griffin Assist uses it automatically with no separate setup. A data-sharing consent step is required before Griffin Assist sends any form data to an external provider. Gutenberg and advanced workflows GriffinForms works with Gutenberg and also includes a stronger technical foundation for advanced evaluators, including a documented REST API surface, capability-aware access control, device management for protected companion routes, and webhook-ready architecture. Multi-step submissions use AJAX handling with server-side validation and anti-spam checks, which helps longer forms feel more responsive while still enforcing validation on the backend. Post-submission actions such as emails and other follow-up work can also be processed in the background, which helps more complex workflows stay smoother after a form is submitted. These are not the first thing most users need, but they are there when the deployment calls for them — whether the form is a simple contact form or a complex multi-step workflow. Helpful docs:

• Embedding forms
• Multi-page forms
• Conditional logic

Privacy-conscious by default Form submissions stay in WordPress by default. External services are only involved when you enable them, such as payments, CAPTCHA, or email delivery providers. See the External Services section below for details. GriffinForms also includes per-form compliance profiles (Standard, GDPR, and HIPAA-ready) with submission hashing, layout snapshots, configurable retention policies, and WordPress personal data export and erase integration when those workflows matter. External Services GriffinForms can connect to these third-party services when enabled:

• Google reCAPTCHA (spam protection): Terms and Privacy
• Stripe (payments): Terms and Privacy
• PayPal (payments): Terms and Privacy
• Cloudflare Turnstile (spam protection): Terms and Privacy
• hCaptcha (spam protection): Terms and Privacy
• SendGrid (email delivery): Terms and Privacy
• Mailgun (email delivery): Terms and Privacy
• MailChimp (audience sync): Terms and Privacy
• OpenAI (AI form building, when configured): Terms and Privacy
• Anthropic (AI form building, when configured): Terms and Privacy
• Google Gemini (AI form building, when configured): Terms and Privacy
• xAI Grok (AI form building, when configured): Terms and Privacy
• Mistral (AI form building, when configured): Terms and Privacy
• GriffinForms deactivation feedback (optional, only when you submit feedback while deactivating the plugin): if you select a reason and choose to send feedback, GriffinForms transmits that reason, any optional comment you write, your site name and URL, and your plugin, WordPress, and PHP versions to a GriffinForms-owned endpoint so we can improve the plugin. Your administrator email address is included only if you tick the "allow contact" option. Nothing is sent if you choose "Skip & Deactivate." Feedback is delivered through GriffinForms infrastructure and the Brevo transactional email service. If you tick the "allow contact" option, your feedback is also raised as a support request in GriffinForms' Zoho Desk helpdesk so we can follow up with you. GriffinForms: Privacy. Brevo: Terms and Privacy. Zoho: Privacy.

Learn more

• Documentation: GriffinForms Docs
• User docs: GriffinForms User Docs
• Templates: Form Templates
• Releases: Release Notes
• Privacy: Privacy Policy

Use-case guides

• WordPress contact form
• WordPress user registration form
• WordPress multi-step form
• WordPress payment form
• WordPress file upload form
• WordPress conditional logic form

3.2.4.0 – 2026-07-11 Minor

• Reworked the optional deactivation feedback so it is delivered reliably through a hosted GriffinForms service instead of depending on your site's own mail server, which frequently failed to send. The deactivation prompt itself is unchanged — sharing a reason is still entirely optional, and deactivation always completes immediately whether or not you leave feedback.
• When you tick "I'm happy to be contacted about this" and provide your email, that feedback is now routed to GriffinForms support so we can follow up, in addition to the anonymous reason summary.
• Disclosed the deactivation feedback service and exactly what it sends in the External Services section of this readme, in line with WordPress.org guidelines. Data is only ever sent if you choose to submit feedback on deactivation.

3.2.3.0 – 2026-06-10 Minor

• Introduced a Column Manager for all list views. A columns icon in the list toolbar opens a modal where you can show or hide columns, drag them into any order, choose a display variant for columns that support multiple formats (such as showing a username with or without the full name), set a custom percentage width per column, and control how many items appear per page. Preferences are saved site-wide and persist across page loads.
• Added optional Last Edited and Last Editor columns to all list surfaces that track edit history. Last Editor supports a username-only display variant.
• Added Klaviyo as a recognised marketing integration in Core. A Klaviyo icon appears on submissions that have been synced, and the single submission page shows a Klaviyo marketing activity card alongside other integration cards. Full sync functionality activates with GriffinForms Pro.
• Fixed the single log entry page so the related-item ID cell renders its "Open" link as a clickable link instead of printing raw HTML.
• Corrected Column Manager label mismatches where the modal showed a different name than the table heading for four columns: Attachments (submissions), Signals (forms and submissions), Log Type (logs), and Date / Time (logs).
• Renamed the internal isread column key to readstatus for clarity; existing preferences migrate automatically on next save.

3.2.2.0 – 2026-06-08 Patch

• Square is now a recognised payment option in GriffinForms. Full payment processing is activated by the Pro plugin.
• Fixed the payment field builder preview so a single product card no longer stretches to fill the full field width when only one product is configured.
• Fixed the payment field in the Gutenberg block preview so configured products now render as actual cards instead of a static placeholder.
• Fixed the address field country dropdown in the Gutenberg block preview inheriting an unwanted minimum height from the global select control rule.

3.2.1.0 – 2026-06-06 Patch

• The command palette resting pill now updates immediately when the form name is saved via the inline canvas input or the Form Options modal — no page reload required.
• The native <select> preview for dropdown fields in the builder now stays in sync with option changes made in the inline option editor. Adds, deletes, renames, and reorders are all reflected after each save.
• Previous, Next, and Submit button labels are now editable directly on the builder canvas — click the button text, type, and the label saves on a short debounce. The Page Navigation Editor accordion in the right sidebar has been removed.
• Form Options and Notifications modals now fetch fresh content from the server each time they open, so changes made via inline editing or AI database patching are immediately visible without a page reload.

3.2.0.0 – 2026-06-06 Minor

• Fixed a builder bug where the last radio or checkbox option could refuse to move when you tried to drag it upward.
• Improved no-theme frontend styling so form buttons follow the active site theme more naturally instead of feeling visually out of place.
• Cleaned up no-theme frontend details, including validation message styling, Likert table borders, stepper presentation, and excess empty space inside payment cards.
• Fixed the builder so switching back to the default style correctly clears the previously applied themed background.
• Improved publish-location tracking so forms embedded with shortcodes or the Gutenberg block are recorded more reliably when posts and pages are saved.
• Reduced builder clutter by hiding empty form, page, and row headings/descriptions until they are actually needed.
• Fixed Gemini provider errors being shown as misleading Griffin Assist validation failures.
• Added clearer Gemini quota error messaging when the connected Google AI project has no usable request quota.

3.1.9.0 – 2026-06-02 Patch

• Griffin Assist thinking stream is now rendered live in the chat window as it arrives, giving real-time visibility into the AI reasoning phase. The stream clears automatically when the final response lands.
• Batch operations now show an incremental per-item status list in the chat — each item progresses through waiting, working, and done states as the operation runs.
• The intent classifier now returns structured output (operation, target scope, target attribute, batch flag, and confidence) fed from the operation catalog, replacing the coarse three-value classification. When confidence is low, the assistant surfaces candidate paths as clickable options rather than guessing.
• Payment field product cards on the builder canvas now support inline editing — click any product name, price, or description to edit it in place without opening a panel. Image placeholders have an Add Image button that opens the WordPress Media Manager. Add Product remains a separate canvas panel for new products only.
• The builder canvas now shows an aurora-style animated overlay while a Griffin Assist request is in flight, blocking accidental edits and signalling AI activity.
• Clicking a form name in the All Forms list now navigates directly to the form builder. The deprecated Edit Form page is no longer the default destination for that link.
• The "Show page headings" toggle in the progress bar settings has been renamed to "Use page headings as step labels" to accurately reflect its behaviour. The Step Name field description now cross-references the toggle. No logic or storage changes.
• Submissions list has a dedicated Read/Unread column immediately after the submission name, moving the unread orb out of the Signals column.
• Date range filters on list pages now convert site-local day boundaries to UTC before comparing against the stored created timestamp, fixing incorrect results on sites with a UTC offset.
• The right-sidebar accordion on single submission pages now opens the first panel by default instead of the User Registration panel.
• Required field indicator is now a global setting under Settings → General. Choose an asterisk (default), custom text, or nothing. The setting propagates to the frontend, builder preview, Gutenberg block preview, and template previews.
• Conditional logic value inputs for text-type conditions now render as a contenteditable rich field with inline variable tag pills instead of a plain textarea. Tags are removable and the Insert Variable button has been redesigned.
• Deleting a dropdown option while another option's label is being edited no longer triggers a race condition that restores the deleted option.
• Column headers on the Forms, Submissions, and Logs list tables no longer wrap to a second line at narrow viewport widths.
• No-theme mode now applies explicit font weights to field labels (600), checkbox and radio labels (500), and floating labels (400) to prevent site-theme inheritance from affecting form typography.
• Recent entries widget in the builder right sidebar now renders nonce-failure responses as a styled error message instead of displaying raw JSON.
• Checkbox and radio option groups on the frontend are now flush with the left edge. Bootstrap's default left indent is removed via a scoped CSS override.
• Fixed a PHP 8.4 deprecation notice on the New Form and Edit Form pages caused by InputRadio passing a null css_class to wp_kses_post. Fixed a second deprecation on the New Message page caused by RichText passing a null value to wp_editor.

For earlier release notes (3.1.8.0 and below), see https://griffinforms.com/releases/