Lorixen.
EN

Long application forms: letting people save and come back

Short answer: Anyone filling in a form that takes more than ten minutes will be interrupted, so give them a way to stop without losing their work. The usual options are an emailed resume link, a proper account with saved drafts, or quiet autosave in the browser, and most long forms need two of the three. Tell people how long a draft lasts, warn them which answers (uploads, signatures, payments) won't be kept, and treat the resume link like a key to their answers.

A membership application, a supplier onboarding pack or a scholarship form from a private trust can easily run to forty questions. People start these on a lunch break, realise they need a document from home, and close the tab. If the form forgets them, a good share never come back. The fix is rarely a redesign of the questions; it is giving the form a memory.

The three ways a form can remember someone

Emailed resume link. The person clicks "Save and continue later", types an email address, and receives a unique link back to their half-finished answers. Gravity Forms documents exactly this flow in its Save and Continue guide: the form generates a link to the current state of the submission, offers to send it by email, and the link lasts 30 days by default. WPForms describes a similar add-on, with a copyable resume link, an optional email and the same 30-day expiry in its Save and Resume documentation (both as of November 2026; check the provider's page before relying on the numbers).

An account with drafts. Applicants log in and see "Your applications: 1 in progress". This suits forms people return to over weeks, or where staff need to see drafts. It costs more to build and adds a sign-up step at the start.

Browser autosave. A script copies answers into the browser's storage as people type, so an accidental refresh or a closed tab doesn't wipe them. MDN's Web Storage guide explains the difference that matters here: sessionStorage lasts only for the page session, while localStorage survives the browser being closed and reopened. Autosave only works on that one device and browser, so it is a safety net, not a resume feature.

A sensible default for most organisations: autosave for accidents, plus an emailed link for deliberate pauses. Add accounts only when people genuinely return several times.

Symptom → cause → fix

What you see Likely cause What to change
Many people start, few finish, and the drop-off sits on one page That page asks for something people don't have to hand (a reference letter, a certificate, a bank detail) List everything they'll need before page one, and put a "Save and continue later" link right next to that question
Applicants say their resume link "doesn't work" The draft expired, or the email never arrived Show the expiry date in the confirmation and the email; check the email lands in inboxes, not spam
Returning applicants find their uploaded files missing Some upload fields aren't kept when the form is saved Tell people before they save; switch to an upload field that stores files at upload time if your tool offers one
Signature or payment boxes are blank after resuming Sensitive fields are deliberately not stored in drafts Move signatures and payment to the very last step, after everything that can be saved
Answers vanish after a phone refresh No autosave, or the browser blocked storage Add autosave with a storage check, and show a small "Saved a few seconds ago" note
Staff can't find a draft when someone phones for help Resume links aren't recorded anywhere staff can see Choose a tool or build that lists partial entries in the admin area
People open the form on a work laptop and can't continue on their phone Autosave is tied to one browser Offer the emailed link as well, and say so on the page

Why uploads and signatures behave differently

Both plugin vendors call this out. Gravity Forms notes that a single-file upload field doesn't keep a file added before saving, because files are only checked at final submission, while its multi-file field validates at upload time and keeps them. WPForms lists password, signature, file upload and card payment fields among those that are not stored when someone saves progress. Neither is a bug: they are design choices to avoid holding sensitive or unchecked data in a half-finished record. Your job is to arrange the form so those fields come last.

Why autosave sometimes silently fails

MDN points out that a browser may appear to support storage but give the page none to use, for example in some private browsing modes, and that a full quota throws an error. A good autosave checks first and, if storage isn't available, tells the person to use the save link instead of pretending everything is fine.

Gravity Forms' documentation is blunt about this: anyone who has the resume URL can open and continue the saved submission, so the site must run over HTTPS. Practical habits follow from that:

  • Don't put the resume link in places other people can see, such as a shared office printer queue or a public chat.
  • Keep drafts only as long as people realistically need them, and say how long that is.
  • Never display saved personal details on the page before the person has re-entered something only they know, if the form holds anything sensitive. An account login does this naturally.
  • Delete abandoned drafts on a schedule rather than letting them pile up.

What counts as acceptable handling of personal data depends on your organisation, so check the rules where you operate.

Small design details that help people finish

  • A progress indicator with honest numbers. "Step 3 of 6" beats a bar that jumps around.
  • A visible save link on every page, not just at the bottom of the last one. WPForms places its link near the submit button by default; on long pages, a copy near the top helps.
  • A confirmation that says what happens next: "We've emailed a link to sam@example.com. It works until 4 December." The date is far more useful than "30 days".
  • A reminder email a few days before the draft expires, if your tool or build supports it.
  • Clear wording on the button. "Save and finish later" is easier to understand than an icon.

A hypothetical example

Imagine a sports club whose membership form asks for a photo, medical contact details and a direct debit mandate. Restructured, it collects personal details and contacts first, offers the save link on every page, asks for the photo as a multi-file upload so it's kept, and leaves the payment details and signature to a final short page. Nothing about the questions changed; only the order and the memory.

FAQ

Is an account better than an emailed resume link?

Only if people come back several times or need to track the status of an application afterwards. For a one-off form, an emailed link is less friction and easier to build.

How long should a saved draft last?

Long enough for the slowest realistic gap, often a few weeks. The 30-day defaults in common WordPress form plugins are adjustable; whatever you pick, state the actual date in the confirmation.

Can autosave replace a save button?

No. Autosave protects against refreshes and closed tabs on the same device. People who switch devices or come back days later still need a link or an account.

Why do people say the form "lost" their attachments?

Usually because the upload field they used isn't kept in drafts. Swap the field type if your tool allows, or ask for files at the end.

Planning a long form that people actually finish is the kind of build we enjoy, so tell us what yours needs to collect.

Sources

WhatsAppLet’s talk