Comparison
Browser automation vs auto typer
These two get lumped together and they are not the same category of thing. Browser automation drives a whole page. An auto typer enters text into one field you picked. Most people searching for the first actually want the first, and should not read the rest of this page.
What browser automation is
Selenium, Playwright, Puppeteer and the commercial RPA platforms all do a version of the same job: they hold the browser and act as the user. A script locates elements by selector, clicks them, navigates between pages, switches tabs, waits for things to load, reads values back off the page, branches on what it finds, and repeats over a list of inputs. It runs unattended, on a schedule or in a build pipeline, with nobody watching.
The cost is real and it is ongoing. Somebody has to write the script, which means somebody has to be able to write code or drive an RPA builder. Selectors break when the site is redesigned. Logins expire. A flow that worked in March fails silently in June and you find out from the data. Automation is worth every bit of that when the task is repeated hundreds of times or has to run while you sleep. It is a poor trade when the task is "get this paragraph into that box".
What an auto typer is
Typist is the narrow version. You open the side panel, write or paste the text you want entered, click into the field on the page where it should go, choose a speed, and press Start. Typist enters that text into that one field, at that pace, while you watch. There is no script, no selector, and nothing to maintain. When the site changes, nothing about Typist changes, because Typist never knew anything about the site in the first place — it types into whatever field you focused.
It follows that Typist cannot do the things automation does. It does not click, does not navigate, does not switch tabs, does not fill a second field after the first, and has no conditional logic of any kind. One field, one run, one person present.
| Browser automation | Typist | |
|---|---|---|
| Scope | The whole page and the whole session | One field you have focused |
| Clicks and navigation | Yes | No |
| Conditional logic | Yes | No |
| Setup | Write and test a script | Paste text, pick a speed |
| Needs coding | Usually yes | No |
| Runs unattended | Yes, that is the point | No, you press Start |
| Maintenance | Selectors and flows break | Nothing to maintain |
| Pace of entry | As fast as the script runs | 20 to 400 wpm, your choice |
Use automation, not Typist, when
- The job runs on a schedule, or overnight, or in CI, with nobody at the keyboard.
- It has to log in, navigate several pages, and pull something back out.
- It fills many fields per record and many records per run — two hundred rows from a spreadsheet into a CRM is an automation job, not a typing job.
- It has to decide something: if this field is empty, do that instead.
- You are testing a site, where acting as a user across a whole flow is the entire exercise.
If any of those describe your task, stop reading and go write a Playwright script. You will be done sooner and the result will be better.
Use Typist when
- There is one field and you already have the text for it.
- It happens often enough to be annoying but not often enough to justify code — the shape of most repetitive browser data entry a single person does.
- You want the entry to take time on purpose, at a pace you control, rather than finish instantly.
- You would be the one maintaining the script, and you would rather not.
The middle case
Filling a handful of boxes on a form you meet weekly sits between the two. Typist handles it one field at a time — you focus a box, run the text, focus the next — which is fine for three or four fields and tedious for twenty. The forms page is honest about where that line falls, and saved snippets are what make the repeat bearable.
Questions
- Is an auto typer just a worse automation tool?
- It is a smaller one. Automation is more capable in every direction and costs setup and upkeep to get there. If your task needs one field filled and nothing else, that capability is a price you are paying for nothing.
- Can Typist fill a whole form in one go?
- No. It types into the single field you have focused, then stops. Moving to the next field is something you do.
- Can I schedule Typist to run later?
- No. A run begins when you press Start, in a tab you are looking at. Anything unattended is an automation job.
- Where does Typist work?
- In editable browser fields — text boxes, text areas, rich-text editors and Google Docs documents. If the thing you have clicked is not an editable field, Typist says so and asks you to click into one. The overview page goes through this in detail.
- Does anything about the page leave my browser?
- No. Unlike a hosted automation platform, there is no remote runner holding your session. The text in the panel stays on your device and goes only to the page you are typing into, and the address and contents of that page are never sent anywhere.
If the narrow tool is the one you want, the speed control page explains the part of it you will actually touch every time.
Free plan: 300 words a day. A Google sign-in is required before typing.