Help & feedback

SaveForm Support

Found a form that SaveForm doesn’t handle correctly? Have feedback about the MVP? Open an issue and describe what happened.

Open a GitHub issue

A useful report

Help us understand the problem.

When possible, include:

  • the website or domain where the problem occurred;
  • the type of form field that failed;
  • what you expected to happen;
  • what actually happened;
  • your Chrome version, if relevant; and
  • your SaveForm version.

Quick answers

Frequently asked questions

Where are my presets stored?

Locally in the Chrome profile where SaveForm is installed.

Does SaveForm upload my saved form values?

No. The current MVP does not send saved form values to SaveForm servers.

Does SaveForm save sensitive fields?

SaveForm is designed to exclude identifiable passwords, authentication and recovery codes, payment and bank details, government and patient identifiers, medical-condition fields, API and session secrets, private keys, and file uploads. Detection cannot determine whether arbitrary text in a generic field is sensitive, so do not save confidential or highly sensitive information in ordinary fields.

Does SaveForm work on every website?

No. It works best with standard HTML form controls. Highly customized components may not be fully supported.

Why were some fields not restored?

SaveForm skips fields when it cannot match them safely instead of guessing.

What happens if I uninstall SaveForm?

Chrome clears SaveForm's local extension storage when the extension is removed. SaveForm has no cloud backup, so those presets are not recoverable through SaveForm.

Is there cloud backup?

Not currently.