Long forms get abandoned. A user starts filling out your application, intake form, or multi-step questionnaire, then gets pulled away before they finish. Save Progress gives your users a save-and-continue button they can click at any point, letting them pause and pick up exactly where they left off.
Whether your users are logged in or just browsing as guests, Save Progress keeps their work safe. No restarts, no lost data, no lost leads for you.
With Save Progress, you can:
Key Features of Save Progress
Add a save-and-continue button to any form
Save Progress adds a Save field to your Ninja Forms field library. Drag it anywhere on your form and a save-and-continue button appears in exactly that spot. No code, no templates, no configuration required beyond placement. It works on any form you already have.

Registered users save and return from any device
When a logged-in user clicks save, their progress is recorded server-side in your Ninja Forms submissions area as a saved state. They can close the tab, switch devices, and return days later. When they come back to the form, they see a “Load Saved Progress” prompt and can pick up exactly where they left off. No data entry repeated.

Guest users keep their progress without signing in
Not every visitor has an account. Enable local browser storage in the form’s Advanced settings and non-registered users can save their progress too. Their data is retained in the browser so they do not have to re-enter anything when they return to the same form on the same device and browser. No account required, no friction added.
Reduce form abandonment on long and multi-step forms
Form abandonment is a real conversion problem, and long forms are the biggest culprit. Save Progress directly addresses this by removing the pressure to finish in one sitting. Users who know they can save and come back are far more likely to complete the form at all. Higher completion rates, more submissions, fewer lost leads.

Users can manage multiple saves
When multiple saves are enabled (toggled on in the form’s Advanced tab), users can create more than one saved state for the same form. Each save is timestamped and listed in a customizable “Load Saved Progress” table. Users can load any previous save or edit an existing one. This is especially useful for forms users return to repeatedly, such as applications or quotes.

Trigger email notifications when users save
Any Ninja Forms action can be set to fire on save instead of (or in addition to) firing on submit. Use this to send yourself an email notification the moment a user saves a form, capturing their partial data as a lead before they ever finish. You can also show users a custom success message when they save, so they know their progress is safe.

Compatible with Multi Step Forms and File Uploads
Save Progress carries save state across all steps of a multi-step form. Users can save mid-way through a lengthy process and return to the exact step they left. File upload references are preserved in the save too, so users do not need to re-upload attachments when they return. Save Progress works fully with both the Multi Step Forms and File Uploads add-ons.

Pair with User Management for the full save-and-return experience
Server-side saves require users to be logged in. Combine Save Progress with the User Management add-on to give visitors a complete save-and-return flow: they register directly on your site, save their form progress, and come back to finish without losing a single entry. It is the most complete answer to form abandonment in the Ninja Forms ecosystem.
Stop Losing Form Completions to Abandonment
The Save Progress add-on is included with the Ninja Forms Pro and Elite memberships, or available as a standalone purchase. Pick your plan above and give your users a save-and-continue button today.
Priority email support and 14-day money-back guarantee included.
How Saving Works: Logged-In Users vs. Guests
Save Progress uses two different save mechanisms depending on whether the user is logged in to your WordPress site.
Logged-in users: Progress is saved server-side and recorded in Ninja Forms under Forms > Submissions as a saved state (separate from completed submissions). Saves are portable: the user can return from any device or browser and load exactly what they saved. Site admins can view, edit, or convert saved states to full submissions from the same dashboard they use for completed entries.
Guest users: When local browser storage is enabled, progress is stored in the visitor’s browser. Their data persists if they navigate away and return using the same device and browser. Because saves are browser-local, they are not portable across devices and will be lost if the user clears their browser data.
For teams that need portable saves for all users, pairing Save Progress with the User Management add-on gives guests a path to register and unlock the full server-side experience.
Manage All Saved Forms from Your Admin Dashboard
Every server-side save appears in your Ninja Forms submissions dashboard under Forms > Submissions > View Saves. You can see the full list of saved states for any form, view the partial data a user entered, edit a save, or promote a saved state to a completed submission without requiring the user to resubmit. This gives you full visibility into in-progress entries and keeps partial leads within reach.
Common Use Cases
- Reduce drop-off on long applications: Job applications, grant applications, and membership forms often lose completions simply because they take time. Give applicants a save-and-continue button so they can finish on their own schedule.
- Capture leads before submission: Trigger an email notification on save to capture a prospect’s contact information the moment they pause. You have the lead even if they never return to submit.
- Support multi-step form completion: Pair Save Progress with Multi Step Forms so users can save mid-process. Save state carries across steps, and file uploads are preserved. Start with a pre-built multi-step template or build your own.
- Let repeat users maintain multiple drafts: Enable multiple saves for quote request forms, order configurators, or enrollment forms so users can maintain and compare several in-progress versions at once.
- Give guests a frictionless experience: Enable local browser storage for forms where you do not want to require registration. Guests can pause and return on the same browser without signing up for anything.
- Build a full register-save-return flow: Combine Save Progress with User Management so visitors can create an account, save their progress server-side, and return from any device to complete the form.
Let Your Users Save Progress and Come Back Later
Save Progress is included with the Ninja Forms Pro and Elite memberships, or available as a standalone purchase. Choose your plan above and start reducing form abandonment today.
Priority email support and 14-day money-back guarantee included.
Can I save my progress and come back later?
Yes. Save Progress adds a save-and-continue button to any Ninja Forms form. Click it at any point to save your entries. Logged-in users can return from any device and load their saved progress. Guests who save via local browser storage can return using the same browser on the same device.
Is there a way to save my progress and come back later without an account?
Yes. When a site owner enables local browser storage for a form, non-registered visitors can save their progress without signing in. Their data is stored in the browser and restored when they return to the same form on the same device and browser. No account is required.
Do users need to be logged in to save form progress?
Server-side saves require a logged-in WordPress user. For guest users, site owners can enable local browser storage, which saves progress in the visitor’s browser without an account. To give guests portable saves across devices, pair Save Progress with the User Management add-on so visitors can register and log in.
How do I add a save and continue button to my WordPress form?
Activate the Save Progress add-on, then open any form in the Ninja Forms builder. A Save field will appear in your field library. Drag it onto your form wherever you want the save button to appear. That’s it. No code required.
Does the save-and-continue button work with multi-step forms?
Yes. Save Progress is fully compatible with the Multi Step Forms add-on. Save state carries across all steps, so users can save mid-process and return to the exact point they left. File upload references are also preserved across saves.
Can users have multiple saved states for the same form?
Yes. Multiple saves can be enabled in the Advanced tab of the form builder under Save Progress settings. Once enabled, users can create and manage multiple timestamped saves for the same form and choose which one to load when they return.
What happens to saved forms in the WordPress admin?
Every server-side save appears in Ninja Forms under Forms > Submissions as a saved state, separate from completed submissions. Site admins can view the partial data, edit a saved state, or convert it to a full submission without requiring the user to resubmit.
Can I get an email notification when someone saves a form?
Yes. Any Ninja Forms action, including email notifications, can be set to trigger on save. In the Emails & Actions tab, toggle the Save option for any action to fire it when a user clicks the save button. This lets you capture lead data before a form is ever submitted.
Changelog
3.0.29 (03 February 2025)
Bug Fixes:
- PHP deprecation notice Creation of dynamic property $table
- View Saves button link on the new Submissions page
Other:
- Workflow updates
3.0.28 (25 September 2023)
Bug Fixes:
- Fixes \”Load saved progress box remains at the top of the form when logged out\”
3.0.27 (8 February 2023)
Bug Fixes:
- Update script registration to remove moment.js
Other:
- Centralize automated build and testing
3.0.26 (11 January 2023)
Bugs:
- Ensure register_rest_route is called such that it prevents PHP notice
- Prevent \’optional parameter\’ warning in PHP 8
Other:
- Automate testing and build
3.0.25 (25 January 2021)
Bugs:
- Resolved an issue that was sometimes causing saves to not be properly deleted after form submission.
3.0.24.2 (13 March 2020)
Security:
- Patched an Auth Bypass vulnerability associated with saved form data.
- Thanks again to Timothy B Jacobs for pointing this out!
3.0.24.1 (27 January 2020)
Security:
- Patched SQL Injection and Auth Bypass vulnerabilities associated with saved form data.
- Patched an XSS vulnerability in the admin save viewer.
- Many thanks to Timothy B Jacobs for practicing responsible disclosure!
3.0.24 (12 November 2019)
Bugs:
- Resolved an issue that sometimes prevented loading a save when multiple saves were enabled on a form.
3.0.23 (12 August 2019)
Bugs:
- Corrected an issue that was causing some actions to fire improperly on save.
3.0.22 (24 July 2019)
Bugs:
- The save table should no longer display on form load when there are no saves.
3.0.21 (12 June 2019)
Bugs:
- Resolved an issue that rarely caused an undefined index warning when the save button is clicked.
3.0.20 (16 May 2019)
Bugs:
- Save Progress should now work properly when there are multiple instances of a form on the page.
3.0.19 (2 April 2019)
Bugs:
- Resolved an issue that sometimes caused an undefined index warning to appear on form load.
3.0.18 (11 January 2019)
Bugs:
- Resolved an issue that was preventing the Stripe action from loading on forms where Save Progress was enabled.
3.0.17 (30 November 2018)
Bugs:
- Fixed issue where making changes in the form builder sometimes caused form publish to fail.
3.0.16 (24 August 2018)
Bugs:
- Resolved an issue that was preventing saved states from loading properly in Internet Explorer.
3.0.15 (4 June 2018)
Bugs:
- Resolved an issue that sometimes caused the dashboard to not display any forms.
- Styling of the save table options in the form builder should now match similar settings.
3.0.14 (8 May 2018)
Bugs:
- Updating the required status of a field in the form builder should now be reflected in saves.
- Updating the file type restrictions of file uploads fields in the form builder should now be reflected in saves.
3.0.13 (5 April 2018)
Bugs:
- Save data should no longer be removed when a submission fails.
3.0.12 (26 March 2018)
Bugs:
- Local browser storage should now save a drastically increased number of values.
3.0.11 (17 January 2018)
Bugs:
- Table editor fields should now be saved properly.
3.0.10 (14 December 2017)
Bugs:
- Fixed an issue that was causing CSS stylesheets to be loaded unnecessarily on all pages.
- Save times should now display accurately in the save table instead of showing the time of last save for all records.
3.0.9 (13 October 2017)
Bugs:
- Saves should be faster now.
- File Upload fields should now save properly.
3.0.8 (26 September 2017)
Bugs:
- Fixed a bug with missing a missing nonce causing saves to not load.
3.0.7 (20 September 2017)
Bugs:
- Fixed a bug with an array item being accessed before being checked.
- Fixed a compatibility bug with the Table Editor add-on which created circular JSON.
- Fixed a compatibility bug with the File Uploads add-on which was saving upload nonce values.
3.0.6 (13 September 2017)
Changes:
- Added hooks after a save is updated or created.
- Removed Layout & Styles data from the saved data.
- Added filters for inserting, updating, and getting saves.
- Added query support for strings when getting saves with a where specified.
3.0.5 (22 August 2017)
Bugs:
- Fixed a bug that could cause an error when Ninja Forms was not active.
- Fixed a bug that caused the Save Button to show to non-authenticated users.
3.0.4 (02 August 2017)
Bugs:
- Fixed a bug that could cause multiple saves when using Multi-Part Forms.
- Improved processing time for saving forms.
3.0.3 (13 July 2017)
Bugs:
- Fixed an issue with missing JS files in previous version.
3.0.2 (06 July 2017)
Bugs:
- Fixed a bug that created multiple saves when a form contained multiple save buttons.
- Licensing and updating should now work properly.
3.0.1 (23 May 2017)
Bugs:
- Fixed a file name reference that could cause a fatal error on some server configurations.
3.0.0
- Initial release

