What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Ninja Forms lets you build WordPress forms without writing the form markup yourself. Install and activate the plugin, open Ninja Forms → Add New, configure fields and submission actions, save with Publish, then place the form using a Gutenberg block, shortcode, post or page metabox, or a public link. The key to reliable forms is configuring both the visitor-facing form and what happens after submission: a success response, an administrator notification, and a stored submission record.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What Ninja Forms does in WordPress
Ninja Forms is a WordPress plugin with a free core offering and optional paid add-ons. Its drag-and-drop builder creates the form visitors see, while the Emails & Actions panel determines what WordPress does when someone submits it.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A new form normally includes three active actions: Success Message, Admin Email, and Record Submission. Together, they provide a confirmation for the visitor, an email notification for the site administrator, and a saved entry inside Ninja Forms. You can add other actions or integrations when the workflow requires them.
The basic process is the same for a contact form, feedback form, registration form, payment form, or marketing form. Templates can preconfigure a starting structure, but every field, label, requirement, and action remains editable.
#1 Best Overall
Prepare before creating the form
Decide what information you actually need before opening the builder. A short contact form might require only a name, email address, subject, and message. A registration or payment workflow may need additional fields and extensions. Knowing the outcome first prevents a form from becoming unnecessarily long or collecting data you will not use.
- Purpose: identify whether the form is for contact, feedback, registration, payment, marketing, or another workflow.
- Destination: decide which WordPress page, post, or publicly shareable link should display it.
- Data handling: determine whether you need a saved record, an email notification, an export, or an external integration.
- Workflow complexity: establish whether a single-page form is enough or whether you need conditional logic, multiple steps, calculations, file uploads, or payment processing.
- Protection: plan spam controls if the form will be publicly accessible.
Install Ninja Forms and open the builder
- In the WordPress dashboard, open the plugin installation screen and search for Ninja Forms.
- Install the plugin, then activate it.
- Open Ninja Forms → Add New.
- Choose Blank Form for a completely empty canvas, or select a template that matches your use case.
Templates are starting points, not fixed designs. Review every field and action before publishing. A template intended for one purpose may request information that is irrelevant to your audience.
Free tools Windows power users keep installed
One-click scans. No signup required.
Build the form fields
Use the builder’s Form Fields tab to add controls. You can click or drag fields into the form, then open each field’s settings to configure its behavior.
Choose only the fields the task needs
Common contact information and message fields are enough for many forms. Add a field only when its value affects a decision, a response, or a later record. A shorter form is easier for visitors to understand and easier for you to maintain.
Configure labels and instructions
Give every field a clear label that tells the visitor what to enter. Use the field’s available description or instruction setting when an example or format needs explanation. Keep wording specific: a label such as “Order number” is more useful than “Details.”
Set required status deliberately
Mark a field as required only when the submission cannot be processed without it. Requiring optional information creates unnecessary friction and can lead to abandoned submissions. Conversely, leaving an essential address or message field optional can produce records you cannot act on.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Set defaults, validation, and other options
Field settings can include default values, validation rules, and other options appropriate to that field. Use validation to catch an invalid value at the point of entry rather than discovering the problem after an email or record has been created. Preview the form after changing a rule so you can confirm the error message and correction path are understandable.
Configure what happens after submission
Open Emails & Actions after the fields are arranged. This is where you control the visitor response, notifications, storage, and any additional workflow.
Success Message
The Success Message action displays the confirmation after a submission succeeds. Edit it so the visitor knows the form was accepted and understands what happens next. If a response will be sent later, say so without promising a time you cannot meet.
Admin Email
The Admin Email action sends a notification when the form is submitted. Review that it is active and that its recipient and message settings match the person or team responsible for handling entries. Include the submitted information needed to act on the request, while avoiding unnecessary fields.
Record Submission
Keep Record Submission enabled when the site must retain entries in Ninja Forms. Email is not a substitute for a stored record: a message can be overlooked, filtered, or unavailable to another administrator. A recorded entry also gives you a place to verify whether the form accepted the submission.
Add other actions only when they serve the workflow
The same panel can contain redirects, additional email notifications, and other actions. Add an action when it has a clear purpose, then test the order and result of the complete submission. A redirect may take the visitor away from the form before they see a useful confirmation, so decide whether the redirect or a success message is the better experience.
Use advanced settings when the basic form is not enough
The core builder includes advanced controls for display settings, restrictions, and calculations. These settings are useful when a form needs more than a fixed list of fields.
Display settings
Use display controls to adjust how the form appears in its page context. Check the front-end result with the active theme rather than judging only the builder canvas.
Restrictions
Restrictions can limit how or when a form is used. Apply them only when the rule reflects a real process requirement, and test both an allowed and a blocked case before publishing.
Calculations
Calculations are appropriate when values entered in the form must produce a derived amount or result. Verify the calculation with small, typical, and boundary values. If the calculation drives a payment or other consequential action, treat the result as a workflow dependency and test it separately.
Extensions and integrations
Conditional logic, styling options, file uploads, payments, CRM connections, email marketing, and automation are available through documented add-ons or integrations. They are separate implementation decisions, not requirements for embedding an ordinary contact form. Add the extension category that matches the job instead of installing every available option.
Save and preview without confusing the two buttons
Click Publish in the builder to save the form. This button publishes the form configuration; it does not publish a WordPress post or page.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use Preview Changes to open a temporary page and interact with the form in the context of the active theme. Test field behavior, required messages, calculated values, the success response, and any redirect before placing the form on a public page.
Put the form on a WordPress page
Ninja Forms provides four publishing methods. Choose based on where the form should appear and how much control editors need.
| Method | Best fit | What the editor sees | Important behavior |
|---|---|---|---|
| Gutenberg block | A form placed in the block editor | A block preview in the editor | Select the form directly in the page layout, then verify the live front end. |
| Shortcode | A form inserted where shortcode text is supported | Shortcode text while editing | The shortcode becomes a form only when the live front end is viewed. |
| Post or page metabox | Editors who prefer the Ninja Forms panel attached to the post or page | A form-selection control in the editor screen | Publish or update the post or page after selecting the form. |
| Public link | A standalone, shareable form address | A link that can be copied or distributed | Use it when the form does not need to be embedded in an existing page layout. |
Insert with the Gutenberg block
- Edit or create the WordPress page where the form belongs.
- Add a Ninja Forms block.
- Select the form from the block’s form selector.
- Save or publish the page, then open the live page and submit a test entry.
Insert with a shortcode
- Open the form’s publishing or display controls and copy its unique shortcode.
- Paste the shortcode into the page or post at the position where the form should appear.
- Save or publish the page.
- Do not use the editor view as proof that the form is missing. The editor displays shortcode text; the form appears when you view the live front end.
Use the post or page metabox
- Open the post or page editor.
- Locate the Ninja Forms metabox.
- Select the form you want to display.
- Save or update the post or page, then test its public URL.
Share a public link
Use the form’s public-link option when a standalone URL is more useful than embedding the form in a page. Test the link in a private browser window so you see the same public experience as a visitor.
Choose an implementation that matches the workflow
| Requirement | Start with | Consider next |
|---|---|---|
| Collect entries for later review | Fields plus Record Submission | Export or an integration if another system must receive the data |
| Alert a site administrator | Admin Email | Additional notifications when different teams need different messages |
| Show a confirmation | Success Message | A redirect when visitors need to continue on another page |
| Show or hide fields based on answers | Conditional-logic add-on | Test every branch before publishing |
| Calculate a value | Core calculation controls | Payment or other integration if the result triggers an external transaction |
| Accept files | File-upload add-on | Review how uploaded files are handled and who receives them |
| Connect payments, CRM, marketing, or automation | The relevant documented add-on or integration | Confirm that the external service and Ninja Forms action both receive a test submission |
| Reduce spam | A supported spam-protection integration | Akismet, reCAPTCHA, hCaptcha, or Cloudflare Turnstile, depending on the site’s requirements |
Test the complete submission path
Testing should cover the visitor’s form, the WordPress record, and every notification. A form that displays correctly can still fail at the action stage.
Recommended Free Tools
- Open the live page or public link as a visitor would.
- Submit a realistic test with valid values.
- Confirm that the configured Success Message appears, or that the intended redirect occurs.
- Open Ninja Forms submissions and verify that Record Submission created an entry when storage is required.
- Check the configured administrator mailbox for the Admin Email.
- Repeat with an intentionally invalid or incomplete value to confirm required fields and validation behave as intended.
- If the form has conditional logic, calculations, restrictions, file uploads, or integrations, test each meaningful branch rather than only the simplest path.
Why Ninja Forms emails may not arrive
When a visitor says a form worked but no email appeared, separate the problem into three questions: did the form accept the entry, did the email action run, and did the message reach the intended mailbox?
First, verify that the submission exists
Check the Ninja Forms submissions area. If Record Submission is enabled and an entry is present, the form accepted the data even if the notification is missing. If no entry exists, return to the form’s fields, validation, restrictions, and actions and submit another controlled test.
Next, inspect the email action
Open Emails & Actions and confirm that Admin Email is active. Review its recipient and message settings for a typo, an outdated address, or a rule that excludes the current submission. A disabled or misconfigured action cannot deliver a notification even when the form itself appears on the page.
Check the receiving mailbox
Search the intended mailbox, including its spam or junk area, using the subject and sender configured for the action. If the message is present there, adjust the mailbox’s filtering rules or the notification’s identifying details rather than rebuilding the form.
Use the email-deliverability guidance
If entries are recorded and the Admin Email action is correctly configured but messages still do not reach the mailbox, follow Ninja Forms’ email-deliverability documentation for the site’s hosting and mail setup. Keep a recorded submission enabled while diagnosing delivery so you do not lose test data.
Check spam protection when submissions disappear
Spam integrations can block or challenge a submission before the normal workflow completes. Review the active protection settings and test an ordinary visitor path. Ninja Forms documentation lists Akismet, reCAPTCHA, hCaptcha, and Cloudflare Turnstile among supported spam integrations. A protection rule that is too aggressive can look like an email problem because no valid entry reaches the notification action.
Common setup mistakes and their fixes
- Expecting Publish to create a page: Publish saves the form configuration. Insert the saved form into a WordPress page or post separately.
- Assuming shortcode text means the form failed: Shortcode text is expected in the editor; inspect the live front end.
- Removing Record Submission because email is enabled: Keep the record action when entries must be retained or audited.
- Adding every available field: Remove fields that do not affect the response or workflow.
- Testing only the editor preview: Submit from the live page or public link as well, because theme context and front-end behavior matter.
- Installing an extension before defining the requirement: Decide whether the need is conditional logic, styling, uploads, payments, CRM, marketing, automation, or spam protection, then add only the relevant capability.
- Changing several actions at once: Test after each meaningful change so you can identify which setting altered the result.
A practical launch checklist
- The plugin is installed and activated.
- The form starts from an appropriate blank layout or template.
- Each field has a clear label and only necessary requirements.
- Defaults and validation match the information you need.
- Success Message is active and written for the visitor.
- Admin Email is active and addressed to the correct recipient.
- Record Submission remains active when entries must be retained.
- Any redirect, calculation, restriction, conditional branch, upload, payment, CRM, marketing, or automation action has been tested.
- The form is saved with Publish and checked with Preview Changes.
- The chosen block, shortcode, metabox, or public link is present on the intended destination.
- A live test confirms the visitor response, stored entry, and email notification.
- Spam protection is configured and does not block legitimate test submissions.
Maintaining the form after launch
Revisit the form whenever the process, recipient, or connected service changes. Confirm that the Admin Email still reaches the responsible team, that the fields still collect information you use, and that Record Submission remains enabled if retention is still required. When you add an integration or change a calculation, repeat the complete live submission test instead of relying on the builder preview alone.
For a simple contact workflow, the core builder and its default actions may be all you need. More complex requirements should be treated as deliberate extension or integration projects, with each new action tested from the visitor’s first click through the final record or external destination.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
