Skip to main content
Version: 1.28 (Current)

Forms 2.0 - Saving Drafts

caution

This page is preliminary and subject to change as Forms 2.0 continues to be developed.

Long forms take time to fill in, and users get interrupted. With Auto Save Drafts, a Forms 2.0 form saves the user's answers as they type. If they close the tab, lose their connection or come back tomorrow, their answers are still there.

It takes one setting, and there's nothing to build.

Turn on Auto Save Drafts​

  1. Open the form in the Form Builder and go to the Settings tab.
  2. Under General, check Enable Auto Save Drafts.
  3. Click Save.

That's it. The form now saves drafts for every user.

What it does for you​

  • Saves as the user types. About half a second after each change, the answers are saved. They're also saved when the user switches to another tab or leaves the page.
  • Shows that it's working. A small status next to the form shows Saving… and then Saved, so users know their work is safe.
  • Restores automatically. When the user opens the form again, their answers are filled back in, in place of the values the form would normally start with.
  • Handles every field. Text, dropdowns, dates, Sections, and even the entries of a Repeater are saved and restored, with no extra setup.
  • Keeps working when it can't save. If the browser's storage is full or blocked, the status shows Not saved. The form still works, and the answers are still submitted normally.

Drafts are saved in the user's browser, for each form and each user. A visitor who isn't logged in gets a draft for their browser.

Clear the draft when you're done​

A draft stays until it's cleared, so a submitted form doesn't come back with old answers. Two ways to clear it:

  • After a successful submit, add a Clear Draft action to the submit button's On Click Handler, after the action that saves the data. If the save fails, the draft is kept, so the user doesn't lose their answers.
  • To let users throw away their answers, add a Button with Button Type set to Cancel. A Cancel button clears the draft by itself after its actions run.

Good to know​

  • Same browser only. The draft is kept in the browser where the user filled in the form. It isn't available on another device, and it's lost if the user clears their browser data.
  • One draft per form and user. The draft doesn't depend on the page URL. If one form is used to edit different records, for example ?OrderId=5 and ?OrderId=7, the user's draft from one record appears in the other. Keep Auto Save Drafts for forms that create something new, such as applications, registrations or requests.

Security​

Drafts are stored in the browser's local storage, as plain, unencrypted text. That keeps the feature simple and fast, but it means the draft is not protected the way data on your server is:

  • Users can find and read their drafts. Anyone with access to the browser can open its developer tools and see the saved answers. On a shared or public computer, that includes the next person who uses it, until the draft is cleared.
  • Users can change their drafts. A draft can be edited in the developer tools, and the edited values are loaded into the form the next time it opens. This includes fields the user normally can't change, such as fields that are disabled or filled in for them.
  • Every answer is saved as typed. This includes values typed into Password fields, and any personal, financial or health information the form asks for.
  • Other scripts on the site can read it. Local storage is shared by all the pages of your site, so any script running on the site can read the drafts.

The form still checks the submitted values with its validators when the user submits, so treat a value loaded from a draft like any other value the user typed. Don't rely on a field being disabled or pre-filled to protect its value.

If data security matters for the form in question, for example because it collects passwords, payment or health details, or values the user must not be able to change, consider a different method than Auto Save Drafts. You can leave drafts off, or save drafts on your server as described in When Auto Save Drafts isn't enough, where you control who can see and change them.

When Auto Save Drafts isn't enough​

For most forms, Auto Save Drafts is all you need. Consider building your own drafts only when you need something it doesn't do, for example:

  • Users must continue on another device or browser.
  • The form edits existing records, and each record needs its own draft.
  • Admins need to see, report on or follow up on unfinished drafts.
  • The form handles data that shouldn't be kept in the browser. See Security.

Building your own takes much more effort. You take full responsibility for developing, testing and maintaining both halves of it:

  • Saving the draft. Typically a Save Draft button with its Validation Scope set to None, so it saves an incomplete form, and actions that write the answers to your own table. [FormData] gives you all the answers as one JSON value.
  • Restoring the draft. Actions in On Preinit that read the draft back and give each field its value. A token created in On Preinit with a field's name becomes that field's starting value. Fields in a Section need their full name, such as Billing:City, and a Repeater needs its entries loaded into its Initial Entries list.

You also need to decide when a draft is deleted, what happens when there's no draft, and how to keep the restore working as the form changes. Every field you add to the form must be added to the restore too.

Auto Save Drafts does all of this for you, for every field type, and keeps working as you change the form. Start with it, and build your own only when you have a clear need it can't meet.

  • Settings - the Enable Auto Save Drafts setting
  • Clear Draft - clears a saved draft
  • Button - Cancel buttons and Validation Scope

Last updated: November 18, 2026