How to autofill online application forms safelyYour click

It's 11pm, you're on page 4 of 9 of a visa application, and the portal has just asked for your address history again, in a different format from the last form. Your browser offered to fill your name on page 1 and has been quiet ever since. You start to wonder how many more times you will type your passport number this year.

This guide shows how to autofill online application forms properly: what your browser's built-in autofill can do, where it stops, and how to fill long portals page by page, uploads included, without losing control of what gets sent.

How do I autofill online application forms?

Save your details once, then fill each page of the application from them. Read the page, fix anything wrong, and click Next yourself. Repeat until you reach the final review page, then check everything and submit it yourself. For short forms, browser autofill is enough. For long portals with uploads and custom questions, use a page-by-page form-filling extension.

The method matters more than the tool. Online applications fail in predictable ways: a date in the wrong order, a middle name in the given-names box, a scan uploaded to the wrong slot. Filling page by page, with a quick read before each Next, catches those while they are still cheap to fix.

Here is the whole routine in seven steps:

1. Gather your source documents. Passport, previous visas, education and work history, and any reference numbers the portal will ask for.
2. Save your details once. In your browser's autofill settings or in a form-filling extension profile.
3. Open the portal and start a new application. Sign in yourself; never hand your login to a tool.
4. Fill one page. Let autofill or the extension complete what it can.
5. Read every field on that page. Compare against your documents, not your memory.
6. Fix errors the portal shows, then click Next yourself.
7. Stop at the final review page. Read the declaration, save a copy, then submit and pay yourself.

Is Chrome autofill enough for long applications?

Browser autofill is good at the basics: names, email, phone, addresses and payment cards on forms that use standard field names. It is not built for long application portals. It doesn't answer custom questions, attach files, or handle the unusual layouts many government, university and employer portals use, so you will still type much of a long application by hand.

Google's own help page says Chrome can save and fill contact info, payment methods, passwords and, in newer versions, identity and travel details, and it notes that "not all websites and forms are compatible" (Chrome Help (opens in a new tab)). That caveat is the whole story for application portals.

Where built-in autofill usually stops:

• Split fields. Date of birth as three dropdowns, phone numbers with a separate country code, passport expiry as day, month and year boxes.
• Custom questions. "Have you ever been refused a visa?", "Intended start term", "Highest qualification completed". Autofill has nothing saved for these.
• Dropdown wording. Your country might be listed as "Korea, Republic of" or "South Korea". Matching depends on the site.
• Repeated sections. Address history, employment history and travel history that need several entries in order.
• File uploads. Browsers don't attach files for you.
• Multi-page flows. Each page is a fresh form. Autofill has no idea that page 6 depends on what you chose on page 2.

How does filling a multi-page portal page by page work?

A page-by-page filler reads the current page, matches each field to your saved details, fills it, and then waits for you. You review the page and click Next. On the following page it repeats. The portal stays in charge of order and logic, and you stay in charge of every step forward, which is what makes this approach safe on long forms.

Multi-page portals often change later pages based on earlier answers. Pick "married" on page 2 and page 5 suddenly asks for your partner's details. A tool that tries to fill everything in one blind run can't see that branching coming. A tool that works one page at a time simply fills whatever the portal shows next.

What a good page-by-page run looks like:

• It shows you what it filled. Every field it touched is visible before you move on.
• It flags what it couldn't fill instead of guessing. An empty field you notice is better than a confident wrong answer.
• It remembers new answers. When a portal asks something new, you answer once and can save it for next time.
• It never clicks Next for you on the last page. More on that below.

This is how AppliFlo for Chrome works. It is coming soon to the Chrome Web Store. It fills online portals page by page, including multi-page portals, and stops on the final step. Our demo portal is six pages long, and the extension waits for you between each one.

Can an extension upload my passport scan and photos?

Yes, some extensions can attach saved files when a portal page asks for them, such as a passport bio page, a photo or a CV. Uploads are where autofill saves the most time, and also where mistakes hide, because portals often have several similar upload slots. Always open each slot after filling and confirm the right file landed in the right place.

Upload mistakes are common and easy to miss:

• Wrong slot. The passport scan lands in "Other identity document" instead of "Passport bio page".
• Wrong format or size. The portal wants a JPG under a set size and you have a large PDF. Check the portal's own instructions.
• Old document. Last year's payslip or an expired passport scan saved months ago.
• Missing pages. A two-page document scanned as one image, with the second page cut off.

AppliFlo for Chrome can handle uploads such as passport scans and photos as part of the page-by-page run. It still pauses for you on every page, so you can open the upload list and check it before clicking Next.

What should I do when the portal shows an error?

Read the portal's own error message, find the field it refers to, fix that field, and try again. Many portals show errors at the top of the page in general terms ("Please correct the highlighted fields"), which makes long pages painful. A good filler matches each site error to the field that caused it, so you can jump straight there.

Common error triggers on application portals:

• Date formats (DD/MM/YYYY versus MM/DD/YYYY).
• Names with characters the portal doesn't accept, such as accents or hyphens. Follow the portal's instructions and your passport.
• Postcodes that don't match the suburb or state you picked.
• Required checkboxes, like consent or privacy acknowledgements, left unticked.
• Session timeouts on long pages. Save drafts often if the portal allows it.

AppliFlo for Chrome maps the site's own error messages to each field, so on a long page you see which box the portal is unhappy with instead of hunting for a red outline.

How do I stay in control of what gets sent?

Choose a tool that fills but never submits or pays, review each page before you move on, and require a confirmation before sensitive numbers are entered. Read the final declaration yourself and keep a copy of the review page. Control comes from three habits: page-by-page review, confirm-before-fill for sensitive data, and a human-only final click.

Confirm sensitive fields, site by site

Some details deserve a second thought every time: tax file numbers, bank account details, sometimes passport numbers. A good extension asks before it fills them, per site. That way, if you are on a site you didn't expect to give your tax file number to, the tool stops and asks rather than filling silently.

AppliFlo for Chrome fills tax file numbers and bank details only after you confirm, site by site. You say yes once for a site you trust, and you can change it later.

Keep AI away from your values

Some extensions use AI to work out what an unusual field is asking for. That is useful, but it matters what the AI sees. In AppliFlo for Chrome, AI sees the form's field labels, like "Passport number" or "Intended start term", and never your values. Your passport number is not sent to a model to work out where it goes.

Never auto-submit

The last click on an application usually sits under a declaration. On the Australian Form 80, for example, Part S says "Giving false or misleading information is a serious offence" and asks you to declare the information is "complete, correct and up-to-date in every detail" (Form 80 PDF (opens in a new tab)). Online portals carry similar declarations. That's a statement you make, not one a tool should make for you.

That's why AppliFlo never submits a form or pays for you. The count of forms we have submitted on anyone's behalf is zero, by design. We explain the reasoning in why our form filler stops before Submit.

Is it safe to let an extension fill my application?

It can be, if the extension asks only for the permissions it needs, encrypts what it stores, and asks before filling sensitive details. Research presented at The Web Conference in 2024 found browser extensions with page access can read sensitive form fields, so who you trust matters more than which button you press.

Researchers at the University of Wisconsin–Madison found that a meaningful share of Chrome Web Store extensions had permissions that would let them read sensitive input fields, and 190 accessed password fields directly (Nayak et al., WWW '24 (opens in a new tab)). That's not a reason to avoid extensions. It's a reason to check them.

Quick checks before you install any form filler:

• Does it explain why it needs access to the sites you visit?
• Does it say where your saved details are stored and how they are encrypted?
• Does it ask before filling tax, bank or passport numbers?
• Does it say what, if anything, it sends to AI?
• Does it promise not to submit or pay for you?

Our full checklist is in is it safe to save passport details in a browser extension?

How should agents fill portals for clients?

Agents should fill from the client's record rather than retyping, keep the client's sensitive details under the same confirm-before-fill rules, and stop before lodgement so the client or the responsible professional makes the final declaration. The page-by-page method is the same; the source of truth is the client file instead of your own profile.

For agents, the most useful habits are:

• One record per client. Fill portals from it, not from an old application or an email thread.
• Review against documents. Check the passport scan itself, not the record, for names and numbers.
• Clear hand-off. Know who presses Submit and who reads the declaration with the client.
• Keep the record current. If a portal reveals a mistake in the client file, fix the file too.

If you fill university portals for students, the study admissions page shows how this works with AppliFlo. Our education agent student visa guide covers the paperwork around it. If you are applying for jobs yourself, see autofill job applications without auto-applying and the job applications page.

Common mistakes when autofilling applications

Most autofill mistakes come from trusting the fill instead of reading it. The fixes are simple: review each page against your documents, keep saved details current, and check uploads one by one before moving on.

• Stale saved details. A new address, a renewed passport, a changed phone number. Update the profile before you start, not halfway through.
• Given names and family names swapped. Some portals ask for "surname" first. Check against the passport.
• Every-page Next clicking. If you click through without reading, you are auto-submitting with extra steps.
• Assuming one country format. Dates and phone formats differ by site. Look at each field's example text.
• Saving answers that change. "Reason for travel" or "Why this role?" should be written fresh each time.
• Forgetting the copy. Save or screenshot the final review page before you submit. Some portals don't let you see the full application afterwards.

The short version

Browser autofill is fine for checkout pages and newsletter sign-ups. For a long visa, university or job application, fill page by page from details you saved once, read every page, check every upload, confirm sensitive fields deliberately, and submit it yourself. The time you save comes from never retyping; the safety comes from never skipping the read.

This is general information, not legal or migration advice. For visa applications, a registered migration agent or lawyer can advise on your case.