Save and continue later
This feature lets people filling out a form pause and later pick up exactly where they left off — without losing any input.
The description in the interface:
Save and continue later
Respondents can come back later, pick up where they left off, and complete the form without their previously entered data being lost.
Turning it on
In the More tab of the form editor: Save to continue later.
Plan-dependent
This feature isn't available on the entry-level plan.
What people filling it out see
| Element | Text |
|---|---|
| Save button | Continue later |
| Confirmation | Form has been saved! |
| On returning | This form has been saved but not yet submitted! |
| Explanation | You can finish filling out the form later. |
| Discard saved state | Delete all |
| Close dialog | Done |
Why it's worth it
Without this feature, input is lost
A form is only saved when submitted. If someone closes the browser on page 3 of 5, everything is gone — without warning.
For anything that takes more than a few minutes, this feature isn't a convenience — it's protection against frustration and abandonment.
Especially worthwhile for:
- multi-page forms
- forms with many fields
- forms that require gathering documents
- forms mostly filled out on mobile
Important characteristics
A saved state is not yet an entry
Until it's submitted, no entry exists on the Grid. The data is stored temporarily and isn't visible to you.
A Flow with the trigger Entry via form only starts when the form is actually submitted.
The saved state is tied to the device and browser
Someone who saves on their phone won't automatically find that state again on their computer. Mention this in the form description if it's relevant to your case.
Distinguishing it from similar features
| Feature | Purpose |
|---|---|
| Save to continue later | The person filling it out pauses and resumes on their own |
| Prefilled link | You preset values before someone fills the form out |
| Editing entries via form | An existing entry gets changed |
Use the other approach for feedback loops
If you want someone to add to a process later while you can see the state in the meantime, Save is the wrong tool — the data is invisible to you until submission.
Instead, have the entry created immediately and send a prefilled form link via a Flow for follow-up.