Keep input values and prefill a form ¶
Enable browser storage ¶
Workbook → Advanced settings includes Browser storage enabled. For the HTML output, this controls the form-storage behavior in the end user’s browser. Enable it, convert, then test entering values and returning to the same page.
Browser storage is local to the end user’s browser. It is not a server backup or a shared record store. A different browser, cleared storage or browser restrictions can change what is restored. Test the browsers and privacy settings your end users use.
Prefill fields from a link ¶
The converted HTML page can read values from its query string using the generated field identifiers. For a field whose identifier is quantity, a link ending in ?quantity=3 supplies that value. Use the identifiers actually emitted in your converted page, not an assumed Excel address.
Workbook → Advanced settings includes Field names from labels; changing naming can change the identifiers used by these links. Test your link after changing labels or naming settings. Use simple values first and verify text encoding and each control type in the converted result.
Read-only prefills ¶
The HTML query-string helper recognizes _readonly when applying preset values. This is a page-control behavior, not authorization or protection of confidential data. A end user can change the URL; do not put secrets in prefill links.
Check restored and preset values ¶
Test an initial visit, a return visit, your prefill link and Reset. Confirm the resulting values and calculations rather than relying on an assumed order between defaults, browser storage and query-string input.
Check connection requirements ¶
Saving input values in browser storage does not guarantee that the calculator or form works offline. Test the actual intended workflow before distributing a downloaded HTML bundle: external assets, server-backed calculations and submissions may still need a connection. Historical offline-form and installer recipes are not current offline guarantees.