Ninja Forms lets you build and publish WordPress forms without writing form code. Install and activate the plugin, open Ninja Forms → Add New, configure fields and submission actions, then place the finished form with a block, shortcode, metabox, or public link. This guide explains the complete workflow, including email notifications, saved submissions, advanced options, and the checks to make when messages or entries are missing.
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 for creating forms in a visual builder. A new form can start as a blank form or as a template for a common workflow such as contact, feedback, registration, payment, or marketing. You add fields, set their behavior, decide what happens after submission, and then publish the form where visitors can use it.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The plugin has a free core offering with optional paid add-ons. The WordPress.org listing describes Ninja Forms as part of WordPress since 2011. Features such as payments, customer-relationship-management connections, email marketing, automation, file uploads, conditional logic, and advanced styling depend on the relevant add-on or integration rather than on the basic embed process.
What you need before creating a form
- A WordPress site where you can install and activate plugins.
- Access to the WordPress dashboard.
- A clear purpose for the form, such as collecting contact requests, feedback, registrations, or payments.
- A decision about what must happen to each submission: save it in WordPress, send an email, redirect the visitor, show a success message, or pass the data to another service.
- The page, post, or public URL where visitors should find the form.
Planning the destination and the data-handling requirement first prevents a common mistake: publishing a form that appears on the site but does not retain entries or notify the right person.
#1 Best Overall
Install Ninja Forms and open the builder
- In the WordPress dashboard, open the plugin installation screen.
- Search for Ninja Forms, install it, and activate it like any other WordPress plugin.
- Open Ninja Forms → Add New.
- Choose Blank Form for a form you want to design yourself, or select a template that matches the workflow you need.
A template is a starting configuration, not a finished publishing step. Review every field, label, required setting, notification recipient, and action before putting the form on a public page. A blank form gives you the same builder without preconfigured fields.
Build the form fields
Open the Form Fields tab
In the builder, use the Form Fields tab to add controls. You can click a field or drag it into the form. Arrange the fields in the order visitors should complete them, beginning with the information needed to identify or respond to the request.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsConfigure each field
Open a field’s settings and configure the options that apply to it:
- Label: Tell visitors exactly what information belongs in the field.
- Required status: Make a field mandatory only when the submission cannot be processed without it.
- Default value: Pre-fill information when a known starting value is useful.
- Validation: Apply the available validation so the submitted value matches the expected format.
- Other field options: Review any settings exposed for the particular field type before saving.
Keep labels specific. “Email address” is clearer than “Contact,” while “What do you need help with?” gives a visitor more direction than “Message.” Required fields should be limited to information that is genuinely necessary; otherwise, visitors may abandon the form or enter unusable data simply to submit it.
Check the order and usability
After adding fields, read the form from a visitor’s point of view. Confirm that the sequence is logical, that instructions appear next to the field they explain, and that the required status reflects the actual process. Use the builder’s preview later to test the completed flow in the active theme.
Configure what happens after submission
Open Emails & Actions
Open Emails & Actions in the builder. New forms normally include active Success Message, Admin Email, and Record Submission actions.
Keep Record Submission enabled when entries must be retained
Record Submission stores the submitted entry in Ninja Forms. Leave it active when you need a WordPress record that can be reviewed later, even if an email is also sent. Email alone should not be treated as the only copy of a request when the site needs an internal submission history.
Set the Admin Email action
Edit Admin Email to define the notification sent after a submission. Check the recipient address, subject, and included submission data. Make sure the action is active. If different people handle different forms, set the recipient for that workflow rather than relying on an address copied from a template.
Email notification and stored submission are separate actions. A form can record an entry without successfully delivering an email, or send an email while the record action is disabled. Configure both when the workflow requires both outcomes.
Choose the visitor’s success response
Edit Success Message to tell the visitor what happened after submission. The message should confirm receipt and explain the next expected step, such as waiting for a reply. If the process needs to send visitors to another page, add or configure a redirect action instead of leaving the visitor uncertain about whether the form worked.
Free tools Windows power users keep installed
One-click scans. No signup required.
Add other actions only when the workflow needs them
Ninja Forms supports additional actions for redirects and other behaviors. Add only the actions that serve a defined requirement. Extra actions make testing more complicated and can create an outcome that does not match the message shown to visitors.
Use advanced settings and extensions appropriately
Core advanced controls
The documented core controls include display settings, restrictions, and calculations. Display settings affect how the form appears, restrictions limit when or how it can be used, and calculations derive a value from submitted inputs. Test each control with representative values before publishing, especially when a calculated result affects what the visitor sees or what an action sends.
Conditional logic and multi-step experiences
Conditional logic can show or hide fields based on earlier answers, while multi-step arrangements divide a long form into stages. These capabilities are available through documented add-ons or integrations. They are useful when every visitor should not see every question, but they also create more paths to test: each condition, each step transition, and the final submission.
Files, payments, marketing, CRM, and automation
File uploads, payments, customer-relationship-management connections, email marketing, and automation are extension or integration decisions. The basic form embed does not by itself configure those services. Before adding one, identify the service that should receive the data, the fields it requires, and the action that should occur when submission succeeds or fails. Keep the basic record and notification actions where you still need a WordPress copy or an internal alert.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Spam protection
The project lists integrations for Akismet, reCAPTCHA, hCaptcha, and Cloudflare Turnstile. Select the protection method that fits the site and follow its documented configuration requirements. After enabling protection, test a legitimate submission so you know the anti-spam check does not block normal visitors.
Save and preview the form
- Click Publish in the Ninja Forms builder to save the form configuration.
- Use Preview Changes to open a temporary page and interact with the form in the context of the active WordPress theme.
- Submit test data and verify the visible success response, the saved entry, and each configured notification or redirect.
In this screen, Publish saves the form; it does not publish a WordPress post or page. The form still needs to be inserted into a page, post, or public link before site visitors can use it.
Publish Ninja Forms on your site
Ninja Forms provides four publishing routes. Choose according to where the form belongs and how much control you need over the surrounding page.
| Method | Best fit | What the editor shows | What visitors see |
|---|---|---|---|
| Gutenberg block | A form placed in the WordPress block editor alongside other content | A form preview in the editor | The selected form on the published page |
| Shortcode | Pages, posts, widgets, or layouts that accept shortcode text | The shortcode text, not a live form | The form on the live front end |
| Post or page metabox | Adding a form through the Ninja Forms metabox attached to the editor | The selected form in the metabox controls | The form on the published post or page |
| Public link | Sharing the form as its own public destination | No surrounding post or page is required | A standalone form URL |
Insert the Gutenberg block
- Edit the WordPress page or post where the form should appear.
- Add a Ninja Forms block.
- Select the form you created.
- Save or publish the page, then open the front end and test it.
The block previews in the editor, which makes it convenient when you want to see the form in the page layout before publishing.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Insert the shortcode
- Open the form’s publishing options and copy its unique shortcode.
- Paste the shortcode into the page or post editor where the form should appear.
- Save or publish the page.
- Visit the live front end to confirm that the shortcode renders the form.
While editing in the WordPress backend, you will see shortcode text rather than the form itself. That is expected; the form appears when the page is viewed on the live site.
Use the post or page metabox
When the editor provides a Ninja Forms metabox, choose the form there and save the post or page. This approach keeps the form selection attached to that specific piece of content without requiring you to paste shortcode text manually.
Share a public link
A public link gives the form its own address. Use it when the form needs to be shared directly, linked from an email or document, or kept separate from a longer page. Test the link in a private browser window to confirm that a visitor can reach the form without dashboard access.
Test the complete submission path
Do not stop after confirming that the form is visible. Test the same path a visitor will use:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Open the published page or public link on the front end.
- Complete every required field with realistic test values.
- Submit the form and confirm that the success message or redirect matches the intended workflow.
- Check that the submission is present in Ninja Forms when Record Submission is enabled.
- Check the configured recipient inbox for the Admin Email notification.
- If the form uses conditions, calculations, multiple steps, an upload, payment, or spam protection, repeat the test for each meaningful path.
Testing from the front end matters because the builder preview and the published page exercise different parts of the WordPress site. The active theme, page layout, and enabled integrations all participate in the visitor experience.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why Ninja Forms emails or entries may be missing
Start with the two actions
When a submission appears to disappear, first open the form’s Emails & Actions settings. Confirm that Record Submission is active if the entry should be stored, and confirm that the appropriate email action is active if someone should be notified. A disabled action cannot perform its part of the workflow.
Separate storage from delivery
Check the submission record and the recipient inbox as two separate tests. If the record exists but no notification arrives, the form captured the entry and the remaining problem is email delivery or recipient configuration. If neither exists, review the form’s actions and repeat a front-end test before investigating delivery.
Review the recipient and message configuration
Open the Admin Email action and verify its recipient, subject, and included fields. Check that the address belongs to the person or team responsible for the form. When a template has been copied, do not assume its recipient is still correct for the new workflow.
Use the project’s delivery and spam documentation
Ninja Forms maintains documentation for submission handling, email deliverability, and spam protection. Use those resources when the actions are configured correctly but delivery remains unreliable. If an anti-spam integration is enabled, also verify its configuration and test a normal submission so a legitimate request is not rejected.
Choose the right publishing and data workflow
| If your priority is… | Use this approach | Important configuration |
|---|---|---|
| A form embedded in a designed page | Gutenberg block | Keep the form selected in the block and test the page layout on the front end. |
| Portable placement in content that accepts shortcode | Unique shortcode | Remember that the backend shows text; verify the live page. |
| A form selected directly from the post or page editor | Ninja Forms metabox | Save the post or page after choosing the form. |
| A standalone destination to share | Public link | Test the link as an unauthenticated visitor. |
| A WordPress history of every request | Record Submission | Keep the action active and verify a test entry is retained. |
| An immediate internal alert | Admin Email | Check the active action, recipient, subject, and included submission data. |
| Different questions for different answers | Conditional-logic add-on or integration | Test every condition and the final submission path. |
| Payments, CRM, marketing, or automation | The appropriate documented extension or integration | Define the external destination and test success and failure behavior. |
Example: create and publish a basic contact form
1. Start with a contact template or blank form
Open Ninja Forms → Add New and choose a contact template if it provides the fields you need. Otherwise, start with a blank form.
2. Add the essential fields
Use the Form Fields tab to add a name field, an email field, and a message field. Set labels that explain the expected information, make the fields required when the request cannot be answered without them, and apply the available validation to the email field.
3. Configure actions
In Emails & Actions, leave Record Submission enabled so the request remains available in WordPress. Edit Admin Email to send the request to the responsible inbox, and edit Success Message to confirm receipt to the visitor.
4. Preview and publish
Click Publish in the builder, open Preview Changes, and submit a test. Then place the form with a Gutenberg block, shortcode, metabox, or public link. Test the live front end again after the page is published.
Quick Recap
Maintenance checklist
- Review the fields and required settings whenever the information your team needs changes.
- Confirm that Record Submission remains active when the site must retain entries.
- Review Admin Email recipients after staff or responsibility changes.
- Test the live form after changing the theme, page layout, actions, or integrations.
- Retest conditional logic, calculations, uploads, payments, and spam controls after changing their related add-ons.
- Use the submission, email-deliverability, and spam-protection documentation when a configured action does not produce the expected result.
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.
