WPForms Save and Resume - WordPress Plugin

Guide to Setting Up and Using WPForms Save and Resume

WPForms Save and Resume is not meant to make a standard form look a little nicer. It solves a specific problem: a user starts filling out a long form, realizes they need more time, supporting documents, or input from someone else, and should not lose the answers they have already entered. In this guide, we will walk through how to enable the addon in WPForms, which settings to review after installation, how the resume link works, how the email link works, what the save warning does, how partial entries are stored, and which limitations apply to sensitive fields.

This article is written for site owners, editors, marketers, and developers who already use WPForms and want to safely add a "save now, finish later" workflow. It does not cover licensing or activation workarounds. The focus here is on implementing the feature in a real form, validating the outcome, troubleshooting common issues, and understanding when this mode improves the user experience and when it only adds unnecessary friction.

WPForms stores saved responses as partial entries, gives administrators access to them in the form entries area, and at the same time does not save certain sensitive fields. That means implementation is not just a matter of flipping one switch. You need to decide in advance which forms actually need this workflow, what message the user should see, how the link will be delivered, how email delivery will be tested, how the expiration period will be explained, and how partial entries will be distinguished from fully submitted forms.

The guide below follows the actual implementation sequence: first choosing the right forms, then installation and activation, then detailed configuration of the text, link, email, and storage behavior, followed by a practical example for a long application form, validation steps, troubleshooting, and a comparison with similar solutions. That order helps you do more than just turn the feature on. It helps you understand how to use WPForms Save and Resume without losing data and without creating false expectations for visitors.

When saving progress actually makes sense

Save and Resume works best on forms where users have a legitimate reason to stop halfway through. That might be a job application, participant questionnaire, multi-page survey, internal onboarding form, detailed service request, event registration with many questions, or any form that naturally gets completed in stages. If a form only asks for a name, phone number, and short comment, adding a save link usually introduces an extra decision point and distracts from submission.

The main product behavior here is simple: the visitor clicks the save link next to the submit button, WPForms creates a partial entry, shows a confirmation, and gives the user a unique way to return. That return path can be an on-screen link, an email with a resume button, or both. Importantly, the user can save their answers even if required fields are not filled out yet. That is what separates this workflow from a normal form submission: the goal is not to accept a completed application, but to preserve a draft until the person is ready to continue.

The point of the addon is to reduce drop-off on long forms, not to replace form submission. So before enabling it, look at how your audience actually behaves. If people abandon the form halfway through, come back with document-related questions, complain about losing data after stepping away, or need information from multiple sources, WPForms Save and Resume is a good fit. If the form is short and mainly works as a quick lead capture tool, saving progress may hurt conversions by adding an alternate action next to the main submit button.

In practice, the addon is especially useful in four types of workflows. First, long applications where users need to gather documents, resumes, approvals, or detailed responses. Second, multi-page questionnaires where users move through several sections and may stop between them. Third, collaborative completion, where one employee starts the form and another one finishes it. Fourth, sensitive workflows where you need to clearly explain which data will be saved and which fields will need to be re-entered after returning.

You should not automatically enable saving on every form across the site. It is better to do a quick audit: how many fields the form has, how many pages it uses, whether attachments are required, whether the user needs an external document, whether there are financial fields, a signature, a password, or file uploads, whether the data should be stored in the database, how long drafts may be retained, and who on the team will review partial entries. That kind of audit reveals limitations much faster than trying to fix a published form after users start complaining.

Practical rule of thumb: if a user can complete the form in one or two minutes without documents or coordination, Save and Resume usually is not necessary. If the form requires thoughtful responses, multiple pages, or a return visit, the feature becomes part of a normal user workflow.

Who this addon is for and when a different approach is better

WPForms Save and Resume is a good fit for sites that already use WPForms Pro or a higher WPForms tier and want to add controlled draft saving to specific forms. It is especially convenient if the team already manages submissions in WPForms » Entries, works with WPForms notifications, and does not want to build a separate account area just to support unfinished forms.

The addon also works well for projects where visitors do not need to be registered users. Unlike solutions built around user accounts, this one is based on a unique link. The user can copy the link or receive it by email, then open the form later and continue. WPForms documentation specifically notes that the recovery link remains valid for a limited time, so the confirmation text should state this clearly. A saved form is not stored forever.

This solution also makes sense for editorial and service-focused sites where incomplete applications still matter. Partial entries appear in the entries area with a separate status, and the administrator can see which fields are already filled in, when the entry was last updated, and which link can be used to continue. That is useful in internal workflows: for example, a manager can see that an applicant stopped at the document section rather than simply disappearing from the form.

There are also cases where you should think twice. If the form collects payment details, files, signatures, or passwords, you need to account for an official limitation: sensitive fields are not saved in the partial entry. When the user returns, they will have to enter that data again. That is a reasonable privacy safeguard, but it can surprise users if you do not explain it in the warning text or elsewhere in the form. Do not promise that absolutely everything in the form will be saved. Be clear instead: standard responses will be restored, while sensitive fields may need to be entered again.

Another edge case involves forms where an incomplete application has no value to the administrator and should not remain in the database. For example, if you collect highly sensitive medical or legal information, the decision to store drafts should be aligned with the site's privacy policy, retention rules, and internal procedures. WPForms gives you the mechanism, but responsibility for the consent wording, staff access, and data deletion process still belongs to the site owner.

It is also worth comparing Save and Resume with Form Abandonment. The first workflow depends on an intentional user action: the user clicks the save link, understands the warning, and gets a way to return. The second is meant for automatically capturing abandoned forms when the user leaves without saving. These are different use cases. Save and Resume is better for a transparent and user-friendly "finish later" experience. Form Abandonment is better for lead recovery and abandonment analysis. You can consider them together, but one should not be treated as a substitute for the other without changing the user communication model.

What to check before installation

You do not need a major technical audit before installing the addon, but a few checks are worth doing upfront. WPForms Save and Resume is an addon for WPForms and is only available at the appropriate paid tier. The main WPForms plugin should already be installed and active in the WordPress admin, the WPForms license should be verified, and WPForms itself should be updated to a version that is compatible with the current addons. Exact version numbers are best checked in your WPForms account and documentation, because they can change.

The second check is your site's email setup. If you plan to send the resume link by email, the default WordPress mail function may not be reliable enough. In comments under the official WPForms release article, users raised concerns about those emails landing in spam, and a WPForms representative recommended using an SMTP solution for authenticated sending. This is not unique to Save and Resume. It is a common WordPress notification problem: if the domain, sender identity, and DNS records are poorly configured, the email with the resume link may never reach the inbox.

The third check is the form itself. Review which fields it contains. The official documentation lists sensitive field types that are not stored in partial entries: Password, Signature, File Upload, and the Stripe Credit Card, Square, and Authorize.Net payment fields. If the form depends on those fields, users need to be told in advance that they will have to fill them in again when they return. That is perfectly reasonable for a long application: text answers, selections, and contact fields can be restored, while attachments or payment details can be added at the very end.

The fourth check is the page structure where the form is published. If the form is embedded inside a heavy page builder layout, displayed in a popup, surrounded by aggressive caching, or loaded conditionally, saving and returning by link should be tested especially carefully. The WPForms changelog includes fixes related to multi-page forms, Page Break, previews, and interactions with other plugins, so the safe approach is simple: test on a copy of the form and re-check the save-and-return flow after updates.

The fifth check is team access. Partial entries are available through WPForms » Entries, so they will be visible to WordPress users who are allowed to access form entries. If you have multiple editors, contractors, or managers, do not enable draft saving until you have reviewed user roles and the internal rules for accessing application data. A partial entry is still user data, even if the form has not yet been fully submitted.

Installation and initial activation

Installation uses the standard WPForms addon workflow. In the WordPress admin area, open WPForms » Addons, find Save and Resume, and install the addon. If the addon list does not refresh, WPForms documentation recommends refreshing the addon list. After installation, the toggle should switch to Activated. If automatic installation does not work, WPForms also allows manual ZIP installation from your account, but that is an administrative task rather than part of the feature setup itself.

Once activated, the addon does not immediately start saving every form on the site. That behavior is important: Save and Resume is enabled per form. Open an existing form or create a new one, go into the WPForms builder, and open Settings » Save and Resume. There you enable Enable Save and Resume. As long as that switch is off, the form behaves like a normal WPForms form, even if the addon is activated in WordPress.

That approach makes gradual rollout easy. You can first enable the feature on one test form, verify the text, email, link, and partial entry behavior, and only then apply the setup to live forms. Do not begin with your most important form if you do not have a staging copy of the site. It is safer to duplicate a form, trim it down to a few fields, enable Save and Resume, go through the visitor flow, and only then repeat the setup on the real form.

After enabling the feature, make sure to save the form in the WPForms builder. Otherwise you may see the settings in the admin panel but not get the expected behavior on the published page. Then open the page containing the form in a separate browser window, ideally while not logged in as an administrator, fill out a few fields, and look for the save link next to the submit button.

If the link is not visible, check three things: whether the addon itself is activated, whether the feature is enabled for that specific form, and whether you are viewing the public page with the current version of the form. If the site uses page caching, clear the cache after saving the form. If the form is embedded via a block, shortcode, or page builder, make sure you are looking at the page where the correct form is actually published rather than an older copy or hidden variant.

The Save and Resume panel: settings you should not skip

The real setup work does not happen in the WordPress plugins list. It happens inside the form. After you enable Enable Save and Resume, WPForms exposes a group of settings: the save link text, the pre-save warning, the confirmation message, the on-screen resume link, the email delivery option, and the email content itself. These fields determine whether users understand what happens to their data and whether they can get back into the form without contacting support.

Save link text

By default, WPForms uses the text Save and Resume Later. On a Russian-language site, you would normally replace it with a clearer phrase, such as "Save and Continue Later" or "Save Application Draft". More generally, avoid wording that is too vague: the word "save" by itself can sound like a normal form submission. Good link text should make it clear that the application is not being submitted yet.

The link appears next to the submit button at the bottom of the form, so the wording needs to work together with the main button. If the button says "Submit Application", the link can say "Save and Return Later". If the button says "Complete Questionnaire", the link can say "Save Questionnaire Draft". Do not make the save link visually more prominent than the submit button if your primary goal is to get completed submissions. It should be noticeable, but secondary.

Warning before saving

The Enable Disclaimer Page option adds an intermediate screen after the user clicks the save link. On that screen, the user confirms that they want to save their current progress and leave the form. This text should explain three things: what data will be saved, how the user will return, and that sensitive fields may need to be entered again.

For a form with standard fields, a short message is enough: "We will save the answers you entered and generate a link so you can continue later. Do not share that link with other people. Some sensitive fields, if they exist in this form, may not be saved." For a form with files, a signature, or payment, be more specific: "Files, signature, and payment details are not saved in the draft and will need to be added again before submission." That kind of wording reduces frustration when the user returns and sees an empty upload field.

Confirmation message

After saving, WPForms displays a confirmation. This screen should do more than just say "Done." It is the point where the user decides how they will get back to the form: by copying the link or sending it to themselves by email. Explain that the link remains valid for a limited time, that it should not be posted publicly or forwarded to unrelated people, and that the final form has not yet been submitted. That last point is especially important for legal, contest, and HR forms, where a user might mistakenly assume that a saved draft counts as a completed application.

Good confirmation copy answers the question "What should I do next?" For example: "Copy the link or send it to your email. Return using this link to continue filling out the form and submit it. Until you click the submit button, your application remains a draft." This is not marketing copy. It is an instruction at a high-risk moment.

On-screen link and email link

WPForms lets you enable the on-screen link with Enable Resume Link, email delivery with Enable Email Notification, or both at once. If the audience is technically confident and the form is used internally by a team, a copyable link may be enough. If the form is public, email is usually more reliable: the user may close the tab, lose the clipboard contents, or want to open the form from another device.

When email notification is enabled, WPForms displays editable fields for the email content and the follow-up message shown after the user enters an email address. The email must include the Smart Tag {resume_link}, because that is what inserts the actual resume link. If you remove that tag from the message, the user will receive an email with no working way to return to the form. This is one of the most critical checks in the email setup.

Quick configuration test: enable both delivery methods, save the form, submit a test draft, click the save link, copy the link, send the email to an external address, and then verify both return paths in a separate browser window.

How the resume link and email actually work

From the user's perspective, the flow is simple: fill out part of the form, click the save link, confirm the action, receive a link, and come back later. From the site owner's perspective, there is more going on. The resume link does not lead to a blank form. It leads to a state where WPForms can restore the saved answers. That means the link needs to be unique, should not appear in public channels, and should have a clearly explained expiration window.

The official WPForms documentation states that recovery links expire after 30 days. That detail should appear in both the confirmation message and the email. Do not bury the expiration period inside a long policy document. The user should see it at the moment they save the form. If your organization needs a shorter window, WPForms provides a developer filter to change the partial entry deletion period, but that is a developer-level adjustment rather than a normal builder option and should be handled carefully.

Email delivery is especially important for forms that are not completed in one sitting. A user may start an application on a work computer, send the link to themselves, and finish it at home. The official WPForms features page says users can resume on any device through the unique link. In practical form copy, it is better to explain this without making overly technical promises: "Open the link in the email to continue the form with your saved answers."

Privacy matters here. The link effectively opens the saved state of the form, so it functions like a key to the draft. Do not write "forward this link to your coworkers" if the form contains personal data. For a team workflow, it is safer to describe an internal process: who starts the form, who receives the link, which fields each participant fills in, and who is responsible for final submission. If that process is not defined, users may forward the link to the wrong person or assume the form has already been accepted.

There is also an important UX detail. If you enable only the copyable link, the user must save it somewhere reliable on their own. For a public audience, that is weaker than email. If you enable only email, the user must enter a valid address and the email must actually be delivered. That is why it is often reasonable to enable both methods on important forms: the on-screen link gives immediate control, and the email provides a backup path. After testing, you can keep only one method if it better fits your audience.

What to write in the email

The email should be short. It should not restate the whole form and should not read like a marketing campaign. Four elements are enough: a reminder that this is a form draft, a button or link that uses {resume_link} to continue, a warning about the expiration window, and a request not to share the link with unrelated people. If the form is tied to a contest or a deadline-based application, add that saving a draft does not count as submitting it.

A safe email structure, without copying a ready-made template, would sound like this: "You saved a draft of your form. To continue, open the link below. The link is available for a limited time. Do not share it with other people if the form contains personal data. After returning, review your answers and click the main submit button." That kind of message reduces confusion better than a long polished email.

Why the email may not arrive

If the email with the link does not arrive, start by checking WordPress email delivery rather than Save and Resume itself. Notification delivery depends on server mail configuration, the sending domain, SMTP, DNS records, and the recipient's spam filters. In the release article, a WPForms support representative explicitly recommended using an SMTP plugin to improve deliverability. That does not mean the feature cannot work without SMTP, but for a public form, the email flow should not be considered verified until test emails reach multiple external email services.

Save a copy of the email, inspect the subject line, sender, link, spam folder, and the behavior of the resume button. If the link appears on screen but the email never arrives, the issue is usually delivery. If the email arrives but the link leads to the wrong place or opens an empty form, check the form save settings, page caching, page builder conflicts, and whether the form structure was changed after the partial entry was created.

Partial entries in the admin area

When a user saves a form, WPForms creates a partial entry. You can find it in WPForms » Entries: select the form and view the list of submissions. In the status column, incomplete entries are marked as Partial. That is not the same as a fully submitted application. A partial entry means the user intentionally saved their progress and has not yet finished the form.

When you open such an entry, the administrator can see the completed fields and the last modified time. The details panel also includes an action for copying the resume link for that partial entry. This is useful in support-related workflows: for example, when a user contacts support and asks for access to their draft again. But before sending the link manually, make sure you are communicating with the owner of the data rather than an unrelated person. For forms that contain personal information, that check matters more than a fast response.

The official WPForms documentation also emphasizes the limitation around sensitive fields: Password, Signature, File Upload, and payment fields are not saved in partial entries. Those fields will not be available in the admin area, and users will need to enter them again when they return. This is not an error or data loss. It is expected behavior. Good warning text in the form prevents most support requests on this topic.

Partial entries are stored for a limited time. In the default setup, the documentation refers to 30 days, after which incomplete entries are deleted. For administrators, that has two practical implications. First, you should not build an internal workflow that assumes drafts will always be available. Second, if your site is required to retain user data for less or more than the standard period, you will need a separate review and possibly the developer filter that WPForms documents for the deletion interval. You should not change the retention period without understanding the consequences.

When the user returns through the link and submits the form, the status should switch to completed. At that point the entry becomes a normal WPForms submission. If you use reports, exports, or integrations, verify how they behave specifically for completed and partial statuses. For example, the official Save and Resume documentation notes several compatibility cases: partial entries are excluded from Surveys and Polls statistics and from Form Locker entry limits, while User Journey data becomes visible after the final submission is completed.

How not to confuse Partial, Abandoned, and Completed

In the WPForms ecosystem, statuses can depend on which addons are enabled. Save and Resume creates partial entries because the user intentionally clicked save. Form Abandonment creates abandoned entries because the user started a form and left without submitting. Completed means the form was fully submitted. In comments on the WPForms release article, support explained the difference between Abandoned and Partial when the relevant addons are used together. This matters for your team: someone who asked to save a draft should not be handled the same way as someone who silently left the form.

You can describe the internal handling model like this: Partial means do not trigger aggressive follow-up messaging because the user intentionally paused. Abandoned may be appropriate for careful lead recovery if that aligns with your site policy. Completed should move into the main business process. That distinction helps you avoid intrusive communication and interpret reporting more honestly.

Product-specific mechanics worth configuring deliberately

WPForms Save and Resume includes several mechanics that set it apart from a simple "save" button. You should understand them before publishing the form, because this is where expectation mismatches usually happen: where the feature is enabled, what the user sees before saving, how the return path is created, which fields are excluded from storage, how the partial entry appears, and how it disappears after the retention window ends.

Mechanic 1: enabled per form

The addon is activated in WordPress, but it only works where you have enabled Settings » Save and Resume. The user input on your side is the Enable Save and Resume switch inside a specific form. The product behavior is to add the save link and partial entry handling only to that form. The visible outcome is a link next to the submit button on the public page. The check is to open the form outside the admin preview, fill in a few fields, and confirm that the link appears. The failure symptom is that the link never shows up. The safe fix is to verify that the addon is active, the form has been saved, and the page cache has been cleared. The limitation is that the feature should never be assumed to be globally enabled for all forms.

Mechanic 2: warning as consent to pause

The user clicks the save link, and the product may display a warning screen. This is not automatically a legal notice. It is editable text that should explain the action. The outcome is that the person understands they are leaving the form but can return later. The check is to click the save link and see whether a screen appears with the Continue button and the Go Back link. The failure symptom is that the user saves a draft without realizing the application has not yet been submitted. The fix is to rewrite the warning, keep the wording short, and remove ambiguous phrases like "application received." The limitation is that the warning text does not replace a proper data-processing policy if the form collects regulated information.

Mechanic 3: two return channels

WPForms can show the link on screen, send it by email, or enable both methods. The user chooses how to preserve access. The product behavior is that the same recovery link becomes available through different channels. The visible outcome is either a copyable link on screen or an email with a Resume Form Submission button. The check is to test both paths. The failure symptom is that the on-screen link works but the email never arrives. The fix is to check SMTP, the sender identity, the spam folder, and the presence of {resume_link} in the email template. The limitation is that the link remains sensitive access to a draft and therefore should not be published or forwarded to unrelated people.

Mechanic 4: sensitive fields are excluded

The user may expect the whole form to be restored. The product does not save everything: the official documentation lists fields that are excluded for privacy and security reasons. The visible outcome is that some fields are blank after the user returns. The check is to create a test form with one regular field and one file upload field, save the draft, return, and see what comes back. The failure symptom is that the user assumes a file was lost because of an error. The fix is to add a warning before saving and a note next to the sensitive field. The limitation is that you should not try to bypass this behavior with custom code when passwords, payments, signatures, or files are involved.

Mechanic 5: partial entry with a limited retention window

After saving, WPForms creates an entry with the Partial status. The administrator can review the completed fields and copy the link. After the configured period, incomplete entries are deleted. The check is to save a test draft, open WPForms » Entries, and find the partial entry. The failure symptom is that the team treats a draft as a real submission or promises the user recovery after an undefined amount of time. The fix is to train the team to read statuses correctly and to include the expiration period in the user-facing text. The limitation is that changing the retention period with a developer filter requires understanding the WPForms scheduler and the site's data policy.

Which forms to enable first and how to design the save workflow

If your site has dozens of forms, do not start by enabling Save and Resume everywhere. Choose two or three forms where saving progress solves a clear problem, and bring those to a high-quality implementation first. That will show you real user questions much faster, help you understand which emails actually get delivered, reveal which fields force users to re-enter data, show how the team handles Partial, and identify where the form text needs revision.

For a job application, the main value is giving users time for thoughtful answers. A visitor may start with contact details and a short profile, then return later to complete the experience, motivation, and resume upload sections. In that kind of workflow, the save option should appear before the most demanding questions, and the warning should explicitly say: "This draft has not yet been submitted to the employer." If the form requires a file, place it closer to the end and add a note that the attachment will need to be uploaded before the final submission.

For a participant questionnaire or event application, the key challenge is often collaborative preparation of information: the user may need to confirm organization details, billing data, attendee lists, or manager approval. In that case, the email link is especially useful because the draft may be reopened later on another device. But if the form contains personal data for multiple people, do not encourage casual link forwarding. It is better to say that the link should be treated as access to a draft and shared only with the responsible person.

For a long survey, Save and Resume helps avoid forcing the user to complete everything in a single visit. However, surveys are especially sensitive when it comes to reporting: partial entries should not be counted as completed responses. WPForms documentation states that partial entries are excluded from Surveys and Polls statistics. So in reporting, separate started, saved, and completed responses. If many people save the survey and never return, that is not only a reminder problem. It may also point to the survey being too long or too difficult.

For internal onboarding forms or operational checklists, the workflow may be collaborative. One employee starts the form, another adds the missing information, and a third reviews and submits it. In that case, it is useful to add a next-step instruction to the confirmation text: who should open the link, which fields need review, and who is responsible for final submission. The official WPForms release article mentions that Save and Resume can support forms completed by multiple people at different stages. But organizing those stages is still your responsibility. The plugin stores a draft. It does not manage a business workflow.

For pricing requests, service inquiries, or pre-consultation forms, saving progress is useful when the questions require preparation. For example, the user may not know the room size, number of employees, budget, timeline, or technical specifications. In those cases, it is better to say "Save your draft if you need time to confirm the details" instead of just "Save form." That phrasing explains why the feature exists and reduces anxiety about losing entered responses.

Payment forms require extra caution. If WPForms Save and Resume is enabled on a form that includes payment fields, the user's payment details should not be stored in the draft. That is correct behavior, but the UX needs to be designed around it. Place the payment step after all text-based answers so the user can save and restore the substantive part of the form and only complete payment during the final submission. If pricing depends on calculations inside the form, be sure to test that the calculation updates as expected after the user returns and before they submit.

Forms with file uploads are also better designed as "information first, attachment last." If a resume, contract, photo, or document upload appears in the middle of the form, users may save a draft and later be confused by an empty upload field. Moving the file field to the end is not always possible, but it often improves the workflow. Another option is to add a short note next to the upload field: "If you save a draft, you will need to choose the file again before submission." That is more honest than trying to hide the limitation.

It is also useful to standardize team terminology. Inside WPForms, the status is called Partial, but in internal instructions you may refer to it as a draft. For example: "A draft is not processed as an application," "A completed entry moves into active work," and "The draft link is sent only to the email owner." The less ambiguity there is in the language, the less likely someone is to tell a user "your application has been accepted" when it has only been saved.

A good Save and Resume workflow is designed around the reason for the pause. If that reason is clear, it becomes easy to write the link text, warning, and email. If the reason is unclear, the feature will feel like an unnecessary technical button. Before enabling it, ask: "What exactly is stopping the user from finishing right now?" The answer to that question will shape the form better than any generic checklist.

Mini decision matrix for choosing the first forms

Practical example: a long application form for a job or event

Imagine an application form that cannot realistically be completed in one short visit. It collects contact details, experience, a motivation letter, answers to several questions, agreement to terms, and possibly a resume file. In this kind of case, WPForms Save and Resume helps not because it is "more convenient," but because users may need to start the application, return to their documents, revise the wording, or continue from another device.

Goal of the workflow

The goal is to create a form where a visitor can save a draft before final submission, receive the link by email, return to the completed text fields, and finish the application later. The administrator should be able to see a partial entry with the Partial status, but should not treat it as a final application. The user should understand that a file or signature, if present, may not be restored and must be added before final submission.

Preparing the form

Create or open the form in WPForms. If it is long, use a multi-page layout so the user sees manageable sections: contact details, experience, detailed answers, documents, confirmation. Save and Resume can also work on a standard form, but Page Break helps users understand progress more clearly. Add a short note at the beginning: "If you need more time, save your draft and return using the link." That note should support the save feature, not replace it.

Do not place the file upload field in the first section unless the file is needed before the user can decide whether to save. It is better to collect the text-based answers first and request the attachment closer to the end. That way, users are less likely to be annoyed by re-uploading the file when they return. If the form requires a signature or payment, move that step to the end and clearly state that this information is entered only before final submission.

Configuring Save and Resume for this workflow

1. Open the form in the builder and go to Settings » Save and Resume.
2. Enable Enable Save and Resume and set the link text to "Save Draft and Continue Later."
3. Enable the warning screen if the form contains personal data, files, a signature, or financial fields.
4. In the confirmation message, explain that the draft has been saved, but the application is only considered submitted after the main submit button is clicked.
5. Enable email notification and verify that the email text includes {resume_link}.
6. Save the form and clear the page cache if the site uses caching.

After configuration, go through the full flow as a regular visitor. Fill in the name, email, several long answers, move to the next page of the form, and click the save link. If the warning screen is enabled, confirm that the button to continue saving and the link to return to the form are both clear. Then copy the on-screen link and email it to yourself. Open the link in a different browser. Standard saved fields should be restored. After the final submission, the entry should move to completed status.

A note on collaborative completion

The official WPForms release article explicitly mentions a workflow where multiple people complete the form at different stages. For that kind of process, the confirmation text needs to be even more precise. For example, if the candidate fills out the first part and an HR staff member completes an internal section, you should not simply say "forward the link to anyone." It is better to define the internal rule: "Share the link only with the responsible staff member through a secure channel." If the form is public and contains personal data, a collaborative workflow should be implemented cautiously and with clear access control.

Testing a collaborative workflow is also different from testing an individual one. One person creates the draft, another opens the link and fills in their part, and the assigned person completes the final submission. After submission, the administrator checks that the entry has moved to completed status and that the partial status is no longer treated as active work. If the form includes a file or signature, add those only in the final step rather than in the middle of the process.

How to verify the result after publication

Validation should cover the entire chain, not just whether the link is visible. The minimum test is to see the save link on the form. A full test is to create a partial entry, receive the link in both ways, return to the form, confirm that standard fields are restored, submit the form, verify the status change, and make sure the email did not land in spam. If you skip any of those steps, the problem may only surface when a real user encounters it.

Run a separate admin-side test as well. Open the form page outside the builder view, fill in the fields using realistic test data, save progress, then go to WPForms » Entries in the admin area and open the correct form. Find the entry with the Partial status, review the completed fields, and test the copy-link action in the entry details. That confirms that the save actually happened inside the WPForms entries system, not just in the browser.

Then test the user flow. Open the recovery link, change one of the answers, and submit the form. Return to Entries and verify that the entry is now completed. If you use integrations, notifications, or export workflows, make sure they are triggered by the completed submission as intended rather than by the act of saving a draft. For marketing and CRM workflows, this is critical: a draft should not trigger the automation designed for a finalized application unless you explicitly designed the process that way.

Test the form with a sensitive field. Do not use real payment details or personal documents. A test file is enough if the form includes upload fields, or a test configuration if payments run in a separate secure mode. The goal is to see which fields will not be restored. After that, rewrite the warning so it matches the actual behavior of the form. The form text should describe the real outcome, not the behavior you wish it had.

Finally, test email delivery. Send the link to addresses on different email services and review the subject line, sender, email body, and button behavior. If the email does not arrive consistently, set up SMTP before launching the public form. Do not shift that problem onto the user with "check your spam folder" if sending from your site domain has not been configured correctly.

Compatibility with other WPForms addons and feature boundaries

Save and Resume operates inside the WPForms ecosystem, so it should be considered alongside other addons. The official documentation highlights several special cases. Save and Resume partial entries are excluded from Surveys and Polls statistics. They do not count toward Form Locker entry limits. Conversational Forms and Form Pages are supported. User Journey data becomes visible in the entry after the user submits the completed form.

These details help prevent incorrect conclusions. If you run a survey and notice that the reporting does not include saved drafts, that is expected because the user has not completed the form yet. If you use Form Locker to limit the number of applications, a partial draft should not consume the slot of a full submission. If you analyze the user path with User Journey, review that data after final submission rather than at the moment the draft is saved.

The logic is different with Form Abandonment. That addon exists to automatically save abandoned forms and help recover lost leads. Save and Resume requires an intentional action from the user. So using them together requires careful communication. A user who clicked "save" has already told the system, "I plan to come back." A user who left without saving is in a different workflow. Do not send both groups the same follow-up messages if you are building post-form communication.

The boundary is even stricter with payment and file fields. Save and Resume should not become a storage mechanism for payment data or a temporary file repository. If the form accepts payment, design the workflow so the payment step appears at the end. If the form requires a resume or document upload, warn users that the file will need to be added again. That limitation may feel inconvenient, but it reduces the risk of storing sensitive data in drafts.

For caching and page builders, there does not appear to be a universal public list of official conflicts specific to Save and Resume, but standard WordPress practice still applies. Forms are interactive elements. If the page is aggressively cached, minified, defers scripts, or rewrites HTML after load, test saving after every optimization change. Do not add random cache exclusions "just in case." Reproduce the issue first, then exclude the specific form page or related scripts according to your caching plugin's documentation.

Safe improvements for email text and retention settings

Most sites can rely entirely on the built-in settings in the WPForms builder. Code is only needed in two cases: if you want to change the Save and Resume email subject through the official developer filter, or if you want to change the partial entry deletion period through the WPForms filter published for that purpose. Both examples below are based on the WPForms developer documentation. Add snippets like these through a child theme, a small site-specific plugin, or a code snippets plugin. Do not edit WPForms, WordPress, or your active theme files directly.

Change the Save and Resume email subject

WPForms provides the wpforms_save_resume_settings_get_email_subject filter for changing Save and Resume email subjects. This is useful if the default subject line is too generic and users may not understand which form the link belongs to. The example below is a small custom adaptation based on the official filter: it does not change the link logic, it only returns a custom subject line.

/**
 * Changes the WPForms Save and Resume email subject.
 * Based on the official wpforms_save_resume_settings_get_email_subject filter.
 */
function site_save_resume_email_subject( $subject ) {
    return 'Link to continue your saved form';
}
add_filter( 'wpforms_save_resume_settings_get_email_subject', 'site_save_resume_email_subject' );

The check is simple: save a form, send the link to a test email address, and confirm that the subject line changed while the email body still includes a working link. To roll back the change, disable the snippet or remove the filter. If emails stop sending after adding the code, disable the snippet first, because even a small PHP mistake can break delivery.

Change the partial entry retention period

By default, the Save and Resume documentation refers to a 30-day retention period for partial entries. WPForms also publishes the wpforms_save_resume_tasks_deleteexpiredentriestask_expire_period filter, which lets you change the deletion period. This setting should match your site's data policy. For example, a form with a short application deadline may warrant a shorter window. But do not change the period just because it feels "cleaner." If it is too short, users may lose the chance to return.

/**
 * Shortens the retention period for Save and Resume partial entries.
 * Based on the official WPForms developer filter.
 * Review the site's data retention policy before using this.
 */
function site_save_resume_expire_period( $expire_period ) {
    return '-14 days';
}
add_filter( 'wpforms_save_resume_tasks_deleteexpiredentriestask_expire_period', 'site_save_resume_expire_period', 10, 1 );

Testing this is more involved than testing the email subject. WPForms documentation notes that changing the filter does not immediately delete entries unless the scheduled action runs. For manual verification, the WPForms admin area includes a scheduled actions section where you can find the cleanup task. On a live site, do not trigger deletion without a backup and a clear understanding of the consequences. To roll back the change, disable the snippet and restore the default behavior. Any change to the retention period should also be reflected in the confirmation text and email copy.

If you are not sure whether custom code is necessary, do not add it. For most forms, the standard 30-day window, clear warning text, and reliable email delivery are enough.

Common problems and how to diagnose them

Most WPForms Save and Resume issues do not come from one hidden bug. They come from a broken chain: the addon is active but the form was not saved, the link exists but the email is not delivered, the email arrives but does not include the Smart Tag, the user returns but expected a file to be restored, or the administrator sees Partial and treats the entry as completed. Troubleshooting works best when you move from symptom to cause instead of changing settings at random.

The save link does not appear on the form

Symptom: the setting is enabled in the WPForms builder, but there is no save link next to the submit button on the public page. Possible causes include the addon not being activated, the feature being enabled on the wrong form, the form not being saved after configuration, the page being served from cache, or a different copy of the form being published on that page.

Check: open WPForms » Addons and confirm that Save and Resume is active. Then open the exact form embedded on the page, review Settings » Save and Resume, save the form, and reload the page without cache. If the form is embedded with a shortcode, compare the form ID in the shortcode with the form you actually configured.

Fix: activate the addon, enable the setting on the correct form, save your changes, and clear the page cache. If the link appears only in preview mode but not on the published page, temporarily test the form on a clean page without the page builder or extra optimizations. If it works there, the problem is in the page environment rather than the feature itself.

The email with the link does not arrive

Symptom: the user sees the confirmation message, but the email with the link does not arrive or lands in spam. Possible causes include Enable Email Notification being disabled, the user entering the wrong address, the {resume_link} tag being removed from the email template, the site sending mail through an unauthenticated server, or a misconfigured sender domain.

Check: enable the email notification, send test emails to several addresses, check the spam folder, and inspect the subject line and sender. If other WordPress emails are also being delivered unreliably, configure SMTP and your domain records through your email provider. If the email arrives without a link, restore the {resume_link} Smart Tag in the message body.

Fix: configure SMTP, use a sender on your site domain, restore the required Smart Tag, and repeat the test. If the form is business-critical, keep the on-screen copyable link enabled as well so email is not the only return path.

Some fields are blank after returning

Symptom: the user returns through the link, but a file, signature, password, or payment field is empty. The likely cause is that this is an expected Save and Resume limitation. Official WPForms documentation states that these sensitive fields are not stored in partial entries.

Check: create a test form with a normal text field and a sensitive field, save the draft, and return to it. If the text field is restored but the sensitive field is not, the feature is working as designed. If even normal fields are not restored, check the link, the form configuration, and caching.

Fix: do not try to store sensitive data with workaround code. Move those fields closer to the final step and add an honest warning. A rollback may be appropriate if users consistently do not understand the behavior and the form depends too heavily on fields that cannot be saved.

The link opens the start of the form or does not restore answers

Symptom: the link opens the form page, but the answers are not restored, or the user sees the wrong state. Possible causes include an expired link, major changes to the form after the draft was saved, page caching, script optimization conflicts, or the user opening the wrong link.

Check: create a new draft on the current version of the form and immediately open the fresh link in a separate browser. If the fresh link works, the old draft may have expired or become incompatible with the updated form structure. If a fresh link also fails, test the form on a simple page without caching or optimizations.

Fix: do not change the structure of a live form while applications are actively being collected without warning users. After major changes, either close the old submission cycle or explain that drafts should be completed before the form update. For a caching plugin, add a targeted exclusion for the form page only after you have confirmed the conflict.

The administrator cannot find the partial entry

Symptom: the user says they saved the form, but no Partial entry appears in WPForms » Entries. Possible causes include the save flow not being completed through the confirmation screen, the user clicking the wrong button, the addon not being enabled on that form, the entry having been deleted after the retention window, or the administrator checking the wrong form.

Check: repeat the user's flow on the same public page and open the entries for that form immediately after saving. Make sure you are not looking at a general forms list but at the entries for the specific form. If the entry appears during testing, the original issue may have been user behavior or expiration. If it does not appear, go back to checking whether the feature is enabled and whether the form was saved.

Fix: simplify the link text and confirmation text so users clearly understand when the draft has actually been saved. Add an instruction after the click, such as: "Copy the link or send it to your email." If the team often looks in the wrong place, create a short internal guide explaining the difference between Partial and Completed.

The entry does not include a resend notifications button

Symptom: the familiar resend notification option is missing from the entry page. WPForms documentation notes that when Save and Resume is enabled, the Resend Notifications action is unavailable because it could send all form notifications, not just the email with the resume link. This is intended to avoid confusing or annoying the user.

Check: confirm that you are looking at a form where Save and Resume is enabled. If you need to give the user their return path again, use the resume link copy action from the partial entry details, while verifying identity first. Do not try to restore the old button with custom code unless you understand the side effects for all form notifications.

Fix: train the team on the correct action for partial entries. For completed entries, use the normal WPForms workflows. For drafts, copy the resume link only in response to a justified user request.

How to improve the form around Save and Resume without unnecessary code

The addon solves the technical problem of saving, but the quality of the outcome depends on the form itself. If the form is long, break it into meaningful pages. The first section should be easy: name, email, the main selection, or the request category. That way, users quickly feel the form moving forward, and if they save the draft, you already have enough context. Documents, signatures, and payment steps are better placed near the end because they either are not saved or require extra care.

Add a short note before any demanding section. You do not need a large block of text above the entire form. One line is enough: "You can save your draft and return later using the link." If the form is multi-page, repeat that note before the most difficult section, such as a group of long open-ended questions. Users should be reminded of the feature at the moment of fatigue, not only at the top of the form.

The warning text should sound human. Do not use heavy legal wording unless it is actually needed. It is better to describe the real action: "We will save the answers you entered as a draft. File uploads, signatures, and payment details, if present in this form, will need to be added again. The draft is available for a limited time." That gives users a clear picture of what will happen after they click.

Create a small internal handling rule for partial entries. For example: "Partial is not treated as an application, the manager does not begin processing until Completed, if the user requests the link we send it only after verifying the email, and if the draft contains sensitive information we do not forward the link in an open chat." This is not a WPForms setting, but rules like these are what turn the feature from a convenient button into a dependable process.

If you have form analytics, compare more than just the number of submissions. Look at the number of partial entries, returns, and completions after saving. Save and Resume can improve completion rates for long forms, but it can also reveal that the form itself is too difficult. If many users save a draft and never return, the issue may not be the lack of the feature. It may be unclear questions, too many required fields, or weak motivation to finish the application.

Video demonstration of how the addon works

The official WPForms release article includes an embedded video for Save and Resume. It is useful as a visual confirmation of the core flow: the user sees the save link, passes through the warning screen, gets a way to continue, and the administrator sees the partial entry. Watch it after reading the configuration sections so you can connect the interface steps to the guide text: enabling the feature, the warning, the return link, the email, and the Partial status.

When WPForms Save and Resume is the right choice

WPForms Save and Resume is worth using when the form genuinely calls for a pause: a long questionnaire, application, survey, onboarding flow, multi-page process, or collaborative completion workflow. In that kind of setup, the addon adds a clear chain: save progress, explain the conditions to the user, provide a return link, expose the partial entry to the administrator, and allow the form to be completed later. This is not a decorative feature. It is part of the user workflow.

Before launch, verify four things: the form is enabled specifically under Settings » Save and Resume, the email includes {resume_link}, the warning honestly explains sensitive fields, and the team understands the difference between Partial and a completed submission. If those points are covered, you can move on to real testing on your form and, if needed, download the installation file from the download section on the product page.

If the form is short, does not require users to come back later, mostly consists of file uploads or payment fields, or your team is not ready to treat drafts as user data, then Save and Resume should not be enabled automatically. First simplify the form, configure email delivery, review access roles, and only then add the save workflow. Success here is not measured by how many toggles are turned on. It is measured by whether the user can return without stress, complete the form, and clearly understand what happened to their data.