VKT Toolkit · September 15, 2026 · 9 min read

How to Automate Multi-Step Forms in Chrome (2026 Guide)

Step 1: personal information. Step 2: employment history. Step 3: document uploads. Step 4: review and submit. You filled this out last month for candidate A, and now you're doing it again for candidate B — same company info, same hiring manager, same department address, different name and resume. The wizard is five pages long, forty fields deep, and you'll do it twelve more times this quarter.

Multi-step forms — wizards, application flows, approval chains — are the worst category of repetitive web work. They're too complex for browser autofill, too varied for scripts, and too long for "just type it faster." Here's why, and how form snapshots solve the problem in Chrome.

Why Regular Autofill Fails on Multi-Step Forms

Chrome's built-in autofill has three specific blind spots on wizard-style forms:

• Page-level blindness. Autofill works on the current page's fields by type. When you click "Next" and the form navigates to step 2, autofill doesn't know that step 2 exists — it won't proactively fill fields on a page you haven't loaded yet.
• No form identity. Autofill doesn't track "this is the same form, page 2 of 5." It sees a new page with new fields and tries to match them to your saved identity. If step 2 has fields like previous_employer or clearance_level, autofill has nothing for them.
• URL confusion. Many wizards use query parameters (?step=2) or hash fragments (#step2) to track progress. Some use entirely different URLs per step. Others are single-page apps that show/hide sections without any URL change. Autofill doesn't navigate any of these patterns intelligently.

The result: you get partial fills on step 1 (name, email, address), and then you're on your own for steps 2 through 5. On a 40-field wizard, autofill might cover 6 fields. The other 34 are manual.

How Form Snapshots Work Across Multiple Pages

A form snapshot tool like VKT Form takes a fundamentally different approach: instead of matching fields by type, it captures the entire state of a page's form and replays it onto the same page identified by URL.

For a multi-step wizard, this means:

• Step 1 snapshot: captures all fields on page 1, bound to the URL of step 1.
• Step 2 snapshot: captures all fields on page 2, bound to the URL of step 2.
• Steps 3–N: same pattern — one snapshot per page, each URL-matched.

When you run the wizard again, you fill each step by clicking once in the VKT Form panel. The extension loads the snapshot for the current URL, matches fields by their name attribute (with DOM-order fallback), and pours the values in. You move to the next step, click again, and repeat.

For single-page wizards that show/hide sections without URL changes, all fields exist in the same DOM — so one snapshot captures everything, and you fill the entire wizard in a single click.

URL Matching: How the Extension Knows Which Step You're On

This is the core technical challenge of multi-step form automation, and it's worth understanding how VKT Form handles it:

• Distinct URLs per step (/apply/step-1, /apply/step-2): straightforward — each step's snapshot is bound to its URL. Visit the URL, get the snapshot.
• Query parameter steps (/apply?step=2): VKT Form normalizes URLs by stripping volatile query parameters while preserving stable ones. If step is consistent across runs, it matches correctly.
• Hash-based routing (/apply#step2): common in SPAs. The extension includes the hash in URL matching, so #step2 and #step3 resolve to different snapshots.
• No URL change at all: if the wizard is a single page with JavaScript toggling visibility, all fields are in one DOM. One snapshot captures everything; the fill operation works regardless of which section is currently visible.

If the URL changes between visits in ways that break matching (session IDs, timestamps in the path), the snapshot falls back to matching by the base URL pattern, which covers most cases.

Real-World Multi-Step Form Scenarios

Recruitment and hiring flows

Corporate ATS (Applicant Tracking Systems) like Workday, Greenhouse, and Lever often have multi-page job application forms. The hiring side — submitting offer letters, approval requests, or onboarding forms — repeats even more. Each flow has 5–8 steps with fields that stay constant across candidates (company details, department, manager info). Snapshots let you fill the constant fields and type only what changes.

Insurance and financial applications

Getting an insurance quote online typically involves 4–6 pages: personal details, coverage preferences, vehicle/property info, claims history, review. If you're an agent running quotes for similar client profiles, the first four pages are nearly identical each time. One round of snapshots, and you're filling each step in seconds.

Government service portals

Permit applications, tax filings, benefit claims — government forms are notoriously long and multi-step. They also tend to use older technology stacks where Chrome autofill performs poorly. A snapshot tool that works on classic server-rendered forms (not just SPAs) handles these reliably.

Internal approval workflows

Expense approvals, purchase requests, PTO forms — many companies route these through multi-step internal portals built on SharePoint, ServiceNow, or custom frameworks. The "requester info" and "department" sections repeat every time; only the amounts and dates change.

Step-by-Step: Setting Up Multi-Step Form Automation

1. Install VKT Form from the Chrome Web Store.
2. Navigate to step 1 of the multi-step form. Fill in the constant values — the ones that stay the same every time you run this wizard.
3. Click "Collect" in the VKT Form panel. The extension saves a snapshot of step 1's fields, bound to the current URL.
4. Advance to step 2 (click Next, Continue, or whatever the form uses). Fill the constant fields on this page and click "Collect" again.
5. Repeat for every step of the wizard. Each page gets its own snapshot.
6. Clear variable fields — dates, amounts, names, file uploads — from each snapshot. The goal is to keep only the fields you retype every time.
7. Next time you run the wizard: navigate to step 1, click "Fill" in the VKT Form panel. The constants land. Click Next, fill step 2. Repeat. You type only what's actually different.

The first run (collecting all snapshots) takes about as long as one manual completion. Every run after that saves 60–80% of the typing.

Single-Page vs Multi-Page Wizards: Different Mechanics, Same Tool

Honest Limits: What Multi-Step Automation Can't Do

• Conditional logic. If step 3 shows different fields based on a selection in step 2, you may need multiple snapshots for step 3 (one per branch). The tool fills what's on the page; it doesn't trigger conditional logic itself.
• File uploads. <input type="file"> fields can't be programmatically populated for security reasons. You'll always upload files manually.
• CAPTCHAs and verification. If a step includes a CAPTCHA or phone verification, that step requires manual input. Snapshots fill the fields around it.
• Submission. VKT Form fills fields — it doesn't click "Submit" or "Next" for you. You stay in control of form navigation and final submission.

Within those limits, the time savings are substantial. A 5-step wizard that took 15 minutes manually drops to 3–4 minutes with snapshots — and that compounds across dozens of runs per quarter.

Frequently Asked Questions

More VKT tools live in the extensions catalog, or reach us at [email protected].