Automate repetitive browser tasks by doing them once
Teach Job Recorder a browser task once. On future runs, enter only what changed while it handles the repetitive clicks, forms, navigation, and other browser actions.
Record and replay browser actions in under 30 seconds
- Click Teach New Job
- Perform a browser task normally
- Review the recorded job
- Choose Keep same / Ask me / I'll do this myself
- Save
- Run the job later
- Enter changing values
- Browser handles the repetitive work
Three steps. That's it.
Teach it once
Perform the browser task normally. Job Recorder captures the steps required to repeat it.
Tell it what changes
Choose which values stay the same, which should be requested on every run, and where you want to take over manually.
Run it later
Start the saved job, enter the values that changed, and let Job Recorder handle the repetitive browser work.
Browser task automation for ordinary, repeated work
- Recurring web forms
- Weekly and monthly reports
- Repetitive browser data entry
- Admin portal workflows
- Repeated navigation and form filling
- Recurring back-office browser tasks
Browser automation without building workflows
Job Recorder is designed for people who want browser automation without scripting or constructing complicated workflow diagrams. Instead of programming an automation, perform the task normally and turn the recording into a reusable job — a straightforward way to automate repetitive browser tasks without writing code, sometimes called no-code browser automation.
Nothing runs blind
- Changing values can be requested on each run, instead of being hard-coded.
- Manual checkpoints can pause automation at a point you choose.
- Logins, one-time codes, and CAPTCHAs stay manual — Job Recorder doesn’t try to solve them.
- Potentially sensitive final actions can be reviewed before continuing.
- You can stop a job at any time, mid-run.
Your jobs stay on your computer
- ✓ Your recorded jobs stay on your computer.
- ✓ Job Recorder doesn't store your website passwords.
- ✓ Saved jobs are stored locally in your browser, not on a server.
- ✓ Sensitive form contents aren't sent anywhere as analytics data.
- ✓ Replays reuse your normal browser login sessions — you don’t log in twice.
Honest, on purpose
Job Recorder is an MVP. It does not promise reliable automation for every website or browser interaction.
- Desktop applications outside the browser aren’t automated.
- CAPTCHAs are never solved automatically — they stay manual.
- Native OS dialogs (file pickers, system prompts) require your input.
- Some complex custom controls aren’t fully supported yet.
- Multi-window workflows that span separate windows aren’t supported.
- Canvas-heavy applications (where the page isn’t real DOM) are unreliable.
Common questions
- What is Job Recorder?
- Job Recorder is a Chrome extension that records repetitive browser tasks and lets you replay them later.
- How does Job Recorder work?
- You perform a task once, review the recorded steps, choose which values stay fixed or change, and save it as a reusable job.
- Can Job Recorder automate web forms?
- Yes, supported forms can be recorded and replayed, while values that change between runs can be requested before execution.
- Does Job Recorder work on every website?
- No. The MVP focuses on ordinary browser workflows and does not guarantee support for every website or custom interface.
- Does Job Recorder store my passwords?
- No. Password fields should remain manual and passwords are not saved as job values.
- Where are my recorded jobs stored?
- Recorded jobs are stored locally in the user's browser for the MVP.
- Is Job Recorder a browser macro recorder?
- It performs a similar record-and-replay function, but the product is designed around reusable jobs where changing values and manual steps can be explicitly handled.
- What happens when a website changes?
- If a page's layout changes enough that a saved step can no longer find what it's looking for, the job pauses so you can point it at the right element or take over manually — it doesn't guess.
- Can I stop before submitting a payment or form?
- Yes. You can add a manual checkpoint before a sensitive step, and you can stop a running job at any time before it acts.