Best Form History Extensions for Chrome
Published: October 4, 2026. Updated: November 2026 by Andrew Apell, who builds Form ReDraft
Quick Answer
Short answer: I would install one of three form history extensions on Chrome right now. Typio Form Recovery Reboot saves your input as you type and is the maintained fork of the original Typio. Form History Control (II) deals with history that already exists, offering search, editing and export. Form ReDraft writes an encrypted local draft for each field, refuses credentials and reaches rich text editors. Lazarus, the name most people actually search for, is no longer on the store.
Key Takeaways
- When a tool saves counts for more than which tool it is. A copy taken as you type survives a crash, a reload and a closed tab. A copy offered afterwards is a recovery attempt, not a guarantee.
- Typio Form Recovery Reboot and Form History Control (II) do different jobs. One captures input, the other manages what has already been captured. Neither replaces the other.
- Whatever you install, check that it refuses password and card fields by name and by type, and that deleting your data really deletes it rather than hiding it.
Form history extensions have been around for more than a decade. Lazarus and Typio were the names everyone knew. When those originals stopped being maintained, a small crowd of replacements turned up. Some were careful. Some were abandoned within a single release.
Here I name the three you can install today and explain what each one actually does. I am not publishing a ranked list with a winner at the top. The right tool depends on whether you are losing text while you write it or trying to read history that has already been stored.
The Three, and What Each Does
| Extension | What it does | Choose it if |
|---|---|---|
| Typio Form Recovery Reboot | Saves form input as you type and offers it back after a reload or a crash. | You lose text in ordinary forms and comment boxes and want it back in one click |
| Form History Control (II) | Manages form history entries with search, view, edit, cleanup and export or import, and adds a form filler. | You want to see and clear what is stored, or fill the same forms repeatedly |
| Form ReDraft | Writes an encrypted draft per field on your device, refuses credential fields and covers rich text editors. | You write long answers, use editors such as Notion, and want the copy to stay local |
Lazarus is missing from that table on purpose. It is the extension most people remember, but it is not on the Chrome Web Store at the moment, and recommending it would send you to a dead link. My comparison with Lazarus covers what it did well and why its users went looking elsewhere.
Typio Form Recovery Reboot
Typio Reboot is the maintained fork of the original Typio. Its listing says it saves form input automatically as you type, so text is not lost to an accidental reload or a crash (Chrome Web Store, Typio Form Recovery Reboot, retrieved November 2, 2026).
I trust it for the same reasons I trust any fork. There is a named maintainer, a public repository and a record of adapting to the platform changes that killed the original. Moving to the current extension manifest is exactly the job that ends a project when nobody is left to do it, and somebody did it here.
For the ordinary case, it is the strongest choice I know. That means a textarea or a comment box that empties when the page reloads. It is weaker for editors, where the writing surface is application state rather than a form field.
Form History Control (II)
Form History Control (II) takes a different route. Its listing describes managing form history entries, with search, view, edit, cleanup and export or import, plus an easy form filler (Chrome Web Store, Form History Control (II), retrieved November 2, 2026).
If your worry is what has already been stored rather than what might be lost, this is the tool that answers it. You can read the entries, delete the ones you never wanted and export the rest. Capture tools rarely give you that. Editable history turns a passive record into something you can audit.
The trade-off is that it manages rather than rescues. Sorting out entries after they exist does not help with a rich editor that never produced an entry. The store rating of 3.9 suggests a tool that works for its users without delighting them.
Form ReDraft
Form ReDraft takes capture seriously and keeps it local. Shortly after you pause, it writes an encrypted copy of each field to your own device. It offers that copy back in one click and refuses credential fields before they reach the draft layer. Sync across devices is optional, paid and key based rather than tied to an account.
The difference that shows up in practice is editor support. A restore that writes straight to the element gets overwritten by the next render. Form ReDraft writes through the interface the page itself uses, and that is what lets the text survive a React or Vue form rebuilding itself. The recovery guide explains why that distinction settles most outcomes.
What Separates a Good Tool From a Bad One
- When it saves. A tool that captures as you type has a copy before anything goes wrong. A tool that offers recovery after the fact is asking the browser for something the browser does not keep.
- Which fields it refuses. Password, card and one-time-code fields should be excluded by type and by name, and that exclusion should not be a switch somebody can quietly turn off.
- Where the copy lives. Local storage with optional sync is a different promise from an account backed service. The permission list tells you which one you are getting.
- Whether it handles editors. Test it on a site built as a single page app. A tool that works on a plain form can still be useless everywhere you actually write.
- Whether deletion is real. Deleting means gone, not hidden behind an interface that has stopped listing it.
Where Form ReDraft Sits
I would choose it for long writing, not for auditing history. Drafts are encrypted and local, credentials are refused by design, and the yearly plan exists to carry drafts between machines rather than to unlock the local copy. If your work is short answers in ordinary forms, Typio Reboot is smaller and simpler. If your concern is what has already been stored, Form History Control (II) is the tool built for that question.
A Short Checklist
- Install one tool, not three, and use it for a week on the sites where you actually lose text.
- Test the failure, not the feature. Reload a page with a draft in progress and see what comes back.
- Check the permission list and the privacy statement before you type anything confidential.
- Confirm the export before the archive grows. A tool that cannot hand your text back is holding it.
FAQ
Are form history extensions safe?
I treat them as inherently sensitive, because their job is to remember what you type. Safety comes from refusing credentials, keeping data on your own device by default and leaving every network path off until you switch one on.
Do form history extensions work with password managers?
They should stay out of the way entirely. Password fields are not form history, and a good tool refuses them before it even reads the value.
Why does my form history extension not work on some sites?
Most tools watch for named fields when the page loads. Sites that render fields later, inside shadow roots or with fresh identifiers on every render are invisible to that approach.
Can I move my saved history to a new extension?
Only if the old tool offers an export. Look for a JSON or plain text export before you switch, because the data is usually stored in a format nothing else can read.
Related Articles
How to Stop a Chrome Extension Saving Passwords
How to check what a form tool records in under a minute.
Read moreHow to Save Work on Quora and Single Page Apps
Why modern sites defeat most recovery tools.
Read moreHow to Restore Text Into React Inputs
The test that separates a real restore from a cosmetic one.
Read moreTry a Form History Tool You Can Check
Form ReDraft refuses credentials, keeps everything encrypted on your own device by default and opens no network path until you enable optional paid sync.
Read the documentation